Leaders believe there is one clear intake process, while the people doing the work describe several different ways requests actually reach them.
Certain the process was clear
The survey results went up on a shared screen, and for a moment the PMO leader said nothing. A meaningful share of the people who used the intake process had said they did not know its steps. She was genuinely surprised. She believed the organization had a clear, well-understood intake process, and her own PMO team played a significant role in it.
We asked her a different question. If she had to draw the steps right now, would they actually be clear? In our experience, when people describe how work really reaches them, the path is often very different from the one leadership believes exists.
She did not answer right away, and she did not need to. When an organization lacks an intake process people can find and describe, people submit work however they have historically been able to get results. The process turns into tribal knowledge, personal relationships, and workarounds instead of a shared way of working.
Overlay the drawings and count
Within days she brought in a technical portfolio manager from her PMO as an internal change partner. The first conversation was short. Did the portfolio manager have a clear picture of the current intake process? Not really. A search of the shared folders and the intranet had turned up nothing that showed the steps.
So we suggested the method we use when nothing is written down: ask the people who use the process to hand-draw it on a whiteboard from their own point of view. The worry came back immediately: what if everyone's drawing is different? They almost always are, we said. That is where it gets interesting. With enough versions, you can overlay them and see where the common steps are and where the paths split.
A few weeks later the portfolio manager came back with digitized drawings from leaders across the business area. In a private session with the change team, we laid them over one another. The organization did not have one intake process. It had six. Each path had grown up around a particular type of work, with its own decision points, handoffs, and unwritten rules. Each one made sense on its own. Together they produced a level of complexity nobody could see through, including the people running it.
The work outside every door
The maps showed the formal paths. Interviews and workshops showed what happened around them. When we asked each group how requests arrived at their desks, people started with the usual answers: email, an intake form that only some teams used, and the ticketing tools that handled certain types of work.
Then the conversations turned. People described chat messages, hallway conversations, phone calls, and text messages. One team lead showed us a text thread with an internal client that went back nine months: requests, status checks, escalations. An entire stream of work had been moving through the organization outside every system leadership depended on to understand demand.
The PMO leader asked the question that followed naturally. When someone pulled a report from the ticketing systems to show what people were working on, what was she really looking at? The honest answer was part of the picture, and no one could yet say how large a part. Nobody in the organization could reliably answer a basic question: how much work is coming in?
- Intake form, some teams
- Ticketing tools
- Chat messages
- Phone calls
- Text threads
- Hallway conversations

From six paths to one page
We consolidated the six paths into one view of the steps they shared, so a process that had lived only in people's heads now sat on a single page everyone could see. The next workshop put that consolidated view on the board and asked participants to rate each step as healthy, at risk, or critical. Sticky notes appeared fast. By the end, every step between intake and prioritization had been flagged as at risk or in crisis. Not one person in the pilot group called the intake healthy.
For the first time, the PMO leader could point to specific broken steps instead of relying on assumptions. A few weeks later she assembled a working group from delivery leads, business partners, change managers, technical owners, and her PMO. Over the following weeks they took the existing process apart step by step and rebuilt it around what the organization needed it to do, rather than what it had drifted into. The result was a redesigned intake process on one page, with the routing logic, decision points, and required information visible in a single view.
The channels themselves were handled with a policy rather than a ban. People could still talk about work in email, calls, meetings, and chat. Those conversations were not going away. But work did not officially exist until it entered one of the approved channels, and the formal entry points were connected so that demand could be seen in one place. The policy mattered as much as the technology. Without it, the organization would simply have built new blind spots.
-
Survey
What surfaced Many did not know the steps
-
Within days
Change partner named
-
Weeks later
The reveal Overlaid maps show six paths
-
Next workshop
What surfaced Every early step at risk Intake to prioritization
-
Following weeks
What changed One-page process rebuilt
-
Launch
What changed Hub, sessions, onboarding
-
Three months on
What changed Unfamiliarity fell sharply Repeat survey
A known path instead of a convenient one
Documentation and training were run as one effort, not two. A knowledge hub on the company intranet held the process diagram, step-by-step descriptions, routing logic for each work type, who owned triage, the information each category of request required, and short training videos. Every group attended a session that walked through the new process from its own perspective, and the hub was added to onboarding so new hires learned the front door as part of joining.
Three months later the survey ran again. The share of people who said they were unfamiliar with the intake process had fallen sharply. By the end of the pilot, the six ways in had become two clear paths: one for projects and enhancements, one for day-to-day operational work. The PMO leader summed up what had changed in her own understanding. She had started out believing she had a delivery problem. What she actually had was a visibility problem.
The front door was now real on paper and in training. Making it real in behavior was the next piece of work. Setting consistent expectations with business partners was still in progress when the pilot closed, and the hardest part of that work turned out to start much closer to the top of the organization than anyone expected.
You cannot prioritize demand you cannot see, and you cannot see demand that arrives through doors nobody has counted.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


