A client executive building escalation triggers into a gate process asked the question every program eventually asks: when do you change a target? It is the right question, because the answer decides whether the weekly trend means anything at all. The answer fits on one page, and the page is below.
A target is an external constraint
The target comes from the market window, a customer commitment, a buying season or the growth plan, never from the schedule. The team owns the schedule and the weekly forecast; the target is the contract between the team and the company, and nobody renegotiates a contract because the work got hard.
So a target moves for two reasons only: the external driver behind it moved, or the date has become a fiction nobody is jumping for. Either way, leadership makes the call once, at a gate, in the open, and the original commitment stays visible on the chart. On a healthy program the rarer event points the other way: when a target does change, it moves earlier, not later.

Everything else is a gap
A fixed target is the reference line that makes the trend readable. Every week the team refreshes the plan and re-plots the forecast finish against it; the distance between them is the exposure in days, and the slope is the direction of travel. When the gap will not close, the team states it in days and proposes the pull-ins that would close it, with the risk priced. Then leadership decides.
The four moves
1. Accept the risks and fund them.
2. Change the definition.
3. Retarget, once, in the open, at a gate.
4. Kill the project.
Retarget is on the list. What is not on the list is drift: a target that slides out a week at a time until nobody remembers what the date was for. Drift is an early warning of a future failure, and it is corrosive in a way a hard slip is not, because the gap becomes fiction and the wigglechart loses its memory. A project that looks unrecoverable is still worked as a gap, in days, until leadership picks one of the four moves.
The bounding box fits the rule
Several clients run a bounding box, a practice that came out of Tektronix: a target plus limits, agreed at each phase gate. It fits the rule, read correctly. A limit is a review trigger, not a new target: cross one and the gate convenes. Before the definition gate the target is a window, so narrowing it at the concept and planning gates is the window closing, not a reset. The definition gate is where the window becomes a point and the contract is signed; reopening it afterward is a public act at a gate. Inside the box the team acts without asking, and a breach is a decision for leadership, taken once.

One caution from the field: keep the bounding box in the gate reviews and leave the production wigglechart alone. Limit lines on the chart would add complexity for the many people who already read it every week, and would suggest the one thing the chart exists to deny, that targets can be reset.
The recommendations
- Tie every target to its external driver.
- Use target windows through the concept and planning gates; by the definition gate, make the target a single date. If a later gate ever moves it, keep the original commitment visible.
- Keep the bounding box in the gate reviews and the wigglechart as it is.
- When the gap will not close, state it in days, price the risk, and decide in the open among the four moves.
Once set, a target that moves loses its power to force the behavior you want. The target line never moves; the forecast tells the truth every week; the gap between them is the management information. The one-page position paper is below.
Related on lateralworks: Make your bed and The exception report.