Risk and Resilience
Escalation Thresholds Should Follow Consequence, Not Just Variance
Why cost and schedule tolerances are not enough, and how to design escalation rules around consequence, reversibility, strategic value and risk.
EraNorth Insights
Decision-grade thinking for complex work.
Professional knowledge and strategic perspectives across strategy, projects, operations, engineering, transformation and business performance.
34 articles found
Program Governance
When Transformation Objectives Conflict, Decide What Cannot Be Traded
A practical governance framework for resolving conflicts between safety, quality, continuity, cost, schedule, reputation and benefits in transformation.
Strategy and Foresight
What Your Projects Know That Your Strategy Doesn't
Delivery generates evidence about whether the strategy was right. Most organisations have a mechanism to push objectives down and nothing authorised to carry findings up.
Project Delivery
How Does Work Get Into Your Enterprise Without a Decision?
Every organisation has a priced route for new work and a free one. Work flows down the free one, and the change control system never sees the invoice.
Program Governance
Your Portfolio Committee May Not Be Where Decisions Are Made
Portfolio committees may decide, negotiate or simply consolidate decisions made elsewhere. Effective governance starts with how power actually works.
Program Governance
Who Sits on the Board for the Benefits?
Your programme board represents the money and the builders. The people who must turn the output into value are usually consulted, not seated — and it shows.
Program Governance
When a Sub-Process Becomes a Domain
A discipline moved stakeholders from one control activity to a management domain of its own. What is your organisation still filing as a sub-process of something else?
Program Governance
The Right to Reject and the Duty to Look
Approval registers name who can refuse a finished deliverable. They rarely name what that person had to examine first — or what follows when nobody did.
Program Governance
The Right Stakeholder at the Wrong Time Can Damage Portfolio Decisions
Stakeholder involvement is not automatically beneficial. Portfolio governance improves when the right roles intervene at the right phase with clear authority.
Program Governance
Stakeholder Maps Expire: Portfolio Influence Changes as Strategy Moves
Why portfolio leaders must track how stakeholder power, interests and influence shift as strategy, funding, regulation and dependencies change.
Program Governance
RACI Is Not Accountability: Designing Decision Rights in Matrix Projects
Why responsibility charts are useful but insufficient, and how leaders should design decision rights and accountability in complex matrix environments.
Program Governance
Program Governance Begins With Decision Rights, Not Committees
Effective program governance starts by defining who can decide, escalate, redirect and stop work before designing committees, meetings and reporting routines.
Program Governance
Portfolio Governance Is a Decision-Rights System
Effective portfolio governance clarifies who can fund, challenge, redirect and stop initiatives, and what evidence is required for those decisions.
Program Governance
Governance Should Fit the Organisation, Not the Template
How leaders can design portfolio governance around strategy, culture, authority, regulation and risk without turning oversight into bureaucracy.
Program Governance
Governance Can Reduce Complexity or Become Another Layer of It
How to design governance that clarifies priorities, resolves issues and protects benefits without creating slower decisions and more organisational friction.
Program Governance
Governance by Tolerance: Escalating the Right Decisions at the Right Level
How clear tolerances and decision rights can reduce executive micromanagement while escalating material project and program issues early enough to act.
Program Governance
Drivers, Supporters and Observers: Who Is Allowed to Change What Your Program Is For
Stakeholder maps record who is interested. They rarely record who holds the power to redefine the outcome — which is the only distinction that governs.
Program Governance
Decision Rights Should Change With the Decision
Not every decision should be made the same way. Leaders should match participation, authority and speed to decision quality, acceptance, expertise and urgency.
Program Governance
Change Control Is Capital Allocation in Disguise
Why project change control should evaluate value, opportunity cost, risk and capacity—not merely approve modifications to scope, cost or schedule.
Program Governance
“Best for Project” Requires Decision Rights: Governing the Alliance as a Virtual Organisation
How alliance leaders can make integrated project decisions while preserving clear authority, accountability and obligations to participating organisations.
Program Governance
Assurance and Control Are Different Executive Responsibilities
A practical executive distinction between quality control, quality assurance and independent project assurance across complex delivery systems.
Portfolio Leadership
When a PMO's Mandate Outgrows Its Place on the Organisation Chart
A PMO cannot govern enterprise priorities through reporting alone. Its organisational position, sponsorship and decision rights must match its mandate.
Portfolio Leadership
Agile at Team Level Is Not Strategic Agility at Portfolio Level
Why faster delivery teams do not make an organisation strategically agile unless funding, prioritisation, metrics and portfolio decisions also adapt.
Organisational Capability
Your Organisation Has a Default Conflict Style. Who Chose It?
Conflict handling looks like a set of personalities. It is a designed property of incentives, escalation paths and forums that have no adjudicator.
Organisational Capability
Self-Managed Teams Still Need Governance
Autonomy can improve speed and ownership, but self-managed teams still require clear purpose, boundaries, capability, information and accountability.
Leadership and Decision-Making
Who Can Say No — and Does Your Commercial Motion Ever Reach Them?
Entering a large pursuit through procurement does not risk discounting. It guarantees it: procurement's mandate is price, and nothing else is theirs to move.
Leadership and Decision-Making
What May They Cost You?
Your delegation schedule sets what people may approve. It says nothing about what they may cause you to owe, and only one of those two systems is yours to write.
Leadership and Decision-Making
Stakeholder Conflict Is Often a Resource-Allocation Problem in Disguise
Many stakeholder conflicts persist because scarce people, authority and attention are contested. Leaders must govern the allocation problem underneath.
Leadership and Decision-Making
Reversibility Is an Asset That Decays
Reversibility behaves like a balance sheet item that depletes on a schedule, yet no enterprise register records it — so nobody can name the last undoable approval.
Business Models and Growth
Which Frictions Are You Profiting From Tolerating?
Some customer irritations are revenue lines. Each is an option written against you, and whoever removes it first chooses the timing and keeps the customer.
Business Models and Growth
Price Is a Share of Value Created, Not a Markup on Your Cost
Costing gives you a floor, never a price. The harder question is who inside the organisation may see that floor, because all who see it argue down to it.
AI and Digital Strategy
Your Data Pipeline Is an Operating-Model Decision, Not an IT Project
Who owns data collection across your business units, what happens when none agreed a convention, and why that cost is incurred long before any model exists.
AI and Digital Strategy
What You May Know About a Customer, and What You May Price On It
Your growth function and your risk function are working opposite ends of one mechanism. A framework for what an enterprise may infer, and what it may price on.
AI and Digital Strategy
What Has Your Enterprise Already Authorised a Machine to Decide?
Somewhere between advice and action, machines in your business began deciding alone. Can you produce the artefact that authorised it, and the name on it?
Loading more Insights…