The Mirage of the Well-Written

 Beautifully crafted messages that lack depth, consistency, a binding theme, or contextual relevance are becoming easier to spot — and harder to ignore. They land on our desks with increasing frequency. Polished. Fluent. Empty.

It made me pause. What is behind this phenomenon?

The answer, I suspect, lies not in the tool being used but in a quiet abdication happening inside organisations — one that leaders are yet to name, let alone address. 

Effectiveness, in any meaningful sense, is the product of several things done right together. It demands clarity of purpose before a single word is written. It demands honest engagement with context — the kind that cannot be shortcut. It demands the discomfort of genuine contemplation, the discipline of choosing, and the courage to close. It demands collaboration that is real, not performative. And at the end, when the tide has settled, it demands a reckoning with conscience — a quiet, private audit of whether what was done was right, not just effective.

Communication sits within this chain. It gives form to thought. When done well, it is a multiplier. But it is not the chain itself. 

Here is what AI has changed: it has made the last step — the giving of form — extraordinarily easy. So easy that a generation of professionals is beginning to mistake the output of that step for the output of the entire process. A well-formatted document feels like a completed thought. A fluent summary feels like a resolved problem. The casual reader is convinced. And sometimes, so is the author.

This is the mirage of the well-written.

The danger is not that people are using AI. The danger is that the time and cognitive effort AI frees up is not being redirected into the harder, less visible work that precedes communication. It is simply being reclaimed as comfort. The drudgery tax — the friction of real thinking, of sitting with a problem long enough to understand it, of pressure-testing assumptions, of choosing when there is no clean answer — is being quietly avoided. And because the output still looks credible, no alarm goes off.

For leaders and managers, this is not a technology problem to be managed. It is a standards problem to be led.

Our teams are watching what we reward. If fluency is being mistaken for rigour, if presentation is substituting for preparation, if the polished deck is closing conversations that should still be open — they will optimise accordingly. They are rational. They will take the path that appears to work.

The cognitive habits being formed now — or lost now — will define the quality of judgment our organisations can call upon for the next decade. The capacity to think under pressure, to hold contradictions long enough to resolve them honestly, to do the unglamorous work of genuine analysis — these are not soft skills. They are the load-bearing structures of every good decision ever made.

AI will not blunt those capacities. Allowing them to go unexercised will.

The question worth sitting with is not how much AI our teams are using. It is whether the time being saved is being reinvested in the work that cannot be delegated — or whether it is simply disappearing into the comfort of a document that reads well and means less than it seems.

That distinction is worth our attention. It may be the most important leadership judgment of this moment. 

Beyond Communication

The seven dimensions of genuine effectiveness 

01 — Clarity

Clarity of Purpose

Before a single word is written or a meeting called, there is the question that most professionals skip: what, precisely, am I trying to achieve? Not a broad direction. Not a category of intent. A specific, testable outcome. Clarity is the first discipline — and the one most easily bypassed when tools are available that can generate plausible-looking output from vague input. AI will fill the gap where clarity should be. The output will look coherent. It will not be.

 

02 — Context

Context

Every problem sits inside a situation — with history, stakeholders, constraints, and competing interests that shape what is possible and what is wise. Context cannot be searched for and appended. It is built through immersion, through questions that feel inefficient, through paying attention to what is not said. A document produced without genuine contextual understanding will be technically fluent and situationally blind. Discerning readers will notice.

 

03 — Contemplation

Contemplation and Choosing

Between understanding a problem and acting on it lies the most uncomfortable territory: the space where one must hold competing options, resist premature resolution, and choose. System 1 thinking — fast, pattern-matching, satisficing — is always available and always cheaper. The discipline of genuine deliberation, of sitting with a decision long enough to understand its second-order consequences, is not. AI can model options. It cannot bear the weight of choosing on your behalf — and if you ask it to, you should not be surprised when the choice reflects no one's judgment.

 

04 — Construct & Communicate

Construct and Communicate

This is where AI performs extraordinarily well — and where its contribution must be understood precisely. Communication gives form to thought. A well-constructed argument, clearly articulated, is a genuine asset. But form amplifies what is already there. It does not create substance from its absence. When AI is used to construct and communicate after the prior three dimensions have been done with rigour, the result is powerful. When it substitutes for them, the result is the mirage: impressive in appearance, hollow under examination.

 

05 — Collaboration

Collaboration

