Technical Leadership Coaching FAQ | The Push

The Push is a confidential, 12-week, one-to-one technical leadership coaching process. It includes six biweekly sessions and practical experiments between sessions, focused on one live leadership problem in your engineering environment.

It is for Engineering Managers, Group Managers, and Engineering Directors who are carrying too many decisions, escalations, or pieces of context themselves. It can also fit a technical leader preparing for broader responsibility. It is less useful when you want a generic course or a broad organizational redesign outside your control.

Two explanations are common. The first is unclear authority: people do not know which decisions they own. The second is missing context or risk: they technically have authority, but lack the standards or safety to use it. A practical test is to label three recent escalations by cause, then make one decision boundary explicit and watch whether the next escalation changes.

Delegation can fail because the task moved but judgment did not. It can also fail because the review rhythm is absent, so both sides fall back to constant checking. Test the distinction with one decision: state the outcome, the authority, the guardrails, and the next review point. If the work still returns to you, inspect the missing context or risk rather than assigning it again.

Mentoring primarily shares experience, consulting primarily delivers an external recommendation, and training primarily teaches a curriculum. The Push is coaching-led and tied to your real work: it helps surface the constraint, offers targeted advice when useful, and uses small experiments to change how decisions and ownership move. If you need a delivered organizational redesign or a standard course, it is not the right format.

The six biweekly sessions run across 12 weeks. The work starts by making the recurring leadership problem observable, then tests changes to decision rights, delegation, meetings, stakeholder alignment, or strategic capacity. Between sessions you apply a focused experiment in your actual role and bring back what happened. The exact artifact depends on the problem; examples include a decision-rights map, delegation plan, or meeting reset.

The intended outcomes are clearer decision boundaries, less avoidable escalation, more team ownership, and more capacity for strategic work. These are aims to test, not guaranteed results. Progress is visible when the work changes: for example, fewer repeat escalations, cleaner handoffs, or more decisions made without your approval. The first session defines which signals matter in your situation.

The work can still focus on the part of the environment you can influence: decision boundaries, stakeholder alignment, routines, and escalation paths. The diagnosis should distinguish an authority problem from a constraint you cannot change. If the needed change sits outside your span of control, The Push may help clarify the next organizational conversation, but it cannot promise to redesign the organization.

It may not fit if you need therapy, legal advice, a generic template, or a consulting project that delivers a complete redesign. It is also a poor fit if you are not able to test changes in your real work. A short fit conversation is useful when the problem is still unclear; it should end with a clear next step or a clear reason not to proceed.

The conversation is a short, focused discussion of the recurring problem, the pressure around it, and what keeps returning to you. We test whether the issue belongs within The Push and whether there is a sensible next step. It is not a promise of a universal outcome or a substitute for diagnosis. If there is no fit, that conclusion is useful too.