I’ve watched a $2 million software implementation grind to a halt because the client couldn’t decide who owned the approval process for user acceptance testing.
The vendor was ready. The system worked. The timeline was intact.
But the client’s internal decision latency—the time gap between when information becomes available and when someone actually makes a call—added four months to the project. The delay cost them an extra $600,000 in extended vendor fees, lost productivity, and opportunity costs.
The vendor took the blame in the post-mortem. But the real bottleneck lived inside the client organization.
This happens more often than anyone wants to admit. We spend months vetting vendors, negotiating contracts, and building detailed project plans. Then we ignore the most predictable risk factor: our own inability to make decisions quickly.
The Hidden Cost of Internal Delay
Decision latency isn’t just annoying. It’s expensive.
Research shows that 83% of workflow delays happen because approvals are stuck. The average employee wastes 15% of their workweek waiting for approvals. Organizations lose up to 30% of operational efficiency due to slow decision-making.
Let me translate that into project terms.
For every million dollars you spend on a project, approximately 1,000 decisions must be made. Some are minor. Others have high impact on delivery and value. If your organization takes an extra two days on average to make each high-impact decision, you’re adding weeks or months to your timeline.
Project delays increase costs by 20-30%. A construction project with a $1 million budget could see an extra $200,000 to $300,000 in costs due to delays. In another study, a ten-month delay in market delivery reduced the financial return of a project by 33%—leaving the cost of delay at around 3.5% per month.
You’re not just paying your vendor to wait. You’re paying for extended overhead, lost market opportunities, and the compounding cost of every downstream decision that can’t happen until you make the one you’re sitting on.
What Decision Latency Actually Looks Like
I’ve seen three patterns that create the most damage:
Approval ambiguity. Nobody knows who has the authority to say yes. The project manager thinks it’s the director. The director thinks it’s the steering committee. The steering committee thinks someone already approved it. Meanwhile, the vendor is waiting for feedback on a deliverable that determines the next three months of work.
Research shows that ambiguity surrounding who is responsible for making a decision is a primary cause of delay. These delays cause organizations to lose valuable time developing new products, updating current products, entering new markets, and other vital activities.
SME unavailability. Your subject matter experts are overcommitted. They’re the only people who can answer critical questions, but they’re in back-to-back meetings for the next two weeks. The vendor submits questions. Weeks pass. The vendor follows up. More weeks pass. By the time you get answers, the vendor has moved resources to other projects and your timeline has slipped.
Political maneuvering. Gartner research indicates that 70% of executives attribute decision delays to political maneuvering rather than strategic logic. People protect their influence instead of aligning decisions with organizational objectives. The decision isn’t hard. The politics are.
I watched a procurement team spend six weeks debating vendor selection—not because the options were unclear, but because two executives were fighting over budget control. The project started late. The vendor relationship started with frustration. The entire engagement suffered.
Why This Becomes a Contract Risk
Most contracts assume the client will provide timely decisions, access to resources, and clear direction.
When you don’t, you trigger penalty clauses, change orders, and relationship breakdowns that cost far more than the original delay.
Here’s what I’ve seen happen:
Vendors price risk into proposals. Smart vendors recognize decision latency during discovery. They add buffer time and cost contingencies to their proposals. You end up paying more because the vendor assumes you’ll be slow. You don’t even realize you’re being charged a latency tax.
Change orders multiply. When decisions take too long, vendors make assumptions and move forward. Later, when you finally decide, the work doesn’t match your expectations. Now you’re paying for rework through change orders that wouldn’t exist if you’d made the decision on time.
Vendor relationships deteriorate. I’ve seen vendors disengage from projects where the client consistently delays decisions. The best resources get reassigned. Communication becomes transactional. The vendor starts managing the relationship defensively instead of collaboratively.
According to a global study by World Commerce & Contracting, poor contract management practices cost companies nearly 9% of their annual business value. The contract approval process remains one of the slowest and most frustrating bottlenecks for both legal and business teams.
You lose future opportunities. Clients may lose confidence in an organization’s ability to deliver projects on time, resulting in loss of future business opportunities. But it works both ways. Vendors remember difficult clients. When you need help on the next project, the best vendors will be busy.
How To Measure Decision Latency
You can’t fix what you don’t measure.
I recommend tracking three metrics:
Decision cycle time. Measure the time from when a decision is requested to when it’s communicated. Track this for different decision types: approvals, scope changes, resource allocation, strategic direction. You’ll quickly see where your bottlenecks live.
SME response time. Track how long it takes subject matter experts to respond to vendor questions. If your average response time is longer than 48 hours, you have a problem. If it’s longer than a week, you have a crisis.
Approval queue depth. Count how many decisions are waiting for approval at any given time. If you have more than five decisions in queue, you’re creating a backlog that will compound delays throughout the project.
I worked with a client who started tracking these metrics and discovered their average decision cycle time was 18 days. They thought they were responsive. The data showed otherwise. Once they saw the numbers, they restructured their approval process and cut cycle time to four days.
How To Surface This in Vendor Proposals
The best way to control decision latency is to make it visible before the contract is signed.
I recommend requiring vendors to include decision latency assumptions in their proposals.
Ask vendors to specify response time expectations. Require them to state how quickly they need decisions, SME input, and approvals. Make them quantify the impact of delays. If they assume 48-hour turnaround and you take two weeks, what happens to the timeline and cost?
Require vendors to price realistic scenarios. Ask for three pricing models: optimistic (you respond quickly), realistic (you respond at your measured average), and pessimistic (you respond slowly). This forces both parties to acknowledge that delivery risk is joint.
Make decision rights explicit in the SOW. Specify who has authority to make each type of decision. Name individuals, not roles. Include backup decision-makers. Define escalation paths. Remove ambiguity before it creates delays.
Build decision latency into your project timeline. Add buffer time based on your measured cycle times. If your average approval takes 10 days, don’t plan for two-day approvals. Be honest about your organizational speed.
How To Structure RFPs To Address This
Your RFP should force vendors to surface decision latency risks early.
Include these requirements:
Decision dependency mapping. Require vendors to identify every client decision point in their proposed approach. Make them specify when each decision is needed, who needs to make it, and what happens if it’s delayed.
SME time requirements. Ask vendors to quantify the SME time they need from your team. How many hours per week? Which specific roles? What happens if those people aren’t available?
Delay impact analysis. Require vendors to explain how client-side delays affect their delivery timeline and cost. Make them show their math. This creates shared accountability for keeping the project on track.
Response time commitments. State your organization’s measured decision cycle times in the RFP. Ask vendors to price their proposals accordingly. If you know you take 10 days to approve deliverables, tell vendors upfront. Let them plan for reality instead of optimism.
What Good Looks Like
I worked with a client who rebuilt their entire project governance model around decision speed.
They started by measuring their baseline. Average decision cycle time: 14 days. SME response time: 9 days. Approval queue depth: 12 decisions.
They made three changes:
They created decision tiers. Low-impact decisions got delegated to project managers. Medium-impact decisions went to a weekly steering committee. High-impact decisions got escalated to executives with a 48-hour response commitment.
They assigned decision owners by name. Every decision point in the project plan had a named individual responsible for making the call. No more “the team will decide” or “we’ll discuss in the next meeting.”
They tracked decision latency as a KPI. They published weekly reports showing decision cycle times and approval queue depth. They made speed visible. Leaders started competing to respond faster.
Within three months, their average decision cycle time dropped to four days. Their next vendor engagement came in 15% under budget and two months ahead of schedule.
The vendor didn’t change. The client did.
The Real Work Starts With You
You can’t outsource decision-making to your vendors.
The best vendor in the world will fail if you can’t provide timely direction, clear authority, and available resources. Delivery risk is joint. Your internal processes matter as much as vendor capability.
Start measuring your decision latency today. Track cycle times. Count approval queues. Be honest about your organizational speed.
Then build that reality into your next RFP. Require vendors to price your actual response times. Make decision rights explicit. Create accountability for speed on both sides of the contract.
The projects that succeed aren’t the ones with the best vendors. They’re the ones where both parties acknowledge that speed matters and build systems to support it.
Your next project timeline depends less on vendor capability than you think.
