Imagine this: your team spots a change in customer behaviour. With AI support, it explores the evidence, develops a response and prepares a proposal for a small pilot.
Then the waiting begins.
Sales wants a clearer revenue forecast. Operations needs to check capacity. Finance asks which budget will pay. The proposal reaches the management meeting, where someone requests another round of analysis.
Six weeks later, nobody has rejected the idea. Nobody has authorised the test either.
This is an illustrative scenario, but it raises a question worth asking in your own business: what happens when the speed of insight exceeds the speed at which your organisation can act?
Faster insight can expose a slower organisation.
When considering AI, leaders understandably ask what it could help their teams do faster. Research, analysis, planning and routine tasks are obvious places to look.
Another question: where will the work go next?
If a proposal still needs to pass through unclear responsibilities, competing departmental targets, and repeated approvals, producing it faster may move it up the queue. The time saved in preparing the work disappears in the time spent waiting for permission.
Looking ahead, imagine teams evaluating more options and proposing more experiments with AI support. An organisation that keeps its existing approval process could face a growing backlog of decisions. More possibilities would compete for the same limited management attention.
That is a useful Future Thinking exercise. Before investing in faster tools, ask which parts of the business would struggle if the volume of credible proposals doubled.
Where good decisions lose momentum
Organisational friction is the effort and delay created as work moves between people, teams and systems. Some of it serves a purpose. A significant investment deserves scrutiny. Customer safety, legal obligations and sensitive data require appropriate checks.
The problem begins when nobody can explain what a particular step contributes—or when a modest, reversible experiment faces the same process as a major commitment.
Friction can be surprisingly ordinary. A customer issue belongs to several departments, so none takes responsibility for resolving it. A manager is expected to support a new service but is measured entirely on the profitability of the existing one. A team gathers evidence, only to discover that the person who can approve the next step needs a different set of information.
These situations do not necessarily indicate unwilling employees or poor leadership. People may be responding sensibly to the responsibilities and incentives they have been given.
For an SME, the bottleneck might be equally simple: too many decisions depend on the founder. The business has grown, but the authority to act has stayed in one place.
The consequences extend beyond wasted hours. A delayed test postpones learning. A delayed service change prolongs a customer problem. Repeated waiting can also discourage employees from raising the next useful idea.
Design the decision before buying more speed.
Decision architecture means making deliberate choices about who can decide, what evidence they need, which limits apply, and when to escalate a decision.
Start by distinguishing decisions according to their consequences. A limited pilot with an agreed budget, clear safeguards, and a stopping rule may suit delegated authority. A substantial, difficult-to-reverse commitment calls for a different level of review.
Then give each decision a named owner. Others can contribute expertise or raise concerns, but responsibility for concluding should be clear.
Agree on the evidence required before work begins. Otherwise, teams can spend weeks answering questions that were never made explicit, while each discussion introduces another requirement.
AI also needs a defined role in this arrangement. If it helps prepare analysis or recommendations, someone must remain responsible for checking the evidence and deciding what follows. Faster output matters only if the organisation can assess and use it.
Finally, examine what teams are rewarded for. Asking people to experiment while penalising every short-term disruption sends a confusing message. A bounded test should have an agreed purpose, acceptable limits and a review of what was learned.
A practical test: follow one delayed decision
You do not need to start with a company-wide transformation.
Choose one recent decision that took longer than expected. Reconstruct its journey from the first proposal to the eventual outcome. Separate the time spent doing useful work from the time spent waiting.
Ask five questions:
- Who had authority to decide, and was that clear from the beginning?
- Which evidence helped conclude?
- Which approvals added useful scrutiny, and which repeated earlier checks?
- Where did conflicting priorities or targets hold up progress?
- Could a smaller, controlled test have answered the remaining questions?
The aim is to identify one change you can try. That might mean setting a spending limit for pilots, removing a duplicate approval, agreeing evidence requirements earlier or delegating a recurring decision.
Track whether the change reduces waiting time while maintaining decision quality. That gives you a practical basis for the next improvement.
Prepare for the decisions your future business will need
Future Thinking helps leaders explore how customer expectations, technology and market conditions could change. Business Design examines whether the organisation can respond through its services, business model, responsibilities and ways of working.
The two meet in a concrete question: if you saw an important opportunity tomorrow, what would have to happen inside your business before you could test it?
Your answer may reveal a more useful starting point than another technology purchase or another strategy presentation.
You can begin with the decision already sitting in the queue.
Where is your next move getting stuck?
Bring one important decision that keeps getting delayed.
With a MaxMORIX EXPERTS Strategy Diagnostic, we can examine how it moves through your organisation, identify the main bottlenecks and prioritise practical changes. We agree the scope, deliverables and fee before the work begins.
Get in touch with a brief description of the decision and where progress has stalled. That gives us a concrete starting point for discussing whether the diagnostic is the right fit.
