Waypoint
Start Here

Before You Start: Know Where You Are

In Brief — The twelve steps in this guide are built to be followed in sequence. But before you enter the sequence, two questions need honest answers: Where are you in the EPMO lifecycle? And if you are not starting from scratch, where do you enter? This chapter is a diagnostic — not reading material to set aside. Use it to locate yourself before the sequence begins.

Why Location Matters Before Sequence

A guide that opens with Step 1 assumes you are starting from zero. Most practitioners are not.

You may be inheriting a governance model that exists on paper but not in practice. You may be rebuilding something that was formally active and quietly stopped. You may have a tollgate but no real intake discipline feeding it. You may be operating in an organization that has been through a governance effort before and carries the scar tissue from it.

If the guide begins with "here is the sequence" before you know where you are standing, you are navigating without a starting point. This chapter gives you one.

Two diagnostics follow. Use both.

Diagnostic Part One: Your Lifecycle Stage

The EPMO in Production chapter at the close of this guide describes the full lifecycle of a governance function — from first operation through maturity, potential refurb, and the honest question of whether what was built still serves the organization. Read it in full after you have worked through the sequence. Before you begin, use this condensed diagnostic to locate yourself now.

Read each stage. Stop at the first one that accurately describes your situation.

Stage 0 — Nothing Yet, or Starting Over

The governance model does not exist in any operational form. Either this is new — no intake process, no portfolio inventory, no formal approval structure — or what existed has been formally disbanded or informally stopped functioning.

If this is you: start at Step 1. The sequence is built for your situation.
Stage 1 — Operational but Unstable

The governance model is running. The basic mechanics exist: intake is accepting submissions, the tollgate is meeting, some version of portfolio status is being produced. But it is running with significant friction.

Signs you are here: exceptions outnumber standard cases. Leadership is still actively debating whether the process is worth the overhead. Workarounds to the intake process are common and largely unchallenged. The team is fighting fires while trying to run governance. The governance forum’s outputs are not yet visibly shaping decisions.

If this is you: the framework is in place but not yet delivering credible governance. Your immediate work is not design — it is adoption. Use Step 12’s retrospective discipline to identify the two or three friction points creating the most resistance, and address those specifically. The rest of the sequence is your reference as the model matures.
Stage 2 — Stable but Not Yet Sophisticated

The basic mechanics are running consistently. People know what to expect. The intake form is being used without constant friction. The tollgate has a reliable cadence. The portfolio inventory is being maintained.

Signs you are here: the model is steady but not iterating on itself. CBA quality varies significantly by submitter. Benefits are not being tracked systematically after project close. The five disciplines are applied unevenly — strong on some steps, weak on others.

If this is you: the sequence is producing operational governance. Your focus is calibration: improving the quality of the inputs, building the benefits register discipline, and starting the measurement practices that will build your evidence base. Steps 5, 9, 11, and 12 deserve intensive attention.
Stage 3 — Established, with Blind Spots

The EPMO has developed confidence. The team knows the model. Governance outputs are referenced in leadership conversations. The portfolio inventory is accurate. Decisions that go through the governance process are visibly better than the ones that do not.

Signs you are here: the model has not been materially revised in eighteen months or more. Business units are starting to route work around the process rather than through it. The tollgate is starting to feel like a ceremony rather than a real decision point. A leadership change is either recent or on the horizon.

If this is you: the model needs challenge, not redesign. The external review step in Step 12 is critical. This is also the stage where the political dimension of governance is most exposed — the EPMO is operating in an environment where its authority is established but increasingly contested. That requires active coalition work, not just process execution.
Stage 4 — Proven, with Integration Risk

The EPMO has an evidence base. Leadership references governance outcomes in strategy conversations. The investment process is embedded in how the finance team evaluates capital requests. The benefits register is producing data that shapes future CBA quality.

Signs you are here: the model is starting to feel like infrastructure — functional, present, and increasingly invisible. Budget scrutiny is increasing. The team that built the model may be moving on.

If this is you: your most important work is maintaining the value story with evidence specific enough to survive budget pressure. Step 12’s governance health metrics are your primary operating tool.
Stage 5 — Drifting from Fit

The governance model is producing less insight than it used to. Governance meetings are well-attended but not generating consequential decisions. The metrics show green across the board but the portfolio does not feel like it is performing.

Signs you are here: practitioners in the EPMO are answering questions from two years ago instead of new ones. Business units are building informal governance mechanisms outside the formal model. The intake process is efficient but not insightful.

If this is you: go back to Step 1. Not to restart the whole sequence — to reapply the listening discipline to the organization you have now, not the one the model was designed for. The foundation is worth keeping. The fit needs refreshing.

Diagnostic Part Two: Where Do You Enter?

If you are not starting from zero, and the organization has specific governance functions that are broken while others are working, you do not start at Step 1. Use the following to identify your entry point.

The principle: enter at the step that is visibly failing. The steps before your entry point must be functional enough to support the work you are entering — but they do not need to be perfect.

The portfolio contains no honest picture of what is in flight.

There is no maintained list of active work, or the list exists but cannot be trusted — it is incomplete, outdated, or covers only formally approved projects while significant informal work runs outside it.

Entry point: Step 2 — Inventory. Run Step 1 in compressed form alongside the inventory work.
The intake process does not exist, or is being actively bypassed.

The organization is approving work informally, outside any structured process. There is no front door, or the front door is routinely circumvented by anyone with enough seniority.

Entry point: Step 3 — Intake. Audit Steps 1 and 2 first. Intake built without a listening foundation will be designed for a generic organization, not this one.
The portfolio contains everything with no visible triage.

