GLOBAL PERSPECTIVE · INDEPENDENT THINKING
UNDERSTAND WHAT MOVES THE WORLD.
THE CYGURU COLUMN AN ORIGINAL PERSPECTIVE

Give a Project a Finish Line Before It Grows

A useful project finishes when someone can do what it promised. Set that test early and give later proposals a fair way to enter the plan.

BY GABRIEL NICOLAEV – CYGURU · · 4 MIN READ
READING TOOLS
Black-and-white photograph of worktables with rolled plans and drafting tools.
THE READING GUIDE

Inside this essay

01Decide what someone will be able to do ↓02Give later ideas a place to wait ↓03Invite someone to try the original task ↓

The recommended book is written by the author of this column, who has a commercial interest in its sales.

Decide what someone will be able to do

Suppose two friends agree to make a neighborhood repair directory. They want residents to be able to find someone who can mend a coat, fix a lamp or sharpen a kitchen knife. The first few listings lead to good conversations. One friend proposes a map. Another wants user reviews. A shopkeeper asks for appointment booking. Each idea could improve a directory someone can already use. Taken together before the first release, the ideas can change what the two friends have committed to deliver.

Before the work expands, I would write down a small test for the completed version. Imagine a resident with a broken lamp and no background in the project. They can find a relevant listing, understand which repairs are accepted, and see a way to contact the shop. If there is no lamp repair in the directory, they can see that without searching every listing. The test names the experience the project exists to provide. It gives the people making it a finish line they can both recognise.

A finish line can be written in ordinary language. It should say who can do what, under which conditions, and who will check. The number of listings might matter because a directory with one trade cannot answer the questions it says it covers. The number of pages rarely tells you whether a resident can find a repairer.

Give later ideas a place to wait

Keep a list of suggestions beside the agreed finish line. A suggestion belongs in the current version if the original task cannot be completed without it, if it resolves a serious problem the group overlooked, or if the group deliberately changes the promise. In the last case, name the person who accepts the extra work, the time it will take and what will be moved or dropped.

For example, a map may help a resident compare nearby shops. If the listings already provide the shop’s location, it can be considered after the first users have tried the directory. If the directory serves a neighborhood with several streets carrying similar names and people cannot tell which location is meant, fixing the location information may be part of the original job. The proposed feature and the underlying need deserve separate attention. A cross street might solve the problem without any map at all.

Booking introduces a larger commitment. Someone needs to keep the available slots current, handle changes and tell people what to expect when a shop cannot respond. A small group can decide that it wants to become a booking service. It should be able to name who will run that service on an ordinary week before treating it as a minor improvement to a list.

Invite someone to try the original task

Have a person outside the group try the directory in front of you. Hand them a situation, such as finding someone who can shorten a coat near a bus stop. Avoid explaining the screen in advance. If they cannot see how to find the right trade, watch where they look and ask what they expected to find. Change the directory where their experience shows that the promised task is still difficult.

Use a second example to test a different part of the promise. Suppose there is no listing for a lamp. A clear message can tell the resident what the directory covers and what it has yet to add. That absence is meaningful. A person deciding whether to make a trip deserves a legible answer even when the answer is disappointing.

The test also helps settle smaller aesthetic disputes. Both friends may have a legitimate preference about how the directory looks. They can agree who settles a question that does not materially affect the agreed use. Leaving every detail open until both people feel equally attached to the outcome can quietly extend the work beyond what either person originally volunteered to do.

Make room for the work that follows

Once people start using the directory, an old phone number can spoil an otherwise good listing. Assign someone to receive corrections and decide how they will identify listings that need another check. This is the operating promise the project leaves behind. Write it separately from the first release so everyone can see whether their commitment includes maintaining the result.

I have written about giving a first success an operating successor. Completion here is earlier and narrower. The friends can decide that a usable directory has been delivered, that corrections now belong to a designated person, and that future proposals will be evaluated with a different budget and date. The original contributors can then decide whether they want to take part in that next stage with a clear account of what it asks.

The point of writing a finish line is that a project can learn and still have a date on which someone receives something useful. Scope can change when a reason is strong enough. The change should be visible to the people whose evenings, money or reputation make it possible. Once a resident can find the coat repairer on their own, the group has kept a promise. Further work can begin from that accomplishment.

Gabriel Nicolaev — CyGuru

Sources & further reading

No Plan, No Future — official product page ↗

Editorial illustration. Photograph by Gallen-Kallelan Museon on Unsplash.

FOLLOW THE CONNECTION

Another angle on this subject

Continue through related ideas, decisions and consequences.