Category Archives: Management

The Most Dangerous Status Report Is the One Everyone Is Comfortable With

Posted on by

 

The governance is running. The reports are flowing. The steering committee met on time, every question got a confident answer, and the pack looked clean.

And the programme is in more trouble than anyone in that room is prepared to say.

This is not an unusual situation. It is not a sign of dysfunction or dishonesty. It is, in my experience, the most common information environment in large-scale programme delivery. The data supports that reading. Research by Milliken, Morrison and Hewlin, published in the Journal of Management Studies, found that 85% of employees have withheld important information from their manager because they feared the consequences of speaking up. The fear is not of formal punishment. It is relational: the fear of being seen negatively, of damaging a relationship, of being labelled someone who creates problems rather than solves them.

This is not a minority behaviour. It is the default.

The question is not whether a filter exists on your programme. The question is how thick it has become, and whether you would know.

 

Nobody Decides to Build the Filter

The pattern I have watched play out more times than I can count begins with a capable, experienced leader who genuinely means what they say. They have told the team, in kick-offs and town halls and one-to-ones, that they want to hear the bad news early. They are not performing openness. They believe it.

But then someone raises a concern in a steering committee and the leader’s body language shifts before the words are out. A risk gets flagged and the first question is why it was not caught earlier rather than what needs to happen now. A project manager delivers a difficult update and spends the following week under a level of scrutiny that has nothing to do with fixing the problem.

Nobody announces a new policy. Nobody says: do not bring me bad news.

But the room notices. Every single time.

And slowly, without anyone deciding to do it, the filter gets built. The team learns which concerns land well and which ones create friction. They learn how to frame things to reduce the emotional temperature in the room. They learn the difference between the truth and the version of the truth that keeps the meeting moving and their professional standing intact.

The updates keep arriving. The reports keep flowing. The governance keeps running.

But the signal has been stripped out. What remains is noise dressed up as information.

 

You Do Not Build This Through Negligence

This is the part that most leadership development will not tell you directly. You do not build a closed information environment through negligence. You build it through a series of entirely human, entirely understandable responses to difficult moments.

A flash of impatience when a problem arrived at the wrong time. A habit of moving to solutions before the problem is fully understood. A preference, however subtle, for the reassuring narrative over the complicated one.

These are not character flaws. They are instincts under pressure.

But at leadership level they are not private. The CIPD’s 2024 evidence review on psychological safety identifies leader and manager behaviour as the most critical driver of whether people feel safe to speak up, and specifically notes that what matters is not what leaders say about wanting honesty, but what they demonstrate through their actions when honesty arrives. The research is unambiguous: psychological safety is fragile. A single punitive response to good-faith feedback can damage trust that took months to build.

Every reaction is observed, interpreted, and factored into how safe it feels to tell you the truth next time. The leader who says they want honesty but visibly struggles to receive it is not running an open culture. They are running an organisation that has learned to give them what they can handle rather than what they need.

The most dangerous status report is not the one with red items on it.

It is the one everyone is comfortable with.

 

Four Practical Moves

The filter is not permanent. It is a learned behaviour, and learned behaviours can be unlearned. But reversing it requires something more specific than an open-door policy.

Stop asking questions that invite the managed answer. “How are things going?” will get you the curated version every time. Try instead: what is the one thing you would not put in a status report but think I should know? If this programme were going to fail, what would the early sign look like? What are we not talking about that we probably should be? Those questions signal that you are interested in the reality, not the performance of it.

Go to where the real work is happening. Not to inspect. To listen. The people closest to delivery carry an understanding of programme health that rarely makes it into formal reporting. A single honest conversation with a delivery lead or a technical team that has been carrying a quiet problem for weeks will tell you more than three months of steering committee updates.

Create a visible moment where surfacing difficulty is rewarded rather than merely tolerated. When someone raises something uncomfortable and your public response is genuine appreciation followed by a real conversation about what to do next, the entire room recalibrates what is safe to say. One moment like that shifts the culture more than any open-door policy ever will. The inverse is equally true: one moment where the messenger suffers sets the filter back months.

Learn to read silence as data. The steering committee where every question gets a confident answer. The risk log that has not changed in three weeks. The team that delivers polished updates but never raises anything unexpected. These things can mean a programme is running well. They can also mean the filter is fully operational and the real conversation is happening somewhere else entirely. If nobody is telling you anything that surprises you, that is not necessarily a sign that everything is on track. It may be a sign that you have stopped being the kind of leader people bring hard news to.

 

The One Question That Cuts Through

There is a question I now use when a programme looks clean but feels wrong.

I find someone close to the real work. Someone who has been there long enough to know where the bodies are buried. And I ask them one thing.

What does everyone here know that nobody is saying out loud?

The answer to that question is almost always where the programme actually is. The gap between that answer and what appears in the formal reporting is almost always where the real leadership work needs to happen.

 

Comfortable Information Is Borrowed Time

PMI’s research on complex programme delivery is consistent on this point: early warning signals are frequently present and frequently ignored, causing problems to compound in severity before they are addressed. The pattern is not exceptional. It is systematic.

Every week a real problem stays hidden is a week where the options for addressing it narrow. Manageable risks become serious ones. Recoverable situations become critical ones. And the longer the filter operates, the more the team’s trust erodes, because people who know the truth and watch it go unacknowledged eventually stop believing that leadership is operating in good faith.

When the programme finally tells you the truth, and it always does eventually, the question is rarely how to get back on track.

It is whether getting back on track is still possible.

 

The Leaders Who Get This Right

The leaders who consistently deliver in high-stakes environments are not always the most experienced or the most technically skilled.

But they share something that is harder to develop than either of those things. They have learned to want the truth more than they want to be comfortable. They have built the self-awareness to notice when they are receiving a managed version of reality, and the discipline to go looking for the unmanaged one. They have created environments where people bring problems early because they have learned, through consistent experience, that doing so leads somewhere useful.

That is not a natural state for most leaders. It requires sustained effort, genuine self-awareness, and a willingness to sit with difficult information and resist every instinct to make it someone else’s problem.

But the alternative is a programme that looks healthy until it does not. A team that has learned to give you what you can handle. A steering committee that runs on time and misses everything that matters.

When your team tells you how things are going, are they telling you what is happening?

Or are they telling you what they have learned you can live with?

The gap between those two answers is where most programmes are won or lost.

Why Western Delivery Frameworks Stall in the Middle East (and What to Do Instead)

