In Learning How to Learn, in the section “The Aim and the Destination,” Idries Shah quotes Saadi of Shiraz:
“I fear that you will not reach Mecca, O Traveller, for you are on the road to Turkestan!”
The verse appears in chapter two, story six of Saadi’s Gulistan. In that story, an ascetic at a king’s table performs for the benefit of his audience. His conduct advances his reputation for devotion while taking him away from the practice itself. Shah uses the line to ask what a traveler expects to achieve by setting out. In project work, the same question is worth asking after the team has traveled some distance.
Name the destination in terms another person can verify
Imagine a water utility commissions a new map for reporting service interruptions. The project sponsor wants customers affected by a main break to receive an accurate first update sooner. That gives the team something to measure: the time from the utility’s confirmation of the break to the publication of an approved notice for the affected area. Verify that the notice reaches the intended channels and that the affected area is correct. An early message sent to the wrong streets creates another problem.
Before the team picks a platform, have the service owner and a duty supervisor walk through a few past cases. Record how long it took to confirm the affected area, approve the notice and publish it. Name a review date and how the utility will compare like cases. The UK Government Service Manual recommends looking at an entire user journey and combining performance data with other evidence. In this example, the staff who run the process can explain delays the timestamps alone leave unexplained.
Put a checkpoint before the next major commitment
Suppose the prototype puts a break on a map in seconds. A tabletop replay reveals that no one on the evening shift has delegated authority to approve the notice. More map features would leave that delay intact. The evidence gives the sponsor a choice: arrange qualified approval coverage and test the workflow again, or reallocate the next tranche of work to whatever still delays publication. If the map also helps dispatch crews, it can have a separate purpose with a separate test and budget.
Build that review into the plan ahead of time. Before buying integrations or expanding the rollout, have staff replay a representative case from detection through publication. Bring the resulting notice and elapsed time to the review. A demo can show that the map renders. The replay should show whether the intended customer would have received the right update and where the process still stalls.
Decide openly whether the route or the destination has changed
- Continue when the evidence shows that the approach advances the stated outcome and the safeguards still hold.
- Change the route when the outcome still matters and evidence points to a different constraint. Name the person who can remove it and book the next test.
- Reconsider the destination when the underlying need or the sponsor’s priorities have materially changed. Write down the new outcome, the evidence for the decision and the work the team can now stop.
This applies the Vitaver Playbook’s Mission First principle to a project in progress. The sponsor owns the outcome and the next spending decision. The project lead owns the evidence and the proposal. The receiving team should be able to repeat the test. At the next review, put the mission and the latest evidence side by side and ask whether another month on this route will move the team closer to the result it set out to achieve.