Genuine collaboration — the kind that surfaces assumptions, challenges direction, and builds shared ownership — is one of the most cognitively demanding activities in organisational life. It is also one of the easiest to simulate. A meeting can be held without thinking together. Feedback can be solicited without being absorbed. Consensus can be declared without being earned. The question for leaders is not whether their teams are collaborating, but whether the collaboration is real — whether it is changing the thinking, not just the documentation.

 

06 — Closure

Closure and Completion

Effectiveness requires the discipline of ending — of making the final call, closing the loop, and moving forward with commitment. This is harder than it sounds in environments where optionality is valued and accountability is diffuse. The temptation is to let a well-written summary substitute for a decision. It does not. Closure is an act of will, not of writing.

 

07 — Conscience

Conscience

The last dimension is the quietest — and in many ways the most important. It is the private reckoning that follows when the problem is solved and the tide has passed: did I act rightly? Were my values intact? Was anyone diminished by how I operated? Conscience does not announce itself during the work. It surfaces in reflection. Leaders who do not create the conditions for this reflection — in themselves and in their teams — will find that effectiveness, over time, becomes something they are no longer proud of.

 

A quick self check: For each dimension, mark your honest rating on two scales — how good you are at this (Capability), and how satisfied you are with the time you invest here relative to what you know it deserves (Time Investment). The gap between the two is where your work lies.

A Call to Leaders and Their Teams

The seven dimensions above are not a framework to be presented in a deck. They are a map of where effectiveness actually lives — and where, under the gravitational pull of available tools, it is quietly being abandoned.

The obligation of leadership in this moment is not to restrict what tools teams use. It is to hold the standard of what good work requires — and to ensure that the next generation understands the difference between a document that is well written and a problem that is well solved.

The cognitive sharpness required for the first six dimensions — clarity, context, contemplation, genuine collaboration, decisive closure, and an honest conscience — is not a given. It is a muscle. Muscles that are not used atrophy with time,  That is law of nature! 

Reflection for self and team members:

The dimension I have been most avoiding: 

 

The time AI has saved me — where has it actually gone? 

 

One concrete change I commit to: 

 

Date of next honest review: 

 

 

Effectiveness is not the output. It is the integrity of the process that produced it.

The Governance Slide Deserves Better From customary slide to living practice

The governance slide is a customary part of every transformation program charter. It appears near the end of the presentation — mostly to be received rather than interrogated. 

It passes without contest, or at most some suggestions on names to be included, seldom who to exclude, in the governance structure.   It does this partly through familiarity — three boxes, three frequencies, multiple arrows pointing upward, a structure that resembles what everyone has seen before — and partly through the comfort of its deliverables. 

A governance structure, once approved, demands tangible evidence of its own existence: calendar invites to meetings that include everyone who carries influence over the program, whether or not they hold direct accountability for it; minutes that record discussions and file them; status reports that confirm the forum met and the slides were presented. These artefacts are not nothing. They create a paper trail. They satisfy assurance requirements. They give the impression that the program is being watched.

The question the slide does not invite — and that the room has rarely developed the habit of asking — is whether any of this watching actually governs anything.

What Governance Actually Is

Governance is not a structure to be designed and filed. It is a set of acts — best described in verbs — that either happen or do not. 

Every governance tier shares three universal acts regardless of its level. It must decide — not note, not discuss, not explore, but reach a conclusion with a named owner and a committed date. At every meeting, it must account for what it decided at the last. And it must communicate conclusions precisely enough that they survive interpretation by people who were not in the room. When a forum notes rather than decides, the verb has changed. So has the nature of what is happening. The verb is the test. 

Besides, the verbs to be part of three tiers include  

Steering Committee —  Sensing · Legitimising · Protecting · Re-calibrating.

Senses shifts in the external environment before they reach the program team. Legitimises the program's mandate in forums it cannot access. Protects the conditions the program needs — shielding it from shifting organisational priorities. And re-calibrates: this is the only tier with the standing and perspective to ask whether the governance design itself remains fit as the program evolves. 

Program Review —  Surfacing · Prioritising · Redirecting.

Surfaces uncomfortable variance early enough for corrective action to still matter — not after it has been managed locally for weeks and arrived upward already softened. Prioritises when demands exceed capacity. Redirects — issues corrective action, resolves the impasses the Core Team could not, and re-establishes what the next period must deliver.

Core Team —  Executing · Flagging · Integrating.

Executes against the integrated plan. Flags problems before local workarounds begin to disguise systemic risk. Its meeting has failed when it becomes a status report. It is working when it is a short, honest, forward-looking account of what is committed and what stands in the way.

