SteerCo Escalation Patterns: When To Bypass Your Boss

Programme-management training treats escalation as process: write the risk, route the path, follow the cadence, watch the resolution. The reality of escalation in a fintech programme is a craft, not a process. The senior Programme Manager who has been through one regulator-deadline rollout has internalised a set of patterns the training never covered, including, occasionally, when to bypass their own boss.

The bypass is the most controversial of the patterns and the most practiced quietly. It is also the one that most reliably distinguishes a senior PgM from a competent mid-level one. The senior PgM uses it sparingly, with documentation, with a defensible reason. The junior PgM either never uses it (and the programme suffers) or uses it routinely (and gets rolled out of the company within 18 months).

This is the operator's view: the five escalation patterns a senior PgM needs, the rules of each, when bypass is appropriate, and the four traps that consume PgM careers around escalation work.

Pattern 1: The structured escalation

The pattern. A risk emerges. The PgM follows the documented escalation path: line manager → SteerCo → executive sponsor. Each step has documented inputs, decisions, and outputs. The risk is resolved at the appropriate level.

When it works. Most of the time. Programmes that are running well, with sponsors who engage, with line managers who respond, with SteerCos that meet on cadence, these are the programmes the standard escalation path serves.

The senior PgM discipline. Even on programmes where the structured escalation works, the PgM keeps the audit trail clean. Every escalation is documented in writing (RAID line + email + SteerCo minute). Every decision is recorded with the decision-maker and the date. The discipline matters not because escalation will fail (it usually does not) but because if it later does, the audit trail is the evidence that the PgM did their job.

Pattern 2: The pre-escalation rehearsal

The pattern. Before raising the risk at SteerCo, the PgM walks each individual senior attendee through the risk in 1:1s in the week before. The SteerCo conversation is rehearsed, every senior has seen the data, formed an opinion, and entered the room knowing what is going to be asked.

Why senior PgMs do this. Surprises in SteerCos go badly. A risk raised cold to a room of seven senior executives produces seven different reactions, none of them aligned, all of them defensive. A risk pre-walked to each individual produces a SteerCo conversation that converges on a decision because the conversations already happened.

The senior PgM discipline. The pre-rehearsal is not lobbying, the PgM presents the data, listens to each senior's view, integrates the feedback, and arrives at SteerCo with a clearer recommendation than they would have had alone. The room agrees because the work is done before the room.

When it does not work. When the pre-rehearsal becomes politics, the PgM is shaping the recommendation to please each senior individually, and the recommendation ends up incoherent. The discipline is to listen and integrate, not to placate.

Pattern 3: The bypass

The pattern. A risk emerges that the PgM's direct manager either cannot or will not escalate appropriately. The PgM goes around the manager, escalating directly to the manager's manager, or to a peer-level decision-maker outside the line.

When this is appropriate. Four genuine cases:

• Regulator deadline. A regulatory deadline is at material risk and the line manager is not engaging at the urgency required.
• Material safety / licence exposure. The risk threatens the platform's licence or a major regulator-facing programme, and the line manager's response is structurally inadequate.
• Direct conflict of interest. The line manager has a personal interest (their previous role, their previous decision) that compromises their judgment on the risk.
• Acute responsiveness failure. The line manager has been demonstrably unreachable or unresponsive for an unacceptable duration in a fast-moving situation.

The senior PgM discipline. A bypass is documented, transparent, and reversible. The PgM does it in writing (an email to the bypass target with the line manager copied; not behind their back). The PgM names what was tried, what failed, and why the bypass is the right call. The line manager finds out at the same moment as the bypass target.

When it goes wrong. When the bypass is done covertly (the line manager finds out from a third party). When the bypass is done routinely (it stops being an exceptional pattern and becomes the operating model). When the bypass is done without an audit trail (the PgM cannot defend the call later).

The senior PgM tell. "I had to escalate over my line manager once in the last two years, and here is why and how I did it." The frequency is low; the documentation is high; the relationship with the line manager survives.

Pattern 4: The horizontal lift

The pattern. A risk emerges that crosses functions and the line manager is the wrong escalation path because the issue is not in their reporting line. The PgM goes laterally, engaging a peer-level decision-maker in the function where the issue actually sits.

When this is appropriate. A risk that is operationally owned by engineering, risk, compliance, or operations rather than by the PgM's line. Going up the PgM's line (typically programme office or PMO) does not move the risk; going laterally to the function that owns it does.

The senior PgM discipline. The horizontal lift is communicated upward too, the line manager hears about the lateral engagement quickly and is not blindsided when the SteerCo discusses it. The horizontal partner knows the engagement is part of the PgM's job, not a power grab.

When it goes wrong. When the lateral partner is misidentified (the PgM goes to the wrong function and produces noise). When the lateral engagement is treated as an end-run (the line manager and the PMO find out after the fact). When the lateral path is over-used (the PgM is seen as bypassing the structured escalation path routinely).

Pattern 5: The deliberate non-escalation

The pattern. A risk emerges. The PgM judges that escalating now would harm the programme, produces a SteerCo distraction, raises a false alarm, consumes senior bandwidth for a risk that can be managed at the operational level. The PgM chooses to not escalate, document the risk in the RAID, and manage it through the standard programme cadence.

When this is appropriate. Most risks. SteerCos exist to handle the risks that exceed the programme's normal management capacity; the routine ones do not belong there.

The senior PgM discipline. The risk is documented in the RAID, with the conscious decision not to escalate, and the trigger conditions that would change that decision (e.g., "if the vendor's response is not received by date X, escalate to SteerCo"). The non-escalation is not the same as ignoring; the audit trail shows the judgment.

