Step 01
Understand the intent
Clarify the strategic priorities and the outcomes the operating model must enable.
What We Do · 01
Strategy, governance, capabilities and decision-making aligned around how the organisation needs to work.
Business Problem
Most organisations do not lack ambition. They struggle because the way work is organised — who decides, which capabilities exist, how teams hand over, what gets measured — has drifted away from what the strategy now requires.
Restructures and new roles follow, yet the same friction returns. Decisions escalate because ownership is unclear, and critical capabilities are either duplicated or have no home at all.
How Akmalito Helps
Akmalito works with leadership teams to describe how the organisation needs to operate, then designs the structures that make it possible. The result is a practical picture people use to make decisions, not a document that sits on a shelf.
What the organisation must be able to do, which capabilities set it apart and where each one should sit.
Who decides what, at which level and in which forum — designed to speed decisions up, not add layers.
How strategy, processes, people, information and technology fit together in the future state.
A sequenced path from today’s model to the target, with owners, dependencies and early wins.
Our Approach
Four steps, each ending in a leadership decision, so direction stays with the people accountable for it.
Step 01
Clarify the strategic priorities and the outcomes the operating model must enable.
Step 02
Capabilities, decision flows, governance and pain points as they really work today.
Step 03
Options tested with leaders against real scenarios, not abstract principles.
Step 04
Roadmap, ownership and governance to move from design into daily operation.
Business Value
Accountability sits where the knowledge is, so fewer decisions stall or escalate.
A capability view shows where to invest, where to consolidate and what to stop.
Structures, governance and processes reinforce each other instead of pulling apart.
Expert Perspective
When a transformation stalls, the usual diagnosis is execution: more resources, better change management, a stronger project office. Sometimes that is right. Often it is not.
Many transformations are asked to deliver something the operating model was never designed to support. The programme builds new processes, systems and roles, but decisions still follow the old hierarchy, budgets still flow through the old structure and performance is still measured against the old targets. The new way of working is launched into an environment that quietly rejects it.
Decisions take too long. Project teams wait for approvals from forums that have neither the mandate nor the information to decide.
Ownership is contested. A new process crosses three departments, and each assumes another owns the outcome.
Adoption is weak. People are trained on the new way of working, but their incentives, reporting lines and priorities still reward the old one.
Adding more programme management to these problems usually adds meetings, not progress.
A transformation cannot outperform the operating model it runs inside.
Who owns the outcome, not just the project? Programmes end. Someone in the line organisation must own the result afterwards — with the authority to act on it.
Do decision rights match the new way of working? If the design assumes local decisions but every exception still goes to a central committee, the old model will win.
Are the required capabilities funded and located somewhere? A capability that belongs to everyone tends to belong to no one.
Does governance measure the new behaviour? If budgets, reviews and KPIs reflect the old model, people will rationally follow them.
If the answer to two or more of these is no, the programme is probably not the root cause.
The answer is rarely a large reorganisation. More often it is a small set of operating model decisions made early: clear ownership of end-to-end outcomes, decision rights adjusted for the new processes, and governance and measures aligned so the new way of working is also the easiest one to follow.
Treat the operating model as part of the transformation scope, not its background. It is less visible than a new system, but it usually decides whether the system is used as intended.
Discovery Call
Let’s understand what is getting in the way and whether Akmalito can help.