The AmplifierLearn · Entry point
For managers and team leads: avoidance with authority
A careful, principled engineering manager told his team not to rush. Six months later three of them were gone, and he was standing at the head of the table saying he had fought for every one of them. This page is for anyone who could be him.
Planned for release phase 2. The page is complete as a draft; interactive parts run in the browser and do not yet save to an account.
In brief
Two rules. Leadership has to be visibly using the tools — not because you need to, but because your team will do what you do, not what you say; a directive on Slack changes nothing, twenty minutes at a junior's desk asking real questions changes everything. Invest in the framework, not the tools: tool training is a sunk cost in two years; training in the clear thinking that lets people evaluate, select, direct and integrate any tool compounds. If you are mid-career, the Amplifier Stack is your version of the model.
The pattern in most companies right now
Senior leadership reads about AI and gets nervous. A directive goes out. It lands at middle management, where the people receiving it are not fluent, built their careers on capacities AI threatens, and are quietly terrified. They forward it downward without translating it, because they do not know how to. The actual work of figuring out what integration means in any specific role lands on individual contributors with no training, no examples and no leadership modelling. Some jump in and outsource their thinking. Some dig in and refuse. Most are stuck in the middle, doing neither well. And the people most affected — contractors, juniors, anyone without political cover — are the first to be cut when the company decides it has been too slow.
The asymmetry that makes you dangerous
Karan, in the book, demanded engineering quality from his team while himself avoiding the tools that were changing what quality looked like. He was asking his team to absorb a new posture while he, the boss, kept the old one. That asymmetry was the killing thing, and it is the structural failure of leadership in a great many Indian companies right now. The Dependent hollows themselves; the damage is contained. The Avoider with authority hollows the world around them, and from inside their own head they are the protector — which is why they cannot, for a long time, connect the empty chairs to themselves.
If you have people reporting to you, the AMQ has a band for this: the Structural Avoider. It is the placement with the heaviest cost, and the hardest climb, because the recovery is not personal but organisational — and it begins with you, in public.
What visible engagement looks like
Not a directive. A senior person sitting down at a junior person's desk and being curious about the work, in a way that signals the work matters. Walking the team through a real example of how you yourself prepared a brief, evaluated an output, or caught a structural problem — including where you got stuck. Most companies have lost the muscle for that. The ones that find it again are the ones that will make it through the decade.
In Chapter 9 the whole climb is twenty minutes: Karan reads a junior's proposal, sits in the chair beside his desk, asks two good engineering questions, suggests one two-paragraph section, waits while it is added, and then says the thing he has been deciding whether to say. "You did this work better than I would have done it three months ago. I should have been giving the team more of this kind of work for a long time." He is not yet the fluent, modelling leader the book describes. He is a man who has stopped resisting the climb, which, given where he started, is a very large change.
Framework, not tools
The training portal in the book has eight courses on individual tools and none on how to think. A company that trains its people on this year's coding assistant will find in two years that the assistant is gone and the training is a sunk cost. A company that trains its people on the clear thinking that lets them evaluate any new tool, select between alternatives, prepare inputs, evaluate outputs and integrate work across tools has trained on something that compounds. The tools are downstream of the thinking.
If you are mid-career yourself
You cannot start from scratch and should not want to. The Amplifier Stack: keep the domain expertise, add AI fluency fast (months, if the foundation is there), double down on the human skills that will differentiate you once everyone has the same tools. The question is not "how do I keep up?" It is "what is the thing only I can do, and how do I spend the next ten years doing more of it?"
A first-time manager's version
When the protagonist's flatmate is promoted to his first team, he asks what it takes to be a good manager. The answer does not mention the framework. It says: figure out what you actually want from your team before you ask anything of them. Not the deliverables — the texture of what good would look like. Figure that out alone, on a Sunday, with no laptop. Then you will know what to ask for. That is Step 1, applied to leading people, and it is where every team's version of the framework begins.
Bring the framework to your team.
A masterclass runs one real project through all eight steps with the author in the room. Or start with the AMQ for yourself, this week, before anyone else on the team takes it.