Archive

Management

Marshall’s Law

‘Managers cannot afford to be seen to have studied.’

That’s it. That’s the law.

And yet it explains so much about why organisations remain stubbornly, wilfully ignorant of decades of research into what makes collaborative knowledge work actually work.

The Dynamic

Think about it. Deming, Ackoff, Seddon, Goldratt, Herzberg, McGregor, Rosenberg – the literature on effective organisations is vast, accessible, and largely uncontested. The evidence is in. Has been for decades. So why does almost nothing change?

Because for a manager to act on this research, they’d first have to admit they’d read it. And to admit they’d read it is to invite the question: ‘If you knew all this, why haven’t you been doing it?’

It’s a trap. A beautiful, self-reinforcing trap.

Roots in the Playground

If this dynamic feels familiar, it should. It starts early. Any boy who’s been through school knows the rules: don’t be seen to have studied. Don’t be seen to care about lessons. Don’t be seen to have tried. The kid who aces the test must do so effortlessly – or face being labelled a nerd, a swot, a try-hard. The social penalty for visible effort is swift and brutal. Willis documented this brilliantly in his study of working-class lads in the Midlands – the counter-school culture where academic effort was the ultimate betrayal of the group. Jackson’s later research confirmed the pattern extends to girls too, coining the term ‘ladettes’ for the female equivalent of the same anti-study posturing.

We like to think people grow out of this. They don’t. They just swap the playground for the open-plan office. The same dynamic that made teenage boys hide their textbooks now makes managers hide their Deming. The same social calculus that punished the studious child punishes the learning executive. The labels change – from ‘nerd’ to ‘out of touch’ or ‘academic’ – but the underlying message is identical: knowing things is fine, being seen to have learnt them is not.

The Unwritten Rules

In most organisations, managers are expected to already know how to manage. It’s supposed to come naturally, like some innate gift bestowed upon promotion. Studying – actually reading books, engaging with research, attending to the evidence – implies you don’t already know. And that’s career-threatening.

Better to wing it. Better to rely on gut instinct, received wisdom, and whatever the last conference speaker said. Better to be confidently wrong than to be seen learning.

The Cost

The cost is staggering. Organisations full of intelligent, motivated people consistently underperform – not because the knowledge of how to do better doesn’t exist, but because the people in positions to act on that knowledge cannot afford to be seen possessing it.

And so the same dysfunctions persist. The same mistakes recur. The same research goes unread. Generation after generation of managers reinvent the same square wheels, because admitting someone else had already invented the round one would mean admitting they’d bothered to look.

A Cultural Problem

Marshall’s Law isn’t about individual managers being lazy or stupid. It’s about a culture – the prevailing organisational culture – that punishes learning and rewards the appearance of innate competence. A culture where ‘I read a book about this’ is heard as weakness, and ‘I just know’ is heard as strength.

Until that culture changes, the research will continue to gather dust. And organisations will continue to wonder why things never seem to get any better.


Marshall’s Law was first stated on Twitter (now defunct), circa 2012–2015. This post gives it a permanent home.


Further Reading

Ackoff, R. L. (1999). Re-creating the corporation: A design of organizations for the 21st century. Oxford University Press.

Deming, W. E. (1986). Out of the crisis. MIT Center for Advanced Engineering Study.

Goldratt, E. M., & Cox, J. (1984). The goal: A process of ongoing improvement. North River Press.

Herzberg, F. (1968). One more time: How do you motivate employees? Harvard Business Review, 46(1), 53–62.

Jackson, C. (2006). Lads and ladettes in school: Gender and a fear of failure. Open University Press.

Marshall, R. W. (2018). Hearts over diamonds: Serving business and society through organisational psychotherapy. Falling Blossoms.

Marshall, R. W. (2021). Quintessence: An acme for software development organisations. Falling Blossoms.

McGregor, D. (1960). The human side of enterprise. McGraw-Hill.

Rosenberg, M. B. (2003). Nonviolent communication: A language of life (2nd ed.). PuddleDancer Press.

Seddon, J. (2003). Freedom from command and control: A better way to make the work work. Vanguard Consulting.

Willis, P. (1977). Learning to labour: How working class kids get working class jobs. Saxon House.

The Software Crisis: An Opportunity for Go-Ahead Managers to Step Up and Stand Out

In 1968, at the NATO Software Engineering Conference, computer scientists first coined the term ‘software crisis’ to describe projects routinely exceeding budgets, missing deadlines, and delivering unreliable systems. Nearly 60 years later, the same fundamental problems persist. Projects still exceed budgets by 200-300%, timelines slip by months or years, and technical debt accumulates faster than teams can address it.

This isn’t an acute crisis—it’s a chronic condition of the software industry. And that creates an extraordinary opportunity for leaders willing to recognise what six decades of industry leaders have largely missed: the software crisis represents the ultimate leadership vacuum.

Understanding the Persistence of the Problem

The longevity of these challenges is remarkable. The issues identified at that 1968 NATO conference—cost overruns, schedule delays, maintenance difficulties, and unreliable software—read like a checklist of today’s software development problems. According to recent industry surveys, 70% of software projects still fail to meet their original scope, timeline, or budget requirements. The average enterprise maintains over £1.2 million in technical debt, whilst developer productivity has actually declined despite advances in tooling and methodologies.

This persistence reveals a profound truth: the software crisis isn’t fundamentally a technical problem—it’s an organisational problem that has resisted solution for generations. Tools, languages, and platforms have evolved dramatically since 1968, but the underlying organisational challenges remain largely unchanged.

What’s changed is the stakes. Software was once a specialised tool used by large corporations and research institutions. Today, it’s the foundation of nearly every business operation and customer interaction. The cost of poor software management has multiplied exponentially, but so has the value of getting it right.

The Hidden Opportunities in Six Decades of Failure

The persistence of software challenges creates extraordinary opportunities for leaders who can succeed where generations have struggled. After 60 years of industry-wide failure to solve these fundamental problems, the leaders who can deliver consistent results become exceptionally valuable. Here’s what’s separating the rare successes from decades of disappointment:

Market Positioning Through Reliability Whilst competitors struggle with delayed launches and buggy releases, organisations that master software delivery gain enormous market advantages. Customers increasingly value reliability over flashy features. The leader who can consistently deliver working software on time becomes invaluable to their organisation and attractive to competitors.

Talent Magnetism Through Better Processes Top developers actively seek organisations with mature development practices. By implementing modern DevOps, continuous integration, and collaborative development environments, leaders can attract and retain the best talent—creating a virtuous cycle of improvement and innovation.

Executive Visibility Through Problem-Solving C-suite executives are acutely aware of software challenges affecting their business objectives. The leader who can articulate technical problems in business terms and deliver noticeable improvements gains unprecedented access to senior leadership and strategic decision-making.

Strategic Actions for Transformation Leaders

The path from crisis to opportunity requires deliberate action across multiple dimensions. Here’s how exceptional leaders are distinguishing themselves:

Invest in Developer Experience The best managers recognise that developer productivity directly impacts business outcomes. This means advocating for better tooling, reducing bureaucratic overhead, and creating environments where engineers can focus on attending to the needs of the Folks That Matter™ rather than fighting mandated processes. When developers are purposefully productive and engaged, quality improves and timelines become predictable.

Bridge the Communication Gap Technical teams and business stakeholders often speak different languages, leading to misaligned expectations and failed projects. Exceptional managers become translators, helping engineers understand business priorities whilst ensuring executives appreciate technical constraints and trade-offs. This translation capability becomes increasingly valuable as software becomes central to every business function.

Champion Incremental Innovation Rather than pursuing dramatic overhauls that often fail, smart managers focus attention on the way the work works. Small, consistent improvements to collective assumptions and beliefs compound into significant competitive advantages.

Build Cross-Functional Collaboration The days of throwing requirements over the wall to development teams are past. The search for success invites tight collaboration between product management, design, engineering, and operations. Managers who can orchestrate these cross-functional teams create more innovative solutions and faster time-to-market.

Practical Implementation Framework

Transforming the software crisis into career opportunity invites a systematic approach. Here’s a proven framework for making immediate impact:

Start with Quick Wins Have people identify the most painful bottlenecks in the current development approach and address them first. This might mean automating manual deployments, implementing code review standards, or establishing clear definition-of-startable and definition-of-done criteria. Quick wins build credibility and momentum for larger changes.

Invest in Your Team’s Growth The best managers understand that their success depends entirely on their team’s capabilities. Invire applications for training, conferences, and certification programmes. Encourage experimentation with new tools and methodologies. Enable internal knowledge-sharing sessions where team members can learn from each othe and from other parts of the business.

Communicate Success Stories Don’t assume your achievements will be noticed automatically. Regularly communicate improvements in business terms that executives understand. ‘We reduced deployment time from 4 hours to 20 minutes’ becomes ‘We can now respond to customer feedback 12 times faster and deploy revenue-generating features the same day they’re completed.’ Oh, and manage expectations above all.

Building Long-Term Leadership Capital

The leaders who thrive aren’t just solving immediate problems—they’re accomplishing what the industry has failed to achieve for six decades. This creates extraordinary personal leadership capital and sustainable competitive advantages.

Develop Technical Credibility You don’t need to become a programmer, but you need to understand the technical landscape well enough to participate in informed decision-making and ask insightful questions. Invest time in learning about emerging technologies. Technical credibility earns respect and enables better decision-making.

Cultivate Strategic Thinking Connect software development initiatives to broader business objectives. Understand how improved deployment practices enable faster market entry, how better quality reduces customer support costs, and how modern architectures support scalability. This strategic perspective makes you a valuable contributor to high-level planning.

Build External Networks Engage with the broader software development community through conferences, user groups, and online forums. Understanding industry trends and best practices helps you anticipate challenges and opportunities before they impact your organisation. This external perspective often provides innovative solutions to internal problems.

The Competitive Advantage of Solving the Unsolvable

Organisations that successfully transcend the software crisis don’t just survive—they emerge as rare exceptions in an industry that has struggled with the same fundamental problems for 60 years. The managers who lead these transformations establish themselves as having accomplished something that has eluded generations of industry leaders.

Consider that the software crisis has outlasted entire technological revolutions. We’ve moved from mainframes to personal computers to mobile devices to cloud computing, yet the same challenges persist. This suggests that the solutions aren’t primarily technological—they’re leadership solutions that most managers have failed to implement successfully.

The career trajectories of the rare managers who have successfully led software transformations are telling. Many now hold C-suite positions at major corporations, serve on boards of technology companies, or lead successful startups. They’ve distinguished themselves by solving problems that most of their peers couldn’t address despite decades of industry attention.

The Courage to Stand Out: Confronting FOSO in Software Leadership

Before embarking on the journey to solve the software crisis, it’s crucial to acknowledge a significant psychological barrier that has contributed to its 60-year persistence: the Fear of Standing Out (FOSO). Like zebras finding safety in the anonymity of the herd, many capable managers have quasi-rational reasons for avoiding the visibility that comes with tackling transformational challenges.

Understanding FOSO isn’t about overcoming a character flaw—it’s about recognising a legitimate protective mechanism. The software development manager who notices fundamental process problems but keeps quiet has likely observed what happens to colleagues who “rock the boat.” They’ve seen eager managers volunteer for transformation initiatives, only to find themselves burdened with unrealistic expectations, working longer hours for the same compensation, and becoming targets during organisational restructuring.

In many organisations, standing out means standing in the line of fire. The manager who proposes significant changes becomes responsible for their success, often without additional resources or authority. When these initiatives face inevitable setbacks—and software transformations always encounter obstacles—the visible leader bears the blame whilst those who stayed safely in the background remain protected.

This dynamic helps explain why the software crisis has persisted across generations of managers. It’s not that capable leaders haven’t recognised the problems; it’s that many have made calculated decisions to prioritise job security and work-life balance over the risks of high-visibility transformation efforts. They understand that acclaim and its inevitable bedfellow, opprobrium, arrive as a package deal. The manager who successfully transforms software delivery will certainly receive recognition—but they’ll also face criticism from those who resent change, colleagues who question their methods, and stakeholders who focus on any shortcomings rather than overall progress.

For managers supporting families or operating in volatile industries, avoiding this double-edged sword of visibility often makes perfect sense.

However, confronting the software crisis requires accepting that meaningful change demands courage and calculated risk-taking. Machiavelli understood this challenge centuries ago when he observed:

“There is nothing more difficult to take in hand, more perilous to conduct, or more uncertain in its success, than to take the lead in the introduction of a new order of things, because the innovator has for enemies all those who have done well under the old conditions, and lukewarm defenders in those who may do well under the new.”

This wisdom proves particularly relevant to software transformation efforts. The manager proposing modern development ideas will face resistance from those comfortable with existing ways of doing things, scepticism from colleagues who’ve seen previous initiatives fail, and tepid support even from those who might benefit from improvements. The managers who successfully lead software transformations understand they’re choosing growth over safety, opportunity over security, whilst accepting Machiavelli’s warning about the inevitable opposition that accompanies meaningful change.

Mitigating the Risks of Leadership

For managers considering stepping forward, the key isn’t eliminating risk—it’s managing it intelligently:

Build Political Capital First: Before proposing major changes, establish credibility through smaller successes. Demonstrate competence in low-risk scenarios before taking on transformation initiatives.

Secure Stakeholder Buy-In: Ensure senior leadership genuinely supports the initiative, not just in principle but with resources and protection from political fallout.

Create Shared Ownership: Frame transformation as collaborative effort rather than personal crusade. Share credit generously whilst maintaining clear accountability for results.

Document Everything: Maintain clear records of decisions, constraints, and progress. This protection becomes invaluable when initiatives face criticism or when leadership changes.

