Category Archives: Management

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.

Learning How to Learn: The Meta-Skill That Will Define the Next Generation

Posted on by

“Trying to predict the world even in five or 10 years’ time is almost impossible now. But what you can say with certainty is that it’s going to be very different.”

That observation from Demis Hassabis, the CEO of Google DeepMind (ABC News) perfectly captures the uncertainty of our current era. With technology moving at breakneck speed, the future is a moving target.

However, one thing is becoming painfully clear: your success will depend less on what you already know and much more on how quickly you can learn whatever comes next.

 

Why Mastery is a Trap
We used to believe in mastery. You went to school, you learned a trade or a profession, and you spent the next thirty years refining that specific set of skills. But static knowledge has a very short shelf life today. Industries and workflows are evolving too quickly for that old model to hold up.

Hassabis is right. In a world reshaped by automation and AI, the most important skill is not mastery of a specific tool. It is the ability to acquire new skills, adapt your mental models, and refine the actual process of how you take in information. This is what we call a meta-skill.

 

What Meta-Skills Actually Look Like
Developing these skills means moving beyond just “studying” and toward a more active way of thinking. It involves a few core shifts in perspective.

  • Curiosity over Comfort: You have to stay curious enough to explore new ideas even when they feel threatening to your current expertise.
  • Critical Thinking: You need the ability to evaluate information in real time, especially as we are flooded with more data than ever before.
  • Resilience: You have to get comfortable with being a “beginner” over and over again. That is a hard pill for many established professionals to swallow.

 

Building a Culture of Constant Growth
If you are leading a team, your job is no longer just to manage their output. Your job is to foster an environment where learning is part of the daily routine.

  1. Make Learning a KPI: Start measuring and tracking the new skills your team is acquiring, not just the tasks they are completing.
  2. Flexible Frameworks: Provide different ways for people to grow. Some people learn through mentorship, others through experimental labs or micro-courses. There is no one-size-fits-all approach.
  3. Reward Curiosity: Celebrate the people who share knowledge or experiment with new ways of working, even if those experiments do not always lead to an immediate win.
  4. Lead by Example: Show your team your own learning process. Let them see that curiosity is an asset and that “not knowing everything” is the first step toward innovation.

 

The Reality of the Future Predicting the future might be impossible, but preparing for it is not. The winners of the next decade will not be the people who cling to what they already know. They will be the ones who invest in the meta-skill of learning how to learn. They will be the ones who can reinvent themselves as quickly as the world reinvents itself.

Knowledge expires. The ability to learn is the only thing that doesn’t.

Your Software Vendor’s Roadmap is Not Your Business Strategy

Posted on by

It is a trap that many organizations fall into without even realizing it. A new software platform arrives with promises of innovation, efficiency, and total transformation. The vendor’s roadmap looks polished and exciting. The slides show a future where every problem is solved by a scheduled update or a new feature rollout.

But here is the reality: Your software vendor’s roadmap serves their future, not yours. It is not your strategy.

Too many leaders conflate the two. They mistake a product plan for a blueprint of their own organization’s future. When that happens, you stop being a business led by a vision and start being a customer led by a subscription.

 

The Incentive Behind the Roadmap
Software is no longer just a back-office tool. It is the nervous system of your business. Vendors understand this deeply, and they build their roadmaps to keep you invested in their specific ecosystem.

Their objectives are simple. They prioritize features that help them capture more market share. They showcase updates that strengthen their own position against their competitors. They design “lock-in” features that make it harder for you to leave.

This does not make them bad people. It makes them smart businesses. But it also means that you, as a leader, must draw a hard line between their commercial plan and your strategic direction.

The Risks of Strategic Drift
When you confuse a roadmap with a strategy, you face three primary risks:

  1. Strategic Drift: You begin following vendor priorities instead of your own. You end up shaping your technology to serve their vision rather than the other way around.
  2. False Efficiency: You might implement features just because they are available, not because they actually solve a business problem.
  3. Dependency: You become so reliant on a single vendor’s path that you lose the ability to pivot when your market changes.


