A missed startup milestone is a signal to examine the plan, not a reason to change every goal. This guide provides a weekly review process for deciding whether to continue, remove a blocker or revise an assumption. For choosing your initial targets, see our business goal-setting guide.
Create a milestone record before work begins
Write down the outcome, due date, owner, evidence needed for completion and assumptions behind the target. “Launch our service” leaves too much room for interpretation. “Publish the approved offer, enable enquiries and complete an end-to-end enquiry test by Friday” is easier to verify.
Keep activity and outcomes separate. Making sales calls is an activity; securing qualified enquiries is an outcome. Track both when the relationship is uncertain. A completed task does not prove customers want the offer.
Use a short weekly review table
The following is an illustrative example for a new service business, not a recommended sales benchmark.
| Milestone | Evidence this week | Decision | Next owner and date |
|---|---|---|---|
| Test the offer with five prospective buyers | Three conversations recorded; two postponed | Finish research before revising the offer | Founder: reschedule by Tuesday |
| Publish an enquiry page | Page live; confirmation email not delivered | Resolve the delivery blocker | Website owner: retest by Thursday |
| Deliver the first paid pilot | No confirmed booking yet | Review lead quality and proposal feedback | Sales owner: analyse on Friday |
Add the actual result beside the planned result. Attach the relevant enquiry records, test results or completed deliverable. If evidence is missing, mark the milestone unverified rather than declaring success because the deadline has passed.
Diagnose the cause before changing the target
- Execution: was the agreed work completed?
- Dependency: did a supplier, approval or technical issue prevent progress?
- Capacity: were the required hours or skills available?
- Assumption: did customer evidence contradict the plan?
- Measurement: is the result recorded accurately?
Different causes require different responses. A broken enquiry form calls for a repair and another test. Consistent buyer feedback that the offer solves the wrong problem calls for a review of the offer. Lowering the sales target will not fix either issue.
Record a specific decision
Choose one action: continue the plan, unblock delivery, reduce scope, revise the assumption or stop the activity. Record the reason and evidence. Give the next action an owner and date. If you change a deadline or target, keep the original value in the record so later reviews can distinguish learning from repeatedly moving the goalposts.
For a change that affects cash or delivery commitments, update the budget and affected plans as well. Do not promise the same scope on a shorter schedule without checking capacity. Escalate decisions that exceed the team’s spending or approval authority.
Check the next review rather than declaring the problem solved
At the following review, confirm whether the agreed action happened and whether the original blocker has gone. Keep a small decision log: date, observation, decision, owner and follow-up result. Over several reviews it can show recurring issues, such as approval delays or optimistic time estimates.
This review process is a practical planning template, not a claim that a particular growth rate is achievable. Set thresholds using your actual capacity, customer evidence and financial constraints. The purpose is to make changes deliberate and traceable while preserving enough time to do the work.