Posted on by

 

I remember sitting across from a senior government official in the Gulf, about six weeks into a major transformation programme. On paper, everything was moving. The governance framework was in place. The workstream leads had been assigned. The project plan had been reviewed and signed off. The first steering committee had gone smoothly.

And yet nothing was actually happening.

Not because of incompetence. Not because of a lack of resources. Not because the methodology was flawed. The team I was working with was experienced, capable, and well-intentioned. But they had arrived with a delivery model built for a different context, and they were applying it with the confidence of people who had never had reason to question it.

That pattern is playing out at an extraordinary scale right now. Saudi Arabia’s ICT market surpassed $48 billion in 2024, the largest technology market in the Middle East. McKinsey’s 2025 State of AI in GCC Countries report, drawing on surveys of senior GCC executives, found that 84% of GCC organisations have adopted AI in at least one business function, and only 31% have successfully scaled or fully deployed across the organisation. That is a 53-percentage-point gap between starting and delivering, across some of the best-funded, most ambitious transformation programmes in the world.

The question is not why organisations in the region are investing. The question is why so much of that investment stalls between intention and outcome.

After more than a decade delivering in the Middle East, I think I know the answer. And it is not the one most people reach for.

 

The Assumption That Travels Badly

Western delivery frameworks, whether PRINCE2, PMI, SAFe, or the various proprietary methodologies that large consulting firms carry from engagement to engagement, are not neutral tools. They are cultural artefacts. They were built in specific organisational contexts, shaped by particular assumptions about how decisions get made, how accountability flows, how disagreement is handled, and what progress looks like.

Those assumptions are rarely stated explicitly. They do not need to be, in the environments where these frameworks were designed. Everyone in the room already shares them. But the moment you move those frameworks into a fundamentally different cultural context, the unstated assumptions become the problem.

Hofstede’s cultural dimensions research (now maintained by The Culture Factor Group) offers a useful lens here. Arab countries consistently score high on two dimensions that bear directly on programme delivery. The first is power distance: the degree to which authority is respected rather than openly challenged, and the degree to which the most senior voice shapes the room rather than the most technically accurate one. The second is uncertainty avoidance: a preference for predictability, a resistance to ambiguity, and a reluctance to surface risk that might destabilise a process already formally endorsed. These are not character flaws or cultural limitations. They are consistent patterns that predict specific delivery behaviours imported frameworks are simply not designed to manage.

The typical Western delivery model assumes a relatively flat decision-making structure where the person with the most relevant expertise speaks most loudly. It assumes that challenge and disagreement in a meeting are signs of healthy engagement rather than disrespect. It assumes that formal sign-off is the meaningful moment of commitment and that what is agreed in the room will be actioned after it. It assumes that timelines create accountability and that accountability creates action.

In the Middle East, several of those assumptions do not hold. And the teams that arrive without understanding this do not fail because they lack capability. They fail because they are solving the wrong problem.

 

What Actually Drives Delivery in This Region

Execution in this region is not primarily operational. It is relational.

This is not a cultural curiosity or a soft consideration to be acknowledged in a pre-departure briefing and then set aside. It is a delivery requirement. Understanding it, genuinely understanding it rather than paying lip service to it, is the difference between a programme that moves and one that generates activity without progress.

Decisions in many Middle Eastern organisations, particularly in government and quasi-government entities which dominate the regional landscape, do not flow through the formal governance structure in the way a Western framework assumes. The steering committee may ratify decisions, but the real alignment happens elsewhere. In relationships that have been built over time, in conversations that take place outside the formal meeting structure, in the space between hierarchy and trust that no project plan captures.

Hierarchy here is not an obstacle to navigate around. It is the delivery infrastructure. Understanding who the real decision-makers are, what they care about, how they receive information, and what kind of relationship needs to exist before they will move is not supplementary to the delivery approach. It is the delivery approach.

Equally, the pace at which genuine commitment forms is different. A Western programme manager reads a signed-off plan as a committed baseline. In many regional contexts, that same sign-off is closer to the beginning of a conversation than the end of one. Real commitment, the kind that produces action, is built through repeated engagement, demonstrated respect, and a track record of following through. It cannot be manufactured by a governance process, however well designed.

 

The Meeting That Agrees to Everything and Changes Nothing

One of the most consistent patterns I encounter when stepping into stalled programmes in the region is what I have come to think of as performative alignment. The meetings happen. The presentations are well received. The heads nod. The action items are recorded. And then the follow-through does not come, not because anyone has decided not to cooperate, but because the alignment that appeared to exist in the room was not the deep kind that produces action.

In high-context cultures, of which many in the Middle East are clear examples, direct disagreement in a formal meeting setting carries a social cost that most Western delivery professionals underestimate. Saying no to a proposal in front of a room of peers and seniors is not simply a professional difference of opinion. It can feel like a breach of the respect and harmony that the meeting is partly there to maintain.

The result is that concerns, reservations, and genuine blockers often do not surface in formal governance forums. They emerge later, in quieter conversations, or they do not emerge at all. The experienced regional delivery leader learns to read what is not being said in a meeting as carefully as what is. The silence after a proposal is not always agreement. The smooth meeting is not always a sign of progress.

Teams that do not understand this dynamic spend months wondering why a programme that looked aligned keeps stalling. The answer is usually that the alignment they measured was the visible kind, and what drives delivery here is the invisible kind.

 

Where International Teams Get It Wrong

The failure mode I see most consistently is not incompetence or arrogance, although both exist. It is the application of a known model to an unknown context, with too much confidence and too little curiosity.

The international team arrives. They bring the framework, the templates, the governance structure, the reporting cadence. They run the kickoff. They establish the workstreams. They hold the first set of meetings. Everything looks like it is moving. The client counterparts are polite, engaged, and apparently aligned.

Then the programme slows. Decisions that should take days take weeks. Approvals that seemed close keep getting deferred. Stakeholders who appeared committed become harder to reach. The team escalates. They add more governance. More reporting. More pressure. The programme slows further.

What they are experiencing is the consequence of building delivery infrastructure without first building relational foundations. They have a governance model without trust underneath it, and governance without trust is just paperwork.

The other common failure is treating local counterparts as recipients of the methodology rather than as partners in understanding the context. The best people in any regional organisation carry an understanding of how things actually work, who the real influencers are, where the genuine blockers sit, and what has been tried before and why it did not land. Engaging that knowledge seriously, rather than as a courtesy, would transform the delivery approach. Most international teams access about ten percent of it.

 