Every submitted idea is in the portfolio. Nothing has been rejected or deferred. The priority order changes based on who spoke last.

Entry point: Step 6 — Prioritize. But Steps 3, 4, and 5 must be functional enough to produce honest inputs to the scoring process.
Work is being approved without real scrutiny.

There is a tollgate meeting, but it functions as a presentation event. Recommendations go in; approvals come out. The forum is not asking hard questions and is not equipped to stop work.

Entry point: Step 7 — Tollgate. Rebuild the decision criteria, the preparation requirements, and the forum’s mandate to hold work.
Approved work sits without confirmed sponsors, resources, or commitment.

The tollgate approves work. The approved work waits. Sponsors are nominal. Resources are assumed. Nothing formally moves from approved to authorized.

Entry point: Step 8 — Authorize. The eight-point confirmation checklist is your primary instrument.
Delivery is active but nobody knows if the investments are still sound.

Projects are executing. Status reports are being produced. But the governance forum is reviewing only health — schedule, budget, scope — without asking whether the original investment thesis is still valid.

Entry point: Step 9 — Health vs. Value. Add the value conversation to the governance cycle without redesigning everything else.
Projects are competing for resources with no portfolio view.

The portfolio is managed project-by-project. Nobody has a cross-project view of shared resources, dependency risk, or change saturation. Conflicts are discovered when they become crises.

Entry point: Step 10 — Portfolio Governance. The dependency map, capacity view, and saturation view are your primary tools.
Projects close and the value never gets confirmed.

Investments produce deliverables. The benefits are never measured. The outcome owners named in the CBAs are not followed up with. The portfolio has no feedback loop on investment performance.

Entry point: Step 11 — Benefits Realization. Start the benefits register now, retroactively for investments currently in flight.
The governance model works but never improves.

The EPMO is operational and consistent, but it is not iterating on itself. Retrospective reviews happen but do not change practices. The organization keeps making the same governance mistakes.

Entry point: Step 12 — Standardize, Learn, Improve. The governance health metrics give you a standing measurement instrument. The retrospective protocol gives you the process.

Two More Starting Points

The diagnostics above are written for the practitioner who is entering or operating a governance function. Two other situations are common enough to deserve their own path.

I’m an executive or budget holder deciding whether to fund governance.

You are not the practitioner doing the work — you are the person deciding whether to authorize it. Your question is not how to build a governance model; it is whether the investment is worth making. Three things answer that question. First, read the Measuring the Governance Model Itself section on the EPMO in Production page — specifically the bypass rate and benefits realization hit rate metrics. These translate governance discipline into investment language. Second, look at the two field vignettes on that same page: both describe a portfolio where the governance investment was justified by a single discovery in the inventory step. Third, the governance model this framework builds answers one question the organization cannot currently answer: are we deploying capital against the right priorities, and do we know what those investments actually produced? If the answer to either part is no, the investment is justified.

Your path: Read the EPMO in Production page first, then the Introduction. Use the practitioner you are funding as the primary reader for the rest of the framework.
Evaluating who runs this. This framework tells you what good governance build looks like. It does not, on its own, tell you what to look for in the person or team you fund to run it. Five questions worth asking a candidate directly: Can they name, unprompted, the four things a governance charter should contain? Can they describe what they would do in the first 30 days if they discover an underground, undocumented bypass route? Have they ever recommended stopping a project that was delivering correctly? Do they distinguish a problem statement from a proposed solution without being told to? Would they rather inherit a partially-working model or build from nothing, and can they explain why? A candidate who answers all five specifically, without generic process language, has done this work before.
I’m inheriting a governance model that already exists but isn’t working.

This is one of the most common situations a governance practitioner walks into, and the most dangerous to misread. The instinct is to redesign. The correct move is to listen first — the same discipline that applies to a practitioner building from scratch applies equally to a practitioner inheriting something broken. What you have was built by someone, for reasons that made sense at the time. Before you change it, you need to understand what it was solving, what it stopped solving, and what organizational history is attached to it.

The distinction between a refurb and a restart matters here. A refurb preserves the foundation — the artifacts, the institutional habits, the credibility that has accumulated — and refreshes the fit. A restart abandons the foundation and begins from Step 1. Most inherited models need a refurb, not a restart. The EPMO in Production page describes how to tell the difference.

When the model was built by someone outside the organization. A governance model built by an external consultant and never owned by the internal team fails differently than one that simply drifted over time. The resistance is not organizational habit — it is rejection of an imposition. The refurb-vs-restart test still applies, but apply it after one additional question: did the people who will run this model help build it, or were they handed it? A technically sound model nobody inside the organization helped create will need re-grounding through Step 1 listening before a refurb can succeed, even if nothing about the model itself is wrong.

Your path: Read the EPMO in Production page — specifically the Needs a Refurb and Long Goodbye sections. Then run the Diagnostic Part One above to locate where the inherited model sits in the lifecycle. Then use Diagnostic Part Two to identify the specific entry point where the failure is most visible. Apply Step 1’s listening discipline at that entry point before redesigning anything.

Before You Proceed

Whether you are starting at Step 1 or entering mid-sequence, one discipline applies everywhere: do not skip the listening work that corresponds to wherever you are entering.

Every entry point requires you to understand who the informal decision makers are, what the real history of the governance effort has been, and what the organization’s relationship with governance actually is — not what the org chart or the process documentation says it is.

The practitioner who skips that listening at any entry point will be surprised by things they could have learned in week one.

Now: read the Introduction. Then begin at the step that corresponds to where you are.