Develop Exit Strategies: Understand your market value and maintain external networks. Confidence in your ability to land elsewhere reduces the fear of organisational retaliation.

The choice to address the software crisis isn’t just about ambition—it’s about consciously deciding that the potential rewards justify the genuine risks. This decision requires honest assessment of your financial situation, career goals, and tolerance for organisational turbulence. There’s no shame in choosing security over growth, but there’s also tremendous opportunity for those willing to stand out thoughtfully and strategically.

Your Moment to Solve the Unsolved

The software crisis has persisted for 60 years, outlasting countless technological revolutions and management fads. This isn’t a temporary opportunity—it’s an evergreen challenge that the vast majority of managers have chyosen to avoid across multiple generations.

The persistence of these problems means two things: they’re genuinely difficult to solve, and the managers who do solve them become extraordinarily valuable. When an entire industry struggles with the same fundamental challenges for six decades, success becomes a rare, precious and notable career asset.

The question isn’t whether your organisation will eventually solve its software challenges—it’s whether you’ll be amongst the rare managers who accomplish what generations of industry leaders have failed to achieve, or whether you’ll join the long list of those who tried and fell short, or the even longer list of those that never even tried.

The software crisis is real, the challenges are significant, and after 60 years, the stakes are as high as they ever were. But for managers willing to step up, learn, and lead, this persistent challenge represents not just a career opportunity, but a chance to join the ranks of those who’ve solved one of the industry’s most enduring problems.

The question is: will you be the manager who finally cracks the wall of indifference that has plagued the industry for six decades?

Further Reading

Boehm, B. W. (1981). Software engineering economics. Prentice-Hall.

Brooks, F. P. (1995). The mythical man-month: Essays on software engineering (Anniversary ed.). Addison-Wesley.

DeMarco, T., & Lister, T. (2013). Peopleware: Productive projects and teams (3rd ed.). Addison-Wesley.

Deming, W. E. (1986). Out of the crisis. MIT Press.

Glass, R. L. (1998). Software runaways: Lessons learned from massive software project failures. Prentice Hall.

Jones, C. (2013). The economics of software quality. Addison-Wesley.

Naur, P., & Randell, B. (Eds.). (1969). Software engineering: Report of a conference sponsored by the NATO Science Committee. NATO Scientific Affairs Division.

Standish Group. (2020). CHAOS 2020: Beyond infinity. The Standish Group International.

Tribus, M. (1992). Quality first: Selected papers on quality and productivity improvement (4th ed.). National Society of Professional Engineers.

Yourdon, E. (2003). Death march (2nd ed.). Prentice Hall.

The Assumption Prison

Why Management Remains Immune to Transformative Ideas

The Invisible Architecture of Resistance

Core assumptions function like cognitive prison walls that are invisible to those inside them. And doublyt so for shared collective assumptions. When W. Edwards Deming suggested that most problems stem from systems rather than individuals, he wasn’t just proposing a different technique—he was attacking the core assumption that management’s primary role is controlling and evaluating people. This assumption is so fundamental to managerial identity that alternatives become literally unthinkable.

The power of core assumptions lies in their invisibility. They operate as unexamined premises that shape every subsequent thought and decision. A manager who assumes that people are primarily motivated by external rewards will interpret every workplace phenomenon through this lens, making it nearly impossible to recognise evidence that intrinsic motivation might be more powerful. The assumption becomes self-reinforcing because it filters out contradictory information.

A Case Study in Assumption Collision

The story of Deming’s System of Profound Knowledge (SoPK) offers a fascinating lens through which to examine why transformative management ideas so often fail to take hold. Deming’s influence began in Japan in 1950, where manufacturers rebuilding after World War II embraced his teachings with remarkable dedication. Japanese companies like Toyota, Sony, and Honda became exemplars of his principles, developing what became known as the Japanese management philosophy.

Yet Deming’s home country, the United States, was slow to adopt his ideas. It wasn’t until the 1980 NBC documentary “If Japan Can… Why Can’t We?” that American businesses began paying serious attention—and only then because competitive threats forced them to reconsider their management approaches. Even when American companies finally embraced quality management, they typically fragmented Deming’s holistic System of Profound Knowledge into discrete tools and methodologies, missing the interconnected nature he emphasised.

Today, few are the organisations explicitly implementing Deming’s complete philosophy. Whilst fragments survive in e.g. Lean manufacturing, Six Sigma, and agile methodologies, the integrated framework that challenged fundamental assumptions about management has largely faded from view. This pattern raises a troubling question: Are managers themselves the least fertile ground for transformative ideas?

The Managerial Filtering Mechanism

Managers operate as intellectual gatekeepers, but their filtering criteria often screen out genuinely novel ideas in favour of those that appear innovative whilst preserving existing power structures. A truly revolutionary management concept fundamentally threatens managerial identity and authority. It’s much safer to adopt superficial changes that maintain the illusion of progress without challenging core assumptions about hierarchy, control, and decision-making authority.

This creates what might be called “innovation theatre”—organisations enthusiastically adopt new management frameworks, methodologies, and buzzwords whilst carefully avoiding ideas that would require fundamental changes to how managers actually manage. The result is a constant churn of management fads that promise transformation whilst delivering incremental tweaks to existing practices.

The managerial role itself may be antithetical to deep intellectual engagement with new ideas. Managers are rewarded for decisiveness, confidence, and the appearance of control—qualities that conflict with the intellectual humility required to genuinely consider that one’s fundamental assumptions might be dysfunctional. Admitting that a new idea requires abandoning years of learned practices and accumulated expertise carries significant career risk.

The Architecture of Resistance

Core assumptions create what might be called “cognitive architecture”—they determine not just what we think, but what we’re capable of thinking. When an idea challenges fundamental assumptions, it doesn’t just face disagreement; it faces incomprehension. The idea literally doesn’t make sense within the existing framework.

Consider how Deming’s assertion that numerical goals and performance rankings harm performance struck most managers as obviously wrong. Within their assumption set—that measurement drives performance, that competition motivates excellence, that individual accountability ensures results—his claim appeared nonsensical. The problem wasn’t that they evaluated his evidence and found it lacking; they couldn’t process the evidence because it didn’t fit their conceptual framework.

Organisations develop elaborate systems to protect core assumptions from challenge. Performance management systems, budgeting processes, organisational structures, and reward mechanisms all reinforce fundamental beliefs about how work gets done and what motivates people. These systems create a self-contained logic that makes alternative approaches appear irrational, impractical, or incomprehensible.

When someone proposes an idea that challenges core assumptions, the organisation’s immune system activates. The idea gets labelled as unrealistic, academic, idealistic, or inappropriate for “our culture”. This isn’t conscious resistance—it’s the natural response of a system protecting its foundational beliefs from existential threat.

The Assumption Hierarchy

Not all assumptions are created equal. Surface-level assumptions about techniques or tools can change relatively easily. Mid-level assumptions about organisational structure or processes require more effort but remain possible. But core assumptions about human nature, the purpose of management, and how organisations create value resist change because questioning them threatens the entire edifice of beliefs built upon them.

Deming’s System of Profound Knowledge challenged assumptions at every level simultaneously. It questioned surface assumptions about quality control methods, mid-level assumptions about organisational structure and measurement systems, and core assumptions about human psychology and the nature of knowledge itself. This comprehensive challenge to the assumption stack explains why it was either rejected entirely or fragmented into superficial tools that preserved underlying beliefs.

The Consultant-Manager Ecosystem

The management consulting industry has evolved to serve managerial psychology rather than organisational improvement. Consultants succeed by making managers feel intelligent and in control, not by challenging their fundamental assumptions. This creates a market for ideas that appear sophisticated but don’t threaten existing power structures.

Consider how Deming’s System of Profound Knowledge was received versus how McKinsey-style frameworks are embraced. SoPK demanded that managers acknowledge their limited understanding of complex systems and commit to years of learning. McKinsey’s approach offers elegant matrices and clear action steps that preserve managerial authority whilst providing the appearance of strategic sophistication.

Professional managerial culture emphasises action over reflection, implementation over contemplation. This bias towards doing rather than thinking creates impatience with ideas that require extended intellectual engagement. Concepts like psychology or systems thinking or understanding variation require sustained mental effort and tolerance for ambiguity—qualities that may be selected against in typical managerial career paths.

The Innovation Impossibility

This reveals why genuine management innovation is so rare. True innovation requires not just new techniques or processes, but new assumptions about fundamental questions: What is the purpose of an organisation? How do people learn and change? What creates sustainable performance? How should resources be allocated? What role should managers play? Might we do better by eschewing management entirely?

Most “management innovations” are actually variations within existing assumption sets. They rearrange surface elements whilst preserving core beliefs. Genuine innovation would require assumption replacement, which is psychologically threatening and practically disruptive in ways that few individuals or organisations can tolerate.

Many transformative management ideas originate in academic settings where researchers have the luxury of deep, sustained investigation. However, the translation from academic insight to managerial practice often requires simplification that strips away the very nub that made the original idea valuable. Managers invite actionable frameworks, not nuanced theories that require careful study and adaptation.

The Generational Trap

Core assumptions often persist across generations of managers because they’re embedded in educational systems, professional development programmes, and organisational cultures. Business schools teach frameworks based on particular assumptions about markets, competition, and human behaviour. These become so deeply ingrained that graduates literally cannot imagine alternatives.

The tragedy is that many of these assumptions may have been reasonable responses to historical conditions but become counterproductive as circumstances change. The assumption that organisations must be hierarchical might have made sense in stable, predictable environments but becomes a liability in rapidly changing conditions. Yet the assumption persists because it’s foundational to how we conceive of organisations.

Managers are typically promoted based on their success within existing systems, creating a selection bias towards those who work well within current paradigms. This process systematically filters out individuals who might be more receptive to genuinely disruptive ideas. The people who reach senior management positions are often those least likely to question the systems that elevated them.

Alternative Fertile Ground

Interestingly, transformative management ideas often find more receptive audiences outside traditional management hierarchies. Engineers embracing statistical process control, healthcare workers implementing improvement methodologies, or software developers adopting agile practices often show greater intellectual openness than “professional” managers.

This suggests that operational expertise and direct contact with work systems (i.e. normative learning) may create more fertile ground for new ideas than managerial abstraction from actual work processes. People closer to the work may be more willing to acknowledge system limitations because they experience them directly, whilst managers often view problems through layers of reports and metrics that obscure underlying realities.

The Systems Assumption

Perhaps the most fundamental assumption governing management thinking is reductionism—the belief that complex phenomena can be understood by breaking them into component parts. This assumption makes managers comfortable with organisational charts, departmental silos, individual performance metrics, and linear cause-and-effect thinking. (The Analytic Mindset).

Deming’s systems thinking challenged this core assumption by suggesting that organisational performance emerges from interactions between components rather than from the performance of individual parts. (The Synergistic Mindset). This wasn’t just a different technique—it was a different way of understanding reality itself. No wonder it proved nearly impossible to implement fully.

The Contemporary Paradox

Organisations desperately need innovation in management thinking—the challenges of climate change, inequality, technological disruption, and global complexity require management approaches that don’t yet exist. Yet the very people responsible for implementing new approaches may be incapable of recognising or adopting truly transformative ideas.

This creates a disturbing possibility: that management as currently practised may be fundamentally incompatible with the level of organisational learning and adaptation required for 21st-century challenges. The constant cycling through management fads might represent not the search for better ideas, but the systematic rejection of ideas that would require managers to fundamentally reconceptualise their role and methods.

Breaking Free from the Prison

If change requires assumption change, then the question becomes: How do assumptions actually change? History suggests they change through crisis, generational replacement, or encounters with undeniable contradictory evidence. Perhaps the current convergence of climate change, technological disruption, and social transformation will create conditions where existing management assumptions become obviously inadequate.

The path to genuine change might require what could be called “assumption archaeology”—the careful excavation and examination of beliefs that have become so automatic they’re no longer consciously recognised. Organisations serious about transformation would need to create spaces for assumption examination—processes that make the invisible visible and create safety for questioning foundational beliefs.

This suggests a need for something akin to organisational psychotherapy—a disciplined approach to surfacing and examining the unconscious beliefs that drive organisational behaviour. Just as individual therapy helps people recognise and change destructive patterns of thinking, organisational psychotherapy helps institutions identify and transform the assumption sets that keep them trapped in dysfunctional cycles. This process requires skilled facilitators (a.k.a. therapists) capable of creating safe spaces within which organisations might surface and reflect on their collective assumptions and beliefs. I also invites  organisations to be brave enough to confront the possibility that their most fundamental operating principles might be counterproductive.

Alternatively, change might emerge from the edges—from organisations or sectors where traditional assumptions never took hold strongly, or from interdisciplinary approaches that import assumptions from other fields. The rise of design thinking, systems thinking, and behavioural economics might represent the gradual infiltration of different assumption sets.

The Way Forward

The challenge isn’t convincing managers that new ideas are better—it’s creating conditions where different fundamental assumptions become not just thinkable, but necessary for survival. This might require a different type of manager altogether—individuals selected and developed for intellectual curiosity, systems thinking, and willingness to challenge their own assumptions rather than for traditional managerial competencies like decisiveness and control.

Or perhaps the solution lies in abandoning the concept of “management” entirely. If the managerial role is structurally incompatible with the kind of adaptive learning organisations now need, then the answer may not be better managers but different organising principles altogether. This would mean moving towards models based on distributed leadership, self-organising teams, and emergent coordination—approaches that eliminate the assumption prison by eliminating the role that embodies it most completely.

The story of Deming’s ideas—their global spread, fragmentation, and ultimate transformation into something quite different from what he envisioned—illustrates both the power and the limitations of trying to change organisations from within existing paradigms. His work succeeded where it aligned with existing assumptions and failed where it challenged them most fundamentally.

