Step 02

Build the Portfolio Inventory

In Brief — You cannot govern what you cannot see. Before any governance model can function, the organization needs one honest list of everything currently in flight — what it is, who owns it, what it is supposed to accomplish, and what information is missing. The inventory is not an administrative exercise. It is the first real evidence that governance is needed, and the baseline everything that follows depends on.

What’s Actually Happening

The work is everywhere.

Some of it is in a project management tool. Some is in spreadsheets someone built three years ago and still updates manually. Some exists only in a status meeting that happens every other Thursday. Some of it nobody is tracking at all — it just gets done because someone with enough authority decided it needed to happen and enough people complied.

Ask any two senior leaders how many active projects the organization has right now. You will get two different numbers. Ask where the list lives and you will get four different answers. Ask which ones are the highest priority and you will hear about the same five, while sixty others move in the background without anyone tracking whether they are succeeding, stalling, or quietly consuming resources that were already committed somewhere else.

This is normal. It is not a sign that something catastrophic has gone wrong. It is what organizations look like before governance exists. The work did not wait for the process. The process has to catch up to the work.

Your job in this step is to build one list. Not a perfect list. One list.

Why This Step Exists

You cannot govern what you cannot see.

That statement sounds obvious until you try to act on it. The reason most governance efforts fail early is not that the process is wrong. It is that the process was designed without a complete picture of what it was supposed to govern. Leaders walk into a prioritization session and make decisions about the top ten while the other sixty continue without scrutiny. Capacity gets allocated to new work while existing commitments quietly bleed the same resources. Dependencies nobody mapped cause surprises that look random but were always predictable.

The inventory exists to make the invisible visible. Not to judge it yet. Not to score it or rank it or decide what should stay and what should go. Just to see it. All of it. In one place.

There is also a political reality to this step. When you eventually need to make decisions about what to continue, what to stop, and what to defer, you cannot walk into that conversation with a partial list. Someone will always know about the project that was not on your radar, and the moment they name it, the conversation shifts from governance to credibility.

What Good Looks Like

You have a single document — not a database, not a dashboard, not a system — that lists every piece of active work and every proposed work item that has not yet been formally declined. It does not have to be beautiful. It has to be complete.

For each item you know, at minimum: what it is, who is accountable for it, what it is supposed to accomplish, whether it is mandatory or discretionary, and its current status in a single honest word. Active. Stalled. Proposed. Unknown.

Unknown is a legitimate status. It is more honest than guessing, and it tells you exactly where more work needs to happen.

You also know, at the end of this step, roughly how many items exist that have no clear sponsor, no defined outcome, no funding line, or no one tracking them. That number will be higher than anyone expected. That is useful. It is the first real evidence that governance is needed.

How to Do It

Start with what already exists. Every system, every spreadsheet, every status meeting, every email thread someone called a project. Pull it all into one place without editing it. Do not clean it yet. Do not decide yet what is a real project versus a task versus a program. Just collect it.

Then walk the list with the people you interviewed in Step 1. Not in a group. One at a time. Show them what you have and ask two questions:

What is on here that should not be?
What is not on here that should be?

You will learn more from the second question than the first. What people leave off the list on purpose tells you exactly as much as what they put on it.

As you collect, apply a rough classification to each item. Four categories cover most of what you will find:

Mandatory

Regulatory, legal, compliance, audit-driven. The organization does not choose whether to do this work. It chooses how.

Strategic

Tied to a named organizational priority, with a sponsor who can articulate the connection. Not everything that gets called strategic actually is. That distinction matters and will come up again in Step 6.

Operational

Keeps the business running, improves existing capability, addresses known problems. Not glamorous. Often underfunded and undernoticed. Almost always more important than it looks.

Discretionary

Someone wanted it, someone approved it, and the connection to organizational priority is unclear or indirect. This category is larger than anyone admits, and it is the most important category to name honestly.

Do not try to score, rank, or prioritize anything in this step. That is Step 6. If you start scoring now, people will feel evaluated before they feel heard, and the inventory will become political before it is complete.

What Breaks When You Skip It

You build a tollgate process for new work while the existing work continues without oversight. The governance model looks forward without ever accounting for what is already in motion. New projects get rigor at intake while sixty legacy commitments move without scrutiny, consume the same resources, and fail for reasons that a complete inventory would have surfaced weeks earlier.

You also lose the first real opportunity to demonstrate value. An honest inventory, presented without drama, does more to establish the EPMO’s usefulness than any governance framework document. It shows that someone finally counted everything.

Skipping the inventory because the data is messy is the most common version of this mistake. The data will always be messy at this stage. Messy data with a complete list is more useful than clean data with a partial one.

The Gotchas

Chasing perfect data will kill this step. You will never have all the information you want before you need to show something. The goal is a complete list with honest statuses, not a pristine database. Mark what you know, flag what you do not, and move forward.

The list will become political the moment it is visible. Someone will want their project described differently. Let them make the case. That conversation is valuable — it is the first time someone has had to defend the priority of that work using something other than relationship capital.

Every organization has projects that exist only because stopping them would be embarrassing. The executive who championed it two years ago is still in the building. These projects are often the ones most visibly consuming resources and least visibly producing results. They will not volunteer themselves for scrutiny.

Do not confuse activity with investment. A project where someone sends a weekly status email is not the same as a project with a sponsor, a funded budget, a defined outcome, and accountability for delivery. That distinction needs to be visible.

Where the Disciplines Show Up

→ Decision Discipline: The inventory makes visible the decisions that have already been made — what was funded, what was started, what is continuing without scrutiny. It also surfaces the decisions that were never formally made but are being acted on anyway. That distinction is the foundation of the decision discipline you are building.

→ Change & Absorption: The inventory is the first place you can see the cumulative change load on the organization. When the list is complete, you can begin to assess: how much change is already in motion, which parts of the organization are carrying the most, and what the organization’s realistic absorption capacity is.

→ Enterprise Fit: The inventory often surfaces technical overlap, redundant systems being built in parallel, and integrations that were never planned but are now dependencies. These are enterprise fit issues hiding inside the portfolio. Surfacing them during inventory is significantly less expensive than discovering them during delivery.

→ Evidence: The missing information log is your first evidence artifact. It documents what the organization does not know about its own work — and that gap is evidence in itself. Every blank field in the inventory is a decision that was made without the information needed to make it well.

→ Political: Surfacing the portfolio makes visible work that powerful people have been keeping off any formal list. At this step, political discipline means knowing who needs to be briefed before you publish the list, and in what order. The executive who discovers their project has been logged as “unsponsored” without being told first is a problem you could have prevented.

The Key
Visibility before sophistication. A complete, honest, unsophisticated list is worth more than a partial, beautifully scored one. The organization needs to see itself clearly before it can make better decisions.

You know this step is working when nothing surprises you anymore — not when your count reaches a specific number, but when someone stops naming a project you did not already have on the list.

The Artifacts

T12 — Portfolio Inventory

A single document listing every active and proposed work item. For each: description, accountable person, intended outcome, category, current status, and known dependencies. Missing information is flagged, not fabricated.

T13 — Classification Rules

A one-page document that defines what goes in each category and what the category means for governance. Mandatory means no choice. Strategic means a named leader can articulate the connection to an organizational priority. These definitions do work. Write them down.

T14 — Missing Information Log

A list of everything you need to know that you do not know yet. Use this log actively in Step 3. The gaps in your inventory tell you exactly what intake discipline would have captured if it had existed. The missing information log is not a failure. It is evidence.