For the engineer who now runs the organization
You were promoted because your technical judgement was the best available. The role you were promoted into is not a technical one. Nobody marks the transition, and nothing in an engineering career prepares you for the week you now have: interface disputes, resource contention, and a schedule you can no longer personally verify.
This is ongoing one-to-one work on the part of the job that no one trained you for — run by someone who has been in the room for the engineering, not just the management theory.
- Free
- Ten questions, about five minutes
- See your score before giving an email
What we actually work on
Sessions follow the problems in front of you, not a curriculum. In practice the work concentrates in a few places:
- Deciding without complete information. Engineering training rewards waiting for data. Executive work punishes it. Recalibrating that instinct is usually the first thing we do.
- Being believed by people who are not engineers. Translating technical risk into schedule and cost terms a customer, a board or a CFO acts on — without diluting it into meaninglessness.
- Holding a position under pressure. Particularly when the pressure comes from someone more senior who is wrong about a technical reality.
- Delegating judgement, not just tasks. The bottleneck in most scaling engineering organizations is one person who is still the only one trusted to decide.
- Building the structure you outgrew. Decision rights, interface ownership, escalation paths — the things that were unnecessary at forty engineers and are load-bearing at a hundred and forty.
How it runs
Regular sessions, scheduled around your program rhythm rather than a fixed calendar. Between sessions you get asynchronous access — the questions that matter rarely wait for the next slot, and a decision that waits two weeks for a coaching session has already cost more than the coaching.
Who this is not for
If you are looking for general career or life coaching, this is the wrong engagement and we will say so on the first call. The work assumes you are running a technical organization with real delivery pressure, and it is priced and paced accordingly.
Start with the measurement
Before committing to an engagement, take the ten-question diagnostic. It scores where your organization is losing time and gives us both something concrete to talk about on the first call.