You need to be agile.
You are dynamic.
For the Enterprise in Permanent Motion
Digital Dynamism
Digital transformation has no endpoint. There is no level five, no completion date, no moment of arrival. Organisations keep chasing that moment.
It never comes.
Being dynamic is a disposition: the capacity to keep moving well.
Why now
AI is the proof, not the destination
AI has arrived, and organisations are scrambling to understand what it means for their customers, colleagues and business models. The ones that navigate it best will not necessarily have the best models or the biggest budgets. They will be the ones able to move.
AI is exposing weaknesses that already existed: waterfall governance over hybrid-agile delivery, transformation programmes with fictional completion dates, and consensus processes too slow for opportunities that change every few months.
AI is not the problem to solve. It is the current and most urgent test. Digital Dynamism predates AI and will outlast whatever comes next.
The outcome
Dynamism
Dynamism is not a methodology to implement or a practice to complete. It is the capacity to reconsider any decision when reality changes, without being held hostage by sunk cost, an entrenched vendor relationship or an established belief.
The four tenets create two conditions. For the organisation, freedom: the ability to act on what is true now rather than what was decided before. For its people, curiosity: the instinct to ask whether things have to remain as they are - because asking is safe, welcomed and acted on. Even "this is how we have always done it" stops being a wall and becomes an invitation. Mandates produce compliance. Curiosity produces change that sticks - because the person pulling the thread owns what they find.
Freedom without curiosity creates capability without energy. Curiosity without freedom creates frustration. Together they create motion.
Being dynamic gives you freedom from the past.
The tenets
Four tenets
Each tenet depends on the others. This is not a sequence or a methodology. It is a system drawn from my own observations and experience.
Without honest, shared visibility into where an organisation actually is - not where the last status report suggested, or where the roadmap would like it to be - every decision runs on gut or borrowed instinct. Neither produces consistent, directionally correct decisions. Context has to flow beyond the leadership layer to everyone expected to act.
Most organisations mistake strategy for context. A company strategy pitched at such high altitude that almost any initiative can claim alignment provides cover, not context. Functions then create internally coherent versions of reality that do not join up across the enterprise.
Context is a living, shared understanding of where the organisation actually is - maintained continuously, owned collectively and visible to everyone who needs it.
Always knowing where you are, with the clarity to make bold decisions.
Running blind, on gut, or on an instinct that does not fit your reality.
In practice
The watermelon project
A large technology programme runs for years. Status reports stay green - budget on track, schedule on track, requirements met - but the people who have to use it are unhappy. Technology operates in the context of milestones and specifications; the business in the context of commercial outcomes and user experience. The two never genuinely meet: green on the outside, red on the inside. A $30M, three-year investment is eventually replaced by a fifteen-month, $1.5M rebuild once the contexts are joined and the courage is found to change direction. The team built from that shared understanding is still operating and evolving six years later.
Door number three
Where context works, a technology leader and a business leader genuinely partner - not to manage a relationship, but to build and maintain a single view of reality neither could hold alone. The difference is rarely data or technology. It is a shared understanding of priorities: what matters most, what comes first, what the organisation is collectively willing to put last. Door number three - the option that serves the whole enterprise rather than any single function - gets considered, because the people who can see it are finally in the room.
Speed without commitment produces fast decisions that die in implementation. Commitment without speed produces decisions that arrive too late to matter.
Most organisations treat the two as a trade-off. Consultation, debate and bringing people along take time, so they either move quickly and leave the wrong people behind or build consensus so slowly that the window closes.
A dynamic organisation can produce commitment at speed because alignment begins before the decision meeting. Shared context, clear ownership, the right people in the room and psychological safety allow disagreement to happen quickly - and commitment to follow cleanly.
Decisions made quickly, with shared commitment that becomes momentum.
A good decision left unmade - or made too late, without engagement, on bad information.
In practice
The leader who never said yes
Some leaders frame indecision as diligence. Every proposal is met with questions rather than answers; every request for a decision produces a request for more information. The people around them adapt - learning to frame conversations not as "can we do this" but as "we are going to do this unless you tell us not to." The workaround works, but at a cost: extra cycles, unnecessary stress, and a slow erosion of confidence in the more junior people caught in the middle. They are not missing anything. Indecision is the issue. But indecision rarely announces itself as such.
The RFP that answered a dead question
A global organisation spends months travelling to collect requirements, months running an RFP, and months ensuring every stakeholder feels heard. The obvious choice - obvious from the beginning - is eventually selected, followed by more months of contract negotiation. By launch, the original goals have dissolved and the organisational energy is spent. The people closest to the need have not waited; local teams with budget autonomy have already hired agencies to fill the gap. The organisation pays twice. The process was designed to prevent a bad decision. It prevented any decision.
Change takes an emotional toll that cannot be managed away with a communications plan. The person who spent three years becoming an expert in the platform you are abandoning does not only have a skills gap to close. They have invested part of their identity and career path in it. The loss is legitimate.
Transparency runs in two directions, and both are difficult. Receiving a decision without its context leaves people unable to explain it to themselves or others. Being fully read into a situation and asked to deliver a decision to people who cannot be is its own particular burden. Both erode trust when handled poorly.
A dynamic organisation does not pretend these tensions do not exist. It acknowledges what is being lost, gives people room to process it, and treats the experience of those closest to the work as part of the shared context. Losing them emotionally is dangerous to progress, even when the decision itself is right.
People who feel included, heard and able to help because they understand the journey - and are willing to transform themselves with it.
Quiet quitting, passive resistance and lost institutional knowledge because people do not believe their experience matters.
In practice
Training around the loss
An organisation replaces a platform after years of investment. The experts who built their reputation around it are told the decision is rational and given training on the replacement. Their attachment is treated as a capability gap rather than a genuine loss. Resistance follows - not necessarily because the decision is wrong, but because something real disappeared and nobody was willing to say so.
People are not all motivated in the same way. Some need to hear why something will be better - the vision, the upside and the possibilities ahead (I am one of those). Others need to hear what they are being saved from - the risk, the problem, or the pain and frustration being removed. Leading in only one direction can leave half the team unmoved.
Most change programmes choose one mode and let it drive the story. The vision deck is usually all towards: the brighter future, the better place to be, the faster way to act. Half the room may be thinking, "But it works for me now. It is not broken." A dynamic organisation can describe the bright future and the cost of standing still in the same breath. The truth remains consistent; the language meets people where they are.
Feeling integral to the solution is itself motivating. When people understand why a decision was made, see how it connects to what matters to them and believe they have a role in what happens next, they stop being recipients of change and become active participants.
You can see it working when people become curious - seeking out more, learning on their own and running their own experiments. Motivated people do not wait to be brought along. Someone who is not curious is not necessarily resistant; the idea may not have spoken to them yet, or they may not feel empowered to explore it. That can be a message still looking for its audience.
Each person hearing the same truth, told in the language that moves them.
Half the team remaining unmoved because the story was never told for them.
In practice
One truth, two reasons to move
One person hears that a new process will create room for more meaningful work. Another hears that it will remove the repeated failures and late-night fixes they already hate. The context and the decision do not change; only the doorway does. Both can move without being manipulated, because both stories are true.
The two outcomes
Freedom and curiosity
The two outcomes interact simply. Freedom is what the organisation has; curiosity is what its people bring. The tenets produce both: Contextual feeds curiosity, Decisive proves it leads somewhere, Transparent makes it safe, and Motivational sparks it. You need both, and the failure modes of having only one look very different.
Change
The organisation can move and the people want to. The only quadrant where change sticks.
Failed transformation
All capability, no energy. The path is clear - and nobody engages.
Frustration and turnover
People see what is possible but cannot act on it. The best ones leave, or route around you.
No change
Comfortable stasis. No tension, no friction - and nobody minds until the market does.
The diagnostic question for any leader is simple: which quadrant are we in, and which axis is the constraint? The fix is different for each. A frustrated, curious organisation needs freedom. A free but passive one needs a spark.
A closing thought
Why did I write this down?
Because I have spent over 20 years watching companies strive for transformation and struggle with the same things. It is rarely for lack of effort or intent. We are simply not set up to be contextual, decisive, transparent and motivational consistently.
I have been on the receiving end of decisions I could not explain, decisions I strongly opposed but delivered anyway, and excellent ideas that never left the whiteboard. I have also worked in remarkable teams led by people who made reality visible, created genuine commitment and gave their teams reasons to run through walls. I have tried to carry those lessons with me.
I wrote this because these ideas have been swimming in my head as the pace of change accelerates. If articulating them helps someone else say, "I see that too," it was worth it. Most people have good intent; the opportunity is to line that intent up rather than leave it in conflict. These are ideas in motion. If anyone wants to chat about what they see, find hard, or would even challenge - I would love to hear from you.
You do not achieve Digital Dynamism. You are it.
Close
Dynamic comes from the Greek dynamis - power, force, capability. Not a process to follow. Not a methodology to implement. A quality that comes from within and generates motion.
I also struggle with the word agile. When you have to explain "little a" or "big A", it has already lost someone. I am not trying to make fetch happen, but dynamic fits the idea better for me.
Agile is something you are told to be. Dynamic is something you become.