GUIDE / 02

From a template to a working process

The ordinary details between a promising demonstration and something another person can depend on.

THE QUESTION BEHIND THIS GUIDEFrom the criticism of templates

A template can make a complicated idea feel simple. You can see the structure, follow the steps and imagine the result. The next piece of work is fitting that structure to the people and circumstances that will actually use it.

Know what the template gives you.

A template gives you a starting arrangement. It might include example content, a sequence of tasks or an explanation of how something could work. That can save time and make an unfamiliar idea easier to explore.

It still contains assumptions. Someone chose what information would arrive, who would do the work and what a successful outcome would look like. Before you copy those choices, write them down. Which ones fit your situation? Which ones have not been checked?

The useful question is not whether the template looks complete. It is whether the important assumptions are true in the place you want to use it.

Follow one complete case.

Pick an ordinary example and trace it from beginning to end. Where does it start? What information is needed? Who receives it? What decision follows? What tells everyone the task is finished?

A HYPOTHETICAL EXAMPLE

A repair shop wants a more consistent way to respond to new inquiries. A sample message is only one piece. The shop also needs to know who checks the inquiry, what details they need, when to call and how to record the next step.

This repair shop is a fictional teaching example, not a reported implementation.

Draw the sequence on paper. At each arrow, ask what moves from one person or step to the next. An unclear arrow is often more important than an impressive box.

Give the work an owner.

A process needs someone who knows what they are responsible for. “The team will handle it” leaves too much room for different interpretations. Name the role that notices new work, the role that makes a decision and the role that takes over when the normal path stops.

Access matters too. The right person needs permission to see or change the information required for the task. Sort that out through the normal authorized route before asking them to rely on the process.

Keep the handoff simple enough that someone can explain it without opening a long document. What has happened, what needs to happen next and who is taking it from here?

Try the uncomfortable cases.

The neat example is not the whole job. What happens when information is missing, a message arrives twice, someone changes their mind or the responsible person is away? A useful process needs a visible place for these cases to go.

For the repair-shop example, an inquiry without a phone number should not quietly disappear. A duplicate request should not trigger two people to make the same call. A customer who no longer needs help should not keep receiving the same next step.

You do not need to solve every possible exception on day one. Start with the ones you can already anticipate. When the process cannot continue safely or clearly, make the human fallback obvious.

Make a small proof of the whole path.

Run a controlled example through the complete sequence with the people who will use it. Observe the result at the end, as well as the individual steps. Record where you had to intervene or supply missing context.

A convincing demonstration is useful, but dependence raises another set of questions. Can the next person repeat the task? Can they see what happened? Can they recover if the result is wrong? Is there a way to return to the previous method while you fix something?

Those questions make the boundary clearer. You can say which part works, under what conditions and what still needs attention. Precision builds more trust than treating an unfinished process as complete.

The working-process check.

Before depending on a new process, write a plain-language answer to each question.

StartWhat event begins the work, and what information is required?
OwnershipWho is responsible for the next action?
CompletionWhat observable result means this case is finished?
RecoveryWhat happens when a normal step cannot continue?
RepeatabilityCan someone else follow the path without its creator explaining every step?

Keep what helps. Finish the fit.

Use the template for the head start it gives you. Then spend time on the parts that make it belong to the actual situation: people, information, responsibility and recovery.

That is where a reusable idea becomes a useful piece of work.