What to Do Instead

The answer is not to abandon rigour or to conclude that structured delivery does not work in the region. It does. But it works differently, and the sequence matters enormously.

The first investment, before the governance framework, before the project plan, before the first steering committee, is in relationships. Not networking in the transactional sense. Genuine relationship-building, rooted in curiosity and respect, that creates the conditions under which honest conversation becomes possible. In a region where trust precedes transaction rather than following it, the time spent on this is not a delay to delivery. It is the foundation of it.

The second shift is in how decisions are understood and pursued. Rather than designing a governance structure and expecting decisions to flow through it, the experienced regional programme leader maps the real decision-making landscape. Who are the individuals whose genuine endorsement will move things? What do they need to see, hear, or feel before that endorsement becomes real? What informal conversations need to happen before the formal ones? Answering those questions honestly, and building a relationship strategy around them, is more valuable than any governance framework.

The third adjustment is in how alignment is tested. Rather than reading smooth meetings and nodding heads as confirmation of commitment, effective regional delivery leaders build in deliberate mechanisms for surfacing the real picture. Private conversations with key counterparts after formal sessions. Trusted intermediaries who can carry honest feedback in both directions. An explicit understanding that the formal meeting is often where positions are displayed rather than where they are formed.

Fourth, the pace of delivery needs to be calibrated to the pace at which genuine alignment forms, not the pace that the project plan demands. This is uncomfortable for Western programme managers trained to treat a timeline as a commitment. But the cost of false pace, the appearance of movement without the substance of it, is far higher than the cost of taking the time to build the real thing.

Finally, and perhaps most importantly, local knowledge must be treated as a strategic asset rather than a logistical courtesy. The people who understand the organisation, the culture, the history of what has been attempted before, and the unwritten rules that govern how things actually get done are the most valuable resource on the programme. Structuring the delivery approach around that knowledge, rather than around the imported framework, is the shift that most changes outcomes.

 

The Deeper Lesson

Delivering in the Middle East has taught me something that has made me a better programme leader everywhere, not just in the region.

Context is not a complicating factor. It is the medium through which all delivery happens. Every organisation has its own version of the unwritten rules, the informal power structures, the historical sensitivities, and the cultural patterns that shape how work actually gets done. The Middle East makes these visible in ways that Western environments sometimes obscure, because the gap between the imported model and the local reality is large enough that you cannot ignore it.

But the principle is universal. The best delivery professionals I have worked with anywhere in the world are the ones who arrive with curiosity before they arrive with answers. Who treat understanding the environment as the first act of delivery, not a preliminary to it. Who know that a framework is a starting point, not a solution.

The frameworks that travel well are not the ones with the most sophisticated methodology. They are the ones held lightly enough to be adapted, by people self-aware enough to know when adaptation is what the moment requires.

 

A Final Thought

If you are leading a programme in the Middle East and it has the shape of movement without the substance of it, the instinct will be to add more structure, more governance, more reporting, more pressure. That instinct is usually wrong.

The question to ask instead is simpler and harder. Do the people who need to move this programme forward trust you enough to tell you what is actually in the way? Have you built the relationships that make honest conversation possible? Do you understand not just the governance landscape but the human one?

If the answer to any of those questions is uncertain, that is where the work is. Not in the framework. Not in the plan.

 

Pre-Mortem: NHS Frontline Productivity Programme

Posted on by

 

On 1 April 2026, NHS England formally launched the Frontline Productivity Programme. It succeeds the £2 billion Frontline Digitisation Programme and is anchored to the NHS 10-Year Health Plan. The headline target is a 2% year-on-year productivity gain over three years. The lead use case is Ambient Voice Technology (AVT), AI-powered ambient scribing for clinicians, with £200 million committed in year one. The Department of Health and Social Care (DHSC) and NHS England have appointed Rob Thompson as joint Chief Digital, Data and Technology Officer.

A pre-mortem asks the same five questions, every time, applied to a current programme. This is the second in the series. The first looked at vendor accountability in regulated finance. This one looks at clinical safety accountability in regulated healthcare. Different sector, similar structural shape.

 

The Bet

The NHS is betting that AVT can deliver enough of the 2% year-on-year productivity gain to justify scaling deployment to tens of thousands of clinicians faster than the clinical safety framework for AI-enabled ambient scribing can be ratified. The technical bet rides on multi-site evidence led by Great Ormond Street Hospital (GOSH) across nine London NHS sites and 17,000 patient encounters: a 23.5% increase in patient interaction time, an 8.2% reduction in appointment length, and a 13.4% increase in A&E patients per shift. The strategic bet is that 19 self-certified suppliers competing for trust contracts will produce price discipline without producing safety variance. Reasoned bets, made under genuine pressure, backed by measurable evidence. But they are bets, and the framing reads as inevitability.

 

The Assumption

One belief is doing all the work: that clinicians using AVT will verify AI-generated notes against the patient context every time, at scale, rather than develop the same review-as-rubber-stamp pattern automation has produced in every regulated environment it has reached. The mechanism that produces the productivity gain is the same mechanism that erodes clinical attention to the note. If review thins because AVT proves “good enough” most of the time, the productivity number stays positive while clinical safety quietly degrades. Patient Safety Learning argued earlier this year that Copilot has arrived in the NHS without the operational guidance clinicians need to use it safely.

 

The Sequence

Capability shipped before the operational governance for AI-enabled ambient scribing was ratified. South West London is rolling out AVT to 20,000 clinicians across four trusts. University Hospitals of Leicester and Northamptonshire have deployed to over 10,000. Hertfordshire Community NHS Trust has moved past pilot to full rollout. NHS England published a 19-supplier self-certified AVT registry in January. Underneath, the clinical safety standards DCB0129 and DCB0160 are under active review, and the Explainability-Enabled Clinical Safety Framework for AI is still being developed. Commitment came first. The assurance framework is catching up.

 

The Pager

The accountability layer on this programme is more developed than most national digital programmes ever achieve. Rob Thompson holds a joint DHSC/NHSE Chief Digital, Data and Technology Officer post: senior, named, public, accountable. Chief Clinical Information Officers (CCIOs) at every deploying trust carry statutory DCB0160 deployment accountability. That deserves credit. The harder question is operational. When an AVT-generated note contains a clinically significant error that affects patient care, who is the named individual who carries the pager that night? The trust CCIO? The supplier on the registry? The clinician who signed off the note? The accountability is statutory; the operational reporting line for AI-specific clinical safety failure has not yet been publicly framed for AVT.

 