The Assumptions Behind the Slide — and What Needs Contesting?

Governance does not fail because the design is wrong. It fails because the design mistakes a simplification for a reality — and no one takes responsibility for managing the distance between them. 

There are five assumptions about the operating context and human that need reality test:

Assumption 1 — Issues arrive pre-classified and can be cleanly routed to the appropriate tier.

Reality:  They cannot. Issues exist on a continuum. A decision about delaying a workstream by two weeks is simultaneously operational in execution terms, tactical in resource terms, and strategic in stakeholder-signalling terms. What gets decided where, needs to be guarded to avoid extremes in terms of all decisions seen important enough to rise to the top or left to core team to guess.   

Assumption 2 — Each tier's information needs are fully met by what rises from the tier below.

Reality:  This is a structural conflict of interest. The people producing the information are also the people being evaluated by it. When independent information accountability is absent, governance is not receiving filtered information — it is governing with structural blind spots that no amount of honest reporting from below can fill. Each tier has independent information obligations of its own to add to what comes from below. 

Assumption 3 — A scheduled meeting cadence is an adequate decision mechanism.

Reality:  It is not. Critical issues arise between sessions. When governance has no out-of-cycle mechanism, they are either resolved informally — by whoever is available, without the right authority — or deferred until delay becomes damage. This is an architectural gap, not a behavioural one. Every governance design needs a named escalation mechanism: a specific trigger, a named person, a defined timeline. The structure existed. The escalation discipline did not.

Assumption 4 — Consequential conversations happen inside governance forums.

Reality:  They happen before them. Positions are pre-negotiated in bilaterals. Coalitions form across tiers between meetings. This is not a governance failure — it is organisational life. The question is whether the formal structure retains enough clarity in its decision rights to remain the legitimate site of consequential decisions, or gradually becomes the place where predetermined conclusions are given procedural cover. Governance that has lost that legitimacy is still meeting. It has stopped mattering.

Assumption 5 — All participants are equally committed to the structure, regardless of seniority, style, or culture.

Reality:  Culture, hierarchy, and organisational history do not disappear because a charter has been signed. The most important variable in any governance system is the behaviour of the most senior person in the room. A governance structure that does not account for the specific leadership style and cultural context of its most senior participants — designing around them, not despite them — is a structure that will gradually become whatever those leaders are most comfortable with.

When the Mechanism Needs Reviewing?

Governance is designed at inception and then treated as settled infrastructure. It is not. There are several signals to infer that governance is failing — and when those signals appear, they call for review without waiting for permission or a convenient moment on the calendar.

The signals are observable and specific. 

• Key participants begin missing meetings or sending proxies without explanation — not once, but as a pattern. 
• Decisions made in one forum are revisited in the next without new information, suggesting that the first forum lacked the authority or the confidence to make them stick. 
• The same category of issue appears on the agenda at all three tiers simultaneously, which means it has not found its appropriate level and the tiers have not been able to route it. 
• Commitments made in governance forums are quietly skipped and no one surfaces the breach. 
• Escalations arrive late — after the decision window has passed — because the escalation mechanism has no teeth or the culture has learned not to use it. 
• Participants arrive without preparation, treating attendance as presence rather than engagement. 
• The minutes record discussion rather than decisions. The information pack looks the same at every tier, compressed rather than differentiated.

The astute architect does not explain them away — they name them, and they convene the people with the authority to redesign what is no longer working.

There is a second, distinct trigger that is almost universally overlooked. When the chair changes at any of the three tiers — when a new Steering Committee sponsor is appointed, when the program director is replaced, when the Core Team lead moves on — the governance mechanism should be explicitly re-endorsed, not passively continued. 

A governance structure designed around one chair's style, instincts, and relationships does not transfer automatically to their successor. The incoming chair brings a different risk appetite, a different relationship with the tiers above and below, and a different understanding of what the forum is for. If the mechanism is not reviewed and re-endorsed with their genuine understanding and commitment — not merely their presence in the next meeting — it will operate on assumptions that no longer hold, governed by a design built for a person who is no longer there.

Leadership change at any tier is a governance reset moment. Treating it as one is the difference between a governance structure that adapts and one that drifts.

When next time the slide appears? 

