Working closely with leadership teams as a fractional CTO on technology and digital initiatives over the years has taught me that projects rarely fail due to bad intentions or a lack of effort.
More often, they drift off course because certain behaviours, usually subtle at first, begin to distort decision-making, communication, and trust. These behaviours are not always obvious, and they are rarely labelled as incompetence at the time. They often present as authority, urgency, or experience.
Only later do their effects become clear.
This article isn’t about psychology in the academic sense, as I am nowhere a subject matter expert in this field. It’s a reflection on patterns I’ve repeatedly observed in real organisations, and how those patterns quietly introduce friction into otherwise capable teams and partnerships.
My observations are:
When control becomes more important than outcomes
One of the earliest warning signs I’ve seen is when leaders appear less concerned with whether a solution works, and more concerned with maintaining control over how decisions are made.
This often shows up as unnecessary intervention in areas outside their direct responsibility, or repeated changes in direction without clear reasoning. These actions are usually justified as “keeping standards high” or “protecting the business,” but the practical effect is confusion within teams and erosion of ownership.
When people sense that decisions are being overridden without explanation, they stop thinking proactively. Energy shifts from problem-solving to self-protection, and delivery slows, not because the team lacks skill, but because clarity has been replaced by caution.
Creating ambiguity to retain relevance
Another pattern I’ve seen is the deliberate or unconscious creation of ambiguity. For example, I’ve seen programme sponsors redefine ‘success’ three times during a transformation, leaving teams unsure what they were actually delivering.
Instead of defining success clearly, some leaders keep goals loosely worded or frequently reinterpreted. This makes progress difficult to measure and allows decisions to be reframed after the fact. When outcomes are unclear, accountability becomes selective.
In these environments, meetings increase, documentation multiplies, and debates repeat, yet direction remains elusive. What looks like complexity is often a lack of commitment to clear decisions, and teams are left navigating moving targets.
Using urgency as a shield
Urgency is a powerful tool, and in the right context it can be healthy. But I’ve also seen urgency used to shut down discussion, bypass challenge, or avoid uncomfortable questions.
Phrases like “we don’t have time for this” or “let’s just get on with it” can prevent teams from addressing foundational issues early. Over time, this creates rework, frustration, and delivery risk, the very things urgency was meant to avoid.
In practice, genuine pace comes from alignment. Artificial urgency usually signals unresolved thinking.
Ignoring data sets that help better decisions
Another quiet but damaging pattern appears when relevant data is available, but selectively ignored because it challenges a preferred narrative.
In many organisations, dashboards, reports, and historical trends exist to inform better decisions, yet they are sometimes dismissed as “too detailed,” “not the full picture,” or simply inconvenient. This often happens when data contradicts senior assumptions or exposes uncomfortable trade-offs. Instead of using evidence to refine direction, decisions are driven by instinct, hierarchy, or past experience that may no longer apply. Over time, this creates a widening gap between what the data is signalling and what the organisation chooses to act on.
The result isn’t just poorer outcomes, it erodes trust with partners and teams who can clearly see the signals, but are repeatedly asked to ignore them.
Shifting blame while retaining authority
In struggling projects, it’s common to hear delivery teams or partners blamed for lack of progress. What’s less often examined is whether the original direction was clear, consistent, or realistic.
I’ve observed situations where leaders distance themselves from outcomes while continuing to control decisions. This creates a one-way accountability model: authority remains centralised, but responsibility is distributed downward.
The result is predictable. Trust erodes, partners become cautious, and teams focus on compliance rather than outcomes. One of the most common demonstration of this behaviour is ignoring expert advice, and the person in the process.
Protecting behaviours that follow the line
One of the most persistent patterns I’ve witnessed is that when incompetence exists at senior levels, it is rarely isolated. It is often reinforced by a surrounding set of behaviours designed to protect it.
This typically shows up in the form of leaders favouring those who align unquestioningly with their decisions, rather than those who ask difficult or clarifying questions. Over time, people learn that survival depends less on contribution and more on compliance.
A common example is when individuals who raise genuine concerns or alternative viewpoints are labelled as “difficult,” “negative,” or “not aligned,” while those who agree publicly – regardless of delivery quality – are rewarded with influence, visibility, or safety.
The effect on teams is profound. Capable people either disengage, leave, or stop speaking up. Decision-making becomes increasingly narrow, risk is hidden rather than managed, and group thinking replaces independent judgement. What appears on the surface as harmony is often fear-driven alignment.
In partnerships, this dynamic is particularly damaging. External advisors or delivery teams are subtly encouraged to “fall in line” rather than challenge assumptions. Short-term agreement is achieved, but long-term value is sacrificed.
In my experience, this is one of the clearest signals that a project is being shaped around protecting positions rather than delivering outcomes.
Why these behaviours persist
These patterns are rarely driven by malice. More often, they emerge in environments where:
- Admitting uncertainty feels risky
- Authority is closely tied to personal identity
- Decision-making is under constant scrutiny
- Personal agendas form consensous
- Programme success is seen as a threat
In such conditions, behaviour shifts toward protecting position rather than enabling progress. Ironically, this protection often introduces exactly the instability leaders are trying to avoid.
What effective leadership does differently
In contrast, the most effective leaders I’ve worked with create clarity early and revisit it often. They are explicit about what they know, what they don’t, and what still needs to be explored. They invite challenge, not as a test of loyalty, but as a safeguard against blind spots. When decisions are made, they explain the reasoning, even when others disagree.
This approach doesn’t slow teams down – it accelerates them. People work with confidence when direction is stable and intent is transparent.
A shared responsibility in partnerships
Strong partnerships are not built on confidence alone. They are built on clarity, trust, and a willingness to address friction before it becomes failure.
As a CTO working across multiple organisations, much of my effort goes into surfacing ambiguity early, asking difficult questions respectfully, and helping leadership teams translate intent into shared understanding. Not because it’s comfortable, but because it prevents chaos later.
Strong leadership cannot eliminate uncertainty. It prevents uncertainty from becoming disorder.
A final reflection
Taken together, these patterns follow a familiar trajectory. Control replaces clarity, ambiguity substitutes decision-making, urgency suppresses challenge, accountability drifts away from authority, and compliance is rewarded over competence.
None of these behaviours appear disruptive in isolation. Many are even defended as “strong leadership” in the moment. But collectively, they create environments where confusion compounds, trust erodes, and capable teams are quietly disempowered.
This is where good partnerships either strengthen or quietly begin to fail.
In my experience, the organisations that avoid this trap are not those with the loudest confidence or the fastest pace, but those willing to confront uncomfortable dynamics early, name blockers honestly, and prioritise shared understanding over personal protection.
Incompetence rarely announces itself; it hides in behaviours that feel safe in the moment and expensive in the long run.