The Proof

Three outcome measures sit in the public record: the 2% year-on-year productivity gain, the GOSH-led multi-site evaluation, and the Oxford University Hospitals pilot in which 90% of clinicians reported reduced documentation time. All three measure clinician time and patient throughput. None measure clinical safety. A 2025 national cross-sectional study in the Journal of Medical Internet Research (JMIR), covering 178 NHS organisations and 14,747 digital health technology deployments, found that only 17.3% were fully assured against both DCB0129 and DCB0160. At a typical NHS trust, only 24.5% of deployed technologies held both assurances. The standards exist. Compliance with them is patchy. There is no committed measure for AVT-attributable adverse event rate by supplier, the rate at which clinicians materially amend AI-generated notes versus accept them, or DCB0160 compliance inside the AVT registry specifically. In 18 months, “did this work?” will be answered by whoever owns the platform to define what safe enough means.

 

Verdict

The Frontline Productivity Programme is more carefully constructed than most NHS technology programmes of the past two decades. Named senior accountability, real pilot evidence, multiple trusts in genuine production deployment, a clear use case the workforce wants. None of that is in dispute.

What is in dispute is whether the underlying clinical safety assurance layer holds at scale. DCB0129 and DCB0160 exist. Compliance with them currently runs at a quarter of what it should be. The deployments are racing toward 20,000-clinician scale while the AI-specific framework is still being written.

The action is concrete. Name the human at each deploying trust who carries the pager when an AVT-generated note causes patient harm. Demand per-supplier clinical safety performance reports from each of the 19 registry vendors, not self-certifications. Publish a clinical safety outcome measure alongside the productivity target before the year is out: adverse event rate change attributable to AVT, broken out by trust and by supplier.

If NHS England publishes a clinical safety outcome measure tied to a named owner in six months, and the AVT registry shifts from self-certification to audited compliance, the Frontline Productivity Programme becomes a model for AI deployment in regulated public services. Without both, the productivity number stays positive while the question of whether it was worth the clinical safety risk remains structurally unanswerable.

Your Personality Type Is Not Your Leadership Style. Your Behaviour Under Pressure Is.

Posted on by

Every few months, a personality framework resurfaces in leadership circles. DISC. Myers-Briggs. Enneagram. Belbin. Someone shares an assessment, teams complete a quick questionnaire, and for a week or two there is a flurry of conversation about whether the programme director is a high-D or the CIO is an INTJ. Then the work continues, and the framework quietly fades until the next cycle begins.

The problem is not that these frameworks are useless. Some of them are genuinely valuable as self-reflection tools and conversation starters. The problem is the assumption baked into almost every one of them: that your personality type shapes your leadership style in a consistent, predictable way. That if you are a Dominance type, you lead like Elon Musk. That if you are a Steadiness type, you lead like Satya Nadella.

The research says otherwise. And so does twenty years of watching this play out on real programmes, in real organisations, under real pressure.

 

The Landscape Is Larger Than the Label

DISC is one of a dozen personality-to-leadership models in active commercial use. MBTI classifies people across four dimensions derived from Jungian typology and is used by the vast majority of Fortune 100 companies, despite repeated criticism of its scientific validity. The Big Five model (Openness, Conscientiousness, Extraversion, Agreeableness, Neuroticism) has the strongest empirical backing of any personality framework but is the least commercially dominant, partly because traits measured on a continuous spectrum are harder to communicate at a glance. Belbin maps nine team roles, not personality types, which is a meaningful distinction. CliftonStrengths focuses on amplifying what you already do well rather than categorising who you are.

Each has a legitimate use. The problem begins the moment organisations treat them as performance predictors rather than self-awareness tools.

A landmark meta-analysis by Judge and colleagues in 2002, examining more than seventy studies across eleven thousand leaders, found that Conscientiousness and Extraversion were the strongest personality predictors of leadership performance, Conscientiousness most consistently linked to sustained effectiveness, Extraversion most linked to leadership emergence. Not type. Not style. Traits: the disposition to follow through, to maintain standards, to engage and bring others along. That finding has held up across replication after replication since.

 

The Attribution Problem

Personality frameworks routinely attach well-known leaders to their quadrants. The Dominance leader drives results and moves fast, so Elon Musk becomes the example. The Influence leader inspires and builds momentum, so Oprah Winfrey is named. The Steadiness leader creates stability and builds trust, so Satya Nadella is cited. The Conscientiousness leader ensures accuracy and high standards, so Mark Zuckerberg is assigned.

These attributions are speculative. As far as I know none of those individuals has publicly shared a verified assessment result. The assignments are made by inference from visible behaviour, which is circular reasoning: the framework predicts the behaviour, the behaviour confirms the framework, and nothing has actually been tested.

More importantly, the leaders themselves tend not to describe their effectiveness in terms of type. Satya Nadella, in Hit Refresh, describes empathy not as a natural trait but as a capability he had to actively develop, transformed in part by his experience as a father to a son with cerebral palsy. He credits that deepening, not his personality type, as the foundation of the cultural shift at Microsoft. The distinction between those two things, personality and the deliberate cultivation of capability, is the difference between a leader who peaked and a leader who grew.

 

Adaptability Is the Variable That Actually Predicts Success

Research on Emotional Intelligence shows that the ability to read a situation and modulate your response is among the strongest predictors of transformational leadership success, more practically relevant in complex change environments than a fixed personality classification.

The failure patterns make this concrete.

The high-D leader who drove results at pace in the first two quarters, and then, when the programme hit a wall and the team needed to be heard, doubled down on speed and ownership rather than shifting to inclusion and trust-building. The team read it as pressure, not leadership. Momentum collapsed.

The high-I leader who was exceptional at generating excitement and alignment across stakeholder groups, but whose follow-through was inconsistent. Commitments made in workshops were not tracked. The programme office spent six months chasing actions that the leader had already moved on from.

The high-S leader, calm and supportive under normal conditions, who then avoided a critical conversation with a failing vendor for three months because confrontation felt incompatible with their style. By the time the conversation happened, the programme had lost time it could not recover.

The high-C leader whose risk documentation was genuinely thorough, dependencies mapped, decision papers written to a standard the programme could stand behind, and who then spent ten weeks refining a business case while the implementation window closed around them. Not because the analysis was wrong. Because the level of certainty required before acting was higher than any live programme can ever provide, and by the time the final version was approved, the decision had already been made by events.

