Where is your transformation actually stuck?
A confidential diagnostic for boards and senior leaders. Answer a handful of honest questions about how your organisation runs today, and read the pattern underneath the problem, the one most transformations get wrong before a platform is ever chosen.
Six to eight questions, two quiet minutes. Nothing is submitted, and nothing leaves your browser, unless you later choose to ask for the full reading.
Answer for the organisation as it is today, not as you intend it to be.
Which of these is closest to your organisation right now?
Read the pattern underneath
If this came back Structural, it is worth an hour with someone who has seen the pattern before. Leave your email and the owner will send you a longer, more personal reading of what you have here, along with a time to talk. No list, no sequence, no follow-up machine.
If something is still nagging that these questions did not reach, a short, confidential conversation usually finds it faster than another form. No list, no sequence.
Start a conversation →The Stalled Moderniser
You have paid for change many times over, and little of it has become the way you actually work.
You have run the pilots, bought the tools, and held the workshops, and the organisation still works much the way it always did. Each effort lands inside the team that started it and stops at that edge. The distance between what you have paid for and what is genuinely in daily use keeps widening.
The Strategy–Systems Gap
The plan is sound, and the machine underneath it was built for a smaller, slower company.
The ambition set at the top has moved ahead of what the business can currently carry. The strategy assumes an operating platform you do not yet have, and the strain shows up as slipped timelines and quiet workarounds. Everyone still believes in the plan, and it keeps arriving late.
The Over-Extended Leadership
The company moves faster than its decisions can, and the same few people have become the bottleneck.
The business has grown faster than its decision-making. Choices of every size collect at the top, the senior team is stretched across all of them, and the group that used to be your advantage has become the place things wait. The rhythm that fit a smaller company is still the one you run.
The Fragmented Estate
You are running a business you cannot see in one piece.
Your data, tools and processes have grown up in separate places, and no one holds the whole picture. Every serious question has to be assembled by hand, and by the time it is, people trust the answer less than the work it took. Leadership is deciding on a view of the business that stays slightly out of focus.
The Silent Attrition
The people you can least afford to lose are the quietest ones, and some have already started to go.
The people you most need are going quiet, and some are already leaving, taking what they know with them. It follows a stretch of change that was handled as logistics. The signs were readable well before they reached the numbers.
The Compliance & Trust Exposure
Nothing has broken loudly yet, and that is the only reason this has stayed off your agenda.
Security, data, HR and ethics are being handled one incident at a time. Nothing has failed loudly, so none of it has reached the agenda. For a name like yours the exposure shows up as reputation first, and reputation is slow and costly to rebuild.
The Decision Fog
Every view of the business looks right on its own, and the decisions still keep coming out wrong.
You cannot get a single clear read of the business, because the strategy makes sense in its own view and the operation makes sense in its own view, while decisions that look right in one of them keep quietly failing in the other, and leadership ends up holding two pictures of the same company that never quite become one. This is the condition Jigen takes its name from.
Does strategy set at the top routinely lose shape by the time it reaches the people who execute it?
Strategy is set clearly enough at the top and rarely survives the journey down to the people who actually carry it out, so that by the time direction reaches the floor it has passed through enough hands to be reinterpreted, and what gets executed and what was intended are no longer quite describing the same thing. The intent was sound the whole way along and the transmission is where it was lost, which is why the answer usually lies in shortening and holding to account the path between a decision and the action it is meant to produce.
Is your most important current change effort owned by a committee rather than one accountable person?
The change that matters most has no single owner, its responsibility spread across a committee in a way that looks like consensus and works in practice as diffusion, since when everyone owns a thing nobody in particular is answerable for it quietly stalling. Initiatives held this way tend to lose their momentum at exactly the point where they most need one empowered person who is able to force a decision and carry the consequences of it.
Do routine decisions wait on one or two senior people before anything can move?
Decisions of almost every size end up queuing behind one or two people at the top, so that what once felt like careful control while the company was small has gradually become the main constraint on how quickly it can now act. The cost of this runs deeper than speed alone, because senior time is being spent on calls that should never have reached it while the decisions that genuinely do need that judgement are left waiting in the very same line.
Are your transformation efforts reported mostly as activity completed rather than outcomes changed?
Progress is reported mostly as activity, the workshops held, the systems rolled out, the milestones passed, none of which is wrong in itself and none of which actually confirms that anything has changed for the business underneath it. When a programme cannot point to the specific outcome it has moved, that is usually a sign it has not yet moved one, however much has genuinely been done in its name.
Has your strategy set ambitions your current systems and processes were never built to carry?
The ambition set at board level quietly assumes an operating platform the company does not yet have, so that a strategy which is perfectly sound in itself is being asked to run on foundations built for a smaller and slower business, and the strain of that shows up as slipped timelines and a steadily growing set of quiet exceptions. A plan that cannot survive contact with its own infrastructure is still only a statement of intent, and turning it into a route the business can follow means closing the distance between the two.
Does growth tend to arrive as pressure your organisation absorbs rather than a shape it planned for?
Growth tends to arrive as something the organisation absorbs rather than something it has planned a shape for, so that each new market or product or acquisition is met by the same structures stretched a little further, until that state of being permanently stretched has quietly become the normal operating condition. Growth taken on this way eventually costs more to hold together than it ever returned, and the strain of it rarely announces itself until it is already well established.
Do new tools reach a pilot team and then stall before the whole organisation adopts them?
New tools reach a pilot team and then stop there, leaving the organisation to run two ways of working in parallel, and the older and more familiar one almost always wins out in the end. A pilot that is never actually made the default tends to settle in as a permanent exception rather than a step forward, one that quietly teaches everyone the change was optional all along, while the company carries on much as it did before.
Is it hard to get one trusted view of the business without a reconciliation exercise?
There is no single trusted view of the business, since the numbers live across different systems and teams and regions, and any real question sets off a reconciliation exercise before it can even be answered. Leadership ends up making its decisions on a picture it can only partly see, and spends more of its energy agreeing on what the number actually is than on what ought to be done about it.
Do critical processes depend on spreadsheets or manual steps only a few people understand?
Critical processes are running on manual workarounds, the spreadsheet that only one person really maintains, the hand-off that happens largely by memory, the step that exists nowhere except in somebody's daily routine, and the whole arrangement holds up perfectly well right until that person happens to be away. It also hides the real cost of systems that were never properly connected, since the resilience of the business is quietly resting on individual effort that could walk out of the door on any given morning.
Is security and data protection addressed mainly in response to incidents rather than by design?
Security and data protection tend to be dealt with only once something forces the issue, rather than being built in from the start, and because nothing has yet failed loudly the whole area stays comfortably off the agenda. For an established organisation the exposure reaches reputation well before it reaches anything technical, and the moment it finally becomes visible to everyone is the most expensive possible moment to be starting the work.
Have you bought more software capability than the organisation actually uses?
The organisation has bought more capability than it currently uses, with licences and platforms accumulating faster than the working habits that would make them worth owning, so that the gap between what has been paid for and what is genuinely in daily use keeps steadily widening. The tools themselves are rarely the issue here, since adoption was quietly assumed to follow the purchase rather than being actively led, and it seldom manages to on its own.
Are there core systems the organisation depends on but is afraid to change?
Core systems the business depends on have quietly become systems that no one is any longer willing to touch, because they work well enough that changing them feels riskier than leaving them exactly as they are, and so they end up setting the ceiling on what the rest of the company is able to do. Left alone for long enough the underlying risk does not fade away, it simply compounds out of sight and eventually chooses its own moment to surface.
Have you lost, or do you sense you are losing, the people you can least afford to lose?
The people you can least afford to lose are usually the first to sense that something has started to drift and the quietest about acting on it, so that some of them leave outright while others stay and withdraw in a way that is harder to see and every bit as costly. By the time any of this shows up in the attrition figures, the decision to go was generally taken some time earlier, in conditions that were perfectly visible to anyone who happened to be reading them.
Is change usually announced to your people rather than built with them?
Change tends to be announced to the people it lands on rather than built together with them, and handled as a logistics exercise in that way it saves a little time at the outset and then costs it back many times over in resistance, quiet non-adoption, and goodwill that is slow to return. People will generally get behind what they had some hand in shaping, and they find quiet ways to route around whatever was simply done to them.
Would the departure of a few individuals take critical know-how out the door with them?
Critical knowledge lives in a handful of individuals rather than in the organisation itself, an arrangement that stays perfectly efficient right up until one of them leaves, at which point real capability walks out of the door and cannot simply be rehired to replace it. Know-how that has never been made institutional is a dependency the business has been carrying all along without ever having properly priced it.
Are HR, conduct, and ethical questions handled case by case rather than by a clear standard?
Matters of HR, conduct, and ethics are handled case by case as they happen to arise, without a clear standard that people can see in advance and rely on, and while that reactive approach looks pragmatic in the moment it reads, over any length of time, as inconsistency, which is corrosive to trust in precisely the situations where trust is being tested. A standard that is set out calmly, well before it is actually needed, is what ends up protecting everyone once things are no longer calm.
Has your leadership team outgrown the rhythm of meetings and decisions it still runs on?
The leadership team is still running on the rhythm it settled into when the company was a good deal smaller, so that the meetings, the decision forums, and the reporting lines that once fitted it neatly now leak decisions and blur who is accountable for what. The team itself is generally very capable, and what has quietly failed to keep pace is the operating rhythm around it, which was never redesigned to match the size and shape of the company they are now actually leading.
Is morale treated as something to spend on the way to a target rather than a condition to protect?
Morale is treated as a variable to be spent on the way to a target rather than a condition to be protected on the way there, and it tends to hold up for a while and then give way, at which point the recovery turns out to be a good deal slower and more expensive than whatever the pressure originally seemed to save. A business is always more than the numbers on its dashboard, and the dimension that never appears there is often the very one that quietly decides whether the plan survives contact with the people meant to deliver it.
What surfaced here is real and still manageable. A good team can hold this, as long as it is named now and not left to quietly settle.
This is material. It is already shaping how the business runs week to week, and it tends to set harder the longer it stands.
This reading is structural. Problems this deep stay where they are until someone moves them, and they are usually what sits under a good strategy that keeps underdelivering.
Very little surfaced here, and that is worth noting in itself. On the answers you gave there is no structural pattern showing from where you sit today, which is either reassuring or a sign that the thing troubling you lives somewhere these questions did not reach.
Underneath that, a second pattern is close enough to name.
You answered nothing that left your browser. This reading was put together here, for you, and we kept none of it.