When it goes wrong. When non-escalation is the default and risks accumulate. When the PgM is protecting their own optics ("I do not want to look like I am bringing problems") rather than managing the programme. When the trigger conditions are not documented and the PgM forgets the risk until it materialises.

The four traps PgMs fall into around escalation

Trap 1, Escalating everything. The PgM brings every risk to SteerCo. The SteerCo's signal-to-noise ratio drops; senior attendees stop engaging; the routine pattern becomes "this is the PgM who never decides anything themselves". The remedy is to filter: most risks should be operationally managed; only the ones that exceed normal capacity belong at SteerCo.

Trap 2, Escalating nothing. The opposite pattern: the PgM absorbs every risk personally. The programme runs until it does not; the eventual collapse is dramatic; the post-mortem reveals that the PgM saw it coming for months. The remedy is to be honest about which risks exceed the programme's capacity and escalate them in time.

Trap 3, Covert bypass. The PgM bypasses the line manager without telling them. The bypass succeeds operationally but destroys the working relationship. The PgM gets the result, then loses the line manager's trust for every subsequent decision. The remedy is to bypass openly, in writing, with the line manager copied, with the reasons stated.

Trap 4, Politics dressed as escalation. The PgM uses the escalation path to advance their position rather than the programme's. The SteerCo notices within two meetings; the PgM's standing collapses. The remedy is to put the programme first, document the reasoning, and let the work speak.

The unwritten rules

A working set of unwritten rules that experienced PgMs follow:

1. Never escalate a problem without proposing a path. A SteerCo that hears "X is bad" without "and here is what I propose we do" loses confidence in the PgM. Bring a recommendation.

2. Never blindside the line manager. Even when bypass is appropriate, the line manager finds out at the same moment as the bypass target. Always.

3. The audit trail is the protection. Every escalation, every bypass, every non-escalation is documented. The PgM who has been through a regulator inquiry has internalised this; the PgM who has not, has not.

4. Match the urgency to the medium. Email for routine; phone or text for material; in-person for severe. A regulator-deadline risk announced by email at 11pm Friday will be read on Monday morning.

5. Build the relationship before you need it. The PgM who has built relationships with the senior decision-makers in the programme has escalation paths that the PgM who only meets them at SteerCo does not. Pre-build.

6. Be wrong sometimes. A PgM who is always right on escalation is escalating too narrowly. A PgM who is wrong 20-30% of the time is calibrating well, the senior attendees occasionally disagree, and that is healthy.

7. Let the programme outlive the escalation. Programmes that survive multiple SteerCo escalations are built on relationships that survive escalation. The PgM whose escalations damage the relationships is operating short-term.

When the line manager is the problem

The hardest case. The line manager is, for whatever reason, not the right escalation path for this risk. Three patterns:

• The line manager is structurally conflicted. Their previous decision is what produced the risk. Escalating through them produces defensive responses, not solutions.
• The line manager is operationally overwhelmed. They have too much else on their plate to engage with the risk on the timeline required.
• The line manager is structurally distant. They are physically remote, time-zone misaligned, on extended leave.

In each case, the senior PgM bypasses with documentation. The bypass is reversible, the line manager remains in the loop, the programme continues to flow through them when the issue resolves. The bypass is a temporary expedient for a specific risk, not a permanent operating shift.

The PgM who never bypasses, no matter the circumstance, is rigid and ships less than they should. The PgM who routinely bypasses is undisciplined and burns relationships. The senior PgM bypasses once in 18 months for a defensible reason, with audit trail, and the line manager respects the call.

The senior-PgM tell

The interview question that distinguishes senior PgMs on this topic: "tell me about a time you had to escalate over your line manager. What happened?"

The junior answer says "I have not had to do that." (Either has not been in the right programmes, or is not telling the truth.)

The mid-level answer tells the story but the reasoning is thin, they did it because the manager was "slow" or "unsupportive". The bypass was an act of frustration.

The senior answer tells the story with the four genuine cases (regulator deadline / safety / conflict of interest / responsiveness failure) clearly identified. The documentation is explicit. The line manager survived the bypass because it was done openly. The programme shipped. The relationship recovered. The PgM does not present it as a triumph; they present it as a tool they had to use once, deliberately, and would prefer not to use again.

That answer is the operating posture. It is also the answer that the hiring manager, who has been through their own version of the same moment, recognises immediately.

FAQ

What if the line manager retaliates after a bypass? The audit trail (the email with line manager copied, the documented reasons, the SteerCo record of the escalation) is the protection. Senior leadership reads retaliation against documented bypass as a line manager problem, not a PgM problem.

Should the PgM tell HR before a bypass? Rarely. The bypass is a programme decision, not an HR decision. Unless the bypass also involves a misconduct concern, HR engagement complicates the narrative.

What is the difference between escalation and confrontation? Escalation is about decision-making; confrontation is about behaviour. The PgM escalates risks; the PgM confronts conduct. The two paths are different even when the same individuals are involved.

How do you maintain the line-manager relationship after a bypass? A direct conversation, in person, within 48 hours of the bypass. "I escalated above you on X because [genuine reason]. I would prefer not to do it again; here is how we can avoid it." The line manager respects the conversation more than they respect the avoidance.

Does this apply equally in remote / distributed teams? The principles apply. The mechanics shift, pre-rehearsals happen on Zoom, in-person bypass conversations become video calls, audit trails are even more important because side conversations are harder. Distributed teams probably formalise these patterns more, not less.

Should the PMO train PgMs on escalation patterns? Yes, but the training has to include the unwritten rules, not just the documented escalation paths. Most PMO training covers the structured pattern (pattern 1) and ignores the other four. A PgM who only knows pattern 1 will be limited.

If this resonated, also read The RAID + SteerCo PMO Stack That Ships, Program Management vs Product Management in Fintech, and Where PMOs Fail: Six Patterns.