Take a Project Problem You Cannot Solve to the Right Decision-Makers and See It Through

## Treat Raising a Problem as a Request for a Decision, Not a Handoff Use escalation when a project issue exceeds the current owner’s authority, expertise, capacity, or acceptable risk. Escalation is not a transfer of responsibility; it is a structured request for a decision, resources, protection, or specialist help that the existing level cannot provide. - State the outcome the escalation is intended to secure. - Keep the project owner responsible for coordination until ownership is explicitly reassigned. - Distinguish an emerging risk, an active issue, and a crisis requiring immediate response. - Continue safe containment and evidence collection while the decision path is activated. ## Set the Conditions for Raising a Problem Before Trouble Starts Include escalation rules in project governance before pressure rises. Objective triggers reduce hesitation and personal politics by showing when a threshold has been crossed and which role can accept the resulting exposure. - Define thresholds for safety, customer impact, cost, schedule, scope, quality, compliance, and reputation. - Set time-based triggers for blocked decisions and unresolved dependencies. - Identify events that require immediate specialist or executive notification. - Review the triggers when project scope, stakeholders, contracts, or operating conditions change. ## Check the Facts and Limit the Damage Before Raising the Problem Perform a rapid fact check without delaying urgent protection. Confirm what happened, what remains uncertain, the current impact, plausible next effects, and the actions already taken to stabilize the situation. - Verify important claims with the people and records closest to the event. - Separate observations, interpretations, forecasts, and rumors. - Protect people, customers, assets, and evidence within existing authority. - Record why the issue cannot be resolved safely at the current level. ## Choose Whether to Go to Managers, Specialists, or Both Select the route according to the capability needed. A management route provides authority, priority, funding, or organizational alignment; a functional route provides technical, legal, security, financial, operational, or other specialist judgment. Some issues need both routes in parallel. - Map each trigger to a primary owner, delegate, and backup route. - Notify the next capable level rather than broadcasting to unrelated leaders. - Activate specialist paths for risks that require protected expertise or mandatory handling. - Coordinate parallel reviews through one project-level owner and one decision record. ## Involve Only the Fewest People Who Can Decide and Act Involve enough authority and expertise to act, while limiting noise and conflicting direction. Skipping levels without cause can weaken accountability, but following a chain mechanically can waste time when impact is growing. - Start with the defined level unless urgency, unavailability, or severity activates a bypass. - Explain the reason when a level is skipped or a broader audience is included. - Give every recipient a role in deciding, advising, acting, or staying informed. - Remove observers who no longer need updates after the route is stable. ## Prepare a Short Summary of the Facts and the Decision Needed Make the escalation understandable without burying the recipient in raw detail. Present a current, traceable view of the problem, the exposure, the work already completed, and the decision or support needed next. - Summarize the event, time, affected scope, status, and confidence in the facts. - Quantify current and potential impact where credible evidence allows it. - List containment, attempted fixes, dependencies, and remaining uncertainty. - Present viable options with consequences, recommendation, owner, and decision deadline. ## Tell Decision-Makers What You Need First, Calmly and Without Blame Use direct conversation for urgent alignment, followed by a written record. Keep language factual and proportionate so recipients can distinguish severity from emotion and act without reconstructing the project history. - Lead with the decision needed, urgency, and material impact. - Use a consistent structure for facts, assumptions, actions, options, and next update. - Avoid blame, speculation, unsupported certainty, and irrelevant detail. - Confirm what each recipient understood, accepted, and committed to do. ## Give Customers and Partners the Same Facts Through One Spokesperson Assume that customers, partners, and internal groups may escalate through their own channels. Provide corresponding leaders with the same current facts and approved message so external concerns do not reach senior stakeholders before the project’s decision chain is prepared. - Name one communication owner and define who may speak for the project. - Tailor detail to the audience while keeping facts and commitments consistent. - State what is known, unknown, being done, and expected next. - Record material communications, decisions, promises, and changes in position. ## Keep One Action Log and Regular Updates Until the Problem Is Under Control After raising the issue, run it as an active management process. Maintain one action log, decision record, owner map, and update cadence so the added authority improves resolution rather than creating parallel and contradictory work. - Assign owners and deadlines to decisions, containment, recovery, and communication. - Track changes in impact, confidence, dependencies, and residual risk. - Re-escalate when a decision misses its window or the exposure crosses a new trigger. - Reduce the audience and cadence as uncertainty and impact decline. ## Close Out the Problem and Record Lessons for Next Time End the escalation deliberately when the required decision is implemented, immediate exposure is controlled, and remaining work fits normal governance. Preserve the evidence and learning so future teams can act earlier and with less disruption. - Confirm the closing decision, accepted residual risk, owners, and follow-up dates. - Notify stakeholders that the route, cadence, or authority level has changed. - Review trigger quality, communication, decision speed, and avoidable delay. - Update governance, risk registers, contact paths, training, and preventive controls.