The governance slide deserves to be designed, not just drawn. Designing it means answering, before approval, the questions the room has learned not to ask: What specific class of decisions belongs to each tier — not as a principle but as a written list? What is the out-of-cycle escalation mechanism when an issue cannot wait? What independent information obligation does each tier carry beyond what the tier below provides? And who is responsible for calling a review of the governance design itself when it is no longer working?

It’s worth spending time on this slide, even if it appears late in the show!

 

This article is part of the PEACE Framework Reflection Series — a set of independent pieces on transformation leadership, each taking one theme and allowing deeper reflection. 

Why-Sharing: From Unconscious Habit to Conscious Mastery!

This piece is an invitation to examine your own relationship with WHY — honestly, specifically, and without the comfort of assuming your current default is right. 

There is a question most leaders never ask themselves — not because it is difficult, but because it does not occur to them that the question exists. The question is not whether to share WHY. Most leaders have a settled view on that, shaped by experience and reinforced by habit. The question is: what is actually driving my choice in this moment? Is it the genuine demand of the situation? Or is it personal comfort, unconscious habit, or the proximity of the person across the table?

Why-sharing is not a binary. It is a spectrum that every leader navigates continuously — often without recognising that they are navigating it, and rarely with the conscious precision the situation deserves. The leader who develops deliberate mastery of that spectrum — who can share WHY fully when the situation demands it, manage it carefully when legitimate constraints apply, and calibrate its depth and specificity to make the WHAT feel inevitable rather than arbitrary — is more effective, more scalable, and more trusted than either the chronic withholder or the indiscriminate sharer.

"The question is not whether to share WHY. It is: what is actually driving my choice in this moment — the demand of the situation, or the comfort of my habit?"

 

THE DEMAND FOR WHY IS NOT CONSTANT — IT IS PROPORTIONAL TO DISCOMFORT

The most important thing to understand about Why-sharing is that the organisation's need for it is not fixed. It varies — dramatically — with the nature of the WHAT that follows.

When the WHAT is comfortable — familiar, safe, aligned with existing interests and identity — the demand for WHY is low. People accept the instruction and move. When the WHAT is uncomfortable — threatening to existing roles, demanding sacrifice, requiring people to abandon what has worked before — the demand for WHY rises sharply and immediately. In these moments, WHY is not information. It is the consent mechanism. It is the psychological permission slip the organisation needs to move through difficulty. Without it, people do not simply comply reluctantly — they resist actively, invoke politics, or comply in form while sabotaging in substance.

The implication for the leader is direct: the more uncomfortable the WHAT you are asking, the more essential the WHY becomes. The leader who systematically under-provides WHY at precisely the moments it is most needed — because those moments are also the most politically charged and the most personally exposing — is withdrawing the consent mechanism at the point of maximum demand. That is not efficiency. It is the primary cause of transformation failure.

This also explains why leaders who rarely face resistance rarely develop a Why-sharing capability. If the WHAT is never uncomfortable enough to trigger demand, the leader never learns that WHY is a capability they need — until the moment they ask something genuinely difficult, and find they have no practice in providing the consent that makes it possible.

WHY MUST BE SPECIFIC ENOUGH TO SELECT THE WHAT — NOT JUST JUSTIFY IT

There is a second discipline in Why-sharing that is less commonly understood: the WHY must be specific enough to make the WHAT feel inevitable, not just defensible. A WHY that is too broad opens a field of competing WHATs, each of which can legitimately claim to serve the same purpose — and the choice between them then looks arbitrary, or worse, political.

Consider a leader who shares: we need to reduce costs significantly to avoid bankruptcy. That WHY is honest, urgent and real. But it supports manpower reduction, cheaper raw material sourcing, asset divestiture, product rationalisation, capex deferral and a dozen other WHATs simultaneously. The organisation that receives this WHY without further specification will either debate endlessly which WHAT to implement, or accept the leader's chosen WHAT while privately suspecting it was decided before the WHY was articulated.

The WHY needs two levels. The first is the purpose — why action is needed at all. The second is the constraint set — why this WHAT and not another. That second level is where the WHAT becomes inevitable rather than whimsical. Without it, the WHY justifies without selecting — and a WHY that justifies without selecting invites the organisation to substitute its own preferred WHAT.

LEGITIMATE CONSTRAINTS — AND THE DISCIPLINE TO DISTINGUISH THEM FROM AVOIDANCE

Not all withholding of WHY is avoidance. Two constraints are genuine and worth naming precisely — because naming them honestly is itself a form of integrity.