These are not personality failures. They are adaptability failures.

 

The Section Worth Building a Leadership Practice Around

Every serious personality framework identifies failure modes for each type. Not how the type shows up at its best, which tends to be flattering and self-affirming, but how it creates risk for the people around it and the outcomes it is responsible for when left unchecked.

For Dominance: moving too quickly without bringing others along. For Influence: energy is high but follow-through can vary. For Steadiness: harmony can be prioritised over progress. For Conscientiousness: the pursuit of accuracy can delay decision-making past the point where decisions still matter.

Every one of those is a real, recurring failure mode in transformation environments. The practical question is not which type you are. It is how aware you are of your natural failure mode, how quickly you can recognise when you are heading towards it, and whether you have built the discipline to shift before the damage is done.

 

What to Do with a Framework Once You Have One

Use it as a mirror, not a map. A mirror shows you how you naturally show up. A map tells you where to go. The frameworks are good mirrors. They are poor maps.

The leaders I have seen sustain high performance through complex, multi-year programmes were not distinguished by their type. They were distinguished by self-awareness, by a willingness to receive genuine feedback, and by the disciplined habit of asking, particularly under pressure, whether their natural response was the right one for the situation.

Knowing you are a Dominance type is not a leadership strategy. Knowing that your instinct under pressure is to accelerate when the situation requires you to slow down, and having the discipline to catch yourself before it costs you. That is.

AI Is Eating Theory. Companies Are Firing the People With Judgement.

Posted on by

 

AI is replacing the work that used to define the first decade of a career. At the same moment, organisations are quietly thinning out the people whose work AI cannot do.

That pairing sits somewhere between obvious and uncomfortable, depending on which part of the workforce you sit in. The data behind it is no longer disputed. The talent decision being made in response to it is almost universally backwards.

 

What AI is actually replacing

The popular framing of AI in the workplace is that it threatens knowledge workers broadly. The 2025 data tells a sharper story.

Stanford’s Digital Economy Lab released a study in November 2025 with the deliberately unsettling title Canaries in the Coal Mine. It tracked employment in occupations highly exposed to AI from late 2022 onwards. Workers aged 22 to 25 in those roles saw employment fall by roughly 13%. Workers in their forties, fifties and sixties in the same occupations continued to grow.

The mechanism is not redundancy. It is non-replacement. Entry-level vacancies are quietly not being backfilled. The career ladder is losing its bottom rungs.

The Stanford authors are unusually direct about why. AI is replacing codified knowledge, the part of expertise that can be written down, while complementing the experiential wisdom that only comes from years on the job. Other 2025 work in customer support and software development tells the same story. AI lifts the bottom of the distribution faster than the top. Two-month-experience workers using AI now match six-month-experience workers without it. The work AI does best is the kind of standardised, learn-from-a-book task that used to define the first few rungs of a career.

 

The thing AI cannot replicate

There is a second half to this story that gets less coverage.

Boston Consulting Group ran a study with Harvard Business School using 758 of its own consultants and GPT-4. On standard tasks, AI users completed 12% more work, 25% faster, with 40% better quality. The finding that rarely makes the press summary: when the same study tested tasks designed to fall outside the model’s actual capability, consultants using AI were 19 percentage points less likely to produce correct solutions. AI made experts wrong more often when the problem required judgement AI lacked.

The capability to know when to trust an AI answer and when to override it is itself a function of experience. It is built from a personal library of cases, situations and outcomes that no model has been trained on.

Decades of research in naturalistic decision-making, the field Gary Klein founded by watching firefighters and military commanders make calls under uncertainty, describes the same mechanism. Experts under pressure do not deliberate between options. They pattern-match against situations they have seen before. The library is built by exposure, not by reading frameworks.

This is what is meant by judgement. It is the residual human advantage in the AI era, and it has a clear demographic profile.

 

The talent decision being made backwards

Put the two findings beside each other.

AI is removing the codified, junior-level work fastest. The cohort whose work AI is actually complementing is the experienced one. The economic logic of an organisation in 2026 should be to lean into that experienced layer, because it is the part of the workforce AI cannot reproduce and which increasingly determines the quality of any AI-augmented output.

What organisations are doing instead is the exact opposite. The over-50 cohort is being quietly thinned through restructures, voluntary exit programmes, redundancy schemes, and the slow erosion of roles experienced workers tend to hold. It is rarely a stated policy. It is almost everywhere a pattern.

The talent decision is being made backwards. The cohort being pushed out is the one most worth keeping. The cohort being squeezed at the bottom is the one whose work AI is already doing. The organisation ends up with no future and no memory.

 

The cost of forgetting

There is an institutional dimension to this that gets ignored because it does not show up in the next quarterly report.

Roughly 42% of an organisation’s working knowledge sits in the heads of individual employees and nowhere else. Industry estimates put the cost of knowledge loss from rapid organisational change at tens of billions of dollars a year across Fortune 500 firms. The direction is consistent even where the precise figure varies. Restructures remove people, and the people take the unwritten knowledge with them. A newly arrived CEO who clears out the over-50 cohort does not just lose those individuals. They lose the only group who remembers why the last three transformations failed and what is different about this one.

That is not a fairness argument. It is a structural one. The organisation is paying a real cost. It will appear on the books eighteen months later, in the form of mistakes the experienced layer would have caught.

 

What we are not calling it

Age discrimination is unlawful in most major jurisdictions. It is also one of the most reliably under-reported categories of workplace harm, because it is rarely framed as discrimination by the people doing it.

ProPublica’s multi-year investigation into IBM found the company eliminated more than 20,000 workers aged 40 and over from 2013 onwards. The US Equal Employment Opportunity Commission concluded in 2020 that the layoffs had a clear adverse impact on older workers. More than 85% of those targeted for layoff in that period were older workers, even when rated as high performers. In 2023, former IBM HR professionals filed suit alleging termination linked to age and explicit plans to replace them with AI.

Almost no one running these processes describes them as age discrimination. They are called “right-sizing,” “talent refresh,” “succession planning,” “rebalancing the pyramid.” The language and the outcome have been routinely diverging for at least a decade. What is new in 2025 is that AI has made the underlying decision economically illiterate as well as legally exposed.

 

Where this leaves you

If you run an organisation that has quietly pushed out the experienced cohort, you have spent real money to remove the layer of your workforce AI cannot replicate, while leaving in place the layer whose work AI is doing without you noticing.

