The Front Door Is Not Real Until Leaders Use It

A global technology organization rebuilt its intake process and still found people being asked to work outside it. The process held only after the leadership team admitted the habit, closed the urgent-work loophole, and committed to using the front door themselves.

01 SURFACE
The condition

A redesigned intake process exists, but work keeps arriving through side channels, and much of it starts with the most senior people in the organization.

A new process, and the same side door

The global technology organization had done the hard discovery work. It had found that its intake process was not one process at all, documented a single version people could see, and started teaching it. The survey that kicked off that work had a second finding, though, and it landed harder than the first. A large share of respondents said they had been asked to do work outside the intake process entirely.

The PMO leader sat with that slide for a long time. Her question was the right one: with that much work hidden, how would she ever know what people were actually working on?

Our answer was blunt. The evolved intake process would never work if the people with the most authority routed work around it. The system was not failing because of its design. It was failing because the people who used it had learned they did not have to. She agreed, and said she suspected the executive leadership team was part of the pattern. She asked us to put the same data in front of them and watch how they reacted.

The CIO went first

The leadership meeting was scheduled for the following week. The CIO opened it and handed it to us. The slide showed the survey results, how often work bypassed intake, and what that did downstream to capacity, prioritization, and delivery predictability. The bypass was concentrated at the senior levels. We made one request of everyone in the room: when the new process launched, commit to using the front door yourselves, and redirect side-channel requests back into it.

Some executives lean back in a meeting like that and let others speak first. The CIO did the opposite. Without being prompted, he said he had done it himself. He had sent chat messages straight to delivery leads asking for things, and he had never thought of it as bypassing anything. He had thought of it as being efficient. Seeing the data, he said, he could finally picture what that looked like from the front line.

That admission changed the temperature of the room. He was not describing a violation. He was describing a habit, one that forms because executives experience a process differently than everyone else does. What feels efficient from the top looks like an exception from below, and enough exceptions teach an organization that the front door is optional. Once he had said it plainly, several other leaders acknowledged the same behavior in themselves.

Senior leaders in a candid working session around a table with laptops and papers.

What happens when it is genuinely urgent

Then came the objection every leadership team raises, and it was a fair one. What happens when something is genuinely urgent?

The answer was already built into the redesigned intake. An emergent pathway existed for work that truly could not wait, and escalation routes existed for time-sensitive requests. Urgency was a reason to use a faster lane, not a reason to leave the system. With that question answered, the leadership team made a shared commitment: every request from an executive would enter through one of the approved intake channels. No exceptions.

Figure 1
Urgency got a lane, not an exception
Where it goesWhat it means
Genuinely urgent workEmergent pathwayFast, and still visible
Time-sensitive requestEscalation routeSpeed without a side deal
Any executive requestApproved intake channelNo exceptions
Side-channel askRedirected to intakeWithout dismissing the person
The urgent-work objection was answered with routes that already existed in the redesigned intake. Every path still ended inside the system.

The circle was wider than the leadership team

Over the following weeks we worked with the leadership team on the new expectations: how to submit requests through the right channel, how to redirect a side-channel request without making the person feel dismissed, and how to model the behavior they wanted everyone else to follow.

One conversation in that training changed the scope of the effort. An executive pointed out that much of the side-channel work their teams carried was not coming from leadership at all. It was coming from the business. Sales representatives texted delivery leads. Operations managers called engineers. Finance sent direct emails. If bypass behavior was going to drop, the business units had to understand the front door too.

The PMO leader asked for the support to take that on and asked us to bring the same training to business unit leads. Sessions followed with representatives from sales, operations, finance, marketing, client services, and human resources. The message did not change from room to room. The front door only works when everyone uses it, and there is only one front door.

Figure 2
Where side-channel work really came from
  • Executive chats to delivery leads
  • Sales texts to delivery leads
  • Operations calls to engineers
  • Finance emails to teams
Approved intake channelsTrained across leadership and six business functions
The bypass started with leaders, but it did not end there. Once the business named its own habits, the training followed them.

Not one hundred percent, and a different first question

A few weeks after the business sessions, we came back to look at the early results. More work was entering through formal channels, and delivery teams were reporting fewer side-channel requests. We were careful not to overstate it. Side channels had not disappeared and formal intake had not captured everything. The direction was clear, and the result was not total.

The PMO leader's read was the one that mattered. It was working, she said, not perfectly, but working. What she noticed most was that the conversations had changed. When someone on her team mentioned a new request, the first question now was whether it was in the system. Before, nobody had asked that question at all.

The leadership team had started out believing intake was an operational tool that the PMO ran. They finished understanding it was also a behavior, and one they had to embody personally. A well-designed front door can be undone quietly by the smartest leader in the building, one helpful chat message at a time.

Figure 3
What moved, and what did not
Before the commitment
  • Leaders messaged delivery leads directly
  • Bypass felt like efficiency at the top
  • Teams acted on requests from anywhere
  • Nobody asked where a request came from
A few weeks later
  • More work entering formal channels
  • Fewer side-channel requests reported
  • First question: is it in the system?
  • Side channels reduced, not gone
The change was directional and honest about its limits. The clearest shift was the question people asked before acting on a request.

A process is only real when the people with the most authority are also constrained by it.

Share With Your Team

Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.

Not sure where to start?

Answer five questions about where work stalls. We send back a starting plan: where to begin and what to look at first.