How to Stay in the Driver’s Seat
A roadmap should be a data point, not a set of marching orders. Here is how to maintain your own strategic independence.

  • Strategy First, Tools Second: Your strategy must exist independently of your tech stack. If you cannot describe your goals without mentioning a specific software name, you are probably too deep in the vendor’s roadmap.
  • Diversify Your Architecture: Do not build your entire future on a single product. Create a flexible environment that allows you to integrate and adapt. This gives you the leverage to walk away or pivot if a vendor changes course.
  • Challenge the Feature Requests: The best vendors actually listen. Use your influence to push for features that serve your strategic objectives rather than just accepting whatever they have scheduled for Q3.
  • Maintain Ownership of the Vision: IT and business leaders must be the ones steering the ship. Vendors are partners, not pilots. Your strategy should dictate the tools you use, never the other way around.


The Role of Leadership
This is not just a technology issue. It is a leadership issue. Too often, executives delegate roadmap alignment to technical teams and assume that is the same thing as having a strategy. It isn’t.

You have to ask yourself: Are we shaping this technology around our business goals, or are we bending our business goals to fit this technology?

 

Closing Thoughts
A vendor’s roadmap is designed to secure their future. Your strategy is designed to secure yours. When you fail to distinguish between the two, you risk building someone else’s vision instead of your own.

Your competitive advantage does not come from following a software vendor’s plan. It comes from executing your own.

Why It Is Important to Have a Love for Learning

Posted on by

Why a Love for Learning is Your Greatest Asset

Knowledge is no longer a static thing that you acquire once in your twenties and carry with you for the rest of your life. It has become a living force. It shapes how we raise our children, how we grow as individuals, and how we navigate our careers in a world that refuses to stand still.

At the heart of all this growth is one essential ingredient: a genuine love for learning.

 

Learning as a Parent: Modelling Curiosity
Children do not just listen to what we say. They absorb what we do. When you demonstrate a love for learning, you are showing your children that curiosity is not just something for the classroom, but a way of life.

Curiosity breeds a specific kind of confidence. When a child sees a parent ask questions, try new things, or explore ideas without a fear of “not knowing,” they learn that mistakes are not failures. They learn that “not knowing” is just the first step toward a new discovery.

By cultivating a family culture of curiosity, you are equipping them with the resilience they will need to thrive in a future that we cannot even fully imagine yet.

Learning as Personal Fuel
A love for learning is not confined to your professional life or academic pursuits. It is about personal fulfillment. It is the drive to understand a new hobby, to learn a second language, or to dive into a topic that has nothing to do with your day job.

This kind of exploration keeps your mind sharp and your perspective broad. It prevents you from becoming stagnant. When you stop learning, you start settling for the version of yourself you were yesterday. A love for learning ensures that your personal growth never hits a ceiling.

The Professional Necessity of Adaptability
In the workplace, the ability to learn has become the ultimate competitive advantage. We often talk about “upskilling,” but that sounds like a chore. A love for learning turns that chore into an opportunity.

If you enjoy the process of acquisition, you are no longer threatened by new technologies or shifts in your industry. You become the person who can pivot when everyone else is panicking. You don’t just survive change; you lead it. This mindset shifts you from a “fixed” professional to an adaptable one, making you indispensable in an economy that prizes agility above all else.

 

How to Cultivate the Habit
A love for learning is like a muscle. If you don’t use it, it weakens. But you can strengthen it with a few simple shifts in your daily routine.

  • Stay Humble: Admit when you don’t know something. It is the only way to open the door to new information.
  • Follow Your Interests: Do not just learn what you think you “should” learn. Follow the topics that actually excite you. Passion makes the process effortless.
  • Make it Social: Share what you are learning with others. Discussing a new idea is often the best way to solidify it in your own mind.

 

The Bottom Line The world is moving faster than ever, and the amount of information available to us is staggering. In this environment, a love for learning is not just a “nice to have” trait. It is your survival kit.

It is the thing that keeps you relevant at work, engaged at home, and curious about the world around you. Knowledge might expire, but the hunger to find it never does.