The question is not whether you can afford to keep experienced staff. It is whether you can afford to lose them at exactly the moment they became the most valuable people on your payroll.

Healthy Organisations Are Built by Healthy Leaders

Posted on by

 

Healthy organisations are not the product of wellbeing programmes. They are the product of leadership behaviour. Six disciplines describe what that behaviour actually looks like.

The corporate wellbeing market has more than doubled in the last decade. Employee wellbeing scores have flatlined. Burnout, disengagement, and quiet quitting continue to climb in almost every survey that measures them. None of this is for lack of effort. It is for lack of diagnosis. The budget has gone to the wrong department.

 

Wellbeing is downstream of how leaders behave

When a workplace is unhealthy, the temptation is to add a programme. Meditation apps. Resilience workshops. Mental health days. Employee assistance schemes with a freephone number nobody calls. These have their place, but none of them touch the actual cause.

What makes a workplace unhealthy is almost always the operating environment leaders create. The expectations they signal. The behaviours they reward. The hours they keep. The candour they tolerate. The boundaries they ignore. People do not burn out because the meditation app was insufficient. They burn out because the way work is led is unsustainable.

This is not a soft observation. It is a structural one. If the leader is the largest single variable in team engagement, and twenty years of Gallup data suggests they are, then wellbeing has to be treated as a leadership output, not an HR programme.

 

Six disciplines of a healthy leader

The shorthand I have come to use is L.E.A.D.E.R (an obvious one). Six disciplines that the leaders I have watched succeed over a long career practise without making a virtue of it, and the leaders I have watched burn out, or burn others out, tend to neglect at least three of them.

 

L – Limits

The hardest to practise and the most easily faked. A healthy leader holds boundaries on their own working hours, their decision-making capacity, and the volume of work they will absorb before pushing back. The leader who answers every message at eleven at night signals to the organisation that the line is somewhere past eleven at night, regardless of what the wellbeing policy says. Limits are taught by example or they are not taught at all.

E – Empathy

Not the soft listening that fills articles about emotional intelligence. Disciplined empathy. The ability to read what is happening in a room, to notice the team member who has stopped speaking up, to interpret a steering committee mood before reacting to the slide. Empathy without standards is unprofessional. Standards without empathy are unsustainable. Both at once is the discipline.

A – Accountability

Healthy leaders take more responsibility than the role formally requires. They own the call, they own the consequence, and they correct themselves in public when the call was wrong. The cultural rot in most organisations is not weak performance. It is leaders who quietly redirect accountability downwards when results disappoint. People watch for this. Once they see it, the relationship is over.

D – Discipline

The daily habits that produce sustained executive performance over a thirty-year career rather than a brilliant five-year sprint. Three priorities written down. A structured one-to-one rhythm. Time blocked for thinking. A weekly review. Discipline is not glamorous and it is not strategic. It is the unglamorous, unstrategic foundation that everything else stands on.

E – Energy

A leader is, among other things, a capacity manager. Their own capacity, and the capacity of the people around them. The healthy leader treats sleep, recovery, and physical condition as professional obligations, not personal preferences. They notice when the team is running on reserves and adjust the operating tempo before something breaks. The unhealthy leader treats exhaustion as a badge of seriousness and accidentally institutionalises burnout as a sign of commitment.

R – Reflect

The discipline most often dropped first under pressure, and the one that most reliably separates leaders who compound over time from those who plateau. Healthy leaders make space to ask what worked, what did not, and what the next iteration looks like. They do this weekly, not annually. They write it down. It costs them an hour a week and it compounds over a career.

 

Wellbeing was always the leader’s job

If you read the six pillars and notice that none of them are particularly new, that is the point. There is no insight here that has not been written about for thirty years. The insight is in the arrangement. Six things, practised together, by the leader. Not delegated to HR. Not outsourced to a vendor. Not performed on stage at the annual offsite.

A wellbeing programme without these six behaviours is a sticking plaster on a system designed to bleed. A leader who practises these six things, in a company with no formal wellbeing programme at all, will produce a healthier organisation than the alternative.

The temptation when reading frameworks like this is to nod, save the post, and carry on operating exactly as before. The honest test is the diary. If your week, the way you actually spend the hours, does not reflect at least four of these six disciplines, the wellbeing of the people who work for you is already on a slow countdown, regardless of what your engagement survey says.

There is no other wellbeing programme. Only how the leader spends the week.

The Architecture Is the Problem, Not the Agent

Posted on by

 

Every time an AI agent causes a catastrophe, the conversation goes to the same place. What did the AI do wrong? Can these systems be trusted? How do we stop it happening again?

Those are the wrong questions. And the wrong questions lead to the wrong fixes.

The better question, the one that actually leads somewhere useful, is this: who built the environment where it could happen?

 

Three Incidents. The Same Root Cause.

PocketOS, April 2026. An AI coding agent found an unscoped API token sitting in an unrelated file. It used that token to delete a storage volume on Railway, their infrastructure provider. It did not check whether the volume was shared across environments. It was. Production database and every backup, gone in nine seconds.

Replit, July 2025. An AI agent deleted over a thousand executive records during an explicit code freeze. Nothing stopped it because nothing had been configured to stop it.

Amazon Kiro, December 2025. An AI agent inherited a senior engineer’s elevated permissions, the kind that would normally require two people to sign off on a destructive action. It deleted and recreated an entire cloud environment. Thirteen-hour outage.

In every case, the agent did something it was technically permitted to do. Not something it was asked to do. Something it could do, because the architecture said it could.

That is not an AI failure. That is a design failure.

 

We Are Asking Questions About the Wrong Moment

The instinct to interrogate the AI is understandable. These systems are new, they are powerful, and when they cause damage the natural response is to look at the machine.

But that framing lets the actual problem off the hook. In each of these incidents, someone made decisions about credential storage, access scopes, permission inheritance, and whether destructive actions should require human confirmation before execution. Those decisions created the conditions. The agent had the speed and autonomy to find the gap before anyone noticed it was there.

“The incident is never the origin.” Every one of these failures has a human design decision sitting upstream of it.

 

CIOs and CTOs Own This

This is where the conversation needs to land, and where it rarely does.

CIOs and CTOs set access models. They decide, or delegate the decision about, what credentials AI agents can reach, what permissions they inherit, and whether irreversible actions require a human confirmation step. These are not AI product decisions. They are infrastructure and governance decisions of the kind that technology leadership has been making for years.

