Process Orientation

Topics Covered

1. Seeing work as a connected process rather than a collection of isolated tasks.
2. Defining the purpose, customer, inputs, outputs, and boundaries of a process.
3. Distinguishing outcomes from activity and identifying where value is actually created.
4. Mapping steps, decisions, handoffs, dependencies, delays, and failure points.
5. Creating consistent methods while allowing judgment where situations differ.
6. Using standards, checklists, documentation, and visual controls to reduce avoidable errors.
7. Finding root causes instead of repeatedly treating symptoms.
8. Improving flow by reducing rework, waiting, duplication, unnecessary approvals, and confusion.
9. Measuring process performance through meaningful quality, time, cost, and customer indicators.
10. Treating improvement as an ongoing cycle of observation, experiment, learning, and adjustment.

Thinking Exercises

1. Choose a routine task and identify its customer, inputs, outputs, and definition of quality. Which of these is currently assumed rather than agreed?
2. Map the task as it actually happens, not as the procedure says it happens. Where do delays, workarounds, and repeated efforts appear?
3. A recurring error has been noticed. List possible system causes before identifying an individual to blame.
4. Which process measure could improve while the real customer experience gets worse? What additional measure would provide balance?
5. Imagine you could change only one step in a process this month. Which change would reduce the most risk or effort, and what evidence would justify it?

Feedback Points

1. Document the current process before proposing an improvement so the discussion is based on reality.
2. Make handoffs explicit: define what is transferred, when, to whom, and at what quality level.
3. Look for root causes and recurring patterns rather than relying on reminders or heroic individual effort.
4. Use small experiments and evidence to test improvements before making broad changes.
5. Review processes with the people who perform and receive the work; they often see hidden friction first.

Freewriting Exercises

1. The Work Behind the Work

• Choose a task that appears simple from the outside. Describe all the preparation, checking, waiting, coordination, correction, and follow-up that it actually requires. Identify which steps create value for the recipient and which exist because of earlier confusion, missing information, or process history. Write a short description of the process as it is today, followed by a description of the process you would design if you were starting with the desired outcome rather than inherited habits.

2. Following a Handoff

• Trace one piece of work as it moves between people, teams, or systems. Describe what each person needs to know, what they receive, what they add, and what they pass onward. Focus especially on the points where responsibility or information becomes unclear. Write about how the handoff feels from the receiving person's perspective. Then propose a simple agreement covering inputs, timing, quality, ownership, and what should happen when the information is incomplete.

3. The Recurring Problem

• Write about a problem that keeps returning despite repeated reminders, corrections, or individual efforts. Describe the visible symptom and the cost it creates. Now ask what conditions make the problem likely: unclear standards, competing priorities, poor design, missing training, unreliable tools, or an unrealistic workload. Imagine running a small root-cause investigation. Record the questions you would ask, the evidence you would collect, and the smallest experiment that could test your leading explanation.

4. A Process Improvement Experiment

• Select one process that could be made clearer, faster, or more reliable. Describe the current state and the specific improvement you want to test. Define what will change, who will participate, how long the trial will run, and what evidence will count as success. Include possible unintended effects, such as shifting work to another team or reducing quality for speed. End by writing how you will share the learning whether the experiment succeeds, fails, or needs another attempt.

5. Designing for the Next Person

• Imagine that someone new must take over a responsibility tomorrow with limited guidance. Write what they would need to know to produce a good result: purpose, sequence, decisions, examples, exceptions, contacts, tools, and quality checks. Identify the knowledge currently held only in people's memories. Then create a short outline for a process guide that would support independence without turning every situation into a rigid rule. Explain how the guide would be reviewed and improved over time.