From Consensus to Action: What Organisations Can Learn from the Algorithm Debate

Reading Rachel Sylvester’s piece on Keir Starmer’s pledge to ban “addictive algorithms,” one thing stands out immediately: this is not a discovery problem. It’s an execution problem.

For years, the harms of algorithm driven engagement, particularly on children have been widely understood. Policymakers, parents, and even insiders within tech companies have acknowledged the issue. Yet meaningful action has lagged. It took legal rulings, public pressure, and political will to push the conversation from agreement into commitment.

This pattern is not unique to the government. It plays out in organisations every day.

At some point, every company reaches a moment where everyone knows something is wrong, an inefficient process, a failing product, a broken customer experience. The diagnosis is rarely the issue. The challenge is acting on it with urgency.

Most institutions are not designed for that. They are built for control, risk mitigation, and consensus. Over time, this creates layers, governance, approvals, competing agendas that slow execution to a crawl. Starmer’s reference to an eight year journey to legislate online safety is not unusual; it is what happens when systems prioritise caution over action.

Even when urgency is acknowledged, timelines stretch. A “three month consultation” sounds decisive, but when the problem is already known, it is still slow.

In practice, breaking this pattern comes down to a simple but powerful operating mode. Conviction at the top, trusted champions in the middle, operators who deliver, and clear ownership of budget.

1. Conviction at the top

Change requires leadership that is willing to take ownership, absorb risk, and act decisively. Not symbolic support, real authority to cut through inertia and, when necessary, bypass the red tape that slows organisations down. But conviction is not just intent, it is clarity.

As a leader, you must define the problem and the outcome with precision. A practical way to do this is by framing a hypothesis:

We believe that [this problem/opportunity exists]

For [this group/customer/part of the business]

Because [evidence or insight]

If we [take this action]

Then we expect [this measurable outcome]

We will know we are right when [specific success metrics/KPIs are achieved]

This shifts thinking from opinion to testable direction and gives the organisation a shared definition of success. From there, map the initiative using a lightweight business model canvas. You do not need complexity, just enough structure to ensure you are looking at all angles:

• Value proposition

• Customer or user segment

• Costs and investment

• Revenue or business value

• Key activities and dependencies

• Risks and constraints

• 
  

This combination creates clarity at speed.

Alongside this, you must understand the trade offs. What are you deprioritising? What metrics will move? What is the cost of disruption? Speed without this awareness creates chaos. With it, you get intentional execution.

How this is communicated matters just as much. This cannot be delegated. It must be delivered directly. When leadership shows up, it signals seriousness, sets focus, and defines expectations. And those expectations must be explicit: when champions and operators ask for support, the organisation responds, immediately. Conviction also sets the tone for accountability. Misalignment, obstruction, or competing agendas cannot be allowed to derail progress.

However, conviction without openness is dangerous. One of the most common failure modes is filtered reporting, teams delaying bad news until it is too late.

For initiatives like this, that is unacceptable.

Leaders must create an environment where bad news travels fast. Set clear reporting expectations, define cadence, and choose people who are comfortable escalating early. The goal is not to be shielded from problems, it is to stay close enough to intervene when it matters. That is conviction at the top: clarity, ownership, visibility, and a system that prioritises truth over comfort.

2. Trusted champions in the middle

These are the individuals with proxy power, those who translate intent into movement. But selecting them is not just about trust; it is about composition.

You need domain experts who understand the problem deeply. But expertise alone is not enough. Many experts are not naturally wired for timelines, milestones, or delivery structure, and that is fine.

This is why you pair them with strong project managers.

Together, they create balance: one drives depth and quality, the other drives pace and accountability. Plans will evolve, but you still need a benchmark. Without it, progress becomes subjective and drift sets in.

Crucially, these individuals must also be empowered to make decisions within clear boundaries. Without that, they become a relay point rather than a driver of progress. They also play a key role in protecting momentum, ensuring that internal resistance, competing agendas, or unnecessary debate do not slow the initiative down.

That pairing only works if the individual driving structure is also a strong communicator. They must create clarity across the organisation and establish simple, effective communication flows using existing tools.

Alongside communication, you need a practical mechanism to plan time and manage workload. The approach will depend on the problem you are tackling, but the principle remains the same: structure the work in a way that is visible, trackable, and adaptable.

For example:

• Delivering a feature → story mapping + Jira timelines

• Improving customer service → workstreams tracked at team and programme level

• Other initiatives → adapted tools like Monday.com, Asana, or equivalents

The tool itself is secondary. What matters is visibility: what is being done, by whom, by when, and how it connects to the outcome.

In practice:

• Use dedicated initiative channels for visibility

• Record key sessions so teams can catch up quickly

• Maintain regular stakeholder updates

• Capture progress, risks, decisions, and learnings in existing systems

Finally, maintain a single source of truth. Without it, teams drift.

The mistake organisations make is assuming capability alone is enough. Without structure, even the best experts slow down. With it, they accelerate everything.

3. Operators who deliver

These, alongside champions, are the doers. They turn intent into reality.

They must understand:

• the problem

• the initiative

• who is involved

• their role in it

  
  

Without this, execution fragments. With it, it aligns. They also work symbiotically with experts, bridging the gap between theory and delivery.

You need people with the right mindset: action oriented, comfortable with ambiguity, and accountable for outcomes. But mindset is not enough, focus is critical. If this is a priority, it must be treated as one. Operators cannot be split across multiple initiatives. This is where leadership trade offs become real: you either reallocate resources or bring in additional capacity.

As Head of Operations, your role is to eliminate friction. The biggest risk to momentum is context switching. Protect focus, and execution accelerates.

Operators should also be measured against short cycle outcomes, not just activity. Progress should be visible weekly, not just at the end.

At the same time, establish a clear way of working. Build on what exists, but avoid over engineering new processes. In many cases, the fastest way forward is not to redesign how the organisation works, but to simplify it.

Too much process is often the very thing slowing you down.

Instead, lean into lightweight approaches, Kaizen, lean agile, short feedback loops, iterative delivery. When operators are focused, aligned, and supported by simple structures, they become a force multiplier.

4. Clear ownership of budget

Speed without accountability creates waste. Someone must own the financial picture, ensuring resources are deployed effectively and transparently.

But budget is not just control, it is a signal of priority. Where funding flows, attention follows.

Allocating budget to an initiative tells the organisation what truly matters. It also forces clarity on trade offs: what you fund, what you pause, and what you stop.

Without this discipline, organisations fall into a familiar trap, spreading effort thinly, achieving little, and burning time and money.

Why this matters

When these elements are in place, organisations move differently.

Decisions happen faster. Barriers are removed earlier. Progress becomes visible.

More importantly, learning accelerates. If something does not work, you adjust quickly and try again, rather than spending months committing to a single path and realising too late it was the wrong one.

Without this structure, the opposite happens:

• initiatives drag on

• teams burn out

• budgets get consumed with little outcome

• organisations become highly efficient at going nowhere

The lesson is simple: agreement is not action. Organisations do not fail because they lack awareness. They fail because they lack the structure and the courage to act quickly enough. The difference is not knowledge. It is execution.

If you need a fractional expert to help your organisation tackle a problem, whether commercial, delivery, or tech focused, drop us a message at agilegoesape@gmail.com. If you think a colleague or friend would benefit, share this with them.