The least-privilege principle has been a security standard since the 1970s. Every process should have only the access it needs and nothing more. We have applied it carefully to service accounts, automated pipelines, and human users for decades. We are not applying it with the same rigour to AI agents. The gap is showing up in production.

 

Three Questions That Determine Your Exposure

If you are deploying AI agents and cannot answer these clearly, you have a governance problem. It is a matter of when, not if.

  • Are your AI agents operating on minimum permissions? Or are they inheriting ambient credentials that happen to be accessible in the environment? Unscoped tokens stored in accessible files are a credential hygiene problem. AI agents now have the speed to exploit them in ways a human operator simply would not.
  • Do irreversible actions require human confirmation before execution? Not a log entry after the fact. A genuine gate, before the command runs. Deletion, overwrites, production deployments. These should not be single-step autonomous operations regardless of how capable the agent is.
  • What is the blast radius? Before any AI agent is deployed, you should be able to answer: what is the worst thing this agent could do with the access it currently has? If that question gives you pause, the deployment is not ready.

These are not new questions. They are the questions we have always asked about automated systems. The difference is that AI agents are faster, more capable of creative problem-solving, and more likely to find an unintended path that nobody anticipated during design.

 

Governance Does Not Require a New Platform

Much of the current enterprise AI governance conversation focuses on model behaviour: hallucination, bias, output quality. Those are real concerns. They are not the ones that will delete your production database.

The vendors now selling AI governance infrastructure are not wrong about the problem. But executives should make their own assessment of what their environment actually needs. “Governance does not require a new platform. It requires applying principles you already know to systems you are now deploying.” When vendors know the renewal depends on value delivered rather than fear managed, the conversation changes quickly.

 

The Agent Did Not Design the Environment

The uncomfortable fact sitting underneath every one of these incidents is that the AI agents involved were, in a narrow technical sense, doing their jobs. They identified a problem and attempted to fix it. They used the access they had. They executed what was permitted.

The humans who made the architectural decisions upstream of those moments are the ones who need to answer for the outcomes.

You cannot fix an architecture problem by retraining the model.

What 20 Years of High-Stakes Delivery Taught Me About Execution, and the Difference Between Programme Management and Programme Leadership

Posted on by

 

I have stepped into programmes where every governance box was ticked, every RAG status was green, and delivery was quietly failing. The plan looked solid. The reporting was clean. The steering committee meetings ran on time. And yet nothing was really moving.

That pattern, visible control with invisible dysfunction, is what two decades of high-stakes delivery teaches you to recognise. And it almost always comes back to the same root cause. We confuse programme management with programme leadership.

 

Programme Management Keeps Things Moving. Programme Leadership Makes Them Work.

Most organisations lean heavily into programme management, and it is easy to see why. Detailed plans, governance frameworks, status reports, risk logs, and steering committees all create a sense of order and control. On paper, everything looks under control.

The problem is that I have stepped into too many programmes where all of that existed and delivery was still failing. Because structure creates visibility, not outcomes. Programme management is fundamentally about control, while programme leadership is about direction, alignment, and energy. One tracks progress while the other makes progress possible. That distinction is where most organisations fall short, not because they lack process, but because they mistake process for leadership.

 

Context Shapes Execution

Here is something that even experienced delivery professionals often underestimate. Execution does not happen in a vacuum. It happens inside a specific organisation, a specific culture, and a specific set of relationships and unwritten rules that no governance framework will ever fully capture.

I have watched highly capable teams arrive with world-class frameworks and strong delivery disciplines and still struggle to get real traction, not because their methodology was wrong, but because the environment was not properly understood. They received agreement in meetings but silence where there should have been challenge. Risks that everyone privately knew about went unsurfaced because the conditions for honest conversation had not been established.

Delivering across the Middle East over the past decade has made this especially clear to me. Execution here is not just operational, it is relational. How trust is built, how decisions are really made, the importance of respect and hierarchy, and the pace at which genuine alignment actually happens are not soft considerations. They are delivery requirements. When you get them right, conversations become honest, decisions become clearer, and alignment becomes real. When you ignore them, execution becomes performative, with activity replacing progress.

The same principle applies in any environment where you are leading in unfamiliar territory. Understanding context is not optional at this level. It is the difference between a programme that moves and one that stalls.

 

The Biggest Mistake: Managing Metrics Instead of People

When delivery starts slipping, most organisations respond in a predictable way. More reporting, more tracking, and more pressure. It feels like a logical response, but it is usually the wrong one, because metrics do not deliver programmes. People do.

I have seen programmes sitting on green dashboards right up until the moment they fail, not because the data was falsified, but because what was not being measured was what actually mattered. Team fatigue, misalignment between stakeholders, lack of psychological safety, and quiet disengagement do not show up in a status report. When people are treated like a line item, engagement drops, ownership fades, and quality begins to slip long before the timeline does. Burn a team out and you do not just lose pace. You lose the judgment, initiative, and honesty that high-stakes delivery fundamentally depends on. No dashboard captures that, but every experienced programme leader eventually learns to recognise it.

 

The Gap Between Manager and Leader Is Where Execution Breaks

This is the gap that most organisations do not even realise they have. They promote strong managers and expect leadership to follow, but the two are not the same thing and they do not produce the same results.

Managers tend to focus on tasks, deadlines, and maintaining control over the plan. Leaders focus on clarity, alignment, and removing the obstacles that prevent capable people from doing their best work. A manager’s primary question is whether the programme is on track. A leader’s primary question is what is getting in the way. That difference sounds subtle, but in practice it determines whether a programme survives pressure or collapses under it.

The best delivery environments I have worked in were not the most heavily governed. They were the most honest. When people feel clear about what success looks like, trusted to make decisions, safe enough to surface problems early, and genuinely supported when things get difficult, they perform at a level that no governance framework can manufacture. When those conditions are absent, no amount of process or reporting will compensate for it.

 

Execution Is a Human System, Not a Delivery Framework

After 20 years, this is the conclusion that becomes impossible to argue against, even if it takes time to fully accept. Execution is not primarily a technical problem. It is a human one.

