A delivery group said yes to every request because it had nothing to point to when it wanted to say anything else.
Every Request Was Urgent
The front-office delivery group of a global IT organization was drowning in requests. They came from every corner of the business it served. Sales wanted enhancements to the customer platform. Recruiting needed integrations. Payroll had compliance work that could not wait. Client delivery wanted new dashboards. Every request solved a real problem, and every requester framed it as urgent.
The team kept saying yes because it did not feel it had another option. It had once described itself as a luxury yacht. It now felt more like a life raft. Across the IT organization the pattern was visible in where time went: more than eighty percent of available hours went to keeping the lights on and finishing existing projects, which left little room for improvement or new strategic work.
The PMO leader raised it in one of our working sessions. The team could not bring itself to say no. Every request came from someone it knew, with a legitimate reason, and there was no defensible basis for ranking one above another. So the backlog grew, lead times slipped, and the team worked nights and weekends to keep up.
The Missing Third Answer
The usual response is to teach people to prioritize. That misses the cause. The team's judgment was fine. What it lacked was organizational backing for that judgment. When someone challenged a decision to put work off, there was no policy to point to, so the decision became personal: one person saying no against another person being told no. In that contest, the person lower in the hierarchy almost always loses.
The PMO leader had assumed the fix was helping the team find the spine to refuse. Permission to say no matters, but on its own it pushes requesters to find their way around the process. The goal was a third answer: not yet. Not yet acknowledges that the work matters and says it is being sequenced behind commitments that matter more right now. She recognized it as the language the team had been missing. With it, she said, half the conversations they were avoiding would become much easier.
The team was not short on courage. It was short on policy. The governance it needed was not another approval step. It was a set of rules a team member could apply the moment a request arrived.
- Only two answers: yes or no
- The refusal rests on one person
- Pushback becomes a contest of rank
- Requesters route around the process
- Work acknowledged and sequenced later
- The reason points to an agreed policy
- Disagreement follows an escalation path
- The decision rests on rules, not rank
Twelve Factors, Each With an Owner
Over a series of workshops, front-office leaders and the internal change team worked out which factors should influence priority. We opened with a simple-sounding question, using one system everyone knew: should the application a request touches affect its priority?
The answers split at once. Some leaders said yes, for reasons ranging from business impact to funding to customer impact. Then a development manager said not for his teams, and another leader agreed. In their areas, work crossed several applications every day, and which one was involved was not a variable they used.
No one was wrong. The question was not whether the application mattered but when. Some factors bear on almost every decision. Others apply only under specific conditions. Policies would not replace anyone's judgment. They would say when and how that judgment applied.
Every candidate factor went through the same four-part template. Define the what: its scope, rules, and exceptions. Decide the when: its cadence and triggers. Specify the where: the point in the process where it applies and where its decisions are recorded and shared. Clarify the who: who decides, who is consulted, and the escalation path when people disagree.
By the end, the group had twelve factors. Each had a defined scope, a written policy, named owners, and an escalation path, and each had been agreed by partners from across the business. The factors were then mapped onto the stages of the workflow, so anyone scoring work knew which ones applied in discovery, in planning, and in execution.
| What the policy says | |
|---|---|
| Work type | Critical incidents go first |
| Business support | Multi-unit asks move up |
| Business value | Measurable value ranks higher |
| Urgency | Only critical, time-bound work |
| Application | Counts only in set cases |

The Request Marked Urgent
The test came shortly after the policies went into daily use. A business unit submitted an enhancement to its customer platform and labeled it urgent. Before, the receiving team would have tried to squeeze it into an overloaded backlog and let existing commitments slip.
This time the team evaluated it against the policies. It supported a single business unit. No regulatory deadline drove it. It was not blocking other work. It was a worthwhile enhancement that deserved attention, and it was not the most important work in front of the organization. The answer was not no. It was not yet, with a defensible reason.
The business partner pushed back, as partners often do. Instead of letting the email chain become an argument, the team pointed to the policy, which kept the exchange on the rationale rather than the person. A further challenge would follow the escalation path to the prioritization forum and the IT leadership team, not to someone who could be leaned on. A personal judgment had become an organizational policy.
-
The request Marked urgent An enhancement for one business unit
-
Checked against policy One unit, no regulatory deadline, not blocking
-
What changed Not yet, with a reason Worthwhile, but not the most important work
-
Partner pushes back The team points to the policy, not a person
-
If challenged Escalation path if needed To the forum and IT leadership
Decisions That Could Be Explained
The following month the front office launched its prioritization forum. For the first time, prioritization discussions began from criteria everyone had helped write. Decisions could be explained, deferrals could be defended, and business partners understood why work ranked where it did, even when they did not like the order.
The forum's first sessions built on the same footing. Business partners shaped a shared set of criteria for weighing requests, and every session recorded what was accepted, deferred, or cut. Decisions about what comes next are now made against shared criteria for value, urgency, and capacity, and they are written down.
That is governance without bureaucracy. It added no approval layer. It moved the rules to where decisions are made, so most calls could be made by the team, when a request arrived, with a reason anyone could check, and the forum was left for disagreements that genuinely needed it. It was not finished: by the close of the pilot, the forum was not yet the place where every priority call got made. But a team that had only ever been able to say yes now had a third answer, and a policy behind it.
Governance earns its place when it lets the people closest to the work make a defensible call without calling a meeting.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