Understanding this dynamic offers hope for those seeking genuine organisational transformation. By recognising the assumption prison that constrains management thinking, we can begin to design approaches that work around or through these constraints. The key lies not in better arguments for new ideas, but in creating conditions where new assumptions become inevitable.

The most profound management innovations may not come from management at all, but from the gradual recognition that our fundamental assumptions about how organisations work, how people learn, and how change happens need to be completely reimagined. Only then can we escape the assumption prison and build organisations truly capable of addressing the challenges ahead.

Further Reading

Argyris, C. (1990). Overcoming organizational defenses: Facilitating organizational learning. Allyn & Bacon.

Argyris, C., & Schön, D. A. (1978). Organizational learning: A theory of action perspective. Addison-Wesley.

Deming, W. E. (1986). Out of the crisis. MIT Press.

Deming, W. E. (1993). The new economics for industry, government, education. MIT Press.

Gabor, A. (1990). The man who discovered quality: How W. Edwards Deming brought the quality revolution to America—in the stories of Ford, Xerox, and GM. Times Books.

Kanter, R. M. (1983). The change masters: Innovation and entrepreneurship in the American corporation. Simon and Schuster.

Kuhn, T. S. (1962). The structure of scientific revolutions. University of Chicago Press.

Laloux, F. (2014). Reinventing organizations: A guide to creating organizations inspired by the next stage of human consciousness. Nelson Parker.

Senge, P. M. (1990). The fifth discipline: The art and practice of the learning organization. Doubleday.

Walton, M. (1986). The Deming management method. Dodd, Mead & Company.

Do Project Managers Realise They’re Obsolete?

The Tech Industry’s Quiet Revolution Against Traditional PM Roles

The tech industry has been running a quiet experiment for the past decade, and the results are brutal for traditional project managers. Whilst PMPs keep updating their LinkedIn profiles with shiny new certifications, most successful tech companies have quietly ditched project management roles. They’re using self-organising teams and product-focused approaches instead.

The harsh truth? Many project managers in tech are desperately hanging onto jobs that the industry has already moved past.

What’s Wrong with Projects Anyway?

