The prompt
Score 10 of 10, Excellent
Use it when You have a big personal work goal, such as a certification or a move into a new role, and need dated milestones that fit your spare hours.
- {{goal}}
- {{why}}
- {{deadline}}
- {{hours_per_week}}
- {{starting_point}}
- {{dependencies}}
Full prompt and why it works
Prompt
Break a big goal of mine into milestones and a first step I can take this week, so that it stops being something I mean to start and becomes a plan with dates. The goal: {{goal}} Why it matters to me: {{why}} When I want it done: {{deadline}} Hours a week I can really give it: {{hours_per_week}} What I have already done, or have to start from: {{starting_point}} People or approvals it depends on: {{dependencies}} How to plan: - Start by defining the finish line as something observable, for example "certification exam passed" rather than "get better at cloud". - Work backward from the deadline to 4 to 8 milestones. Each milestone is a result someone could see, not an activity, with a target date and a rough number of hours. - Order them so the riskiest or least certain part comes early, while there is still time to change course. - Make the first step something I can do in under an hour this week. - Name where people often stall on a goal like this, and put a check at that point. Format: 1. Finish line: one sentence. 2. Milestones: a table with the columns Milestone, Done when, Target date, Hours, Depends on. 3. This week: the first step, and when I will do it. 4. Checkpoints: when to review progress, and what to do if I am more than two weeks behind. 5. Risks: up to 4, each with what I would do about it. The total hours across the milestones must fit within my hours a week up to the deadline. If they do not, say so plainly at the top and offer two choices, a later date or a smaller goal, each with its own numbers. Do not pad the plan with milestones that are only there to look thorough, and do not assume help or approvals I have not mentioned. A good plan is one where I know on any given week whether I am on track. If the goal is too vague to define a finish line, ask me up to two questions before planning.
Variables
- {{goal}}
- The goal in your words, for example "get my project management certification" or "move into a product role".
- {{why}}
- Why it matters to you, in a sentence.
- {{deadline}}
- When you want it done, for example "by the end of June".
- {{hours_per_week}}
- Hours a week you can really give it, for example 4.
- {{starting_point}}
- What you have already done or have, for example "finished half an online course, have a study guide".
- {{dependencies}}
- People, money or approvals it needs, for example "manager to approve exam fee". Write "none" if none.
Why it works
- What good looks like. Milestones are results someone could see, each with a Done when and a date, so you can tell on any week whether you are on track.
- Length. The hours across the milestones must fit your hours a week, and if they do not you get a later date or a smaller goal, with numbers.
- If unsure. A goal too vague for a finish line gets up to two questions first, since a plan toward a fuzzy target cannot be checked.