A Commitment Without Scope Is a Guess With a Deadline

A delivery group serving many business units kept inheriting commitments no one had scoped together. One shared weekly forum, with clear limits on what it would not do, moved scoping ahead of the promise.

02 SCOPE
The condition

Work reached delivery teams as a short description and a due date, agreed in conversations the teams never attended.

Requests That Arrived as a Date

A delivery leader inside a global IT organization ran a group that served many business units at once. Her teams were capable, and she was proud of them. The pressure on them came less from the volume of work than from the way it arrived.

In a single day, one project manager brought her another priority that had come out of a private conversation with a business partner, and a second appeared at her door with an even larger request from a different part of the business. Neither conversation had included her people. What reached the team was a short description and a due date, set by business units that could not see the work already in flight. It worked like a game of telephone. By the time a request reached the people who would build it, most of its meaning had been lost and the date had hardened.

Pushing back one message at a time had only added heat. She wanted the project managers to advocate for her teams, but they were carrying requests in good faith. The structure gave them nowhere else to put them.

Figure 1
How a request lost its meaning
  1. Business has a need
  2. Where it broke Private one-on-one Delivery not in the room
  3. Where it broke Description and a date No view of work in flight
  4. Where it broke Team receives it Scope found while building
Each step was reasonable on its own. Together they delivered a date without a shared understanding of the work behind it.

Scoping Had No Home

The gap was structural, not personal. There was no shared, standard place to scope incoming work across all of the group's business relationships. Each project manager and business-facing leader gathered scope in separate one-on-one conversations, and those conversations never added up to a common understanding of what was coming.

The cost landed on delivery. Work reached the teams before anyone had confirmed it was worth doing. Working out what they were being asked to build pulled the teams away from what they had already promised, which made every existing commitment harder to keep. Each new date was a guess, and the guesses compounded.

A Room Built From the Objections

The strategy was a single recurring forum where the leaders who took in this group's work would scope it together. Its job was deliberately narrow: build just enough shared understanding that a request could be prioritized or sent back for further definition, and keep work that was not clearly scoped from reaching the teams.

For the kickoff we brought in everyone who took in work for the group, including the project managers whose one-on-ones had been feeding the pressure. For the first time, the people receiving, leading, and delivering the work were in one room. It was awkward. The delivery leader told them that if they were serious about changing how they worked, they had to build it together.

We asked what the forum could accomplish, and the answers came fast: transparency, alignment, real visibility into what was coming before it landed, a place to settle competing priorities instead of letting the business fight it out, and realistic estimates behind any date they committed to. One participant observed that half the delay was simply figuring out what they were being asked to do. The delivery leader added the outcome she cared about most: one view of incoming demand.

Then the lead for business analysis and solution design pushed back. It sounded to her like a status meeting, and she had watched discussions about incoming work turn into design by committee. Her teams owned design, and she did not want a forum improvising solutions for them.

So we asked the opposite question: what is this forum not responsible for? She engaged immediately. It would not set budgets; the budget cycle had its own process. It would not design solutions. It would not decide which person on which team delivered the work, and it would not try to answer every question the business had. It would scope and prioritize, then hand her designers work that was ready for them. With that boundary written down, she said she could work with it.

Figure 2
What the forum would and would not do
The forum does
  • Scope incoming work
  • Set the order of work
  • Check capacity before committing
  • Show status of work in flight
The forum does not
  • Set budgets
  • Design solutions
  • Assign people to work
  • Answer every business question
Writing down the second list is what won over the strongest skeptic. Her teams kept ownership of design; the forum took ownership of scoping and order.

Once a Week, Before the Commitment

By the end of the workshop the forum had a purpose: clarity and visibility into all of the group's work. It would decide the order in which work was done, whether there was capacity to commit to incoming demand, and the status of delivery already under way. Its value reached past the delivery teams to the business units, IT functions outside the group, and third-party vendors, all of whom would now share one understanding of current priorities.

Once warmed up, the participants named what made the work hard, talking over one another: business units chasing their own priorities, IT teams elsewhere with no idea what this group was working on, dependencies on vendors, and incomplete requirements that already carried a due date. Each side assumed the worst about the other because neither could see what the other was doing.

They agreed to meet weekly to review incoming work. The first meetings tested the idea, and the invitation widened to the business units themselves. A handful of representatives came, hesitantly.

A colleague writing on a whiteboard of notes while a teammate follows the discussion.

What Visibility Bought

The feedback turned positive quickly. Business representatives said that seeing progress against delivery commitments, and the full picture of everything the teams were carrying, gave them more confidence. The design lead who had expected another free-for-all changed her view after attending. She told the delivery leader she owed her one, because the forum had made a real difference in balancing the group's commitments to the business.

With the work visible, the delivery leader could weigh her teams' capacity against the incoming flow of requests and show the value they were delivering. Commitments were no longer made in rooms delivery never entered.

It was not a finished system. A new meeting is its own change effort. Early support does not mean people understand what consistent attendance will ask of them, and the forum was not yet the place where every priority call got made. But scoping now happened before the commitment, in a room everyone could see into.

The forum earned its place by what it refused to do. Scoping got a home because design, budget, and staffing kept theirs.

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.