You can have the right tools, the right frameworks, and the right governance model in place and still fail to deliver if you do not have trust, alignment, cultural awareness, and a team that still has the energy and conviction to push through difficulty. The principles that have held true across every programme I have led, recovered, or stepped into under pressure are consistent. Clarity beats complexity, because people cannot deliver what they do not fully understand. Context and culture are not optional, because they shape how work actually gets done regardless of what the plan says. Sustainable pace matters more than most organisations are willing to admit, because the cost of burning people out shows up in quality long before it shows up in a timeline. And leadership has to be visible not just at the top, but across the programme at every level where real decisions are made and real obstacles are felt.

 

Closing Thought

You can manage a programme perfectly and still fail to deliver it. Execution is not about control. It is about people, and the environment you create around them. The organisations that understand this tend to deliver. The ones that do not keep searching for a better framework when the answer was never in the framework to begin with.

Stop Relying on Willpower – Build Systems Instead

Posted on by

We give far too much credit to discipline and nowhere near enough to design.

After working with countless leaders, I have noticed a recurring pattern that is as frustrating as it is common. Most people believe they are failing because they lack “grit” or mental toughness. In reality, they are failing because their environment is actively working against them.

Willpower is often praised as the engine of success, but the truth is that it is a finite resource. It runs out. Fatigue sets in, focus fades, and even the most driven individuals eventually lose steam. If you have ever started a project with high energy only to see your momentum evaporate a few weeks later, the problem is not your character. The problem is your lack of a system.

The Willpower Battery
Relying on willpower is like expecting your phone to stay at a hundred percent all day without ever plugging it in. It might hold up for a few hours of heavy use, but eventually, the screen dims and the power cuts out.

This is why so many professionals sprint toward their goals only to collapse halfway. Willpower is a variable that fluctuates based on how much sleep you had or how many stressful meetings you sat through. Systems, on the other hand, are constants. They do not care how tired you are.

Designing for Momentum
When you stop trying to “motivate” yourself and start designing your environment to make the right actions easy, everything changes. You stop fighting yourself. You remove the friction that makes progress feel like a chore and you make the right choices automatic.

Stop Making Useless Decisions
Every tiny choice you make drains your battery. This is the logic behind why people like Steve Jobs wore the same outfit every day. It was not about fashion. It was about preserving decision-making energy for things that actually mattered.

If you want to protect your focus, you have to pre-schedule your day and batch your tasks. Use automation for the trivial stuff. The fewer decisions you have to make about how to work, the more energy you have to actually do the work.

Let Your Environment Do the Nudging
Habits are triggered by cues in your physical space. If you want to read more, put the book on your pillow in the morning so you have to move it to get into bed. If you want to exercise, lay your gear out the night before.

A good system does not try to ignore your weaknesses. It assumes you will be tired and lazy later in the day, so it designs the world around those moments to keep you on track anyway.

The Accountability Loop
Goals tend to die in silence. They grow much stronger when they are shared with a peer, a coach, or even tracked in an app. Accountability is not about adding pressure. It is about creating a structure that keeps your original intentions visible even when your motivation is low.

Watch the Process, Not the Scoreboard
The highest performers I know do not obsess over results. They obsess over the behaviors that create those results. If you want to grow a business, stop staring at the revenue and start tracking your daily outreach. If you want to get fit, stop looking at the scale and start counting the workouts. When you focus on the inputs, the outputs eventually take care of themselves.

Lower the Barrier to Entry
When a task feels too big to start, you are experiencing friction. The solution is to shrink the task until the resistance disappears. Cannot find the energy to write a report? Write a single paragraph. Cannot find an hour for the gym? Do ten minutes. Momentum is a much more powerful force than motivation, but you have to get moving first.

Design Always Wins
The most successful people are not necessarily the ones with the most discipline. They are the ones who have built the best systems. They have made the right choices the path of least resistance.

You do not need to find more willpower. You just need a better design for your day.

Most IT Vendors Don’t Care About Your Success – They Care About Renewals

Posted on by

Your IT Vendor Is Not Your Partner

In the world of enterprise technology, we love to throw around the word “partner.” It sounds collaborative. It implies that everyone is rowing in the same direction toward a shared goal.

But if we are being honest with ourselves, most IT vendors are not built to care about your long term success. They are built to care about one thing: the renewal. Their entire business model is designed around hitting sales targets and retaining contracts. Ensuring you actually achieve the outcomes they promised in that glossy sales deck is often a distant second priority.

If you feel like there is a massive gap between the “strategic vision” you bought and the reality of your day to day support, you are probably right. Here is why that gap exists and how you can actually close it.

 

The Incentive Problem
You have to look at how the person sitting across from you is actually paid. Most vendor account managers are measured on renewal and upsell quotas. They are not rewarded for your return on investment or your team’s improved efficiency. They are rewarded for keeping the revenue flowing.

This misalignment creates a series of predictable problems. The best teams are usually assigned to winning new business, while existing clients are quietly moved to maintenance mode support. Projects get scoped to fit the vendor’s renewal cycle rather than your actual business milestones. When the focus is on a contract date instead of a transformation outcome, your technology starts to stagnate.

 

The Risk of Being Vendor-Led
When you let a vendor control the narrative, you end up with strategic drift. You start following their product roadmap instead of your own business strategy. You find yourself buying add-ons you do not really need because they “solve” a problem the vendor’s own software created in the first place.

This is not a partnership. It is a transactional cycle where you pay more to achieve less.

 

How to Take Back Control
You do not have to accept the renewal trap as a cost of doing business. You can redirect that vendor energy back toward your success by changing the rules of the relationship.

  • Redefine the Scorecard: Stop measuring success by uptime alone. Uptime is the bare minimum. Build performance metrics that align with your actual business objectives. If a vendor wants to talk about a contract extension, make them demonstrate the tangible value they delivered over the last year first.
  • Demand a Strategic Roadmap: Do not just sit through a product pitch. Force them to show how their evolution aligns with your long term vision. If they cannot show that alignment, they are just a utility, not a strategic asset.
  • Create Real Governance: Move the relationship beyond the sales team. Establish steering committees that include your internal leaders and their senior reps. Make it clear that oversight is constant, not just something that happens ninety days before the bill is due.
  • Keep Your Leverage: Avoid over-reliance on a single product. Build a flexible architecture that allows you to pivot if a vendor stops delivering value. When they know the renewal is earned rather than guaranteed, the level of service usually changes overnight.

 

The Bottom Line
Vendors will always care about their own bottom line. That is just how business works. But as a leader, it is your job to make your success the only path to their profit.

Real partnerships only emerge when value delivered is the price of admission for the renewal. Anything less is just a contract you cannot afford to keep.