Before we talk about why project coordinators are becoming irrelevant, let’s be honest about why the whole project approach is broken in tech. (See also: #NoProjects)

Projects create fake deadlines for work that never really ends. Your app doesn’t magically stop needing updates when the ‘project’ finishes. But projects pretend everything has a neat beginning, middle, and end. This is ridiculous in tech where products need more or less constant updates.

Projects also focus on the wrong stuff. Instead of asking ‘did we solve the customer’s problem?’ they ask ‘did we hit our deadline and stay on budget?’ Teams end up caring more about finishing the project than building something people actually need.

And here’s the kicker—projects waste tons of time on planning and meetings. How many hours do tech teams spend in status meetings, writing reports, and sitting through steering committee presentations? All that time could be spent actually building stuff.

The biggest problem? Projects break up teams just when they’re getting good at working together. You spend months learning how the code works, understanding the business, and figuring out how to collaborate. Then the project ends and everyone gets shuffled to different teams. It’s insane.

The #NoProjects Revolution

The #NoProjects movement, started by folks like P G Rule and FlowChainSensei, isn’t just complaining about projects. They’ve got a better way.

Instead of temporary projects, successful tech companies now use persistent product teams. These teams stick together and own their product long-term. No more ‘hand it off to maintenance’ nonsense. If you build it, you keep updating it.

This isn’t just theory. Companies like Spotify, Netflix, and Amazon prove it works. They organise around products, not projects. Their teams stay together, learn deeply about their domain, and can move fast because they’re not constantly starting over.

The #NoProjects crowd figured out that the problem wasn’t bad project coordination—it was the whole idea of projects in the first place. When you stop trying to force continuous work into temporary boxes, everything gets easier.

Self-Organising Teams: The Coordinator Killer

Self-organising teams in tech have basically made traditional project managers irrelevant. These teams have developers, designers, product people, and QA folks who collectively own their work. They don’t need someone else to coordinate for them.

Here’s what’s wild—these teams often move faster than teams with dedicated project managers. When six smart people can figure out their own priorities, plan their own work, and make their own decisions, why add another layer of oversight?

The best part? These teams actually understand the technical work they’re doing. They can make smart tradeoffs between features and technical debt. They know when to cut scope and when to push back on unrealistic deadlines. Traditional project managers usually don’t have that technical depth.

Product People Ate Their Lunch

Whilst project managers were busy updating their Gantt charts, product specialists swooped in and took over the strategic parts of their job. Product people combine market knowledge, technical understanding, and execution skills in ways project managers never did.

Product specialists own outcomes, not just timelines. They decide what to build, understand why it matters, and can make calls about technical tradeoffs. They’re not just coordinating other people’s work—they’re directly contributing to the product’s success.

Many companies discovered that a strong product specialist working with a self-organising engineering team gets better results than the old project manager + team structure. Product people bring strategic thinking that traditional PMs usually lacked. Better yet, have the self-organising engineering team also be or become the product domain specialists.

Agile Killed the Project Manager Star

Agile development pretty much destroyed the traditional project management playbook. Agile is all about working software over documentation, people over processes, and responding to change over following plans. That’s the exact opposite of traditional project management.

Most companies that have adopted Agile have tried to rebrand their project managers as Scrum Masters at first. But that mostly fails because good Scrum Masters need to understand the technical work, whilst traditional project managers usually don’t have that background.

The DevOps Bump

DevOps eliminated a lot of the handoff problems that project managers used to handle. When development teams own their own deployment, monitoring, and production support, there’s way less coordination needed.

Modern tech teams do continuous integration, infrastructure as code, and automated testing. Code flows from development to production with minimal human coordination. When this stuff is automated, what exactly is the project manager coordinating?

The ‘you build it, you run it’ philosophy means teams are responsible for their stuff end-to-end. This eliminates the need for someone to handle handoffs between development and operations teams.

Startups Don’t Use Project Managers

The most telling evidence comes from startups. Most successful tech startups operate without any dedicated project managers. They use self-organising teams, clear product vision, and direct communication.

Startups that try to add traditional project management usually find it slows them down. All the planning meetings and status reporting kill their ability to move fast and adapt quickly.

When startups do eventually need more coordination, they hire product specialists, engineering leads, or technical programme leads—roles that combine coordination with domain expertise and direct value creation.

Enterprise Companies Are Catching On

Even big, slow enterprise companies are starting to figure this out. Their most innovative teams usually operate with minimal traditional project management oversight. Internal studies keep showing that self-organising teams with clear product ownership deliver better results faster.

The enterprises still clinging to traditional project management are finding themselves at a competitive disadvantage. They’re slower to market and less able to adapt than competitors who’ve embraced product-focused, team-based approaches.

The Desperate Rebranding Campaign

Seeing the writing on the wall, lots of project  managers are frantically trying to rebrand themselves. They’re getting Scrum Master certifications, learning basic coding, or calling themselves ‘technical programme managers’ or ‘delivery leads.’

This rebranding reveals the profession’s fundamental problem. If traditional project management skills were still valuable, there wouldn’t be any need to constantly learn new skills and change job titles.

The most honest take? These aren’t career progressions—they’re career pivots. Project managers who successfully move into product roles, engineering leadership, or technical roles have basically admitted that traditional project management wasn’t enough.

The Bigger Picture: All Traditional Oversight Is Under Threat

But here’s the thing—project managers aren’t the only ones feeling the heat. The whole traditional hierarchy of ‘oversight’ and ‘supervision’ is crumbling in modern organisations, especially in tech.

Think about it: when teams are self-organising, when knowledge workers can make their own decisions, when tools automate most management tasks, what exactly do traditional supervisors do all day? The same forces killing project management are questioning the need for layers of oversight, period.

Netflix famously operates with minimal traditional hierarchy. Their teams make decisions, own outcomes, and course-correct without multiple layers of approval. Amazon’s two-pizza teams work similarly—small, autonomous groups that don’t need constant supervision to function effectively.

The pattern is clear: high-performing organisations are flattening their structures and empowering teams to operate independently. A few traditional command-and-control hierarchies are being replaced by networks of autonomous teams with clear missions and accountability for results.

Even the concept of ‘people oversight’ is evolving. Instead of supervisors who assign work and monitor progress, successful companies are moving towards coaching, mentoring, and servant leadership models. The focus shifts from controlling people to enabling them.

This isn’t just happening in tech startups. Even massive organisations like Spotify, Haier, and Morning Star have demonstrated that you can scale to thousands of employees without traditional hierarchical structures. When people are trusted to do their jobs and held accountable for outcomes, most traditional oversight becomes unnecessary toxic overhead.

The uncomfortable truth for anyone in a traditional oversight role: if your primary function is coordinating other people’s work, monitoring their progress, or making decisions they could make themselves, your role is probably next on the chopping block.

The Evidence Is Overwhelming

The #NoProjects movement isn’t just talk—it’s backed by real results. Companies that ditched traditional project structures report faster delivery, happier teams, better products, and lower costs.

These companies organise around persistent teams rather than temporary projects. They fund product areas instead of specific initiatives. They measure customer outcomes instead of just project completion metrics.

The success of these approaches proves that the problem wasn’t insufficient project management—it was the overhead and artificial constraints that project management created.

What This Means for Project Managers

The evidence from the tech industry is crystal clear: traditional project management has become largely obsolete in modern technology companies. Self-organising teams, product-focused structures, DevOps practices, and the #NoProjects movement have eliminated most of the management work that once justified project coordinator roles.

For project managers currently working in tech, the choice is simple: evolve or become irrelevant. You might choose to transition into a role that creates direct value through technical skills, product expertise, or strategic thinking.

The project managers who acknowledge this reality and successfully move into product roles, technical positions, or engineering leadership will survive. Those who keep insisting that traditional project management is still relevant will likely find themselves out of work as the industry continues moving forward without them.

The tech industry’s revolution against traditional project management is basically complete. The only question is whether individual project managers will adapt in time, or whether they’ll keep clinging to an obsolete profession whilst the industry moves on.

Why Progress Dies in the Executive Suite

The Great Management Reckoning

Across industries and organisations, we’ve witnessing something unprecedented, yet long overdue: a collective uprising from the very people who were meant to benefit from decades of management initiatives, transformation programmes, and cultural change efforts. Teams are no longer politely nodding along to leadership’s latest improvement campaigns. Instead, they’re delivering a blunt message: “If you can’t or won’t make the necessary changes to make this work, then frankly, sod off with all your exhortations.”

This isn’t just workplace grumbling about the latest fad. It’s a reckoning that’s been building for decades, spanning everything from Agile adoptions to diversity initiatives, from digital transformations to sustainability programmes.

The Pattern Repeats Everywhere

Whether it’s Agile adoption, DevOps transformation, digital-first strategies, environmental sustainability, diversity and inclusion efforts, or employee wellbeing programmes, the same depressing cycle plays out:

Leadership announces bold new directions. Consultants are hired. Frameworks are adopted. Teams are trained. Metrics are established. Progress is measured, celebrated, then quietly forgotten as the next initiative takes centre stage. Meanwhile, the fundamental organisational structures, incentive systems, and collective assumptions that created the original problems remain completely untouched.

I bet you’re so bored with the situation that this post solicits no more than a yawn.

Gallup’s employee engagement surveys tell the story with brutal clarity. Despite decades of management innovations, leadership development programmes, and cultural transformation efforts, roughly 70% of employees remain fundamentally disengaged at work. These figures have barely budged even as organisations have spent billions on change management, coaching, and improvement initiatives.

The Theatre of Change

What we’ve created instead is an elaborate theatre of change. Organisations implement the visible trappings of progress whilst steadfastly refusing to address the underlying power structures and cultural assumptions that make real change possible.

Teams are asked to “embrace innovation” whilst being buried under approval processes that kill creativity. They’re told to “think like owners” whilst being treated like replaceable cogs. They’re encouraged to “speak truth to power” whilst watching colleagues who do so get marginalised or managed out. They’re expected to deliver “customer-centric solutions” whilst working in silos that make customer focus nearly impossible.

The sustainability team produces glossy ESG reports whilst the business continues prioritising quarterly profits over long-term environmental impact. The diversity and inclusion programme runs unconscious bias training whilst the same homogeneous leadership makes all the important decisions. Ddigital transformation initiatives implement new tools whilst preserving analogue processes and hierarchies.

The Uncomfortable Truth About Management

Here’s what decades of failed transformation efforts have taught us: meaningful organisational change requires management to fundamentally alter how they work, not just how they ask others to work. It demands giving up comfortable assumptions about control, hierarchy, and decision-making. It means accepting that the solutions to complex problems often emerge from the people closest to the work, not from executive strategy sessions.

Most critically, it requires acknowledging that the very management practices and organisational structures that got leaders to their current positions might be precisely what’s preventing their organisations from adapting to a complex, rapidly changing world.

But that level of self-examination and change is hard. It threatens established power structures, comfortable routines, and career advancement paths. It’s much easier to hire consultants to “fix the culture” whilst leaving management behaviours unchanged. It’s more comfortable to implement new processes than to examine why people circumvent existing ones. It’s safer to mandate training programmes than to act on the feedback they generate.

The Gaslighting Industrial Complex

For years, workers have been gaslit into believing that failed transformation efforts were their fault. They weren’t adaptable enough. They weren’t collaborative enough. They were “resistant to change.” They needed more training, more coaching, more commitment to the process. The problem was always with their execution, their attitudes, their willingness to embrace new ways of working.

This dynamic has created a peculiar form of organisational trauma. People know from experience that meaningful change is possible—they’ve seen glimpses of it during crisis situations when hierarchies temporarily flatten, bureaucracy gets suspended, and people are empowered to solve problems directly. But they’ve also learned that these moments are exceptions, quickly snuffed out once “normal” culture reassert itself.

The current backlash isn’t about resistance to improvement. It’s about exhaustion from caring more about organisational health than the people who supposedly lead it. It’s about watching the same dysfunctional patterns repeat whilst being told that transformation is just around the corner if only they’d try harder.

Beyond Organisational Theatre

Consider the current state of popular management initiatives:

Digital Transformation: Organisations spend millions on cloud migrations and AI implementations whilst preserving decision-making processes designed for industrial-age hierarchies and assumptions. The technology changes; the power structures remain identical.

Environmental Sustainability: Companies set net-zero targets and publish sustainability reports whilst maintaining business models fundamentally dependent on unsustainable consumption patterns. The metrics look good; the underlying logic stays unchanged.

Diversity and Inclusion: Organisations track representation statistics and mandate bias training whilst preserving recruitment, promotion, and cultural practices that systematically exclude diverse perspectives from meaningful influence.

Employee Wellbeing: Companies install meditation apps and flexible working policies whilst maintaining performance management systems that create chronic stress and overwork as standard operating procedure.

Customer-Centricity: Businesses reorganise around customer journeys and implement NPS tracking whilst preserving internal silos and incentive structures that make genuine customer focus nearly impossible.

The Innovation Paradox

Perhaps nowhere is this pattern more visible than in innovation efforts. Organisations create innovation labs, hire Chief Innovation Officers, and establish venture arms whilst maintaining procurement processes, risk management frameworks, and decision-making hierarchies specifically designed to prevent anything genuinely new from happening.

They ask teams to “think outside the box” whilst punishing any thinking that threatens established business models, challenges existing partnerships, or questions fundamental assumptions about how value is created and captured. They want the benefits of disruptive innovation without any actual disruption to comfortable arrangements.

What the Data Shows

The persistence of low employee engagement despite decades of management innovation reveals something profound: the problem isn’t with individual initiatives or methodologies. The problem is with the underlying assumption that organisational change can happen without management fundamentally changing how they operate.Or getting the hell outa Dodge altogether.

Gallup’s surveys, along with research from companies like McKinsey, BCG, and academic institutions, consistently show that successful transformation efforts share one critical characteristic: senior leadership doesn’t just sponsor change, they model it by altering their own behaviours, roles and responsibilities, assumptions and beliefs, first. They don’t just communicate new values, they make decisions that demonstrate those values even when it’s uncomfortable or expensive.

The Reckoning Arrives

What we’re seeing isn’t just pushback against specific programmes or initiatives. It’s a fundamental rejection of organisational theatre—the gap between what leadership says and what they actually do, between proclaimed values and lived reality, between transformation rhetoric and management behaviour.

Teams calling out this disconnect aren’t being difficult or resistant to change. They’re being honest about what they’ve observed and experienced. They’re refusing to participate in charades that benefit no one except consultants selling the next organisational panacea, and the personal wellbeing of already well-heeled managers and executives.

The most engaged, capable people are increasingly refusing to pretend that surface-level changes will address structural problems. They’re demanding either genuine transformation or honest acknowledgement that the organisation isn’t actually serious about change.

What Comes Next?

The path forward isn’t about abandoning improvement efforts—the challenges facing organisations are real and urgent. It’s about finally having honest conversations about what meaningful change actually demands from management.

Transformation is primarily a management challenge, not a team challenge. It requires managers to examine and alter their own collective assumptions, behaviours, and comfortable practices before asking anyone else to change. It demands accepting that in complex systems, control is largely illusory and that the best solutions often emerge from unexpected places.

For teams currently living through this frustration: your anger is justified, and your insights are valuable. The problem isn’t with your execution, your attitude, or your willingness to embrace change. The problem is with systems that ask you to transform whilst keeping the people with the most power to enable or block change entirely unchanged.

For folks genuinely committed to transformation: the roadmap has been there all along, visible in every failed initiative and abandoned programme. The question isn’t whether you understand the latest methodology—it’s whether you’re willing to do the uncomfortable work of examining and changing your own behaviour first.

The great management reckoning is here. Across every industry and type of change effort, people are choosing whether they’re serious about transformation or just playing with prettier versions of the status quo. The theatre is closing. It’s time for the real work to begin.


Further Reading

Gallup. (2023). State of the global workplace: 2023 report. Gallup.

Hamel, G., & Zanini, M. (2020). Humanocracy: Creating organizations as amazing as the people inside them. Harvard Business Review Press.

Kotter, J. P. (2014). Accelerate: Building strategic agility for a faster-moving world. Harvard Business Review Press.

Pfeffer, J., & Sutton, R. I. (2006). Hard facts, dangerous half-truths, and total nonsense: Profiting from evidence-based management. Harvard Business School Press.

Sinek, S. (2019). The infinite game. Portfolio.

Womack, J. P., & Jones, D. T. (2003). Lean thinking: Banish waste and create wealth in your corporation (Rev. ed.). Free Press.

The Chronic Belief in Mandatory Management

In business and personal life, we see a powerful, persistent belief: things must be managed. This mindset pervades boardrooms, family dynamics, and individual pursuits alike. When faced with challenges or uncertainty, our knee-jerk response is often to establish control, implement systems, and manage the situation. But why is this our default approach? And how much do we lose by not questioning this assumption?

The Allure of Management

Management as a concept promises order from chaos. Yet, this is most often a vapid, empty promise that fails to deliver on its lofty assurances. This promise is particularly appealing in several contexts:

In business: Companies develop elaborate hierarchies, reporting structures, and performance metrics – all designed to manage human behaviour and business outcomes.

In personal life: We create routines, schedules, five-year plans, and productivity systems aimed at managing our time, goals, and personal growth.

In relationships: We sometimes attempt to manage others’ perceptions, feelings, or behaviours rather than allowing natural dynamics to unfold.

Why Management Becomes Our Default Response

1. Status and Identity

For many professionals, management becomes intertwined with personal identity and status. In many organisational cultures the title of manager signals importance and assumed capability.

2. Fear of Uncertainty

Perhaps the strongest driver of our management impulse is the deep discomfort most humans feel with uncertainty. Management systems create the illusion of predictability in an inherently unpredictable world.

3. Industrial Age Thinking

Our management obsession largely stems from Industrial Revolution principles where efficiency, standardisation, and top-down control were generally assumed to be helpful in factory operations (although, see Deming). These mentalities persist despite significant changes in how value is created today. Even more troubling are the historical roots of modern management practices in plantation slavery systems from the mid-1600s through the 1800s, where overseers developed techniques to control, monitor and extract maximum labour from enslaved people—techniques that were later adapted for factory and office environments. Many of our seemingly neutral management practices carry this deeply problematic lineage.

4. The Illusion of Control

Management provides a comforting sense of agency. When we feel we’re “managing” a situation, we feel less vulnerable to external forces and random chance.

The Façade of Control

What management frequently offers isn’t genuine order but rather the illusion of control. Organisations implement complex systems, metrics, and hierarchies that create the appearance of order while actually:

  • Adding bureaucratic complexity that slows responsiveness
  • Creating rigid structures that resist adaptation
  • Imposing artificial frameworks that don’t match reality’s messiness
  • Perpetuating collective assumptions and beliefs antithetical to the needs of the Folks That Matter™
  • Robbing people of the autonomy so necessary for engagement and motivation

This last point is particularly devastating. When management systems strip individuals of their agency and decision-making power, they undermine the very human factors that drive innovation, dedication, and meaningful work. People inherently need a sense of control over their work to feel invested in outcomes.

The Pretense of Prediction

Management systems operate on the flawed premise that complex systems—whether markets, human behaviours, or organisational dynamics—can be reliably predicted and controlled. This ignores fundamental truths about:

  • The inherent unpredictability of complex adaptive systems
  • The limitations of our forecasting abilities
  • The role of randomness and emergence in how situations actually unfold
  • The nature of humans

When Management Creates More Chaos

Ironically, management interventions often generate the very chaos they claim to resolve:

  • Performance metrics drive dysfunctional behaviours
  • Over-planning creates brittle systems unable to handle surprises
  • Heavy-handed oversight stifles the natural self-organisation that might otherwise emerge

The autonomy deficit doesn’t just harm individual motivation—it cripples the organisation’s collective intelligence and adaptive capacity that emerges when people can respond authentically to challenges.

The Hidden Costs

This default management mindset carries significant costs:

  • Innovation suffers when creative processes are over-managed
  • Trust erodes when relationships become exercises in control
  • Adaptability diminishes when rigid management frameworks can’t accommodate rapid change
  • Joy diminishes when life becomes a series of managed experiences rather than authentic ones

Embracing Practical Alternatives

What practical approaches might serve us better than the management reflex? Several alternatives not only address complexity more effectively but also yield substantial advantages:

Stewardship over control: Rather than managing resources, people, or processes, we might steward them—creating conditions where they can thrive according to their nature. A gardener doesn’t manage plants into growing; they create suitable conditions and work with Mother Nature.

Self-organisation as strategy: Organisations like Buurtzorg in the Netherlands have demonstrated remarkable success by replacing traditional management hierarchies with self-organising teams. Their nurses deliver better care at lower costs with higher job satisfaction precisely because they aren’t “managed” in conventional ways.Few are able to replicate this approach. I can tell you just why, if you’re interested enough to enquire.

Intent-Based Leadership: David Marquet, former nuclear submarine captain and author of the book “Turn the Ship Around!”, advocates for a model where leaders communicate the “why” behind objectives and then trust team members to determine the “how.” His approach pushes authority to where information resides, replacing traditional management with distributed control and decision-making ownership. (See also: The Advice Process)

Minimum viable guidance: Rather than comprehensive management frameworks, many situations benefit from minimal constraints that clarify boundaries whilst leaving maximum room for adaptation and creativity. This approach preserves autonomy while preventing chaos.

Feedback over direction: Instead of managing performance through top-down targets, creating rich, timely feedback loops allows systems and people to self-correct and evolve. This approach harnesses collective intelligence rather than limiting it to manager-directed channels.

Cultivating capability: The alternative to managing people is developing their capabilities—judgement, adaptiveness, and contextual understanding—so they require less management. The paradox is that by deliberately managing less, we often get better results than through more management. How far can we go in eliminating management entirely?

Conclusion

The automatic response that “things must be managed” reveals much about humans’ psychological needs and cultural conditioning. By recognising this cognitive bias, we can make more conscious choices about if management adds any value versus when it may be limiting potential.

Perhaps the most valuable skill in both business and life isn’t managing everything, but discerning if things genuinely needs management and what would flourish with less intervention and more trust. The emptiness of management’s promise becomes evident when we observe how often the most carefully managed systems still fail, while seemingly less-managed environments sometimes thrive through more organic, adaptive processes.

Further Reading

Historical Roots of Management

Cooke, B. (2003). The denial of slavery in management studies. Journal of Management Studies, 40(8), 1895-1918.
Rosenthal, C. (2018). Accounting for slavery: Masters and management. Harvard University Press.

Alternative Approaches

Laloux, F. (2014). Reinventing organizations: A guide to creating organizations inspired by the next stage of human consciousness. Nelson Parker.
Marquet, L. D. (2012). Turn the ship around!: A true story of turning followers into leaders. Portfolio/Penguin.

The Fatal Flaw of Piecemeal Culture Change: Why Your Transformation is Doomed to Fail

Organisations frequently embark on cultural transformation initiatives to stay competitive. However, attempting to change organisational culture and thinking in isolated pockets—rather than holistically—is a strategy destined for inevitable frustration and failure. Here’s why piecemeal cultural change rarely works and what alternative approaches yield better results…

The Interconnected Nature of Organisational Culture

Organisational culture is not merely a collection of independent practices and attitudes; it’s an intricate web of shared values, assumptions, beliefs, and behaviours that permeate every level and department. When we attempt to transform culture in isolation—focusing on just one or two departments or teams—we ignore this fundamental interconnectedness. See also the orthogonal concept ot memeplex interlock.

Consider an organisation where the marketing department embraces innovation and risk-taking while other departments maintain rigid hierarchies and risk-averse decision-making. Marketing’s initiatives will inevitably collide with established processes elsewhere, creating friction rather than progress.

The Inevitable Outcomes of Siloed Cultural Change

When cultural transformation is attempted silo by silos, several entirely predictable outcomes emerge:

1. Cultural Clash and Resistance

Departments operating under different cultural paradigms will naturally clash. The “changed” department begins operating with different assumptions, priorities, and methods than the rest of the organisation. These differences breed misunderstanding, resistance, and often outright conflict. See also: OrgCogDiss.

2. Change Regression

Without organisation-wide support and reinforcement, cultural changes within a single department inevitably regresses over time. The gravitational pull of the dominant organisational culture eventually overwhelms localised efforts, particularly as employees interact with colleagues outside their immediate team. Hint: for a short-term palliative, keeping localised culture changes in a protective bubble can help.

3. Talent Frustration and Exodus

Employees within the “changed” department often become frustrated when their new ways of working clash with the broader organisation. This frustration frequently leads to disengagement and ultimately departure—especially among the most talented individuals who were most enthusiastic about the new cultural direction.

4. Erosion of Credibility

Failed attempts at cultural transformation damage leadership credibility. When employees witness cultural initiatives that start with fanfare but ultimately fizzle or create more problems than they solve, they become cynical about future change efforts.

A More Effective Approach: Systemic Cultural Transformation

So how do we break free from the cycle of failed piecemeal change efforts? What would it take to transform an organisation’s culture in a way that actually sticks? And is there an approach that addresses the entire organisation as a system rather than just its isolated components?

Rather than siloed interventions, successful cultural transformation necessitates a systems thinking approach that recognises the integrated nature of organisational culture. Organisational psychotherapy stands out as the only approach that comprehensively addresses the shared values, beliefs, assumptions and behaviours of the organisation as a whole. Unlike piecemeal interventions, organisational psychotherapy works at the collective level, helping the entire organisation understand and transform its deeply ingrained patterns of thinking and interacting, more or less in parallel.

How Organisational Psychotherapy Differs from Traditional Change Management

Traditional change management approaches often focus on processes, structures, and explicit behaviours, treating organisational transformation as primarily a managerial challenge. Organisational psychotherapy, by contrast, recognises transformation as fundamentally psychological in nature and differs in several important ways:

  1. Focus on collective mindset rather than individual behaviour – While traditional approaches might target the visible behaviours of individuals or teams, organisational psychotherapy addresses the collective mindset—the shared mental models, beliefs, and assumptions that drive behaviour throughout the organisation. This collective focus prevents the “immune system response” that typically rejects isolated change efforts.
  2. Uncovering unconscious dynamics – Organisations, like individuals, develop unconscious patterns and defence mechanisms that resist change. Organisational psychotherapy specifically works to bring these hidden dynamics to consciousness, examining unspoken rules, taboos, undiscussables, and emotional undercurrents that conventional approaches typically miss but which powerfully influence organisational life.
  3. Enabling authentic dialogue and reflection – Effective cultural change requires vulnerability and honesty about dysfunctional patterns. Organisational psychotherapy invites environments where people can speak difficult truths, enabling genuine examination of cultural assumptions rather than superficial compliance with new directives.
  4. Addressing the organisation as a living system – Rather than treating people or departments or functions as mechanical components to be reengineered, organisational psychotherapy approaches the organisation as a complex, adaptive system with its own identity, history, and emotional life. This systemic view prevents the common mistake of solving symptoms rather than underlying causes.
  5. Working through, not around, resistance – Traditional change management often tries to overcome or bypass resistance. Organisational psychotherapy views resistance as valuable information about the system’s fears and needs, enabling the organisation itself to work through its resistanc,e collectively, rather than dismissing it.
  6. Sustainable integration vs. imposed change – Instead of imposing change from outside, organisational psychotherapy facilitates a process where the organisation develops increased self-awareness and capacity for self-directed evolution, leading to change that is internally coherent and sustainable.

NB. For more details, see: The definitive book on Organisational Psychotherapy fundamentals: Hearts over Diamonds

These distinctive elements make organisational psychotherapy particularly effective for deep cultural transformation, addressing the root causes of organisational dysfunction rather than merely treating symptoms. This means:

1. Unified Vision

Effective cultural transformation begins with a clear, compelling vision embraced by folks across all levels and departments. Without this alignment, mixed messages and contradictory priorities will undermine change efforts.

2. Aligned Systems and Structures

Organisational systems—from performance metrics to decision-making processes—must align with the desired culture. Misalignment between cultural aspirations and operational realities guarantees failure. See also: Change always demands we change the rules.

3. Cross-Functional Integration

Effective cultural transformation requires cross-functional coordination and communication. Creating networks and communities that span departmental boundaries helps ensure consistent cultural understanding and application. See also: Moving to the Synergistic Mindset

4. Incremental but Organisation-Wide Implementation

While transformation doesn’t happen overnight, any successful approach must be organisation-wide even when implemented incrementally. This means starting with foundational elements that touch every department rather than completing transformation in one area before moving to the next.

Conclusion

The interconnected nature of organisational culture means that piecemeal approaches to cultural transformation are fundamentally flawed. Organisations that recognise culture as a system—rather than a collection of independent parts—are far more likely to achieve meaningful and lasting cultural change, and the consequent improvement in business outcomes.

By adopting a whole-system perspective and ensuring alignment across people, systems, and departments, organisations can navigate the complex journey of cultural transformation successfully. The path may be challenging, but the alternative—fragmented cultural initiatives that create more problems than they solve—is ultimately much more costly in both human and financial terms.

PS: This is why Agile transformations limited to a team or software department almost never succeed. When Agile assumptions, principles and practices are confined to technical teams whilst the rest of the organisation continues to operate under traditional management assumptions and beliefs, the cross-functional collaboration essential to effective agility is stifled. The result is most often a frustrated development team caught between Agile aspirations and waterfall business realities—reinforcing the critical need for organisation-wide cultural alignment in any transformation effort.

Management Gobshites

When Management-Speak Crosses the Line

In the tech industry, there exists a peculiar phenomenon: the remarkable ability of managers to speak at interminable length without conveying anything of substance. As software developers and employees, we’ve all experienced it – that meeting where a manager unleashes a torrent of buzzwords, contradictory directives, and unrealistic expectations that leave us questioning our sanity – or theirs. Today, I’d like to introduce you to a colourful Irish term that perfectly captures this behaviour: gobshite.

What Is a “Gobshite” in the Workplace Context?

A gobshite, in its most charitable interpretation, is someone who talks nonsense with remarkable confidence. In the tech world, this manifests as the manager who:

  • Demands we “leverage synergies to disrupt the paradigm” without explaining what that means
  • Insists a project that requires six months be completed in two weeks “because the client is excited”
  • Declares that “coding should be easy” for e.g. tasks involving complex refactoring of legacy systems
  • Claims your carefully documented technical debt is “just an excuse” for not implementing new features faster

The Buzzword Bonanza

Perhaps the most recognisable trait of managerial gobshitery is an excessive reliance on buzzwords. These linguistic smokescreens create the illusion of expertise whilst masking a fundamental lack of understanding.

“We need to pivot to a cloud-native, AI-driven microservice architecture with blockchain integration for maximum DevSecOps agility.”

Translation: “I read about these technologies in a LinkedIn post and now I’m insisting we use them without understanding what they are, the implications or the consequences.”

The Impossible Triangle: Good, Fast, and Cheap

A classic scenario: The manager who demands software that is high-quality, developed quickly, and inexpensive – whilst refusing to acknowledge that these three attributes form a triangle where you can only realistically achieve two.

“I know we agreed on the scope, but can we add these fifteen new features? The deadline stays the same, of course. Oh, and we’re cutting the budget by 30%.”

This isn’t just unreasonable – it’s a form of magical thinking that places impossible burdens on development teams.

The Expertise Gap

One of the most frustrating aspects of dealing with managerial gobshites is their tendency to make technical decisions despite lacking technical expertise.

“Why are you suggesting PostgreSQL? I heard NoSQL is faster. Let’s use MongoDB for everything.”

This casual dismissal of developer expertise is both demoralising and dangerous for project outcomes. It’s the equivalent of telling a surgeon which scalpel to use despite never having performed an operation.

The Human Cost

Beyond the frustration and eye-rolling, this behaviour has real consequences. Developers working under managers who consistently speak nonsense experience:

  • Increased stress from trying to meet impossible demands
  • Diminished satisfaction when their expertise is ignored
  • Lower productivity due to constantly shifting priorities
  • Higher burnout rates from fighting unwinnable battles

Breaking the Cycle

So how do we address the gobshite phenomenon in our workplaces? A few suggestions:

  1. Ask for clarity: When faced with buzzword soup, politely ask for concrete examples or specific actions
  2. Document everything: Keep records of unreasonable requests and contradictory directives
  3. Educate sympathetically: Offer to explain technical concepts in accessible ways without condescension
  4. Document everything: Keep records of changing priorities
  5. Set boundaries: Learn to say no professionally when faced with impossible demands
  6. Document everything: Keep records of all interactions with gobshites
  7. Seek allies: Build relationships with managers who do understand the technical realities
  8. Document everything:Oh, did I mention document everything?

Conclusion

Not all managers are gobshites. The must be one or two somewhere out there that aren’t. Those few are thoughtful, technically knowledgeable folks who create environments where developers can thrive. These few managers understand that their role is to remove obstacles, not create them through nonsensical directives.

But for all those who do regularly spout meaningless jargon and impossible demands – perhaps it’s time we had a term to describe the phenomenon. And “gobshite” fits the bill perfectly.

The next time you’re nodding along in a meeting whilst your manager explains how you need to “synergise cross-platform engagement metrics to create sticky user experiences,” remember: you’re not alone in recognising gobshitery when you hear it.

The Case for Holistic Product Development: When Good Technical Decisions Create Bad User Experiences

A recent frustration of mine with iTunes downloads offers an intriguing case study in why product development could benefit from holistic thinking across the whole product.

The observed behaviour is consistent and reproducible: when requesting a track download, the first attempt almost always fails with a fecking modal error dialogue, but a second attempt 10-15 seconds later succeeds perfectly. While we can’t know the exact implementation details, this pattern suggests how technically sound decisions in isolation can create poor user experiences when systems aren’t considered as a whole.

The Root Cause: Balkanised Development

At its heart, this isn’t a technical problem – it’s an organisational one. The issue likely stems from organisational structures where different teams own different parts of the stack, each optimising for their own metrics and concerns. The CDN team likely focuses on network efficiency and scalability. The client team handles UI and local functionality. Each team makes reasonable decisions within their domain, but no one is looking at how these decisions interact to shape the overall user experience (UX).

How the Problem Manifests

Based on observed behaviour of iTunes during downloads, we can hypothesise what might be happening behind the scenes. When we request a download:

  1. Our request likely hits Apple’s Content Delivery Network (CDN)
  2. If the track isn’t in the CDN’s edge node’s cache, the CDN would need to fetch it from origin storage
  3. Rather than make users wait for this fetch, the system appears to fail fast
  4. By the time you retry, the content seems to be cached and serves quickly

This CDN behaviour would be technically sound in isolation – failing fast on cache misses is a common strategy. The problem emerges when this technically reasonable decision meets the iTunes app’s error handling: a modal error dialogue that demands user intervention. This creates a frustrating experience where users must:

  1. Request the download
  2. Wait for the error
  3. Dismiss the fecking modal dialogue
  4. Wait 10-15 seconds
  5. Try again

The Real Solution: Organisational Integration

While there are various technical fixes available, the fundamental solution lies in how we structure our product development organisations:

Critical Organisational Changes

  • Cross-functional product teams that own complete user journeys i.e. the end-to-end UX
  • System architects empowered to look across organisational boundaries
  • UX representation in all technical architecture decisions
  • Clear ownership of end-to-end user experiences
  • Regular review of system interfaces and team boundaries
  • User-focused metrics that catch interaction issues
  • Product leadership that can bridge technical and user experience concerns

Supporting Technical Approaches

  • Silent retry logic in the client
  • Non-modal loading indicators
  • Download queuing with background completion
  • More informative messaging
  • CDN pre-warming for likely downloads
  • Progressive download starting with cached content

Beyond Technical Architecture

This example highlights how product development requires thinking beyond pure technical architecture and team boundaries. Good product development means:

  1. Understanding that technical decisions are inherently and always user experience decisions
  2. Recognising that system boundaries often reflect team boundaries
  3. Seeing that user experience emerges from organisational structures as much as code
  4. Forming teams around user journeys rather than technical components

The Path Forward

Organisations might choose to evolve beyond purely vertical team structures and embrace more holistic approaches to product development. This means:

  • Strong product awareness that looks across traditional boundaries
  • Organisational structures that mirror user journeys, not technical architectures
  • Teams empowered to attend to the overall needs of all the Folks That Matter™, not just to technical metrics
  • Regular evaluation of how organisational decisions affect user experience
  • Cross-functional collaboration as a default, not an exception

The iTunes download experience shows how even small interaction issues often reveal deeper organisational challenges. While technical solutions exist, the real improvements come from better organisational structures that prevent these issues from arising in the first place.

Key Takeaways

  1. Technical friktion often reveals organisational boundaries
  2. User experience emerges from team structures at least as much as from technical decisions
  3. Organisational “architecture” shapes product development and user experience more than technical architecture
  4. Holistic thinking requires organisational change, not just technical solutions
  5. Great products emerge from organisations structured around attending to the needs of all the Folks That Matter™, not just to technical boundaries

The next time you encounter a frustrating user experience, consider firstly the organisational structures that created it.

Postscript: Conway’s Law and Its Inverse

This entire discussion brings to mind Conway’s Law, which states that “organisations design products that mirror their own communication structure.” Our iTunes case study perfectly illustrates this – the jarring user experience at the boundary between CDN and client likely reflects an organisational boundary between teams.

Reverse Conway

But there’s also the inverse of Conway’s Law, sometimes called the “Reverse Conway Manoeuvre” – the idea that we can deliberately structure our organisations to encourage the system architecture we want. If we want seamless user experiences, we might better choose organisational structures that encourage integration and collaboration across traditional system boundaries.

Postscript 2: Product Aikido – Harmonising with Entropy

This discussion of holistic product development brings to mind the principles of Product Aikido – a philosophy that recognises entropy, not competing teams or systems, as the true opponent in product development. Just as Aikido practitioners seek to blend with and redirect force, Product Aikido teaches us to harmonise with the natural disorder inherent in complex systems rather than fight against it.

The iTunes-CDN example perfectly illustrates what happens when we fail to achieve this harmony. But viewed through the lens of Product Aikido, we can see that the real issue isn’t the clash between teams or components – it’s our collective failure to embrace entropy effectively. The fast-fail approach of the CDN isn’t inherently problematic; the friktion comes from our rigid, balkanised response to that entropy.

Product Aikido would suggest several alternative approaches. Rather than prescriptive error handling, teams could be given mission-type tactics (auftragstaktik) – clear intent like “ensure smooth user experience during cache misses” while leaving the implementation details to those closest to the problem. Rather than letting organisational boundaries dictate our solutions, we could focus on shaping the conditions that turn cache misses into opportunities for delighting users.

Most importantly, Product Aikido reminds us that product development is fundamentally a human enterprise. No amount of technical sophistication can replace the need for implicit communication, trust between teams, and a shared understanding of purpose. Those fecking modal dialogues aren’t just a UX failure -they’re a failure of organisational harmony, a sign that we’ve let our structures work against our purpose rather than with it.

In embracing Product Aikido’s principles, we might find that the path to better products lies not in fighting organisational entropy, but in learning to flow with it.

The Great Unmentionable: Why We Can’t Talk About Executive Wellbeing

In yesterday’s post (“What Really Keeps Executives and Senior Managers Motivated”), I explored how executives’ and senior managers’ personal wellbeing imperatives – being right, preserving power, enhancing identity – shape organisational decisions and culture. Yet perhaps the most significant aspect of these dynamics is that we cannot discuss them openly.

The Theatre of Pain

The approved conversation about executive and senior manager wellbeing follows safe, predictable lines. As noted in my previous post, whilst consultants and coaches prattle on about work-life balance and mindfulness, the real dynamics of identity preservation and power maintenance remain carefully hidden from view. This theatre of conventional wellbeing serves as a sophisticated smoke screen, allowing everyone to acknowledge the topic whilst carefully avoiding its core dynamics.

The Costs of Silence

This undiscussability creates cascading effects throughout organisations. Board members, knowing they cannot directly address how personal wellbeing imperatives shape the company’s strategic decisions, develop elaborate workarounds. The sophisticated evidence avoidance described previously becomes a double bind because it cannot even be acknowledged. Direct reports learn to navigate their bosses’ need to be right without ever acknowledging it explicitly. Entire organisational processes get designed around unspoken recognition of these dynamics.

The Conspiracy of Silence

What makes these issues particularly undiscussable is that acknowledging them would threaten the very identity preservation they serve. Executives cannot openly admit to filtering evidence that challenges their position without undermining that position. The selective blindness that manifests in performance assessment, initiative evaluation, and organisational dynamics reading becomes even more selective because it cannot be named.

The Role of Executive Development

Executive development programmes perpetuate this dynamic. While claiming to offer frank discussions about leadership challenges, they carefully avoid these core issues. Instead of addressing the sophisticated mechanisms of selective attention and strategic blindness, they focus on safe topics like communication styles or strategic frameworks, leaving the real drivers of executive behaviour undiscussed and unexplored.

Governance Implications

The undiscussability of these dynamics creates particular challenges for governance. How can boards effectively oversee executive decision-making when they cannot openly discuss its actual motivations? When achievement-oriented executives display remarkable dexterity in avoiding or reframing evidence, this leads to elaborate shadow discussions where real concerns get raised through indirect means.

Breaking the Silence

The costs of maintaining this undiscussability grow increasingly unsustainable. The cognitive self-defence mechanisms become increasingly baroque when they cannot be acknowledged. In an era demanding transparent leadership and authentic corporate culture, the inability to discuss how executive wellbeing actually operates creates mounting organisational friction.

Conclusions

The undiscussability of real executive and senior manager wellbeing represents more than just another corporate taboo. These dynamics fundamentally shape organisational life at every level, forcing people to develop labyrinthine workarounds for issues they cannot openly acknowledge. Until we find ways to make these issues discussable, organisations will continue paying the price in misaligned decisions and much energy wasted in maintaining elaborate facades.

Further Reading

Marshall, R. W.  (2025, February 12). What Really Keeps Executives and Senior Managers Motivated. Flow Chain Sensei. https://flowchainsensei.wordpress.com/2025/02/12/what-really-keeps-executives-and-senior-managers-motivated/

What Really Keeps Executives and Senior Managers Motivated

The traditional discourse around executive wellbeing misses the mark entirely. Whilst consultants and coaches prate endlessly about work-life balance and mindfulness, actual executives and senior managers grapple with far more fundamental challenges. Their decisions consistently flow from a core drive to preserve and enhance their personal wellbeing – not in terms of work-life balance, but in maintaining their power position, enhancing their perceived competence, and strengthening their identity.

This preservation frequently demands sophisticated forms of evidence avoidance, where potentially threatening information gets filtered, reframed, or simply never sought.

The Existential Stakes of Being Right

At the executive and senior manager level, being right – or at least being perceived as right – becomes existential. One significant misstep can unravel years of carefully constructed credibility. Strategic decisions often stem not from pure business logic, but from calculating which choice best preserves or enhances the decision-maker’s position and perceived judgment. The psychological weight of maintaining this track record often overshadows the actual decision-making process, leading to remarkable dexterity in avoiding or recontextualising contradictory evidence.

Power and Identity: A Complex Dance

Executives and senior managers forge their path through vision, influence, and strategic positioning. Their decisions consistently reflect the imperative to maintain and expand their power base. What might appear as purely business strategy often serves the dual purpose of enhancing the decision-maker’s organisational influence and authority. This requires selective blindness to power dynamics that might suggest alternative interpretations. Even seemingly altruistic choices typically align with preserving or strengthening their position, supported by carefully curated evidence that confirms their chosen narrative.

Identity Preservation and Enhancement

The executive and senior management roles offer unique opportunities for identity amplification. Strategic decisions often serve to reinforce and enhance the decision-maker’s core identity traits. What appears as organisational strategy frequently doubles as personal brand enhancement, with contrary indicators dismissed as “not understanding the full picture” or “missing the broader context.”

A Crucial Truth

Understanding these fundamental drivers of executive and senior manager behaviour reveals a crucial truth: their decisions consistently serve to preserve and enhance their personal wellbeing – defined through power, identity, and perceived competence rather than conventional wellness metrics. This preservation operates through sophisticated mechanisms of selective attention and wilful strategic blindness. But how does this manifest in specific strategic decisions? Let’s examine the concrete ways these psychological imperatives shape organisational direction.

How Strategic Decisions Serve Personal Wellbeing: A Deeper Look

Organisational Restructuring

When executives and senior managers initiate restructuring, the choices often reflect personal position reinforcement. The decision to preserve certain departments whilst disbanding others frequently aligns with maintaining their power base. Warning signs about favoured units get reframed as “growth challenges,” while successes in threatening areas face heightened scrutiny. A senior manager might retain direct control of high-visibility projects whilst delegating problematic areas, ostensibly for efficiency but effectively preserving their track record of success.

Investment Decisions

Major investment choices often serve to enhance the decision-maker’s identity capital. An executive known for digital transformation will champion technology investments, not just for business value, but because it reinforces their market identity as an innovator. Evidence supporting preferred investments gets amplified, while contrary indicators face increasingly demanding standards of proof. Similarly, a senior manager might advocate for particular projects that align with their personal brand, even when alternatives show comparable ROI.

Crisis Management

During crises, the chosen response typically prioritises protecting the decision-maker’s “being right” track record. An executive might opt for a conservative approach not because it’s optimal, but because it poses the least risk to their reputation for sound judgment. Early warning signs that threaten this narrative get systematically downplayed or reinterpreted. Senior managers often choose highly visible, quick-win initiatives over potentially more impactful but riskier long-term solutions, supported by selectively chosen metrics that validate their approach.

Innovation Strategy

The approach to innovation often reflects identity enhancement goals. An executive might champion disruptive projects not primarily for their business potential, but because they position them as a visionary leader. Evidence of success gets broadly interpreted, while failures become “learning opportunities” or “necessary experiments.” Senior managers frequently gravitate toward innovation initiatives that showcase their forward-thinking capabilities to key stakeholders, carefully filtering feedback that might suggest alternative approaches.

Evidence Avoidance and Wilful Blindness

The preservation of executive and senior manager wellbeing demands a sophisticated dance with evidence. What might appear as poor decision-making often reflects a nuanced form of self-preservation. Achievement-oriented executives and senior managers, normally fierce advocates for data-driven decisions, can display remarkable dexterity in avoiding or reframing evidence – and science – that threatens their position or challenges their track record of being right.

This selective blindness manifests most powerfully in three areas. First, in the assessment of their own performance and impact, where contrary evidence gets recontextualised or dismissed as “not understanding the full picture.” Second, in the evaluation of favoured initiatives or strategies, where warning signs get minimised as “early implementation challenges.” Third, in their reading of organisational dynamics, where signals that challenge their power base or threaten their identity get filtered through increasingly elaborate explanatory frameworks that preserve their position.

Conclusions

This exploration reveals a fundamental truth about organisational life: the personal wellbeing imperatives of executives and senior managers profoundly shape not just organisational direction, but the very nature of what gets seen as evidence. Understanding this reality proves crucial for several stakeholders. For those reporting to these leaders, it offers a framework for better anticipating and interpreting decisions. For board members and shareholders, it suggests the need for governance structures that better align personal wellbeing imperatives with organisational success. For the executives and senior managers themselves, acknowledging these dynamics might enable more conscious navigation of the tension between personal and organisational imperatives, and seeing their needs better met.

The implications extend beyond individual organisations to our broader understanding of corporate governance and executive development. Traditional approaches to executive development, focusing on technical skills and conventional wellbeing metrics, may need fundamental rethinking. Instead, programmes might better serve their participants by directly addressing how to manage these personal wellbeing imperatives whilst maintaining organisational effectiveness – and perhaps most crucially, how to remain open to evidence that challenges personal position and identity.

Further Reading

For a deeper exploration of how hidden motivations drive business decisions, see:

Morgen, S. D. (2009). Dirty little secrets: Why buyers can’t buy and sellers can’t sell and what you can do about it. Austin, TX: Waterside Productions.

Clifford, W. K. (1877). The ethics of belief. Contemporary Review, 29, 289-309. Reprinted in Clifford, W. K. (1879). Lectures and essays (L. Stephen & F. Pollock, Eds., Vol. 2, pp. 177-211). London: Macmillan.

The Leadership Paradox: Elite CEOs Reveal Why The People vs Profit Debate Is Completely Wrong

The Executive’s Dilemma

In Britain’s corporate landscape, a persistent narrative echoes through its mahogany-panelled boardrooms: the supposed choice between nurturing people, and driving profits. This perceived dichotomy has shaped strategic decisions for decades, creating an artificial divide that ripples through organisational structures. CEOs and board members often find themselves wrestling with questions like “Do we invest in comprehensive development programmes or focus on quarterly targets?” or “Should we prioritise employee satisfaction or shareholder returns?”

Unpacking the False Choice

The notion that organisations must choose between being people-centric or results-focused stems from industrial-era thinking, where human capital was viewed merely as a means to an end. The precursor to factory robots. This outdated perspective fails to recognise the sophisticated interplay between human motivation and business outcomes. When executives frame their decisions through this binary lens, they inadvertently create self-fulfilling prophecies that inevitably damage both employee engagement and business performance.

The Cost of Binary Thinking

This artificial division manifests in concerning ways:

  • Short-term decision-making that sacrifices sustainable growth for immediate gains
  • Disengaged middle management caught between confusing and conflicting priorities
  • Fragmented organisational culture where departments operate in silos
  • Reduced innovation as employees focus on meeting targets over meaningful contributions
  • Strategic initiatives that fail due to lack of employee buy-in

Breaking Down the Boardroom Barriers

Progressive organisations are discovering that the most effective business strategies don’t require choosing between people and results. Instead, they create frameworks where these elements naturally reinforce each other. Consider how companies like Unilever have integrated sustainability and social responsibility into their core business model, demonstrating that purpose and profit can coexist and thrive.

The Executive’s New Playbook

Forward-thinking leaders are adopting a more nuanced approach:

Strategic Integration

  • Aligning people development and joy in work (Cf. Deming) with business objectives
  • Creating metrics that measure both human and financial capital
  • Developing long-term strategies that account for both elements

Cultural Transformation

  • Moving beyond traditional command-and-control structures
  • Fostering environments where innovation and results coexist
  • Building trust through transparent communication and shared purpose

Resource Allocation

  • Investing in systems that support both people and performance
  • Developing capabilities at all levels
  • Creating feedback mechanisms that drive both personal and organisational growth

The Path Forward

The solution lies not in choosing between people and results, but in understanding how they fundamentally drive each other. This requires a shift in boardroom discussions from “either/or” to “both/and” thinking. Successful organisations are those where executives champion a unified approach, recognising that sustainable business success comes from creating environments where people naturally drive results through their engagement and commitment.

A New Narrative

Has the time has come for British businesses to rewrite the narrative? Instead of perpetuating the false choice between people and results, might boards choose to lead the advance, in creating integrated strategies that recognise the inseparable nature of human capital and business performance? This isn’t just about finding a balance—it’s about recognising that the most powerful business strategies are those that harness the natural synergy between engaged people and exceptional results.

The question facing us today isn’t whether to choose between people and results, but rather how to create environments where focusing on people becomes the most effective path to achieving sustained business success.

The 1911 Management Model That’s Silently Killing Your Software Efforts

In 1911, Frederick Winslow Taylor published “The Principles of Scientific Management,” a seminal work that would revolutionise industrial production. While Taylor’s principles transformed manufacturing in the early 20th century, their ghostly remnants continue to haunt modern software development—creating what we might call “management monstrosities” in organisations worldwide.

The Fundamental Category Error 

At the heart of our industry’s dysfunction lies a profound category error: treating software development as something it’s not. Software development is Collaborative Knowledge Work (CKW) and Cf. Peter Drucker, a distinct category of work that differs fundamentally from:

  • Factory work
  • Manufacturing
  • Office work
  • Service work (call centres, help desks)
  • Even individual knowledge work

Yet organisations consistently fail to recognise or act on this distinction. Instead, they import management practices, assumptions, and beliefs from these other categories—particularly from manufacturing—leading to egregious ineffectiveness.

The Spectre of Scientific Management

Taylor’s model exemplifies this category error perfectly. It was brilliantly designed for manufacturing: break down work into its smallest components, measure everything, and optimise each step for maximum efficiency. Workers were to follow precise instructions, with managers serving as the brains of the operation.

This approach turned factories into well-oiled (but joyless) machines. But when applied to software development, it creates dysfunctional organisations characterised by:

  • Detailed specifications written by analysts who never write code
  • Rigid separation between “thinkers” (architects) and “doers” (developers)
  • Obsessive measurement of productivity through story points and velocity
  • Standardised processes applied regardless of context
  • Management-driven estimation and planning
  • Demotivation and absence of joy in work

Understanding Collaborative Knowledge Work

Collaborative Knowledge Work, as Peter Drucker identified, has distinct characteristics that demand a fundamentally different approach:

Knowledge Creation, Not Reproduction

Unlike manufacturing, where the goal is to reproduce known patterns efficiently, CKW involves creating new knowledge through fellowship and collaboration. Every line of code represents multiple decisions, interpretations, and novel solutions.

Emergent Understanding

In CKW, understanding emerges through the work itself. The act of writing code reveals new insights about the problem space that couldn’t have been discovered through upfront planning.

Social Learning

Knowledge in software teams isn’t just transferred—it’s co-created through interaction. When we separate “thinkers” from “doers,” we break this vital social learning process.

The Cost of Category Error

When we misclassify software development, we create organisations that:

Fragment Knowledge

By separating thinking from doing, we create artificial barriers between those who understand the problem space and those who implement solutions. This leads to demotivation, costly misunderstandings, and repeated rounds of clarification.

Suppress Innovation

When developers are treated as mere implementation resources, their ability to contribute to solution design is stifled. The very people who best understand the technical constraints and opportunities are prevented from participating in crucial decisions.

Chase False Metrics

Story points, velocity charts, and detailed Gantt charts create a comforting illusion of control while masking the inherent uncertainty in knowledge work. This false precision leads to unrealistic expectations and failed efforts.

Breaking Free from Category Error

Recognising software development as Collaborative Knowledge Work leads to fundamentally different approaches:

Integrate Thinking and Doing

Remove artificial barriers between analysis, design, and implementation. Have developers participate in problem analysis, while ensuring analysts and architects maintain close connections with the codebase. Better yet, Asim for Cthulu-shaped people.

Foster Collaboration

Create and nurture environments where knowledge can flow freely between team members. Focus on creating conditions for effective collaboration rather than optimising individual productivity.

Embrace Uncertainty

Rather than pretending we can plan everything upfront, acknowledge uncertainty as inherent to knowledge work. Use short feedback loops and continuous adjustment rather than rigid plans.

Measure Outcomes, Not Activities

Focus on meaningful outcomes like needs met, and business impact, rather than proxy vanity metrics like lines of code or story points.

Conclusion

The persistence of Taylorist thinking in software development isn’t just an inconvenience—it’s a fundamental category error that creates “management monstrosities.” By recognising software development as Collaborative Knowledge Work, we can build organisations that support rather than hinder effective working.

The future of business lies not in treating developers as interchangeable parts in a machine, but in creating environments that support the unique demands of Collaborative Knowledge Work. Until we correctly categorise the nature of software development work, we’ll continue to create organisations that inevitably underperform.

Remember: your software team isn’t a factory, and your developers aren’t assembly line workers. They’re collaborative knowledge workers engaged in creating new understanding through their work. The sooner you choose to embrace this reality, the better your results will be.

Story: The Whiteboard Fiasco

[Based on a true story from my own personal experience]

Beverly stared at the email in disbelief, her morning coffee growing cold beside her keyboard. After three months of waiting, the Innovation Committee had finally responded to her suggestion for installing whiteboards in the development team’s workspace at Consolidated Banking Solutions.

“Dear Beverly,” the email began with corporate sterility, “Thank you for your participation in CBS’s Innovation Initiative. After careful consideration, we regret to inform you that your suggestion for installing collaborative whiteboards cannot be implemented at this time. Our Workplace Aesthetics Guidelines specifically emphasise maintaining a ‘pristine and professional environment.’ The potential for visual clutter and unsightly marker residue would compromise our corporate image.”

She glanced around the office floor, taking in the sea of developers hunched over their monitors, piles of junk in various corners, dirty walls and partitions, communication limited to Slack messages and endless email chains. Just last week, the team had spent four hours in a circular email discussion that could have been resolved in five minutes with a simple diagram.

The rejection email continued: “We encourage you to continue submitting innovative ideas that align with our corporate values of ‘Digital First’ and ‘Paperless Excellence.'”

Beverly couldn’t help but notice the irony. The same management that rejected whiteboards had recently spent a small fortune on a digital suggestion platform that had crashed three times during its first week. Her colleague Tom’s suggestion for improving the platform’s stability had been rejected because “external vendors handle our digital infrastructure.”

Later that afternoon, Beverly watched as facilities management installed a new set of motivational posters. “INNOVATION STARTS WITH YOU,” declared one, featuring a stock photo of diverse professionals pointing at a tablet screen. The poster frame was slightly crooked.

During the next “Innovation Champions” meeting (attendance mandatory), Beverly listened as executives proudly announced that the suggestion scheme had generated over two hundred submissions. They tactfully avoided mentioning that none had been approved.

“Remember,” the Innovation Director concluded, reading from a PowerPoint slide, “we’re building a culture of fearless creativity and boundless possibilities.”

Beverly noticed her teammate Kevin sketching a system architecture diagram on a napkin, then quickly crumpling it when a manager walked by. Heaven forbid anyone witness actual collaboration in progress.

Two weeks later, a company-wide email announced the success of the Innovation Initiative, complete with charts showing “engagement metrics” and “ideation velocity.” Beverly’s suggestion was now a statistic, filed away in a database of rejected ideas, while the real innovations continued to happen in hushed conversations, napkin sketches, and despite – not because of – the official channels designed to encourage them.

The following quarter’s town hall featured a new corporate initiative: “Digital Transformation 2.0.” Beverly started drafting her resignation letter.

A Guide to Status-Seeking in Modern Organisations

Understanding Status Obsession

In contemporary workplaces, the drive for status manifests as a pervasive and often destructive force. This compulsion emerges from deep-seated needs for psychological security, fear of obsolescence, and the misconception that power equates to self-worth. These underlying motivations create systemic dysfunction within organisations, as individuals – quite naturally as self-absorbed human beings – prioritise personal position over collective benefit.

When we examine status-seeking through the lens of systems thinking, as articulated by Russell Ackoff, we observe how individual pursuits of status create ripple effects throughout the organisational ecosystem, often degrading the very systems they aim to influence.

Manifestations of Status-Seeking Behaviour

Information Hoarding and Gatekeeping

Status seekers frequently position themselves as indispensable by becoming information bottlenecks. They meticulously control access to crucial data, processes, or relationships, creating artificial dependencies that serve their interests while hampering organisational efficiency. For instance, a manager might retain sole knowledge of key client relationships or critical operational procedures, making themselves seemingly irreplaceable while simultaneously creating organisational vulnerability.

Territorial Behaviour

The territorial manifestation of status-seeking appears in various forms. Managers might create artificial boundaries around their domains, resisting cross-functional collaborations that could dilute their perceived importance. They often respond to potential encroachment with aggressive defence mechanisms, such as claiming exclusive ownership over projects or ideas, even when shared resources, learning and cooperation would better serve organisational goals.

Competitive Undermining

Perhaps most insidious are the subtle forms of competitive undermining employed by status-seekers. These behaviours might include deliberately delayed information sharing, minimal cooperation dressed as busy-ness, or passive resistance to initiatives outside their control. Status-obsessed individuals often engage in what appears to be constructive feedback but actually serves to create doubt about colleagues’ competence or judgment.

The Systemic Impact of Status Obsession

Organisational Dysfunction

Status-seeking behaviours create profound organisational dysfunction. Knowledge becomes siloed as individuals hoard information to maintain their position. Innovation suffers when collaboration is viewed through a competitive rather than cooperative lens. Decision-making processes become politically charged rather than merit-based, leading to suboptimal outcomes and missed opportunities for organisational advancement.

Degradation of Team Dynamics

Teams led by status-obsessed managers typically experience severe dysfunction. The constant political manoeuvring creates an atmosphere of distrust and anxiety. Creative thinking becomes stifled as team members focus on managing impressions rather than solving problems. Young talent often feels suppressed, leading to a brain drain as promising employees seek healthier environments where their contributions will be recognised and valued.

Personal and Professional Costs

The psychological burden of maintaining status creates significant personal costs. Individuals often experience chronic stress, anxiety, and impostor syndrome. Professional relationships become transactional rather than authentic, as every interaction is viewed through the lens of status enhancement and power dynamics. This constant vigilance in protecting one’s position drains energy that could be directed toward productive work and genuine personal development.

Warning Signs and Red Flags

Individual Indicators

Key warning signs include feeling threatened by colleagues’ successes, difficulty celebrating others’ achievements, and a compulsive need to control all aspects of projects or relationships within one’s sphere of influence. Status-obsessed individuals might find themselves constantly comparing their position to others or experiencing anxiety when not included in certain meetings or communications.

Team-Level Indicators

At the team level, warning signs include reduced open communication, increased political behaviour among team members, and a focus on optics and impression management over substantive work. Teams experience decreased innovation and risk-taking as members and managers prioritise status preservation over experimentation and potential failure.

Systemic Consequences

Organisational Culture Deterioration

The cumulative effect of status-seeking behaviours often leads to a toxic organisational culture characterised by mistrust, reduced collaboration, and decreased innovation. This cultural deterioration can become self-reinforcing, as new employees either adopt similar behaviours to survive or leave the organisation entirely.

Long-term Strategic Impact

Organisations dominated by status-seeking behaviour typically struggle with long-term strategic execution. The focus on individual position over organisational benefit leads to short-term thinking and missed opportunities for genuine innovation and growth. The energy expended on political manoeuvring detracts from the organisation’s ability to adapt and respond to external challenges effectively.

Conclusion

The manifestations and consequences of status-seeking behaviour create profound challenges for modern organisations. Understanding these dynamics is crucial for identifying and addressing destructive patterns before they become entrenched in organisational culture. The costs—both human and organisational—of unchecked status-seeking behaviour underscore the importance of recognising and countering these tendencies in ourselves and our institutions.

Hire Talent or Fire Talent?

The Hidden Reality of Corporate Performance: Beyond Talent Management

The Perennial Management Quandary

In the complex ecosystem of modern organisations, managers face a perpetual challenge that strikes at the heart of human capital management: should they hire exceptional talent or preemptively remove potential disruptors? This question is not merely an academic exercise but a strategic imperative that can define an organisation’s future trajectory.

The talent conundrum represents a profound psychological and organisational tension. Talented individuals bring extraordinary potential—innovative thinking, exceptional skills, and the capacity to transform organisational capabilities. Yet they simultaneously represent a threat to existing power structures, established processes, and the comfortable mediocrity that often characterises corporate environments.

The Psychological Landscape of Talent Management

Most corporate managers harbour a complex, often contradictory relationship with top-tier talent. On one level, they intellectually recognise the value of exceptional individuals. On another level, they experience visceral discomfort with professionals who challenge status quo thinking, question established hierarchies, and refuse to conform to traditional organisational expectations.

This psychological resistance stems from deep-seated organisational dynamics. Talented individuals are not merely employees; they are potential agents of change who can disrupt carefully constructed power networks. They represent both an opportunity and a threat—capable of driving unprecedented innovation while simultaneously challenging the very systems that sustain current leadership.

The Strategic Calculus of Talent Retention

The decision to hire talent or fire talent is never straightforward. It requires a nuanced understanding of:

  • Individual psychological profiles
  • Organisational culture and adaptability
  • Potential for transformative innovation
  • Risk tolerance of existing leadership
  • Long-term strategic objectives

Fundamentally, this decision reflects an organisation’s fundamental approach to growth, innovation, and human potential. Some entities view talented individuals as strategic assets to be carefully cultivated. Others perceive them as potential disruptions to be managed, contained, or eliminated.

A Provocative Perspective

Drawing from the insights of management philosophers like Deming and Ackoff, we understand that this talent dilemma transcends simple human resource management. It represents a deeper exploration of organisational psychology, power dynamics, and the fundamental nature of institutional adaptation.

In the following sections, we will dissect this complex challenge, exploring the multifaceted considerations that inform the critical decision: to hire exceptional talent or preemptively remove potential organisational “troublemakers”.

Reframing Organisational Success

As W. Edwards Deming provocatively observed,

“The problem is not the worker. The problem is the system that allows the worker to fail.”

This profound statement sets the stage for a deeper exploration of corporate dynamics that goes far beyond traditional talent management.

The Deming-Ackoff Principle of Executive Self-Interest

Russell L. Ackoff’s cutting insight reveals the core of organisational behaviour:

“Executives’ actions make sense [only] if you look at them as taken in order to maximise the executive’s well being.”

This perspective fundamentally challenges our understanding of workplace motivation and performance.

The Unspoken Organisational Imperative

Drawing from Deming’s seminal work, we might choose to acknowledge that “Nobody gives a hoot about profit” – a statement that strips away the veneer of corporate altruism. The true organisational imperative is not about collective success, but individual preservation and advancement.

The Real Job: Navigating Unwritten and Unspoken Expectations (the Secret Game)

Psychological Dynamics of Corporate Survival

R.D. Laing’s profound psychological observation perfectly captures the intricate dance of corporate survival:

“They are playing a game. They are playing at not playing a game. If I show them I see they are, I shall break the rules and they will punish me. I must play their game, of not seeing I see the game.”

This quote encapsulates the complex psychological landscape where people must simultaneously navigate organisational expectations while maintaining a delicate balance of perception and strategic silence.

Talent Management Through a New Lens

Redefining High Performance

Deming’s wisdom resonates powerfully here:

“It is not enough to do your best; you must know what to do, and then do your best.”

In the context of executive dynamics, this means understanding the unspoken rules that truly govern organisational behaviour.

The Paradox of Organisational Contribution

As Ackoff might argue, the most successful employees are those who understand that organisational systems are fundamentally designed to protect and elevate existing power structures. Performance is much less about measurable outcomes and much more about navigating complex interpersonal dynamics.

Practical Implications for Professionals

R.D. Laing’s psychiatric insights provide a framework for survival: to survive in the secret game, people must develop a nuanced approach that recognises the psychological games played within corporate environments. This requires:

  • Deep awareness of executive perspectives
  • Keen observational skills that go beyond surface-level interactions
  • The ability to influence subtly without disrupting established power dynamics or treading on sensitive, snowflake toes
  • A sophisticated understanding of organisational and individual psychology

Conclusion: A Radical Perspective on Corporate Performance

Deming perhaps said it best:

“The transformation (a.k.a. abolition) of Western management style will be the most important task of the century – in fact, of any century.”

Understanding the true nature of corporate dynamics requires us to look beyond traditional narratives of talent management.

The most successful individuals are not those who blindly pursue organisational objectives, but those who understand the intricate human dynamics that truly drive corporate behaviour. As Ackoff would remind us, true organisational intelligence lies in recognising and navigating these complex, often unspoken systems of power and self-interest. i.e Your Real Job.

The MBA Menace

The Genesis of a Corporate Calamity

A peculiar species has emerged that threatens the very fabric of human existence: the MBA graduate. These corporate drones, armed with spreadsheets and a disturbing lack of empathy, have become the natural predators of genuine human interaction, creativity, and common sense.

The Anatomy of an MBA Menace

Spreadsheet Warfare

MBA graduates approach life with the precision of a calculator and the warmth of a cryogenic laser. Every human interaction becomes a potential data point, every relationship a potential cost to be minimised. They view the world through a lens of key performance indicators (KPIs), reducing the rich tapestry of human experience to a series of pretty but vacant colour-coded graphs and pie charts.

The Corporate Newspeak

Language itself becomes a weapon in the hands of these graduates. They communicate not in words, but in a bizarre dialect of corporate jargon. “Touching base”, “drilling down”, and “moving the needle” replace genuine communication. It’s as if they’ve been programmed to speak in a language designed to obfuscate rather than illuminate.

The Systematic Destruction of Human Creativity

Innovation by Algorithm

Where once innovation sparked from human creativity, MBA graduates have replaced inspiration with algorithmic precision. They believe that every problem can be solved with a strategic framework, completely overlooking the beautiful chaos of human imagination.

The Quantification of Human Worth

In their world, human beings are reduced to “resources” – human capital to be allocated, optimised, and discarded. Emotions are seen as inefficiencies, passion as an unnecessary variable in their grand economic equations.

The Economic Ecosystem of Destruction

The Consulting Conundrum

Consulting firms become their breeding grounds, where young MBA graduates are indoctrinated into a vapid cult of corporate efficiency. Seagull-like, they parachute into organisations, disrupt existing structures, and leave behind a trail of redundancies and broken team dynamics.

Cost Management as Life Philosophy

Life becomes a perpetual cost assessment. Where spontaneity once reigned, now sits a meticulously planned cost mitigation strategy. Spontaneous joy is replaced by calculated happiness, measured and approved by a committee.

The Psychological Warfare

Emotional Intelligence Deficit

Empathy is not taught in their hallowed halls of business school. Instead, they learn to view human emotions as variables to be manipulated, controlled, exploited, and eventually eliminated from the corporate equation.

The Performance Review of Humanity

Every human interaction becomes a performance review. Friendships are networking opportunities, relationships are potential strategic alliances, and personal growth is measured by career progression.

Conclusion: A Glimmer of Hope

In this apocalyptic landscape, no hope remains. All MBA graduates are soulless automatons. None retain their humanity, nor understand that true business success lies not in cold calculations, but in genuine human connections.

Perhaps there’s a silver lining even so – by exposing the absurdity of purely metrics-driven existence, these graduates inadvertently remind us of the value of human spirit, creativity, and emotional intelligence.

Hiring for “Fit” Breeds Mediocrity

The Empty Promise of “Cultural Fit”

Let’s be honest: “cultural fit” has become one of those corporate buzzwords that managers toss about with gay abandon. Like most platitudes, it sounds rather nice until you begin picking it apart. What exactly are we fitting new hires into? And more importantly, why are we so keen on this “fitting in” notion?

Unpacking the “Fit” Facade

When managers speak of fit, they’re often expressing a preference for candidates who won’t rock the boat. They seek those who will readily adapt to existing power structures, embrace current practices without question, and maintain the comfortable – for the managers – status quo. It’s not about finding brilliant minds who’ll challenge and improve the organisation, it’s all about finding compliant people who’ll keep things ticking over, predictably.

The Mediocrity Trap

Internal Team Dynamics

Within teams, hiring for fit creates an echo chamber effect. When we consistently select individuals who mirror existing team members’ attitudes and approaches, assumptions and beliefs, we inadvertently:

  • Reduce cognitive diversity
  • Limit creative tension
  • Discourage constructive disagreement
  • Reinforce existing blind spots

Of course, we were to hire people who might even for a moment challenge established shared assumptions and beliefs, we might open a Pandora’s Box to challenges, and spark conflicts with prevailing dynamic conservatism (Schon).

External Performance Metrics

When comparing teams built on “fit” versus those embracing cognitive diversity, the differences become stark. Teams prioritising fit often:

  • Struggle with innovation
  • Miss emerging market opportunities
  • Show reduced problem-solving capabilities
  • Demonstrate lower adaptability to change

The Real Cost of Comfort

The pursuit of fit reflects managers’ desire for comfort and predictability (i.e. their own wellbeing). It’s far easier to manage a neat and ordered (sic) team of similar minds than to harness the creative, often messy friction of diverse perspectives. But this comfort comes at a steep price:

  • Reduced intellectual challenge
  • Weakened critical thinking
  • Diminished organisational learning
  • Stunted growth potential
  • An exemplar encouraging all concerned to seek comfort rather than progress.

Beyond “Good Enough”

Excellence rarely emerges from conformity. Meaningful organisational success requires:

  • Cognitive diversity
  • Constructive disagreement
  • Challenged assumptions
  • Fresh perspectives
  • Chellenging and messy collaborations

Moving Forward: From Fit to Growth

Rather than seeking candidates who “fit”, organisations might choose to prioritise:

  • Complementary skills and perspectives
  • Cognitive diversity
  • Capacity for respectful yet bulldog challenging
  • Ability to enhance, not merely fit into, team dynamics
  • Working effectively with Smart Conservatives
  • Surface and reflect on flawed collective assumptions and beliefs

Conclusion

The “fit” platitude serves primarily to maintain mediocrity whilst providing a (false yet oh so attractive) sense of security to management. Organisations can’t afford the luxury of comfortable mediocrity. Is it time to move beyond the simplistic notion of fit and embrace the productive discomfort of genuine diversity – in thought, approach, and perspective?

Dilettantism and the Paradox of Play

“Do nothing that is not play.”

— Marshall Rosenberg

Defining Our Terms

The tension in this post emerges from the precise meanings of dilettantism and play, and how they intersect in the realm of management. Modern usage of dilettante has sharpened the original meaning into something more pointed: “a person having a superficial interest in an art or branch of knowledge.” The dilettante becomes the eternal dabbler, perpetually skimming surfaces, accumulating breadth at the expense of depth.

Play proves more complex to define, existing in multiple forms. At its most basic, play represents voluntary activity pursued for its own sake. Yet this simplicity masks profound variations. There’s the free play of children, unbounded by rules or purpose. There’s game play, structured by rules yet infinitely variable within them. There’s what Michael Schrage terms “serious play”—the rigorous, iterative experimentation that drives innovation. And there’s playfulness itself: an attitude or stance toward activity that transforms work into joyful exploration.

The Heart of the Matter

The paradox emerges in the space between Rosenberg’s liberating insistance on play and Schrage’s insistence – described in his book “Serious Play” – on a focus on purpose. Here lies a tension that every organisation must navigate: true play, the kind that generates innovation and insight, demands both freedom and focus, both lightness and depth.

The Dilettante’s Fatal Attraction

The dilettante, that pretentious dabbler in superficialities, finds themselves drawn to Rosenberg’s philosophy like a moth to a flame. They hear in it permission to remain forever an amateur, skimming across domains, tasting but never digesting, starting but never mastering. Their interpretation of play becomes a justification for perpetual fucking around.

The Nature of Serious Play

Yet Schrage reveals a deeper truth about play—one that the dilettante consistently misses. Serious play, the kind that drives innovation and creates value, emerges from commitment rather than casual posturing. It manifests in the child who spends hours perfecting a tower of blocks, the musician who practices scales with joyful dedication, the scientist who delights in methodical experimentation, and the manager who knuckles down and truly gets to grip with the fundamentals of his trade. Aside: In all my 50 year career to date I have NEVER come across anyone in a management role who was other than a dilettante of the first order.

The Paradox Revealed

Here then is our paradox: the most productive form of play requires a seriousness, a focus on purpose, that seems, at first glance, to contradict the very nature of play itself. The innovation that emerges from genuine play demands a depth of engagement that the dilettante, by definition, cannot muster. Yet this “serious” play – which I prefer to label “purpose-driven play” – retains all the joy, curiosity, and freedom that makes play so powerful in the first place.

Management’s Peculiar Position

Modern management finds itself caught in this paradox. The role demands breadth, requiring managers to engage with multiple domains and disciplines. Yet management culture and the management mythos naturally encourages, and often rewards, dilettantism. Effective management requires the capacity for serious play—the ability to engage deeply and systematically with problems and possibilities. Which is perhaps why we so rarely see any kind of effective management.

Threading the Needle

The resolution, perhaps, lies in understanding that productive play is a bedfellow of expertise and competence, not dilettantism. It combines playful openness and curiosity with the expert’s depth and application. This is the space where innovation flourishes, where creativity meets capability, where freedom serves function.

Conclusion

In the end, Rosenberg and Schrage both illuminate essential truths. Yes, we can choose to do nothing that is not play—and we can choose to understand play in its fullest, most liberating sense. The dilettante’s superficial approach fails not because it embraces play, but because it misunderstands play’s true nature. (Not that dillettantes seek justification for their feckless and shallow posturing. Such intent would run contrary to their very amateurism.  And most of them remain entirely unaware of their very dilettantesque nature.)  Real play – the kind that brings joy, learning and insight, transforms organisations, and creates value – demands both a lightness of spirit, and a depth of engagement which the dilettante, finding it onerous, shirks.

Perhaps the ultimate challenge for managers is to cultivate this deeper form of play—one that maintains joy while pursuing mastery, that preserves curiosity while building autonomy, and encourages bold experimentation whilst guided by a shared purpose. In this light, the dilettante serves as both a warning and a cautionary tale: a reminder of play’s appeal and the perils of its insufficient expression in casual engagement.

Beyoncé Time

The Corporate World’s Most Delusional Management Theory

The Origin Story

Legend has it that Beyoncé once remarked that even in her downtime – whilst eating, showering, or doing mundane tasks – she’s constantly thinking about her music, choreography, and empire-building. Fair play to her, really. When you’re passionate about your art and it’s made you one of the wealthiest entertainers on the planet, who wouldn’t be all in?

The Corporate Hijacking

Some bright spark in management consulting caught wind of this and thought, “Brilliant! Our Karen from Accounts should feel the same way about quarterly VAT returns!” Thus, “Beyoncé Time” was born – the absolutely barmy notion that employees should spend their personal time obsessing over spreadsheets and synergy with the same devotion Beyoncé brings to crafting chart-topping albums.

The False Equivalency

Why It’s Bonkers

  • Beyoncé owns her empire; Karen owns her cat
  • Queen Bey’s creativity leads to millions; reorganising the storage cupboard doesn’t
  • When Beyoncé succeeds, she gets richer; when employees go above and beyond, they might get a pizza party

The Management Delusion

Picture a CEO, sitting in their corner office, genuinely believing their staff lie awake at night thinking, “You know what would streamline our procurement process?” They’ve confused occupational commitment with artistic passion, rather like comparing a hamster on its wheel to an Olympic athlete.

The Reality Check

What Employees Actually Think About in Their Free Time

  • What to watch on Netflix
  • Whether to have chips or a jacket potato for tea
  • If they remembered to put the bins out
  • Literally anything except work

The Toxic Implementation

This misappropriated concept has spawned countless “voluntary” weekend workshops and “optional” after-hours brainstorming sessions. It’s the corporate equivalent of telling someone, “You don’t have to come to my birthday party, but I’ll remember if you don’t.”

Breaking Free from Beyoncé Time

For Managers

  • Understand that Beyoncé’s dedication to her art isn’t comparable to Janet’s dedication to data entry
  • Accept that work-life balance isn’t just a buzzword
  • Realise that paying people properly works better than expecting unpaid devotion

For Employees

  • Remember that Beyoncé gets paid millions for her dedication
  • Understand that your free time is yours, full stop
  • Know that thinking about work 24/7 isn’t dedication – it’s just unpaid overtime

The Final Word

Until your company offers Beyoncé-level rewards, perhaps stop expecting Beyoncé-level devotion. And let’s be honest – even if you did pay them millions, most people would still rather think about their dinner plans than your company’s five-year strategy whilst in the shower.

Besides, I reckon even Beyoncé occasionally just sits on her sofa, eating crisps, and thinking about absolutely nothing. She’s just too savvy to tell us about it.