Step 01

Listen

In Brief — Before building anything, understand what you are actually walking into. The listening step is about mapping the informal system — how decisions are really made, who has actual authority, and what people are protecting — before you propose changing any of it. Every governance model designed without this foundation is built for the organization someone imagined, not the one they are in.

What’s Actually Happening

You walked in and someone handed you a problem they have already decided how to fix.

Maybe it is a deck. Maybe it is a project list. Maybe it is a meeting where they explain what the EPMO needs to look like and what you should build. They are telling you the answer before you have heard the question.

The organization has been running without formal governance. Work gets done. Things get decided. Priorities shift. Money moves. None of it happened through a process you designed, but it happened. The people who made it happen — the executives, the managers, the PMs already in the building — built something, even if it does not look like what you would build.

That something has history, logic, and politics attached to it. They may not talk about the politics openly. They will talk about the history and the logic. Some of it will sound like justification. Some of it will be genuine. Your job right now is to understand what you are actually walking into before you touch any of it.

You are not there yet to fix anything. You are there to understand it.

Why This Step Exists

Not so you can design a better system. Not yet.

Because the fastest way to fail at standing up EPMO governance is to arrive with the answers. The organization will immediately identify you as someone who does not understand their reality, and they will be right. You will spend the rest of your time fighting a credibility deficit you created in week one.

Governance that nobody trusts does not govern anything.

Listening is not a soft skill you perform while waiting to get to the real work. It is the real work. You cannot build a system that improves decisions without understanding how decisions are currently being made — by whom, through what channels, and why that feels normal to the people doing it.

There is also something practical here. Every organization has informal governance. Whoever shouts loudest. Whatever the most senior sponsor protects. Whatever got approved two years ago and has never been re-examined. That informal system is what you are replacing. You cannot replace something you have not mapped.

What Good Looks Like

You have had one-on-ones with every person who influences which work gets approved, funded, started, or stopped. Not a survey. Not a group session. Conversations, one at a time, where people say things they would not say in a room full of colleagues.

You can describe, without looking at a document, the actual path a request travels from the moment someone has an idea to the moment work begins. You know where the formal checkpoints are. You know which ones actually function and which ones exist on paper. You know where work enters outside the formal path.

You know who the informal decision makers are. Not the org chart — who actually says yes or no, whose opinion changes outcomes, whose resistance will matter when you start proposing changes.

You have heard, in their own words, what people think is broken and what they think is working. You have not yet told any of them what you think. That last part is harder than it sounds.

How to Do It

Start with the people closest to the CEO’s priorities and work outward. Not the CEO first — the people who translate the CEO’s priorities into actual work. They will tell you more about how decisions really get made than any executive will in a formal conversation.

In your first two weeks, do not attend status meetings as a participant. Attend as an observer, or do not attend at all. You are not there to report on work. You are there to understand the system that manages it.

Ask the same core questions of every person you sit with:

Walk me through how a new project gets started here.
What happens when two priorities conflict?
What gets in the way of decisions getting made?
What works here that I should not break?
What are you most worried about?

The last question is the most important one. Not because you will immediately fix what they are worried about, but because what people are protecting tells you more about an organization than anything they will show you in a presentation.

When someone gives you a short answer, stay quiet. Let the pause sit. People say the most useful things right after an uncomfortable silence.

Three roles deserve specific attention in your listening schedule. The Business Analyst sits at the intersection of problem definition and solution design — they can tell you where requirements go to die and why the stated request rarely matches the actual problem. The Product Owner manages the daily tension between team-level delivery and portfolio-level commitments — they experience governance as either helpful structure or an obstacle to getting things done. The Product Manager thinks in roadmaps and continuous investment cycles, not discrete projects — understanding their reality tells you exactly where a project-centric governance model needs to flex. These three perspectives are not optional listening. They are where the most important seams in the current informal system are usually visible.

Take notes after the meeting, not during it. Write what they said, not what you think they meant. The interpretation comes later.

What Breaks When You Skip It

You design an intake process for the organization you imagined, not the one you are in.

You build a prioritization model that does not account for the side doors everyone uses to get work approved outside the formal process. You create a governance framework that makes sense on paper and makes the people in the building feel like you never asked them a single question about how they actually work.

Six months in, adoption is low. People route around the process. The EPMO is producing reports that nobody reads and running meetings that feel like compliance exercises.

The failure did not start six months in. It started in week one when you skipped this step.

There is a second failure that skipping this step creates: an authority deficit that is very hard to recover from. The EPMO that launches governance requirements before demonstrating governance value is perceived as overhead from day one. Governance authority is earned through demonstrated usefulness — and usefulness cannot be demonstrated if you have not first understood what the organization actually needs.

The Gotchas

People tell you what they think you want to hear. Especially early. Especially if they sense you have executive backing. The person who agrees with everything in the meeting and then does nothing different is telling you something. So is the person who stays quiet and watches.

You will want to start building things. A blank document is uncomfortable. The urge to produce something visible is real. Resist it. Producing output before you understand the system is how you produce the wrong output efficiently.

What people say they need is not always what they need. Someone who says “we need a project tracker” may actually need a way to tell their boss no to new requests. Listen for the problem underneath the request.

Documents lie. The process map on the wall and the actual path work travels are almost never the same thing. When someone hands you existing documentation, ask how it actually works in practice. The gap between those two answers is where your work begins.

Where the Disciplines Show Up

→ Decision Discipline: The listening step reveals who actually makes decisions — not who the org chart says does. The gap between formal authority and informal authority is the most important piece of information you will gather here. You cannot design a governance model with real decision rights until you understand where the real decisions are currently being made.

→ Change & Absorption: The people you are listening to are already absorbing change. Some of them are at capacity. The listening step surfaces what the organization is currently defending, protecting, and resisting — which is the baseline for understanding how much additional change the governance model itself will need to manage.

→ Enterprise Fit: The informal processes you uncover often exist because the formal processes did not fit the work. That mismatch is an enterprise fit problem. Understanding why people route around existing processes tells you what any replacement process needs to accommodate.

→ Evidence: Every claim about how the organization works that comes from this step is an observation, not a fact. “Based on interviews with seven stakeholders, work appears to enter through at least four informal channels” is more honest than stating it as fact. The distinction matters when you are building the case for change.

→ Political: The listening step is where you map power before you propose anything. You are not just learning how work moves — you are learning whose coalition you will need, whose work the current informal system is protecting, and what it will cost politically to change it. The influence map you build here is a guide to the conversations you need to have before any process change can stick.

The Key
Earn the right to standardize by first understanding what people are protecting. Not what they say they are protecting. What they are actually protecting. You need to understand that system before you propose changing it. Not to preserve it. To know where the resistance will come from when you do.

You know this step is working when you can describe the informal decision-making system — who actually says yes, whose objection kills a proposal, what work moves without governance — and at least three people who operate inside it confirm you got it right.

The Artifacts

Three things come out of this step. None of them are presentations.

T9 — Stakeholder Interview Guide

The questions you will ask, in sequence, with space to record what people said and what you observed. Keep these separate. What someone says in the moment and what you observe about how they said it are different data points.

T10 — Current-State Decision Map

A simple picture of how work actually enters the system, where it slows down, where decisions get made, and where work bypasses the formal path. Drawn from your interviews and direct observation — not from existing documentation. The gap between documentation and reality is the map.

T11 — Influence Map

Who has formal authority, who has informal authority, and where those two things differ. This does not get shared. It is a working document for you. It will tell you whose buy-in is required before any process change can stick — and it will likely differ from what the org chart suggests.