Convert a Vague Project Into Next Actions
Break a vague project into outcome, next actions, and scheduled deep work.
Project label: 'Improve onboarding.' It appears in review every Friday but never becomes executable. Outcome -> Next action -> Deep block -> Waiting-for The common trap is treating a desired state as a task. 'Improve onboarding' feels responsible, but it forces the brain to re-clarify the project every time it appears. Outcome Write the finish line: 'New customers complete their first workflow in 20 minutes without support.' A project needs a visible outcome before next actions make sense. The outcome also prevents random improvement work. Next action Define the first executable move: 'Pull the last 30 onboarding support tickets into…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in