The first is competitive sensitivity. When the specific WHY reveals strategic intent that adversaries can read and respond to, full transparency becomes self-defeating. The discipline is in finding the level of WHY that aligns the internal organisation without telegraphing the external play. A leader can be explicit about the constraint: I cannot share the full reasoning now because doing so would compromise our position — but here is what I can tell you, and here is when I will be able to say more. That transparency about the constraint is itself Why-sharing.

The second is temporal validity. When the WHY has a short shelf life — tied to a transitional moment, a temporary condition — over-explaining it creates a different problem. People who have deeply absorbed a WHY that is about to change are harder to reorient than people who held it with appropriate lightness.

The discipline the leader must develop is in distinguishing these genuine constraints from the more common substitute: the rationalisation of personal discomfort as strategic necessity. Recognising that distinction in oneself, honestly and without self-deception, is the beginning of genuine mastery.

INTEGRITY IN WHY-SHARING — HONEST IN WHAT IS SHARED, CONSCIOUS IN WHAT IS NOT

Integrity in Why-sharing does not mean sharing everything always. It means two things held simultaneously: being honest in whatever is shared — the content is always authentic, never fabricated, never post-hoc rationalisation dressed as genuine reasoning — and being conscious in what to share, driven by the demands of the situation and not by the proximity of the listener.

That second element is the one most leaders violate without recognising it. The natural human tendency is to share more with those who are close — the inner circle, the trusted lieutenants. But the decision of what to share should not be made on those grounds. A junior employee whose role is directly disrupted by an uncomfortable WHAT has as great a claim on the WHY as the senior leader in the room. The WHY shared to the inner circle but withheld from the front line is not strategic — it is selective. And selective sharing, when it follows the contours of personal relationship rather than situational demand, is the precise behaviour that creates the two-tier organisation where politics lives most comfortably.

"Honest in whatever is shared. Conscious in what is not. The decision of what to share must follow the demand of the situation — not the proximity of the listener."

 

THE NATURE OF THE LED — MATURITY, VOLUME AND EXPANSE

The characteristics of those being led influence the execution strategy of Why-sharing — not the structural decision of whether to share, but how. Three dimensions matter here.

The first is maturity. The seniority, experience and capacity of the audience to absorb and respond to reasoning shapes language, tone, depth of explanation, choice of illustration and number of repetitions required. The same WHY, shared with a seasoned leadership team and with a frontline workforce, should sound different. The reasoning is the same. The translation is not.

The second is volume — the number of people who need to receive the WHY to make the WHAT move. As the number grows, the leader's direct Why-sharing capacity becomes the bottleneck. Platform selection, cascade design and repetition rhythm all become critical — because the WHY degrades with every layer it passes through, filtered by each manager's own comfort and conviction.

The third is expanse — the geographic, functional and cultural spread of those being led. An organisation that spans multiple geographies and cultures has no shared experiential foundation to carry the WHY implicitly. It must be stated explicitly, repeatedly, and across every boundary the organisation has crossed. The leader who has grown their organisation inorganically faces the most urgent Why-sharing demand: each acquired entity arrives with its own inherited WHY, and only an explicitly shared new one can integrate them.

WHAT CONSCIOUS MASTERY LOOKS LIKE

The leader who has developed conscious, flexible, integrous command of Why-sharing does not have a single default. They have a repertoire. They share WHY fully and specifically when the WHAT is uncomfortable and no legitimate constraint applies. They share directional WHY when competitive sensitivity constrains the specifics — and they name that constraint honestly. They revisit and update the WHY when its temporal validity has passed — not waiting to be asked, but offering the update as a signal of respect for the people who acted on the original reasoning. And they are consistent in what drives the decision: the situation, always. Not the audience's closeness to them.

The organisation inherits the leader's epistemology. The Why-sharing culture you observe in any organisation is the leader's personal conviction about what works — made institutional. Which means the most consequential development a leader can undertake is not a communication skill. It is the willingness to examine, honestly and specifically, what is actually driving their choices on the WHY spectrum — and to develop the range that the situations they lead require.

 

Why-sharing is not the most efficient approach in every context. But efficiency is a local optimum. WHY is scalable. The WHAT degrades at distance. The WHY compounds — absorbed, extended, applied to situations the leader never anticipated. WHY is resilient. When the WHAT changes, the organisation aligned on WHY can reorient. The one aligned only on WHAT cannot. The leader who builds on WHAT builds something fast within its current limits. The leader who builds on WHY — consciously, honestly, with the specificity that makes the WHAT inevitable — builds something that grows beyond them.