Ways of Working: Turning Effort Into Outcomes

Earlier parts of this book looked at what management really is and how to work with the people you lead. This part zooms out to the machinery between a group of people and the thing they are trying to produce. Call it the way of working: the shared agreement about how work moves from an idea in someone’s head to something finished and useful in the world.

Most teams never decide their way of working on purpose. It accumulates — a habit here, a meeting someone once insisted on, a tool a former manager liked. This part gives you something better: the vocabulary to see the machinery clearly, name the trade-off every method is quietly resolving, and choose deliberately instead of by inheritance. By the end you should be able to look at a struggling team and diagnose the process, rather than reflexively blaming the people inside it.

What a “way of working” actually is

Strip away the frameworks and certifications and a way of working answers a handful of plain questions. Who decides what we do next? How do we know when something is done? How do we tell each other what we are working on? What happens when reality contradicts the plan? A way of working is simply the set of answers a group has agreed to — spoken or not.

Every group has one, whether they chose it or not. A three-person cafe has a way of working: whoever is on the till calls out orders, the kitchen works a ticket rail, and the closing checklist lives on the wall. A hospital ward has one: handover at shift change, a whiteboard of patients, an escalation path when someone deteriorates. A software team has one too — even if it is just “grab the next thing from the chat and hope.”

The question is never whether you have a way of working. It is whether yours is agreed and visible, or assumed and invisible. The invisible kind is where the trouble lives.

In practice — the invisible process

A warehouse team never wrote down how orders get picked, so each shift did it slightly differently. The morning crew batched by aisle; the evening crew picked one order at a time. Neither was wrong, but items got double-counted at the handover, and each shift quietly assumed the other was sloppy. Nobody was sloppy. The process was undefined, so two reasonable habits collided every evening at 3 p.m. Writing the method on one page — one agreed way to pick — ended a month of friction in an afternoon.

What happens without an agreed one

When the agreement is missing, three predictable failures appear, and they rarely look like process problems at first.

• Chaos. Without a shared answer to “what do we do next,” people pick their own priorities. Everything is urgent, nothing finishes, and the loudest request wins instead of the most important one.
• Duplicated effort. Two people solve the same problem because neither knew the other had started. In a clinic that is two nurses chasing the same lab result; on a software team it is two engineers building the same fix.
• Quiet resentment. This is the sneaky one. When the rules of the game are unwritten, people invent their own — and then judge each other for breaking rules that were never stated. The resentment reads as a personality clash. It is almost always a missing agreement.

Notice that none of these announce themselves as “we have no way of working.” They show up as stress, missed deadlines, and people who “just don’t get along.” Learning to see the process underneath is the core skill of this part.

The one tension every method resolves

Here is the idea that makes every framework in this part legible. Underneath all the ceremonies and vocabulary, every way of working is answering a single question:

How much do we plan up front, versus how much do we adapt as we learn?

That is the whole debate. Plan too little and you thrash — reworking, backtracking, discovering in month three something you could have known in week one. Plan too much and you march confidently in a direction that stopped being right months ago, unable to turn because the plan has become the point.

        PLAN-THEN-BUILD  <-------------------->  ITERATE-AND-ADAPT

  Decide the whole path first.        Decide the next step, learn, adjust.
  Great when the goal is fixed        Great when the goal is fuzzy
  and change is expensive.            and learning is cheap and fast.

  Risk: the plan outlives             Risk: motion without direction;
  the reality it was built for.       never converging on "done."

Neither end is correct in the abstract. Pouring the foundation of a building rewards heavy planning — you cannot “iterate” a foundation after the walls are up. Designing a phone app for customers whose tastes you cannot predict rewards the opposite: ship something small, watch what people do, adjust. The skill is not picking a side. It is reading your situation — the cost of being wrong, the speed you can learn, how fixed the goal really is — and landing at the right point on the line.

Every framework you will meet is a pre-packaged answer to this tension. Once you can see the tension, the frameworks stop being mysterious rituals and become tools with a purpose you can evaluate.

The roadmap for this part

This part walks the line from one end to the other, then teaches you to choose. Read the pages in order; each builds on the last.

