The Work Was Not Slow. The Request Was Not Ready.

A regulated product company's marketing team mapped every request from submission to publication. The delay was not in the work. It was at the front of the map, where incomplete requests sat waiting for information nobody had asked for.

02 SCOPE
The condition

A marketing team is blamed for taking 90 to 120 days per request, while most of that time passes before the team has what it needs to start.

Years of being called slow

The marketing and communications team at a regulated product company had heard the same complaint for years. The business believed the team was slow and rarely missed a chance to say so. Some people on the team quietly blamed their own team lead.

So we spent a morning with them mapping their process on a wall, with half the group in the room and half dialed in from home. Website changes, product announcements, press releases: each type of request was traced from the moment it was submitted to the moment it was published, with timestamps, handoffs, and wait states marked along the way. By the end of the session the map covered most of the wall.

When the numbers were added up, the average request took between ninety and one hundred twenty days to complete. Nobody in the room was surprised. They had been told they were slow for a long time. What they had never seen before was where the time was actually going.

The delay lived at the front of the map

The work itself did not take ninety days. Once the team had what it needed, drafting, design, legal review, and publishing all moved in a reasonable timeframe. We pointed to the front of the map. Most of the delay happened before the work ever reached the team.

Requests arrived and sat. Not because anyone was ignoring them, and not because the team lacked capacity. They sat because they were incomplete, and the team had to wait for missing information before it could begin. People dialed in from home leaned toward their cameras to study the map more closely.

The work was not slow. The requests were not ready. The team had spent years absorbing blame for an execution problem that was really an intake problem, and the person they had been blaming was not the cause either.

Figure 1
Where 90 to 120 days actually went
  1. Request submitted Website change, announcement, press release
  2. Where it broke Waiting on missing info Where most of the time went
  3. Drafting and design Reasonable once ready
  4. Legal review Reasonable once ready
  5. Published
Once a request was complete, the production steps moved at a reasonable pace. Most of the elapsed time sat before the team could start, waiting on information the request did not contain.

One question on a blank sheet

The next morning we were back at the wall. We had taped a blank sheet of paper next to the start of the map, and we asked the team to set tools and technology aside and answer one question. What is the minimum information you need to begin work without having to come back and ask for more?

The pause did not last long. Everyone grabbed sticky notes and the list formed quickly: target audience, business outcome, key message, launch date, dependencies, compliance considerations, supporting assets, due date, and approval chain. The team agreed on every item in a short time.

Only then did the intake form enter the conversation. Each item on the list became a required field.

Refusing to fill in the gaps themselves

The team debated a few of the fields. Some felt the information plainly belonged to the business. Others argued that the team could fill in the missing details itself and save everyone the friction.

We pushed back on that second idea. If the team completed the form on the requester's behalf, it would simply move the problem back to its own side of the fence, and nothing would change. The goal was not to make incomplete requests easier to accept. The goal was for requests to arrive ready to work. The team lead agreed that the business was overdue for some tough love, and the fields stayed required.

The policy that came with the form mattered as much as the form. A request missing required information would not move into the backlog and would not be prioritized. It would be returned with a clear explanation of what was still needed. The team lead expected business partners to dislike it at first and was fine with that. We told her the honest part: the form is the easy part. Enforcing the policy is the hard part, and it only holds if leadership backs it.

A team working through papers and notes together around a table.

By the second week, the requests changed

A few days later the first requests came in through the new form. Many were still incomplete. A little nervously, the team returned them, exactly as agreed.

By the second week the pattern had started to change. Business partners began providing all of the required information up front, because they had learned that anything less would come back to them. For the first time, requests were entering the queue in a state the team could act on immediately. The cycle of clarification emails, follow-up meetings, and time spent gathering context began to disappear.

The first change showed up in behavior, not in a new lead-time figure. The business had spent years believing it was waiting on execution. What it learned was that the team had been waiting on information the whole time, and that the business was the only party who could supply it.

Figure 2
From the wall map to ready requests
  1. Day one
    The reveal Map shows 90 to 120 days Most delay before work starts
  2. Next morning
    Minimum information listed Nine items, all agreed
  3. Same session
    What changed Required fields and policy Incomplete requests returned
  4. A few days later
    Policy held First requests come back Many incomplete, returned
  5. Second week
    What changed Requests arrive complete
The policy only worked because the team returned the first incomplete requests exactly as agreed. The business adjusted within about two weeks.

When requests arrive incomplete, the team that receives them inherits the delay and the blame for 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.