The AmplifierPractice · In your field
Tech and Engineering: the framework in your world
For software engineers and technical teams: the framework as it plays out in the book, and the one step that changes most in your world.
In brief
What Step 1 looks like here: Who, specifically, will read this — not "the team", but named people (your reviewer, the teammate who inherits it on Tuesday, the client who sees only the final report), each with a different thing they need from it. And which of your tasks are actually yours: "form a view about whether our approach is right" is a task, and it is easy to assign it, silently, to your manager.
Arjun's first attempt at applying the framework — a pipeline migration inherited from a colleague who was let go — comes back technically correct and completely generic. He has done Step 1 more properly than ever before: three paragraphs by hand on a Sunday morning. He has mapped the flow, caught three gaps with AI as reviewer, decomposed a coarse task into four, chosen three different tools for three different sub-tasks, and handled three small fixes cleanly on Thursday morning. Every individual piece passes its own test. The assembled whole has no centre of gravity.
Four hours of patching produce four different shapes of the same problem. Then he calls Vivek, who asks one question: who is it actually for? Arjun had named the deliverables. He had not named the four humans — Karan carrying it into a quarterly review, Sneha inheriting the tooling on Tuesday, the director's office scrutinising it, the client seeing only the test reports — each of whom wanted a different thing. The rot was upstream, at Step 1. The fix took half a Friday and touched three framing tasks, not eight.
His second attempt, a fraud-detection proposal for a banking client, gets Step 1 right in fourteen minutes. When a senior architect asks what happens when a five-second batch boundary cuts a coordinated transaction sequence in half — the kind of question that had broken a colleague in the same room — Arjun has an answer, because he has already done the thinking the question assumes.
Read the full walkthrough in Chapters 5, 8 and 9 of the book.
The pipeline migration, step by step
Every step, with what was decided and why.