#	Page	What it gives you
1	Ways of Working: Turning Effort Into Outcomes (you are here)	Why an agreed way of working matters, and the plan-versus-adapt tension that runs through the whole part.
2	Plan-Then-Build vs Iterate-and-Adapt	The two philosophies in full — often called waterfall and agile — what each is genuinely good and bad at, and when to reach for which.
3	Scrum: The Rhythm of Sprints	The most popular iterate-and-adapt framework: fixed-length sprints, its handful of roles and meetings, and what the rhythm buys you.
4	Kanban: Visualize Flow, Limit Work in Progress	A gentler, flow-based alternative: make the work visible, cap how much is in progress at once, and improve the flow you can now see.
5	Choosing and Adapting: Fit the Method to Your Context	How to select and tailor a method for your goal, people, and constraints — and how to avoid copying rituals you do not understand.
900	Ways of Working: Revision	A prose recap of the whole part, to consolidate before you move on.

The thread

Here is the through-line to hold as you read. No method is universally correct. Scrum is not “better” than Kanban; waterfall is not a relic to sneer at. Each is a bet about how much to plan versus adapt, and each bet pays off only in the right conditions. The goal is never to be doing the trendy method correctly — it is reliable outcomes for your specific goal, your specific people, and your specific constraints. Keep asking of every practice: what tension is this resolving, and does that resolution fit us? That question is the spine of the entire part, and it protects you from the trap the final page names outright.

The common trap — the cargo cult

The most common way teams go wrong is copying the rituals of a method without its reasoning. They hold the daily stand-up meeting but nobody unblocks anybody; they run “sprints” that are just deadlines with a fashionable name; they fill a board with sticky notes that no one moves. The form is present, the benefit is absent. This is often called a cargo cult — imitating the visible surface of something successful and expecting the results to follow. Throughout this part, resist it: learn why each practice exists before you adopt it, and drop any practice whose purpose you cannot state.

The evidence — process beats heroics

Studies of team performance generally find that predictable systems outperform individual heroics over time. Toyota’s production system became a global reference point less because of any single brilliant worker and more because the way of working — visible flow, small batches, stopping the line when something looked wrong — made good outcomes repeatable rather than occasional. The lesson to carry into this part: a well-designed process is what lets ordinary people produce reliably good results, which is exactly the “reliable outcomes without chaos or burnout” this book is about. Treat specific figures with caution; the durable finding is the direction, not a precise number.

How it connects

This part sits on top of everything before it. A way of working only functions if people feel safe to say “I’m blocked” or “this plan is wrong” — which is why the earlier material on trust and psychological safety is load-bearing here. And it feeds everything after: the meetings, decisions, and communication habits in later parts are where a way of working actually lives day to day. If those later parts feel abstract, come back here and ask what tension the practice is resolving.

Try this

Pick one team you are part of this week — at work, a volunteer group, even a household — and write its way of working on a single page. Answer just four questions: How do we decide what to do next? How do we know when something is done? How do we tell each other what we are working on? What do we do when the plan turns out to be wrong. Do not fix anything yet. Simply notice how much of it was never actually agreed, and where two people would answer the same question differently. That gap is your process, made visible for the first time.

Reflect

1. For a team you know well, is its way of working agreed and visible, or assumed and invisible? What is one piece of it nobody ever actually decided on purpose?
2. Think of a recent team conflict that looked like a personality clash. Could it have been a missing agreement about how work should move — a rule someone broke that was never stated?
3. On the plan-then-build to iterate-and-adapt line, where does your work currently sit? Where should it sit, given how fixed your goal is and how expensive it is to be wrong?
4. Where have you seen the cargo-cult trap — a ritual performed with no benefit, kept because “that’s how it’s done”? What was the practice meant to achieve, and was it?
5. Which of the three failures — chaos, duplicated effort, quiet resentment — shows up most in your world? What does that tell you about which part of your way of working is undefined?

Show reflections

1. The honest answer is usually “some of both.” The useful move is spotting the invisible parts, because that is where the friction hides. A part “nobody decided on purpose” is a default you inherited — and defaults are worth questioning even when they are working.
2. Reframing a clash as a missing agreement is the central skill of this part. If you can trace the conflict to an unstated rule, you have found something you can fix with a one-line agreement, rather than something you can only endure.
3. Good answers separate where you are from where you should be. The tells: a fixed goal and expensive mistakes argue for more planning; a fuzzy goal and cheap, fast learning argue for more adapting. A mismatch here is often the real source of a team’s frustration.
4. Naming a cargo-cult ritual is easy; the sharper question is what it was for. If you can state the original purpose and see it is not being served, you have earned the right either to fix the practice or to drop it — that judgment is what the final page of this part builds toward.
5. Each failure points to a different gap. Chaos suggests no agreed answer to “what next”; duplicated effort suggests poor visibility of who is doing what; quiet resentment suggests unstated rules people are being judged against. The dominant symptom tells you which question to answer first.