Archive

Rightshifting

The Cultural Transformation Paradox: Why Digital Transformation Will Fail Wherever Agile Already Has

We’ve all seen the statistics. According to various industry reports, somewhere between 60-70% of agile transformations fail to deliver their promised benefits. Meanwhile, digital transformation initiatives boast similarly dismal success rates, with studies suggesting that 70% or more fail to meet their objectives. Yet organisations continue to invest billions in these initiatives, convinced that this time will be different.

The uncomfortable truth is that both agile adoption and digital transformation require the same fundamental shift that organisations consistently refuse to make: a complete overhaul of their cultural DNA—their collective assumptions and beliefs about work itself.

The Agile Mirage: Surface Changes, Deep Resistance

Most agile “transformations” are really just process makeovers. Organisations eagerly adopt the ceremonies, tools, and vocabulary of agile whilst leaving their underlying cultural operating system completely intact. They implement daily standups whilst maintaining rigid approval hierarchies. They create cross-functional teams whilst preserving territorial budget processes. They preach customer collaboration whilst rewarding individual performance metrics that encourage hoarding information and credit.

The result? A thin veneer of agile practices layered over an unchanged command-and-control foundation. When pressure mounts, the old cultural reflexes kick in immediately. Managers bypass their newly empowered teams to make decisions directly. Budget cycles force teams back into detailed upfront planning. Risk-averse executives demand comprehensive documentation.

This happens because Agile isn’t really about processes—it’s about fundamentally different beliefs about human nature, decision-making, and value creation. True Agile requires a collective belief that:

  • People closest to the work make better decisions than distant executives
  • Learning through experimentation beats planning through prediction
  • Responding to change creates more value than following predetermined plans
  • Collaboration trumps individual heroics

Note that these (collective) beliefs align with the Synergistic mindset of the Marshall Model. These beliefs directly challenge the foundational assumptions upon which most large organisations are built—namely, the Analytic mindset as described in Rightshifting and the Marshall Model. It’s worth noting that the Agile Manifesto itself, whilst historically significant in crystallising these ideas, has at this point become little more than an historical curiosity—a fusty old relic that organisations reference whilst systematically ignoring its fundamental principles.

The Executive Comfort Zone Problem

Here’s where executives consistently fail: they want the benefits of cultural transformation without the discomfort of actually changing culture. They’re willing to fund new roles, reorganise teams, and implement new tools. But ask them to genuinely redistribute decision-making authority, eliminate layers of approval processes, or accept that their detailed strategic plans might be wrong, and you’ll encounter fierce resistance.

This resistance isn’t malicious—it’s deeply human. The existing culture got these executives to where they are. It validated their skills, justified their positions, and created their success. Asking them to embrace a fundamentally different approach feels like asking them to invalidate their entire professional identity.

So they compromise. They keep one foot in the old world whilst dipping a toe in the new. They want autonomous teams that still seek approval for every significant decision. They want rapid experimentation within predetermined boundaries. They want cultural transformation without cultural disruption.

This resistance isn’t just rational but deeply psychological – requiring the kind of intervention that organisational psychotherapy provides, rather than traditional change management.

Digital Transformation: Same Problem, Bigger Scale

Now we’re being told that digital transformation is the answer to organisational competitiveness. But digital transformation isn’t really about technology any more than agile transformation is about processes. It’s about completely reimagining how organisations create, deliver, and capture value in a digitally-native world.

True digital transformation requires even more radical cultural shifts than agile adoption:

  • From ownership to access: Success comes from orchestrating ecosystems, not controlling assets
  • From planning to sensing: Markets move too fast for traditional strategic planning cycles
  • From efficiency to adaptability: The ability to change quickly matters more than operational optimisation
  • From competition to collaboration: Value creation happens through partnerships and platforms
  • From products to experiences: Customer relationships matter more than transaction efficiency

These shifts are even more threatening to traditional organisational culture than agile principles. They challenge not just how work gets done, but the fundamental business models and value propositions that justify the organisation’s existence.

The Predictable Pattern

Watch what happens in most digital transformation initiatives:

Phase 1: Excitement and investment. New roles are created (Chief Digital Officer, anyone?), consulting firms are hired, and pilot projects launch with great fanfare.

Phase 2: Technology implementation. Organisations focus on the tangible, measurable aspects—new platforms, data analytics capabilities, customer-facing applications. Progress feels real and quantifiable.

Phase 3: Cultural collision. The new digital capabilities bump up against unchanged organisational behaviours. Decision-making bottlenecks prevent rapid iteration. Risk management processes slow down experimentation. Performance metrics reward short-term efficiency over long-term learning.

Phase 4: Accommodation and retreat. Rather than confronting the cultural barriers, organisations find ways to make the new capabilities fit within existing structures. Digital transformation becomes a series of technology upgrades rather than a fundamental reimagining of how the organisation operates.

Phase 5: Disappointment and blame. When the transformation fails to deliver transformational results, organisations blame the technology, the consultants, or the execution—anything except the cultural foundations they refused to examine.

Why We Keep Believing the Lie

If the pattern is so predictable, why do organisations keep falling into the same trap? Several cognitive biases work together to maintain the illusion:

The technology fallacy: It’s easier to believe that new tools will solve organisational problems than to confront the reality that the problems are human and cultural.

The incremental improvement myth: Organisations convince themselves that they can achieve transformational results through incremental changes, avoiding the disruption of true cultural shift.

The expert outsourcing delusion: Hiring consultants and creating new roles provides the psychological comfort that someone else is responsible for managing the transformation complexity.

The measurement misdirection: Focusing on easily quantifiable metrics (tools deployed, teams trained, processes documented) provides false evidence of progress whilst the deeper cultural work goes unmeasured and undone.

The Uncomfortable Alternative

What would genuine cultural transformation actually require? It would mean executives giving up significant control and accepting genuine uncertainty about outcomes. It would mean dismantling organisational structures that have provided stability and predictability for decades. It would mean acknowledging that many of the skills and approaches that created past success might be liabilities in a rapidly changing environment.

Most fundamentally, it would require leaders to model the vulnerability and learning mindset they’re asking their organisations to adopt. They would need to admit what they don’t know, experiment with approaches that might fail, and change course based on feedback from people lower in the organisational hierarchy.

This level of authentic change is rare because it’s genuinely difficult and risky. It requires leaders who are more committed to organisational success than to their own comfort and certainty.

A Different Question

Instead of asking “How can we make digital transformation successful?”, perhaps we should ask “Are we prepared to become the kind of organisation that digital transformation requires?”

This question cuts through the comfortable mythology and forces honest self-assessment. Most organisations, when confronted with this question directly, would have to answer “no”—and that honesty might be the first step toward genuine transformation.

And honestly answering this question might require the kind of deep self-examination that organisational psychotherapy is designed to facilitate.

The alternative is to continue the expensive charade of surface-level change initiatives that provide the appearance of progress whilst leaving the fundamental constraints unchanged. We can keep funding the consultants, implementing the tools, and reorganising the teams whilst wondering why transformation remains elusive.

But we shouldn’t be surprised when digital transformation fails at the same rate and for the same reasons as agile transformation. The problem was never the methodology or the technology—it was always the culture we’re too attached to change.

Further Reading

Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., … & Thomas, D. (2001). Manifesto for agile software development. Retrieved from http://agilemanifesto.org/

Fitzgerald, M., Kruschwitz, N., Bonnet, D., & Welch, M. (2013). Embracing digital technology: A new strategic imperative. MIT Sloan Management Review, 55(2), 1-12.

Gartner. (2022). Gartner survey shows 75% of organisations are pursuing security vendor consolidation in 2022. Gartner Press Release.

Kotter, J. P. (1995). Leading change: Why transformation efforts fail. Harvard Business Review, 73(2), 59-67.

Marshall, R. W. (2013). The Marshall Model of organisational evolution. Retrieved from https://flowchainsensei.wordpress.com/rightshifting/the-marshall-model/

Rigby, D. K., Sutherland, J., & Takeuchi, H. (2016). Embracing agile. Harvard Business Review, 94(5), 40-50.

VersionOne. (2020). 14th annual state of agile report. VersionOne Inc.

Westerman, G., Bonnet, D., & McAfee, A. (2014). Leading digital: Turning technology into business transformation. Harvard Business Review Press.

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.

Please Steal My Work

With all the hoohah about LLMs stealing folks’ IP (not that I’m a fan of IP in any case), here’s a novel plea maybe worth sharing: Please steal my work. Even relabel it as your own, if that’s good for you. Just one polite request: Would you be willing to let me know how it goes for you and the folks with whom you share it? Thanks! – Bob PS. Coupons are available for those unable to afford the cover price of my books.

Why Change Management Fails

The Hidden Culprit Behind Failed Transformations

When organisations embark on change initiatives, the statistics are sobering: approximately 70% fail to achieve their objectives. The knee-jerk reaction is to blame change management itself—the practices, frameworks, and approaches designed to shepherd organisations through transformations. But this critique misses the mark entirely.

Change management isn’t failing us. Rather, it’s the underlying mindset through which we apply these methods that dooms so many initiatives even before they begin.

The Marshall Model: A Framework for Understanding Organisational Evolution

The Marshal Model – “A Model of Organisational Evolution” provides a powerful context for understanding why so many change initiatives fail. Described as a “Dreyfus Model for organisations,” it maps the journey of organisational effectiveness through seven stages across four fundamental collective mindsets (a.k.a. organisational psyches):

  1. Ad-hoc: Characterised by chaos, making up how to do things on the spur of the moment, in tha face of e.g. crises
  2. Analytic: Focused on rules, processes, hierarchies and structured approaches
  3. Synergistic: Systems-thinking oriented, recognising interdependencies and the key role of “socio-” in “socio-technical systems”
  4. Chaordic: Intuitive, adaptive, and thriving at the overlapping edge of chaos and order

According to the Marshall Model, most organisations cluster in the left-most portion of this spectrum—primarily in the Ad-hoc and Analytic mindsets (Marshall, 2010). These mindsets are precisely where our change management problems begin.

Diagram illustrating the four mindsets of organisational transformation, with the Rightshifting curve behind3d diagram of the Marshall Model

The Analytic Mindset Trap

The Analytic mindset, as the Marshall Model defines it, “exemplifies, to a large extent, the principles of Scientific Management a.k.a. Taylorism.” Typical characteristics include:

  • A Theory-X posture toward staff
  • A mechanistic view of organisational structure (hierarchies and functional silos)
  • Local optimisation over system-wide effectiveness
  • Middle-managers as owners of “the way the work works”
  • Command-and-control style management

This mindset dominates modern corporates and thus modern corporate change management, manifesting in detailed change plans, comprehensive stakeholder analyses, meticulously documented communication strategies, and carefully plotted implementation roadmaps.

On paper, this approach appears obvious, thorough and professional. In practice, it most often fails spectacularly.

Why the Analytic Mindset Fails Change Initiatives

The Analytic mindset appears to offer what traditional change management values—structured processes, documentation, clear rules, and methodical planning. However, these very characteristics that seem beneficial actually create fundamental problems when applied to complex human systems. The Analytic approach fails change initiatives in several critical ways:

1. It treats organisations as machines rather than living systems

The Marshall Model notes that Analytic organisations view themselves mechanistically, with functional silos and local optimisation. This approach fundamentally misunderstands the organic, emergent nature of human systems.

As the Marshall Model suggests, more effective organisations (those in the much rarer Synergistic and Chaordic mindsets) recognise that “individual tasks within an organisation are co-dependent on each other, and only have relevance in getting some larger end purpose accomplished.”

2. It overvalues rigid adherence to rules

The Marshall Model characterises Novice Analytical organisations as showing “rigid adherence to rules” with “little or no discretionary judgement.” When this mindset is applied to change management, it creates brittleness precisely when adaptability is most needed.

The model suggests that more effective, e.g. Quintessential, organisations evolve beyond this rule-fixation towards seeing situations holistically, using maxims for guidance where “meaning may vary according to context.”

3. It fragments the organisation into disconnected parts

In the Competent Analytical stage, “all areas of the business are treated separately and given equal encouragement to improve,” with a “situational perception still unwittingly focussed on local optima.”

This fragmentation creates change initiatives that optimise departmental functions at the expense of the whole system, missing what the Marshall Model describes as the Synergistic awareness of “constraints, whole-system throughput and capabilities.”

4. It remains unconsciously incompetent

Perhaps most critically, the Marshall Model notes that organisations in the Ad-hoc and Analytic mindsets share a common characteristic: they are “unconsciously incompetent.” They don’t know what they don’t know.

This explains why so many change initiatives powered by the Analytic mindset proceed with supreme confidence despite fundamental flaws in their approach. The organisation lacks the metacognitive capacity to recognise its own limitations.

(Note: We speak here mainly of the shortcomings of Analytic-minded organisations, as Ad-hoc minded organisations are unlikelt to even consider change management as an option).

Moving Toward More Effective Change: The Synergistic Mindset

The Marshall Model suggests that to improve effectiveness, organisations might choose to evolve toward the Synergistic mindset, characterised by:

  • A Theory-Y orientation (respect for people)
  • An organic, emergent, complex-adaptive socio-technical system view
  • Organisation-wide focus on learning, flow of value, and effectiveness
  • Middle-managers respected for experience and domain knowledge and redeployed as servant leaders
  • Self-organising teams and systemic improvement efforts

This evolution doesn’t happen easily. The Marshall Model notes that between eachof the four mindset lies a “transition zone” where “major upheaval—in the form of a shift of mindset—is required to proceed further.” See: Organisational Psychotherapy as explained in detail and at length in my book “Hearts Over Diamonds”.

Practical Implications for Change Management

Understanding the Marshall Model fundamentally shifts how we might choose to approach change management and organisational change:

  1. Recognise our current mindset: Most organisations attempting change initiatives operate from the Analytic mindset, with all its accompanying limitations
  2. Build awareness of the transition challenge: Moving from Analytic to Synergistic thinking requires what the Marshall Model calls “major upheaval” that preserves “the momentum of change at major decision points”
  3. Adopt systems thinking: Seeing the organisation as an interconnected whole rather than separate parts to be optimised independently
  4. Embrace conscious incompetence: The Early Synergistic stage involves “conscious, deliberate consideration of the organisation as a system” and acknowledging what we don’t yet know
  5. Expect resistance: The Marshall Model warns of the “potential for reversion to Analytical thinking” during the transition, indicating the need for vigilance and persistence

Conclusion: Change Management Through a New Lens

Change management approaches aren’t inherently flawed—they’re being applied through an constraining mindset that guarantees suboptimal results. The Marshall Model helps us understand that lasting organisational change requires more than process improvements; it demands fundamental shifts in how we perceive organisations themselves – in our collective assumptions and beliefs about work and how work works. See alseo: Quintessence.

As the author himself notes, “The prevailing mindset of an organisation comprehensively determines how effective it is, and moreover, how effective it can hope to become.”

Perhaps the most important step in improving change outcomes isn’t adopting new change mangement practices but evolving the mindset through which we apply them—moving from the mechanistic Analytic view that dominates most change initiatives toward the more holistic, systemic perspective that characterises truly effective organisations.

Further Reading

Marshall, RW. (2018). Hearts over diamonds: Serving business and society through organisational psychotherapy. Falling Blossoms. https://leanpub.com/heartsoverdiamonds

Marshall, RW. (2021). Memeology: Surfacing the memes of your organisation. Falling Blossoms. https://leanpub.com/memeology

Marshall, RW. (2022).Quintessence: An acme for highly effective software development organisations. Falling Blossoms. https://leanpub.com/quintessence

Marshall, RW. (2010). The Marshall Model of Organisational Evolution: Dreyfus for the Organisation. Falling Blossoms White Paper Series. Retrieved from https://flowchainsensei.wordpress.com/wp-content/uploads/2019/08/fbwpmmoe51.pdf

Is Software Development Really a Kind of Collaborative Knowledge Work?

Software development has long occupied a unique space in the world of human endeavour. Whilst its outputs are tangible—functioning applications, systems, and digital tools—the process itself is largely invisible to outsiders. This raises an interesting question: Is software development truly a form of collaborative knowledge work (CKW), or are we perhaps mischaracterising its nature?

The Origins of Collaborative Knowledge Work

The term “collaborative knowledge work” has its roots in Peter Drucker’s pioneering analysis of the post-industrial economy. In his seminal 1959 work “Landmarks of Tomorrow,” Drucker introduced the term “knowledge worker” to describe professionals who work primarily with information and theoretical knowledge. This marked a crucial shift from traditional manual labour to what he saw as an emerging class of workers whose primary capital was knowledge rather than manual skills or physical resources.

Drucker’s insight wasn’t merely descriptive—it was predictive. He foresaw that the majority of work in developed economies would eventually center around the creation, manipulation, and application of knowledge. Throughout the 1960s and 1970s, he further developed this concept, arguing that knowledge had become the primary economic resource, displacing traditional factors of production like land, labour, and capital.

The collaborative aspect of knowledge work emerged as organisations began to grapple with the implications of Drucker’s observations. The increasing complexity of knowledge-based tasks meant that no single individual could possess all the necessary expertise. This led to the recognition that effective knowledge work required not just individual expertise, but the ability to combine and leverage diverse knowledge through collaboration.

By the 1990s, researchers and practitioners had begun explicitly examining the collaborative nature of knowledge work. The term “collaborative knowledge work” emerged from the intersection of:

  1. Drucker’s knowledge worker concept
  2. Research into computer-supported cooperative work (CSCW)
  3. Studies of organisational learning and knowledge management
  4. The rise of global, distributed teams enabled by technology

This evolution reflected a deeper understanding that knowledge work isn’t just individual cognitive labour—it’s inherently social and collaborative. Modern knowledge work involves complex networks of interaction, where value is created not just through individual expertise, but more through the synthesis and combination of multiple perspectives and knowledge domains.

The emergence of software development as a discipline coincided with this theoretical evolution. As software systems grew more complex and interconnected, the field naturally embodied many of the principles Drucker and subsequent researchers identified as characteristic of knowledge work. The highly collaborative nature of modern software development, with its emphasis on shared understanding, collective problem-solving, team work, and continuous learning, makes it a particularly illuminating example of collaborative knowledge work in practice.

Understanding Collaborative Knowledge Work

Before diving into software development specifically, let’s establish what we mean by collaborative knowledge work. CKW typically involves:

  1. Complex problem-solving requiring specialised expertise
  2. High levels of interdependence between team members
  3. The creation and sharing of new knowledge
  4. Continuous learning and adaptation
  5. Work that is primarily cognitive rather than physical

The Software Development Landscape

When we examine modern software development practices, the parallels to CKW become striking. Consider a typical development team working on a complex application:

Knowledge Creation and Sharing

Developers constantly create new knowledge through:

  • Architecture decisions that shape system design
  • Novel solutions to technical challenges
  • Documentation that captures insights and rationale
  • Code reviews that spread understanding across the team
  • Technical specifications that crystallise shared understanding

Collaborative Nature

The collaborative aspects are evident in:

  • Pair programming sessions
  • Team-wide architecture discussions
  • Cross-functional planning meetings
  • Shared ownership of code bases
  • Collective code review processes

Continuous Learning

Software development demands perpetual learning:

  • Keeping up with new technologies and frameworks
  • Understanding evolving security threats
  • Learning from production incidents
  • Adapting to changing user needs
  • Improving development processes

Beyond Simple Collaboration

What makes software development particularly interesting as CKW is its layered nature. Developers collaborate not just with their immediate teammates, but with:

  • Future maintainers through clear code and documentation
  • The broader developer community through open source contributions
  • Users through feature development and bug fixes
  • Past developers through code archaeology and maintenance
  • Tools and frameworks through API usage and integration

The Knowledge Dimension

The knowledge aspects of software development are profound:

  1. Tacit Knowledge: Much of a developer’s expertise cannot be easily documented—it’s built through experience and practice.
  2. Explicit Knowledge: Code, documentation, and artefacts represent crystallised knowledge that can be shared and built upon.
  3. Meta-Knowledge: Understanding how to structure, maintain, and evolve complex systems requires high-level thinking about knowledge itself.

Addressing Counter-Arguments

Some might argue that software development is more akin to craft work or engineering than knowledge work. However, this view misses several key points:

  1. Whilst there are craft aspects to coding, modern software development involves far more than just writing code.
  2. The complexity of software systems requires constant knowledge creation and sharing that goes beyond traditional engineering disciplines.
  3. The rapid pace of technological change means that the knowledge component of software development is constantly evolving.

Why It Matters – The Pitfalls of Category Errors

Misclassifying the nature of software development work can lead to significant organisational dysfunction. When companies treat software development as purely technical work or simple task execution, several problems emerge:

  1. Metrics Misalignment: Measuring software development through simplistic metrics like lines of code or number of tickets closed fundamentally misunderstands the knowledge-intensive nature of the work. This can lead to perverse incentives and poor quality outcomes.
  2. Resource Allocation Errors: Treating development as purely technical work often results in insufficient allocation of time and resources for crucial knowledge-building activities like architecture discussions, code reviews, and documentation.
  3. Communication Breakdown: Failing to recognise the collaborative knowledge aspects can lead to communication structures that hinder rather than enable effective knowledge sharing and creation.
  4. Talent Management Issues: When organisations view software development primarily as task execution, they often struggle with:
    • Retention of experienced developers who feel undervalued
    • Career progression paths that don’t acknowledge the knowledge dimension
    • Training programmes that focus too heavily on technical skills while neglecting collaborative and knowledge-sharing capabilities
  5. Process Misalignment: Implementing processes designed for routine production work can actively harm software development efforts by:
    • Fragmenting knowledge work into artificial task boundaries
    • Reducing opportunities for collaborative problem-solving
    • Creating unnecessary documentation overhead that doesn’t contribute to shared understanding
  6. Innovation Barriers: Treating software development as purely technical execution can stifle innovation by:
    • Limiting cross-pollination of ideas
    • Reducing experimentation opportunities
    • Constraining the organic evolution of solutions
  7. Quality Impact: When the knowledge work aspect is overlooked, quality often suffers through:
    • Reduced emphasis on building shared understanding
    • Limited investment in architectural knowledge
    • Insufficient attention to knowledge transfer and maintenance
  8. Management Monstrosities: Miscategorising software development as other than CKW means it will get managed inappropriately.

The consequences of these category errors can be severe and long-lasting, affecting not just the immediate software development process but the entire organisation’s ability to leverage technology effectively.

Conclusion

After careful analysis, it’s clear that software development isn’t just collaborative knowledge work—it’s perhaps one of the purest examples of CKW in the modern economy. The combination of:

  • Complex problem-solving
  • Team-based knowledge creation
  • Continuous learning requirements
  • High interdependence
  • Meta-knowledge management

Makes software development a quintessential form of collaborative knowledge work. Far from deluding ourselves, recognising software development as CKW helps us better understand its nature and potentially improve how we approach it.

This recognition has important implications for:

  • How we structure development teams
  • The tools and processes we use
  • How we measure productivity
  • How we train and develop software professionals
  • The way we manage software projects

Understanding software development as collaborative knowledge work isn’t just an academic exercise—it’s a crucial insight that can help us build better software, more effectively, with happier and more productive teams.

The Software Crisis: A Failure of Imagination and Commitment

Understanding the Software Crisis: A Historical Perspective

The Software Crisis represents a fundamental challenge in technological development that has persistently haunted the computing world since its emergence in the late 1960s. First articulated by computer scientists at the NATO Software Engineering Conference in 1968, this term encapsulates the ever-present disconnect between our technological ambitions and our capacity to create reliable, efficient, and manageable software systems.

The Roots of the Crisis: Complexity Beyond Control

At its essence, the Software Crisis emerged from an exponential growth in system complexity that far outpaced human cognitive capabilities. Where traditional engineering disciplines deal with predictable, measurable materials, software development confronts an almost infinite landscape of potential interactions, variables, and unforeseen, largely people-oreiented, complications.

The Dimensionality of Technological Complexity

Consider software development as navigating a multidimensional maze where:

  • Each line of code introduces multiple potential pathways
  • Interactions between components create exponentially increasing complexity
  • Human error can cascade into systemic failures
  • Technological landscapes shift continuously
  • People issues (assumptions, beliefs, relationships, and the like) transcend all the above

Engineering Aspirations Versus Harsh Realities

While software development has long aspired to be a rigorous engineering discipline, the ever-present Software Crisis reveals the profound limitations of this approach. Traditional engineering relies on:

  • Predictable material properties
  • Stable, well-understood physical laws
  • Precise mathematical modelling
  • Consistent performance metrics

Software development, by contrast, operates in a realm of:

  • Constant technological transformation
  • Unpredictable human creativity
  • Rapidly evolving requirements
  • Inherent system instability
  • Human beings

Generational Capitulation: The Abdication of Technological Responsibility

The most disturbing aspect of the Software Crisis is not its existence, but the contemporary generation’s abject surrender to its challenges. Where early pioneers such as Edsger W. Dijkstra, Donald Knuth, and Fred Brooks fought passionately to address fundamental limitations, today’s software developers have largely descended into a culture of complacent mediocrity.

The Demotivated Developer: A Portrait of Resignation

Modern software development has transformed from a noble pursuit of solving complex problems – such as just how to go about software development –  into a landscape of:

  • Minimal intellectual ambition
  • Preference for copy-paste solutions
  • Wholesale abandonment of rigorous design anmd engineering principles
  • Celebration of quick, disposable implementations
  • Systematic avoidance of deep systemic thinking

The Myth of Pragmatism: Disguised Indifference

Contemporary developers cloak their lack of commitment in the language of “pragmatism”. They argue that accepting imperfection is a mature approach. In reality, this is nothing more than an elaborate rationalization for intellectual surrender.

Technological Stockholm Syndrome

These developers have not solved the Software Crisis—they have Stockholm-syndromed themselves into believing the crisis is an immutable condition rather than a challenge to be conquered. They prefer:

  • Using pre-built libraries instead of understanding core principles
  • Rapid development over robust architecture
  • Temporary solutions over enduring designs
  • Avoiding complexity rather than mastering it
  • Ignoring key aspects such as psychology and human behaviour

The Lost Generation of Ambitious Problem Solvers

Where previous generations of computer scientists and though leaders saw technological challenges as Mount Everests to be conquered, today’s developers view them as immovable mountains to be meekly navigated around. The passion for fundamental problem-solving has been replaced by a depressing culture of resignation.

Acceptance: A Euphemism for Failure

After more than fifty years of attempts, many argue that the Software Crisis is a condition to be managed rather than solved. This is not wisdom—it is capitulation. It represents a collective failure of imagination, ambition, and intellectual rigour.

Conclusion: A Call to Arms

Our ongoing Software Crisis is not an immutable law of nature. It is a challenge that demands relentless engagement, systematic thinking, and an unwavering commitment to pushing technological boundaries.

To the current generation of software developers: your complacency is not pragmatism. It is the slow death of innovation. The Software Crisis will continue to exist precisely because you have collectively decided to accept its existence rather than challenge it.

True innovation has never emerged from acceptance. It emerges from a refusal to be defeated. I myself continue to reject such defeatism.

Replacing Executives With AI

The AI Executive Is Already Here

The algorithmic transformation of corporate leadership is already underway. BlackRock’s Aladdin platform helps financial institutions worldwide manage and analyze investment portfolios worth trillions of dollars. Major corporations increasingly rely on AI systems for strategic decision-making, from supply chain optimization to risk assessment. The future isn’t coming; it’s already arrived, albeit quietly and without a corner office.

AI is by now well known for its errors and hallucinations—its tendency to confidently assert falsehoods and make peculiar mistakes. So an ideal tool to replace the tools running our organisations today? At first glance, AI might seem a preposterous basis for replacing human leadership. Yet, when we consider the track record of human executives—the spectacular corporate failures, the misguided mergers, the missed technological revolutions, and the countless strategic blunders that have sunk formerly mighty organisations—perhaps AI’s occasional confabulations don’t seem so disqualifying after all. At least AI’s errors are predictable, measurable, and systematically improvable, unlike human hubris and groupthink.

The Case for Silicon Leadership

What AI Brings to the Boardroom

  • Data Processing at Scale: Modern AI systems can analyze vast datasets to identify patterns and trends beyond human capability
  • Consistent Decision-Making: AI systems apply the same criteria consistently across decisions
  • Real-time Adaptation: Ability to continuously update strategies based on incoming data
  • Audit Trails: Every decision can be traced back to its underlying data and logic
  • Systematic Learning: Capability to learn from outcomes across multiple scenarios

Real-World Applications and Limitations

In the financial sector, algorithmic trading systems now handle the majority of stock market transactions, demonstrating how AI can manage complex, real-time decisions. However, the 2010 Flash Crash showed the risks of automated systems operating without proper oversight, leading to new regulations for algorithmic trading.

Similar patterns emerge in other industries.

The Human Cost and Opportunity

Beyond the C-Suite

The integration of AI into corporate decision-making is already reshaping organisational structures. According to a 2023 McKinsey study, companies are increasingly automating routine management tasks while creating new roles focused on AI oversight and implementation.

Emerging Roles

The transformation is creating new positions that bridge the gap between traditional management and AI system, and providing candidate positions for AI tro ease into:

AI Risk Officers

“Quis custodiet ipsos custodes?”

Senior positions responsible for overseeing AI-related risks across the organisation. They evaluate potential failures, biases, and unintended consequences of AI systems. Specific duties include:

  • Developing AI risk frameworks
  • Monitoring AI system performance and safety
  • Coordinating responses to AI-related incidents
  • Ensuring AI systems operate within acceptable risk parameters
  • Liaising with regulatory bodies on AI compliance
Algorithmic Compliance Managers

Specialists who ensure AI systems meet regulatory requirements and internal governance standards. Their role encompasses:

  • Auditing AI decision-making processes
  • Documenting algorithm changes and updates
  • Ensuring transparency in automated decisions
  • Managing model validation procedures
  • Maintaining compliance with AI-specific regulations
  • Overseeing algorithmic impact assessments
AI-Human Interface Designers

Experts who design and optimise the interaction between human employees and AI systems. Their responsibilities include:

  • Creating intuitive interfaces for AI tools
  • Developing protocols for AI-human collaboration
  • Optimising workflow integration between AI and human teams
  • Training staff on effective AI collaboration
  • Gathering and implementing user feedback
  • Ensuring AI systems complement rather than frustrate human work
Digital Ethics Officers

Positions focused on the ethical implications of AI deployment in business operations. Their role involves:

  • Developing ethical frameworks for AI use
  • Ensuring AI decisions align with company values
  • Addressing bias and fairness in AI systems
  • Managing stakeholder concerns about AI deployment
  • Overseeing ethical impact assessments
  • Establishing guidelines for responsible AI use

These roles reflect a crucial shift in corporate structure where the focus isn’t on replacing human judgment but on creating frameworks for effective human-AI collaboration. Each position requires a unique blend of technical knowledge, business acumen, and understanding of human factors.

Implementation: Current State of Practice

Case Study: Supply Chain Management

Major retailers like Walmart and Amazon use AI systems for inventory management and demand forecasting. These systems have demonstrated success in:

  1. Reducing stockouts
  2. Optimizing delivery routes
  3. Predicting seasonal demand
  4. Managing supplier relationships

The Regulatory Landscape

Existing Frameworks

Current corporate governance frameworks are being tested by AI implementation:

  • The EU’s AI Act proposes specific requirements for high-risk AI systems in business (note: none of these requirements apply to high-risk human executives)
  • The SEC has guidelines for algorithmic trading systems
  • Financial regulators worldwide are developing AI governance frameworks

Key Regulatory Challenges

  • Establishing clear accountability for AI decisions (wouldn’t it be nice to have clear accountability for human decisions, too?)
  • Ensuring transparency in algorithmic decision-making (ditto for human decision-making)
  • Protecting against systemic risks (hah!)
  • Maintaining fair competition (double hah!)

Looking Ahead: The Inevitable AI Takeover

Let’s be brutally honest: human executives are running on borrowed time. While the current narrative favours a diplomatic “hybrid” approach, the trajectory is clear. AI will replace most human executives, and likely sooner than we care to admit.

Consider the fundamentals: AI systems don’t play office politics, don’t demand golden parachutes, don’t make decisions based on ego, and don’t suffer from the cognitive biases that plague human decision-making. They don’t take two-hour lunch breaks, form old boys’ networks, act like sexual predators, or make crucial decisions based on who they played golf with last weekend.

More importantly, AI systems are improving exponentially while human executive capability remains largely static. Our current crop of executives was trained for a world that no longer exists—one where quarterly planning cycles made sense and where gut feeling was a valid business tool. Today’s business environment demands an absence of human cognitive biases, and real-time adaptation to vast streams of data, something humans simply cannot do effectively.

The resistance to full AI leadership stems more from human psychology than business logic. We comfort ourselves with platitudes about human judgment and emotional intelligence, but the data increasingly shows that many supposed “human” leadership qualities can be effectively simulated or rendered unnecessary by well-designed systems. And that’s before we even start looking critically at the whole “leadership” landscape.

The “Quis custodiet ipsos custodes?”—who guards the guards—question that has haunted human power structures for millennia becomes elegantly dissolvable with AI executives. Unlike their human counterparts, AI systems can be made truly transparent, their decision-making processes fully auditable, their biases measurable and correctable.

The organisations that will dominate the next decades won’t be those that find the perfect balance between human and machine leadership. They’ll be those that have the courage to fully embrace AI leadership, relegating humans to advisory and oversight roles rather than executive decision-making positions. The future of leadership isn’t a dance between silicon and carbon—it’s a changing of the guard.

For those executives reading this: your best career move might be positioning yourself as part of the transition team rather than resisting the inevitable. The writing isn’t just on the wall; it’s in the data, the algorithms, and the bottom line.

Conclusion: The Path Forward

The transformation of corporate leadership through AI is not a simple replacement of humans with machines. Instead, it’s an evolution toward systems that leverage AI’s undoubted strengths. Success will come to organisations that can effectively exploit these elements while maintaining strong governance and risk management frameworks (also AI-enabled).

The key is not to ask whether AI will replace human executives, but how long will it take to happen? AI is the true “innovation” to which so many organisations have been, as yet, only paying lip service.

The Inevitable Disaster: Management’s Poison Touch in Software Development

The Undeniable Truth: Management Always Makes It Worse

In the world of software development, one truth stands above all others: every single management intervention, without exception, makes things worse. This isn’t an exaggeration or a pessimistic view – it’s the cold, hard reality that developers face – and that I’ve personally seen time and time again – every day. Management, in its infinite wisdom, has a reverse Midas touch: everything it touches turns to doodoo.

The Destruction Derby: How Management Ruins Everything

1. Process Pollution

When management meddles with development approaches, the result is always the same: a bureaucratic nightmare that strangles productivity.

Example: A once-streamlined workflow becomes a kafka-esque labyrinth of checkpoints, approvals, meetings, and pointless documentation, turning an hour’s work into a week-long ordeal.

2. Tool Tyranny

Every tool foisted upon developers by management inevitably becomes an instrument of torture, with JIRA standing out as the crown jewel of developer torment.

Example: JIRA, the project management tool from hell, crapped upon teams by managers who mistake micromanagement for productivity. What was once a simple task of writing code becomes a Kafkaesque nightmare of logging hours, updating statuses, and navigating through a labyrinth of epics, stories, and sub-tasks. Developers spend more time wrestling with JIRA’s byzantine interface than actually coding, turning a day’s work into a weeks-long ordeal of clickety-click busywork. The result? A beautiful illusion of control for managers, and a soul-crushing reality for developers who watch their productivity vanish into the abyss of over-engineered management.

3. Team Toxification

Management’s attempts to “improve” team dynamics invariably poison the well of camaraderie and fellowship.

Example: A so-called team-building exercise that pits developers against each other, destroying trust and turning a once-cohesive unit into a den of paranoia and backstabbing.

The Laws of Managerial Destruction

The Metric Massacre

Every metric introduced by management becomes a weapon of mass dysfunction. No exceptions.

Example: Story point targets that turn thoughtful estimation into a farce, with developers inflating numbers just to keep management off their backs.

The Communication Catastrophe

When management tries to “improve communication,” it always results in an avalanche of noise that buries any actual signal.

Example: A new “open communication” policy that floods inboxes with useless updates, ensuring that important messages are lost in a sea of managerial spam. In my past, Sun Microsystems was a classic example of this.

The Expertise Annihilation

The more confidently management intervenes in technical matters, the more spectacular the ensuing disaster.

Example: A clueless executive’s insistence on using blockchain for a simple CRUD application, leading to a bloated, unusable system that solves no problems while creating a hundred new ones.

The Motivation Massacre

Every single management initiative aimed at “boosting morale” is a guaranteed morale killer.

Example: A “fun” gamification system for code commits that turns professional developers into point-chasing automatons, stripping away any remaining job satisfaction.See also: the Cobra Effect.

The Innovation Graveyard

Management’s efforts to “foster innovation” are where good ideas go to die.

Example: An “innovation lab” that’s really just a purgatory for creative thinking, where ideas are committee’d to death before they can see the light of day.

The Inescapable Conclusion: Management Must Go

As we sift through the wreckage of countless failed management interventions, one inescapable conclusion emerges: in software development, management is not just useless – it’s actively toxic. There is not a single documented case, anywhere in the history of software development, where a management initiative has improved things. Not one.

This isn’t about bad managers or poor implementation – it’s about the fundamental incompatibility between traditional management thinking and the reality of software development. The chasm between management’s perception and the actual work of creating software is so vast that every attempt to bridge it only makes things worse.

The solution is as clear as it is radical: the complete and total removal of management from software development. No more “agile coaches,” no more “scrum masters,” no more “project managers.” Just developers, doing what they do best, free from the poisonous touch of management.

The Path Forward: A Management-Free Utopia

The future of software development lies not in “better” management, but in no management at all. Only by excising the cancer of managerial meddling can we hope to unleash the true potential of software teams.

Imagine a world where developers are free to organise their own work, choose their own tools, and communicate in ways that actually make sense for them. A world where innovation isn’t stifled by bureaucracy, where motivation comes from the work – from meeting folks’ needs –  itself rather than arbitrary metrics, and where expertise is valued over authority.

This isn’t a pipe dream – it’s the only way forward. The age of management in software development is over. It’s time to embrace the chaos, trust in the expertise of developers, and finally bid farewell to the destructive force that is management in software development.

The best thing management can do for software development is simple: get out of the way, and stay out. Only then can we break free from the cycle of perpetual deterioration that has plagued our industry for far too long.

Tech Companies Favour Conformity Over Experience

The Shifting Landscape of Tech Talent Demand

In today’s tech job market, a counterintuitive trend has emerged: the increasing preference for junior talent over seasoned professionals. This shift reflects a deeper issue within the industry – the prioritisation of conformity over competence and experience.

The New Normal: Embracing Malleability Over Mastery

  • Junior Talent Boom: Companies are increasingly favoring recent graduates and bootcamp alumni.
  • Cost-Effective Conformity: Junior hires are often seen as more affordable and easier to mold to company culture.
  • The Experience Paradox: Despite the industry’s rapid pace of change, extensive experience is sometimes viewed as a liability rather than an asset.

The Conformity Conundrum: Why Juniors Have the Upper Hand

The tech industry’s growing preference for junior talent is intrinsically linked to a culture that values conformity over critical thinking and innovation.

The Allure of the Impressionable ‘Blank Slate’

We all know that management is synonymous with Command and Control. No surpise then that managers looking for “safe” hires primarily seek hires they feel can be easily commanded and controlled. Hence juniors:

  1. Malleability: Junior employees are often perceived as more conformable to company-specific practices and technologies.
  2. Enthusiasm Without Dissent: Less experienced hires may be more likely to accept established processes without question.
  3. Cultural Indoctrination: It’s easier to instill company values and methods in those with less prior exposure to different workplace cultures.
  4. Innovation on a Leash: While juniors might bring fresh ideas, they typically lack the confidence or clout to push for significant changes.

The Senior Squeeze: Experience as a Double-Edged Sword

As companies lean towards junior talent, senior professionals find themselves in an increasingly precarious position.

The ‘Overqualified’ Paradox

Command and Control managers – the vast majority, then – will naturally steer away from hiring seniors:

  • Perceived Inflexibility: Seasoned seniors are often unfairly assumed to be set in their ways and resistant to new approaches.
  • Threat to Status Quo: Experienced hires might challenge existing – status quo – practices, which can be seen as disruptive rather than valuable.
  • Salary Expectations: Higher salary requirements for senior roles can make juniors seem more attractive, especially in a cost-conscious market. It’s long been said that managers know the cost of everything and the value of nothing.
  • The ‘Outdated Skills’ Myth: Despite their adaptability, senior devs are sometimes unfairly perceived as having outdated technical skills.And people skills rarely get a look in.

The Hidden Costs of the Junior-First Approach

While the preference for junior talent may seem advantageous in the short term, it carries significant long-term risks for companies.

The Price of Inexperience

  1. Knowledge Gaps: Over-reliance on junior talent can lead to critical gaps in deep technical knowledge and industry wisdom.
  2. Reinventing the Wheel: Without experienced guidance, teams may waste time solving problems that have already been addressed in the industry.
  3. Mentorship Vacuum: A lack of senior professionals can hinder the growth and development of junior talent.
  4. Decreased Problem-Solving Capacity: Complex issues often require the nuanced understanding that comes with years of experience.

Strategies for a Balanced Tech Ecosystem

To create a more robust and innovative tech industry, companies might choose to rethink their approach to talent acquisition and development.

For Companies: Bridging the Experience Gap

  1. Value Diverse Experience: Recognise the unique contributions of both junior enthusiasm and senior wisdom.
  2. Create Mentorship Programs: Pair junior and senior employees to facilitate knowledge transfer and mutual learning.
  3. Implement Blind Hiring Practices: Use skill-based assessments to evaluate candidates objectively, regardless of experience level.
  4. Foster Intergenerational Innovation: Create mixed-experience teams to tackle complex problems, leveraging diverse perspectives.

For Tech People: Navigating the New Landscape

  1. For Juniors:
    • Embrace learning opportunities while respectfully offering fresh perspectives.
    • Seek sponsored mentorship from more experienced colleagues.
    • Develop critical thinking skills and people skills to complement technical abilities.
  2. For Seniors:
    • Emphasise adaptability and continuous learning in your personal brand.
    • Showcase instances where your experience led to innovative solutions or prevented costly mistakes.
    • Consider roles where your mentorship and strategic thinking are explicitly valued.

The Future of Tech Talent: Balancing Fresh Perspectives and Seasoned Wisdom

As we look ahead, it’s clear that the tech industry’s current bias towards junior talent and conformity is unsustainable. True innovation and growth require a delicate balance of fresh ideas and hard-won wisdom.

For the industry to thrive, companies might choose to learn to create environments where both junior and senior professionals can flourish. This means valuing the energy and adaptability of junior talent while also recognising the crucial role of experience in driving meaningful innovation and avoiding costly missteps.

By addressing the junior paradox and creating truly diverse teams – in terms of both age and thinking styles – we can build tech ecosystems that are not just productive in the short term, but truly innovative and sustainable in the long run. This balanced approach will be crucial in tackling the complex, multifaceted challenges that the future of technology will inevitably bring.

The Transformative Power of a Simple Question in Organisational Psychotherapy

Large red 3D question mark

Introduction: A Gateway to Workplace Transformation

In the practice of Organisational Psychotherapy (OP), where the focus is on elevating the quality of life for every individual within an organisation, one question stands as a beacon of change: “What would you like to have happen?” This seemingly straightforward inquiry serves as a powerful catalyst, unlocking doors to profound insights and transformative shifts in workplace dynamics.

The Evolution of a Powerful Query

From Therapy to Organisational Change

Rooted in therapeutic approaches like Solution-Focused Brief Therapy and Cognitive Behavioural Therapy, this question has found a new home in OP. It marks a shift to positive approaches that focus on overall well-being at work.

The Psychological Mechanics: Why This Question Resonates

Crafting a Vision of The Ideal Workplace

By prompting individuals to articulate their ideal scenarios, this question gently guides them away from problem-focused thinking. It’s not just about identifying issues; it’s about eliciting a vivid, shared picture of a workplace where everyone thrives.

Empowerment Through Imagination

The question subtly implies that change is not only possible but within reach. It places the brush in the hands of the employees, allowing them to paint their own canvas of workplace satisfaction.

Unearthing Hidden Aspirations

Often, the most brilliant ideas for improving workplace culture lie dormant in the minds of employees. This question acts as a gentle excavator, bringing these treasures to the surface where they can be examined and potentially implemented.

Surfacing Unvoiced Dissonance

Many times in an organisation, different folks will have different perspective on the kind of future ideal they each have in mind. Asking the question in group settings invites folks to shares their differing assumptions and beliefs, and maybe move towards a more common shared perspective.

Practical Implementations: From Theory to Practice

Revolutionising Team Dynamics

Imagine starting every team meeting with this question. It sets a tone of possibility and collaboration, steering discussions towards constructive outcomes and shared visions.

Transforming One-on-One Interactions

In individual sessions, this question becomes a compass, helping employees navigate their personal and professional aspirations within the larger organisational needsscape.

A New Approach to Conflict Resolution

When tensions arise, this question can act as a bridge, shifting the focus from past grievances to future harmony. It encourages parties to envision a shared positive outcome, fostering collaboration rather than competition.

Navigating Challenges: When the Question Meets Resistance

Dealing with Vague or Seemingly Unrealistic Responses

Not everyone can immediately articulate a clear vision. Here, the skill lies in asking gentle follow-up questions, helping individuals refine their thoughts and translate abstract desires into concrete possibilities.

Overcoming the Inertia of Cynicism

In environments where past attempts at change have failed, cynicism can be a formidable barrier. Patience, coupled with small, visible wins, can gradually erode this resistance, reigniting belief in the possibility of positive change.

The Antimatter Principle: A Deeper Dive

“What do you need to have happen?”

This alternative framing, rooted in the Antimatter Principle, shifts the focus from wants to fundamental needs. While powerful, it’s a tool to be used judiciously.

The Challenge of Needs-Based Inquiry

Directly asking about needs can sometimes lead to cognitive roadblocks. Many individuals haven’t consciously explored their – let alone others’ – core needs, especially in a work context. This is why starting with “like to have happen” often proves more effective as an opening.

A Strategic Progression

By beginning with desires and gradually transitioning to needs, we create a safer space for deeper exploration. This progression allows individuals to peel back layers of surface wants to reveal the bedrock of true needs.

Conclusion: The Ripple Effect of a Simple Question

In the grand tapestry of Organisational Psychotherapy, “What would you like to have happen?” is not just a question; it’s a philosophy. It embodies the belief that within every individual and group lies the seed of positive change. By nurturing these seeds through thoughtful inquiry, we can cultivate workplaces that don’t just function, but flourish – environments where every person feels valued, heard, and empowered to contribute to the collective well-being.An where it’s more likely that folks’ needs will get attended to.

As practitioners, leaders, or simply as colleagues, we hold the power to initiate transformation with this simple yet profound question. In doing so, we don’t just change conversations; we change cultures, and ultimately, we change lives.

Organisational Psychotherapy: Helping Organisations Find Their Own Truths

What Is Organisational Psychotherapy?

Organisational Psychotherapy is a relatively new field that applies psychotherapeutic (talk therapy) principles to the workplace. It aims to help organisations surface and reflect on their own dynamics, behaviours, and underlying issues. Much like individual talk therapy, this approach encourages organisations to explore their own truths and discover shared assumptions and beliefs that work best for them.

The Need for Organisational Self-Discovery

The Complexity of Modern Organisations

In the world of business, organisations face numerous challenges. From rapid technological advancements to shifting market demands, companies must adapt quickly to survive. However, many struggle to understand the root causes of their problems, leading to ineffective solutions and recurring issues.

The Limitations of Traditional Consulting

Whilst traditional consulting can offer valuable insights, it often focuses on external solutions rather than internal understanding. Organisational Psychotherapy, on the other hand, encourages companies to look inward and discover their own truths.

How Organisational Psychotherapy Works

Embracing the Current Reality

Organisational Psychotherapy begins by acknowledging and working within the organisation’s existing environment, and within its gamut of existing shared assumptions and beliefs, regardless of how “safe” or “unsafe” it may be. The therapist recognises that creating a completely safe space is often an unrealistic expectation, especially at the outset.

Navigating Organisational Dynamics

The OP practitioner helps the organisation explore its dynamics in the current context, including:

  • Communication patterns
  • Decision-making processes
  • Power structures
  • Unspoken rules and norms
  • (See my OP books Quintessence and Memeology for a full list of 70+ contextual elements)

This exploration occurs even if—and sometimes especially when—these dynamics are fraught with tension or conflict.

Gradual Trust-Building

As the OP process unfolds, trust may gradually build among participants. However, this is a byproduct of the work, not a prerequisite. The therapist skillfully facilitates discussions and exercises that can yield insights even in challenging or adversarial environments.

Uncovering Hidden Truths

Through the OP process, hidden truths begin to emerge. These might include unacknowledged conflicts, ineffective leadership styles, or misaligned values. By bringing these issues to light—even in an environment that isn’t fully “safe”—the organisation can begin to address them effectively.

Adapting to Resistance

Resistance to the OP process is often valuable data in itself. The therapist works with this resistance, using it to gain insights into the organisation’s deeper dynamics and challenges (see also my book introducting OP: Hearts over Diamonds)

The Benefits of an Organisation Finding Its Own Truths

Sustainable Change

When organisations discover their own truths, they are more likely to implement lasting changes. Changes that come from within are often more readily accepted and maintained than those imposed from outside.

Improved Organisational Health

By addressing underlying issues, organisations can improve their overall health (Cf. Lencioni’s book The Advantage. This often leads to better communication, increased productivity, and higher employee satisfaction.

Enhanced Adaptability

Organisations that understand themselves are better equipped to adapt to changing circumstances. They can draw on their self-knowledge to navigate new challenges with confidence.

Conclusion: A Journey of Self-Discovery

Organisational Psychotherapy offers a unique and highly effective approach to improving workplace dynamics. By helping organisations find their own truths, it empowers them to create meaningful, lasting change. As more companies embrace this method, we may see a shift towards more self-aware, adaptable, and healthy organisations in the future.

Understanding Organisational Behaviour Through Evolutionary Stages

Introduction to Organisational Behaviour and the Marshall Model

Organisational behaviour, the study of how individuals and groups act within organisational settings, is a complex field that seeks to understand and improve workplace dynamics and the lot of folks working in orgasnisations of every stripe. The Marshall Model of Organisational Evolution, developed by myself since its inception in 2008, this model has become a powerful tool for change agents worldwide, providing insights into the complex interplay between collective mindsets and organisational effectiveness.

The Four Mindsets: Unveiling the DNA of Organisational Behaviour

1. Ad-hoc Organisations: Chaos as the Norm

Imagine a workplace where firefighting is the daily routine. Ad-hoc organisations operate in a state of constant reactivity, characterised by:

  • Haphazard problem-solving approaches
  • A “reinvent the wheel” mentality
  • Unpredictable processes and outcomes
  • Siloed work environments

These organisations often find themselves trapped in a cycle of inefficiency, struggling to break free from the chaos that defines their operations.

2. Analytic Organisations: The Rule of Order

Novice Analytical: The Rigid Beginnings

As organisations take their first steps towards structure, they enter the novice analytical stage. Here, we see:

  • An almost religious adherence to rules, policies and procedures
  • Decision-making paralysis, without clear guidelines
  • A myopic focus on individual tasks over collective outcomes
  • An allergic reaction to change

While this stage brings some semblance of order, it often comes at the cost of innovation and adaptability.

Competent Analytical: The Efficiency Paradox

Progressing further, competent analytical organisations showcase:

  • Improved problem-solving within predefined boundaries
  • The rise of departmental “kingdoms”
  • An obsession with efficiency metrics, often at the expense of true effectiveness
  • Top-down decision-making hierarchies

These organisations may appear well-oiled, but they often struggle with the bigger picture, trapped in a maze of their own making.

3. Synergistic Organisations: The Dawn of Systems Thinking

Early Synergistic: Breaking Down Walls

As organisations begin to see the forest for the trees, they enter the early synergistic stage, marked by:

  • A growing awareness of organisational interconnectedness
  • Tentative steps towards cross-functional collaboration
  • A shift from short-term fixes to long-term solutions
  • The first seeds of employee empowerment

This stage represents a pivotal moment, as organisations start to question long-held assumptions about how work should be done.

Mature Synergistic: The Orchestrated Symphony

In the mature synergistic stage, we witness:

  • A pervasive culture of systems thinking
  • Seamless collaboration across departments
  • Customer-centricity as a guiding principle
  • A groundswell of bottom-up improvement initiatives

Here, organisations begin to harness the collective intelligence of their workforce, leading to unprecedented levels of innovation and adaptability.

4. Chaordic Organisations: Thriving in Complexity

Early Chaordic: Embracing the Unknown

At the cutting edge of organisational evolution, early chaordic organisations exhibit:

  • An almost prescient adaptability to market shifts
  • Decision-making that seems to border on the clairvoyant
  • Collaboration that emerges organically based on context and expertise
  • An insatiable appetite for new ideas and technologies

These organisations don’t just survive in chaos—they thrive on it.

Proficient Chaordic: The Art of Organisational Alchemy

At the pinnacle of the Marshall Model, proficient chaordic organisations demonstrate:

  • The ability to transmute chaos into innovation gold
  • Resilience that borders on organisational immortality
  • A workforce united by a shared vision and purpose
  • The power to shape entire industries through their actions

These organisations don’t just adapt to the future—they create it.

The Ripple Effect: How Shared Assumptions and Beliefs Shape Organisational Behaviours

The Marshall Model reveals how an organisation’s collective mindset ripples through every aspect of its behaviour:

  • Communication evolves from a game of telephone tag to a harmonious orchestral symphony
  • Decision-making transforms from a rigid flowchart to an intuitive dance
  • Collaboration styles shift from command-and-control to support-and-empower
  • Innovation progresses from happy accidents to a deliberate art form

Practical Applications: Navigating the Evolutionary Journey

Armed with the insights from the Marshall Model, change agents can:

  1. Diagnose behavioural bottlenecks hindering organisational growth
  2. Craft bespoke interventions that catalyse mindset shifts
  3. Design and implement change strategies that resonate with the organisation’s current evolutionary stage
  4. Cultivate insights capable of guiding organisations through transformative leaps

Summary

The Never-Ending Quest for Organisational Nirvana

The Marshall Model of Organisational Evolution offers more than just a map of organisational behaviour—it provides a compass for navigating the complex journey of organisational transformation. By understanding where they are on this evolutionary spectrum, organisations and their change agents can chart a course towards greater effectiveness, adaptability, and ultimately, success in an increasingly unpredictable business landscape.

Organisational Behaviour Through the Lens of Evolution

The Marshall Model of Organisational Evolution also offers a profound insight into the intricate world of organisational behaviour. It demonstrates that behaviour within organisations is not a static phenomenon, but a dynamic, evolving process intimately tied to the collective mindset of the organisation.

As we’ve explored, each stage of evolution—from Ad-hoc to Chaordic—is characterised by distinct behavioural patterns:

  • In Ad-hoc organisations, we see behaviours driven by short-term reactivity and individualism.
  • Analytic organisations exhibit behaviours centred around rule-following and efficiency-seeking.
  • Synergistic organisations demonstrate behaviours that prioritise collaboration and systemic thinking.
  • Chaordic organisations showcase behaviours that embrace and leverage chaos, and drive innovation.

This model reveals that organisational behaviour is not merely a collection of individual actions, but a complex ecosystem shaped by shared mental models, collective experiences, and evolutionary pressures. It suggests that to truly understand and influence organisational behaviour, we must look beyond isolated actions and consider the underlying collective mindset driving these behaviours.

For practitioners in the field of organisational behaviour, the Marshall Model provides a powerful framework for diagnosis and intervention. It allows us to see behavioural challenges not as isolated problems, but as symptoms of an organisation’s current evolutionary stage. This perspective opens up new avenues for driving meaningful change, moving beyond surface-level fixes to address the root causes of behavioural patterns.

Moreover, the model offers a roadmap for organisational development, illustrating how shifts in collective mindset can lead to profound changes in organisational behaviour. It challenges us to think about organisational change not just in terms of processes and structures, but in terms of evolving collective consciousness and capabilities.

In essence, the Marshall Model eliminates the gap between organisational evolution and organisational behaviour, offering a holistic view of how organisations grow, adapt, and transform over time. By understanding this evolutionary journey, leaders and change agents can more effectively navigate the complex landscape of organisational behaviour, guiding their organisations towards higher levels of effectiveness, adaptability, and success in an increasingly unpredictable business world.

As we continue to grapple with the challenges of modern organisations, the insights provided by the Marshall Model undoubtedly play a crucial role in shaping our understanding of organisational behaviour and driving the next wave of organisational innovation and effectiveness.

Further Reading

The Marshall Model of Organisational Evolution

Marshall, B. (2010). The Marshall Model of Organisational Evolution (Dreyfus for the Organisation): How Mindset is the Key to Improved Effectiveness in Technology Organisations. Falling Blossoms.

Dreyfus Model of Skill Acquisition

Dreyfus, S. E., & Dreyfus, H. L. (1980). A five-stage model of the mental activities involved in directed skill acquisition. University of California, Berkeley.

Systems Thinking and Organisational Behaviour

Ackoff, R. L. (1994). Systems thinking and thinking systems. System Dynamics Review, 10(2‐3), 175-188.

Senge, P. M. (2006). The Fifth Discipline: The art and practice of the learning organization. Currency.

Organisational Culture and Effectiveness

Schein, E. H. (2010). Organizational culture and leadership (Vol. 2). John Wiley & Sons.

Chaordic Organisations

Hock, D. (1999). Birth of the chaordic age. Berrett-Koehler Publishers.

Lean and Agile Organisational Practices

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

Organisational Learning and Knowledge Management

Argyris, C. (1999). On Organizational Learning. Wiley-Blackwell.

Nonaka, I., & Takeuchi, H. (1995). The knowledge-creating company: How Japanese companies create the dynamics of innovation. Oxford University Press.

Complex Adaptive Systems in Organisations

Stacey, R. D. (2011). Strategic management and organisational dynamics: The challenge of complexity to ways of thinking about organisations. Pearson Education.

Beyond Command and Control

Seddon, J. (2019). Beyond Command and Control. Vanguard Consulting.

Enhancing Software Development Outcomes

A Cornucopia of Techniques

In the realm of software development, teams have at their disposal a rich array of techniques designed to raise productivity and outcomes. These techniques, evolved over decades, and championed by thought leaders in their respective fields, offer unique approaches to common challenges. Let’s explore some of the most notable ones:

Gilb’s Evolutionary Project Management (Evo)

Tom Gilb’s Evo technique emphasises incremental delivery and the use of quantification, focusing on delivering measurable value to the Folks That Matter™ early and often throughout the development lifecycle.

Goldratt’s Theory of Constraints (TOC)

Eliyahu Goldratt’s TOC encourages teams to identify and manage the primary bottlenecks in their processes, thereby improving overall system performance.

Ackoff and Systems Thinking

Russell Ackoff’s techniques promote viewing problems holistically, considering the interconnections between various parts of a system rather than addressing issues in isolation.

Seddon’s Vanguard Method

John Seddon’s Vanguard method advocates for understanding work as a system, focusing on customer demand and designing the organisation to meet that demand effectively.

Rother’s Toyota Kata

Mike Rother’s Toyota Kata is a practice routine that helps teams develop scientific thinking skills, fostering a culture of continuous improvement and adaptation.

Deming’s System of Profound Knowledge

W. Edwards Deming’s System of Profound Knowledge is a management philosophy that emphasises system thinking, understanding variation, and the importance of intrinsic motivation in the workplace. SoPK consists of four main themes:

  1. Appreciation for a System
    • Understanding how different parts of an organisation interact and work together
    • Recognising that optimising individual components doesn’t necessarily optimise the whole system
  2. Knowledge about Variation
    • Understanding the difference between common cause and special cause variation
    • Recognising when to take action on a process and when to leave it alone
  3. Theory of Knowledge
    • Emphasising the importance of prediction in management
    • Understanding that all management is prediction and that learning comes from comparing predictions with outcomes
  4. Psychology
    • Understanding human behaviour and motivation
    • Recognising the importance of intrinsic motivation over extrinsic rewards and punishments

Marshall’s Organisational Psychotherapy

My own field of Organisational Psychotherapy focuses on techniques for addressing the collective assumptions and beliefs of an organisation, aiming to improve outcomes and overall effectiveness through overhauling these shared assumptions.

The Adoption Quandary

Whilst these various techniques offer glittering avenues for improvement, many development teams find themselves at a crossroads. The crux of the matter lies in two key questions:

  1. Will the effort invested in mastering one or more of these techniques yield a worthwhile return?
  2. More fundamentally though, can we muster the motivation to make the necessary effort?

The Crux: Self-Motivation

The second question is the more critical of the two. It’s not merely about the potential payoff; it’s about the willingness to embark on the journey of learning and mastery in the first place. Crucially, this motivation must emanate from within the team itself, rather than relying on external factors.

Surmounting Inertia

Change is inherently challenging, and the comfort of familiar practices can be a powerful deterrent to adopting new techniques. Teams rarely find the inner drive to overcome this inertia and push themselves towards new horizons.

Nurturing a Desire for Self-Betterment

Fostering a culture that values learning and self-betterment is paramount. When team members view challenges as opportunities for growth rather than insurmountable obstacles, they’re more likely to embrace new techniques. This mindset shift must be initiated and nurtured by the team itself.

Peer-Driven Inspiration

In the all-too-common absence of top-down motivation, teams can look to each other for inspiration and encouragement. By sharing successes, discussing challenges, and collaboratively exploring new techniques, team members can create a supportive environment that fuels self-betterment.

Individual Responsibility

Each team member bears the responsibility for their own personal and professional development. By setting personal goals for improvement and actively seeking out opportunities to learn and apply new techniques, individuals can drive the team’s overall progress.

Conclusion

While the array of available techniques to improve development team outcomes is legion, the true challenge lies not in their complexity or the time required to master them. Rather, it’s in cultivating the self-motivation to pursue excellence and adopt such techniques.

As we ponder the question, “Can we be bothered to make the effort to improve ourselves, our capabilties and our outcomes?”, we must remember that the most successful teams are those who answer with a resounding “Yes” – not because they’re compelled to, but because they genuinely desire to excel. It is this intrinsic commitment to growth and improvement that ultimately distinguishes high-performing teams from the rest. And if the outcomes are simply making the rich (management, shareholders) richer, then none of this is likely to happen.

The journey of improvement commences with a single step, taken not because someone else pushed us, but because we ourselves choose to move forward. In the end, the power to transform our outcomes lies within our own hands. The techniques are there, waiting to be explored and mastered. The question remains: are we ready to take steps towards a better future for ourselves, our teams and our lives? Do we need it?

Postscript

By the bye, this subject was the topic of my keynote at Agile Spain, 2016 2 December 2016, in Vitoria Gasteiz.

Theory P

Aligning Shared Beliefs for Organisational Success

Introduction to Theory P

In the world organisational management, Theory P emerges as a compelling framework for understanding and improving collective behaviour. At its core, Theory P posits that organisational success is inextricably linked to the shared assumptions and beliefs held by its members. This innovative approach introduces the concept of Organisational Psychotherapy (OP) as a vital tool for aligning these shared mindsets with the company’s objectives and purpose.

The Foundation of Collective Behaviour

Shared Assumptions and Beliefs

Theory P argues that the behaviour of an organisation as a whole is not merely the sum of individual actions. Instead, it is profoundly influenced by a network of shared assumptions and beliefs that permeate the entire structure. This collective mindset shapes how employees interpret situations, make decisions, and interact with one another.

Impact on Organisational Success

The alignment—or misalignment—of these shared beliefs with the organisation’s goals can significantly impact its success. When employees’ assumptions are in harmony with the company’s objectives, it creates a synergy that drives productivity, innovation, and overall performance.

The Role of Organisational Psychotherapy (OP)

Defining Organisational Psychotherapy

Organisational Psychotherapy, the ‘P’ in Theory P, is a systematic approach to understanding and reshaping the collective psyche of an organisation. It involves surfacing the underlying assumptions that guide behaviour and strategically aligning them with the organisation’s purpose through group dialogue and reflection

Key Objectives of OP

  1. Uncovering Hidden Beliefs: OP practitioners work to enable organisations to bring their subconscious assumptions to the surface.
  2. Facilitating Alignment: Through various interventions, OP aims to bridge the gap between existing beliefs and desired organisational outcomes.
  3. Fostering Adaptability: By making beliefs visible and explicit, OP helps organisations become more self-aware, more flexible, and more responsive to change.

Implementing Theory P in Practice

Surfacing and Reflection

The initial phase in applying Theory P involves a process of surfacing latent organisational beliefs and encouraging collective reflection. This entails creating safe spaces for open dialogue where team members can articulate and examine their assumptions without fear of judgement. Facilitated group discussions, storytelling sessions, and reflective exercises are employed to bring subconscious beliefs into conscious awareness. This process of surfacing and reflection allows the organisation to gain a clearer understanding of its underlying mental models and how they influence day-to-day operations and decision-making.

Targeted Interventions

Based on the surfacing and reflection, OP practitioners design interventions tailored to the organisation’s specific needs. These might include:

  • Group workshops to explore and challenge existing beliefs
  • Leadership coaching to model desired mindsets
  • Structural changes that encourage and reinforce new ways of thinking

Continuous Evaluation and Adjustment

Theory P emphasises the importance of ongoing evaluation and refinement. As the organisation evolves, so too must its approach to aligning shared beliefs with its objectives.

The Benefits of Embracing Theory P

Enhanced Organisational Cohesion

By actively working to align shared beliefs, organisations can achieve a greater sense of unity and purpose among their members.

Improved Change Management

Organisations that understand and can influence their collective mindset are better equipped to navigate periods of significant change.

Increased Innovation and Performance

When the collective psyche of the organisation is better aligned with organisational goals, it creates an environment ripe for innovation and high performance.

Conclusion: The Future of Organisational Development

Theory P offers a fresh perspective on organisational behaviour and success. By recognising the power of shared assumptions and beliefs, and employing Organisational Psychotherapy to align them ever more closely with company objectives, organisations can unlock new levels of performance and adaptability. As the business world continues to evolve, Theory P may well become an essential tool in the arsenal of forward-thinking leaders and organisational development professionals.

Further Reading

For those interested in delving deeper into the concepts related to Theory P and organisational psychotherapy, may I suggest my books on the subject of Organisational Psychotherapy (all found on Leanpub):

Marshall, RW. Memeology – Surfacing the Memes of your Organisation.

Marshall, RW. Quintessence – An Acme for Software Development Organisations.

Marshall, RW. Hearts over Diamonds – Serving Business and Society Through Organisational Psychotherapy – An Introduction to the Field.

These works provide additional insights into organisational psychology, shared beliefs, and human-centric approaches in business, which complement and expand upon the principles discussed in Theory P.

Note: For specific publication details and full citations, please refer to my blog or contact me directly.

Software and Product Development Remain in the Dark Ages

These days, technology moves at lightning speed with new tools and platforms constantly emerging. But evolution in the way we organise for software and product development often feels like it’s crawling along at a snail’s pace. The way we build apps and products is lagging way behind what’s possible. A big reason for this is that businesses still use outdated and egregiosly ineffective practices for organising both their teams and the way the work works.

Companies Bogged Down in Bureaucracy

Larger companies are weighed down by bureaucracy that crushes agility and innovation. The  Command and Control management style remains ubiquitous, we continue with inflexible planning processes, and unnecessary documentation requirements. What could take a few weeks or months gets dragged out over years of committees, approvals, shilly-shallying, and shifting goalposts.

Teams work silos that block collaboration across groups that need to work together. Protectiveness and territoriality are rampant. Priorities also constantly change with leadership turnover, favouring reactive firefighting over long-term strategy. Software and product people spend more time navigating corporate politics and protecting themselves than doing actual work.

Skewed Work Incentives

Developer and product manager motivation suffers because incentives are misaligned. Individual rewards are based on checking arbitrary boxes rather than doing great work. Perceived job insecurity inhibits taking risks or sharing knowledge.

There is also misguided prestige around working on proprietary codebases and reinventing from scratch. This holds back reusing proven architectures and open sourcing for community collaboration. Inefficiently re-building wheels becomes the norm as devs find motivation in custom solutions over composable building blocks.

Outdated Approaches

Approaches like Agile, DevOps, and cloud computing have helped to a limited extent. But these are incomplete solutions patching over outdated and ineffective organisational foundations rather than rethinking from a clean slate.

Hierarchies are flattened but still exist. Command and Control still predominates. Planning iterates but still relies on traditional projections rather than real-world feedback loops. Migrating to the cloud layers complexity on creaky legacy systems instead of fully modernising as cloud-native.

Renaissance

Truly revolutionising how we build software and products invites a top-to-bottom overhaul, not just tweaks to our present approaches. Organisations could be reimagined from the ground up with different workflows, team structures, and incentive systems. In fact, with a whole host of outdated and relatively ineffective assumptions and beliefs consigned to the trashcan of history.

This could mean, for example, far flatter teams organised around end-to-end product missions rather than subdivided tasks. Compensation might be overhauled to favor collective outcomes and attending to folks needs over individual heroics and pay-per-hour. Business models favouring self-organisation could enable healthier evolution of the way the work works. For a comprehensive list of what “better” looks like, see my books “Quintessence” and “Memeology“.

There’s no one-size-fits-all solution, but one thing is clear. If we want software and product development to leap into the future, first we have to drag our organisational assumptions and beliefs out of the Dark Ages.

How Group Minds Change

While we often think of the mind as belonging to an individual, groups and organisations can develop their own collective mindset – a.k.a. collective psyche – that transcends the viewpoints of any single member. This “group mind” emerges from the shared beliefs, assumptions, and ways of thinking that become entrenched within a organisation over time.

The group mind is an entity distinct from the individual minds that comprise it, yet it is also shaped by the psychological tendencies and biases of those individuals. As people within an organisation interact, reinforce each other’s viewpoints, and establish shared narratives, a collective psyche emerges. This psyche influences how information is interpreted, how decisions are made, and how the organisation responds to change and new ideas.

While the group mind can provide a sense of unity and cohesion, it often also acts as a barrier to growth and adaptation. Outdated assumptions, confirmation biases, and a resistance to changing the status quo can become deeply ingrained, making it difficult for the organisation to evolve. Understanding the forces that shape and maintain the group mindset is crucial for leaders seeking to facilitate meaningful change within their organisations.

Shifting the Group Mindset: How Organisations Can Evolve

When it comes to organisations, whether they are corporations, non-profits, or government agencies, change is often resisted. Entrenched beliefs, established processes, and a fear of the unknown can make it challenging for groups to adapt and evolve their collective mindset. However, understanding the psychological factors at play can help leaders facilitate meaningful change within their organisations.

While leaders can play a role, truly meaningful updates to an organisation’s ingrained “group mind” often arise from the grassroots. Teams have the power to self-organise and proactively evolve the collective psyche. This shared mindset influences how people interpret information, make decisions, and embrace (or resist) change. To become an adaptable, future-ready team, try:

Combating Confirmation Bias

The tendency to seek out information confirming existing beliefs presents a major obstacle. Break through by having everone actively encourage diverse perspectives during meetings and decisions. Invite team members to argue the various sides of issues. Bring in outside experts – including organisational psychotherapists – to help challenge assumptions.

Overcoming the Status Quo Bias

Closely related to confirmation bias is the status quo bias, which is the preference for maintaining the current state of affairs, even when change could be beneficial. This bias stems from a combination of fear of uncertainty, perceived effort required for change, and a false sense of security in the familiar. The status quo feels comfortable, which makes change difficult. But fresh thinking is crucial. Clearly communicate the reasons for change and the benefits of evolving. Provide coaching for indiciduals and organisational psychotherapy for groups to help people navigate ambiguity. Celebrate small wins to build momentum. Provide support and resources to ease the transition.

The Influence of Social Proof

Humans are heavily influenced by the actions and beliefs of those around them – a phenomenon known as social proof. In organisations, this oten leads to the perpetuation of outdated or ineffective practices simply because “that’s the way it’s always been done”. Breaking this cycle requires leaders to invite everyone to model desired behaviors and create an environment where innovation and new ideas are celebrated.

Cultivating a Growth Mindset

At the core of organisational change is the ability to adopt a growth mindset – the belief that abilities and intelligence can be developed through effort and learning. Leaders can foster a growth mindset by encouraging continuous learning, providing opportunities and resources for skills development, and celebrating failures as learning experiences rather than sources of shame.

Increasing Group Emotional Intelligence

Navigating change within organisations is not just an intellectual exercise; it also requires a high degree of emotional intelligence. Folks can choose to empathise with the concerns and fears of their peers and co-workers, communicate effectively, and manage their own emotions during times of stress and uncertainty. Building emotional intelligence within the organisation can help create a more resilient and adaptable culture. By increasing emotional intelligence, people can process these emotions constructively as e.g. a team. Expressly invite an environment of empathy where needs can be heard and concerns can be voiced. Learn to self-manage team emotions and dynamics.

Embracing Change as a Constant

Ultimately, organisations that are able to successfully retune their group psyche will be those that embrace change as a constant. Rather than viewing change as a temporary disruption, these organisations see it as an integral part of their growth and evolution. By fostering an environment that values learning, diversity of thought, and emotional intelligence, organisations that are truly adaptive and future-ready emerge. The most adaptable (Agile!) organisations make evolving shared assumptions and beliefs feel like a source of strength, not pain. Foster this by developing a culture where change is treated as integral to growth and development. Institutionalise mindset updates as a regular team and organisation-wide practice. Lean on communications experts within the organisation to regularly share these updates.

Conclusion

Shifting an organisation’s entrenched “group mind” is an ongoing process, not a one-time event. As the world continues evolving at a rapid pace, the ability to proactively update collective beliefs and assumptions becomes critical for survival.

In her famous essay on leverage points for changing systems, Donella Meadows identified “The Power to Transcend Paradigms” as the highest and most effective point of intervention. A paradigm refers to the shared mental model or set of beliefs that shapes how we understand reality.

For organisations, the “group mind” acts as the overarching constraint that governs how information is perceived, decisions are made, and change is approached. Failing to evolve this ingrained collective psyche essentially renders an organisation unable to see and understand the world with fresh eyes.

Those organisations that can transcend their group mind by continually questioning shared assumptions and beliefs, and entertaining new perspectives, will be the ones poised to thrive amidst volatility. They make evolving their shared beliefs an integral part of operations rather than a periodic disruption.

By developing emotional intelligence, cultivating growth mindsets, and harnessing the creative friction of diverse viewpoints, these innovative entities ensure their collective thinking remains agile and future-focused. Their “group mind” becomes a flexible asset for reinvention rather than a restraint on change.

In our era of constant upheaval across industries, the greatest competitive advantage will belong to those organisations that fully embrace the perpetual journey of transcending their in-the-moment paradigm. They understand that clinging to ingrained collective mindsets inevitably becomes a source of blindness and stagnation. Their identity centers around the reality that questioning “the group mind” itself must remain an eternally iterative process of growth.

A World Where the Greater Good Predominates Over Profits

The Visionary Notion

What if the primary driving force behind commercial and economic endeavors wasn’t the pursuit of profits, but rather benefiting society, the species, Gaia, and the planet? A visionary notion, to be sure, that seems to defy conventional capitalist wisdom. Nevertheless, if we allow our imaginations to roam freely and look back at periods in history where ethical business practices held sway, we can depict a world truly transformed by this paradigm shift.

Profit Motives vs. Ethics and Humanity

Throughout most of human history, the profit motive has reigned supreme in the business realm. However, there have been notable exceptions driven by religious teachings, philosophical movements, and social ideals that prioritised ethical conduct over mere grubby accumulation of more and more wealth. The Quakers, for instance, were renowned for their commitment to honest dealings and consideration of employee welfare, exemplified by the socially-conscious British chocolate makers like Cadbury. The 19th century cooperative movement aimed to create enterprises that equitably shared profits with worker-owners and the local community.

The Beauty of Ethical Business

Would we call businesses truly putting the greater good before profits “beautiful”? At first, such a description may seem like an odd coupling of aesthetics with commerce. But perhaps there is an inherent beauty to enterprises that create sustainable value for society while exhibiting ethical conduct.

Just as we find natural wonders, artistic works, or selfless acts emotionally moving due to their harmony with higher ideals of truth, goodness, and transcendence of ego, so could businesses centered on benefiting all stakeholders embody a different kind of beauty. One not necessarily based on physical appearance, but on being skillfully crafted exemplars of how our economic activities can align with ethical, aesthetic, environmental and humanitarian principles.

This beauty manifests through their products, services, and operations, harmonising with the world rather than undermining it through greed, despoilment, or exploitation. Beautiful businesses are sustainable and circular by design, creating goods to be celebrated and cherished rather than cynically designed for disposability.They invest in creating opportunity and dignity for workers and communities rather than grinding them underfoot for profit margins.

Where today’s shareholder-driven corporations often exemplify grotesque machineries of extraction, ethical enterprises putting people and planet over money could be sublime new exemplars of applied aesthetics – aspiring toward perfection not through profit metrics, but through positively impacting all they engage with. Their beauty would shine through in becoming tightly interwoven threads in an interdependent tapestry, creating joyful, resilient and regenerative systems that elevate our shared potential.

While the traditional business vernacular focuses on the uglyness of lucrative processes, revenue growth, and reputational brand value, a world where ethical enterprises reign would celebrate hallmarks of perfected form: generative models that produce societal good, environmental integrity, attending to folks’ needs, and uplifting the human spirit. Perhaps then, we could appreciate the highest “good companies” not just pragmatically, but aesthetically – as living artworks of conscious, ethical organisation.

A World Oriented Toward the Greater Good

In such a world oriented toward the greater good, companies measure success not just by financial returns, but by positive impacts. Ethical practices like those espoused by certain faith traditions and thinkers are the norm across these industries. Sustainability is prized over short-term gain, with environmental stewardship prioritised over resource exploitation. We’ve seen glimpses of this in recent decades through the rise of corporate social responsibility (CSR), socially conscious investing, and the emergence of benefit corporations legally bound to creating public benefit, not just profits. But such examples have remained the exception rather than the rule in a profit-driven system.

The Global Ethos of the Greater Good

Imagine if this ethos becomes the core operating principle globally. Rather than lobbying for narrow interests, these businesses advocate for the common good. Tax avoidance schemes would be abandoned in a system where contributing one’s fair share is the ethical baseline. Worker rights and equity are vigorously protected, not eroded in pursuit of higher margins. On an individual level, cutthroat workplace could gives way to healthier cooperation, and integration with our personal and community values and family lives. Ethical conduct is rewarded over pure profit-generation at any cost. Kudos is not derived from endless growth metrics, but to positive impacts created for all the Folks That Matter™.

A Sustainable Economic Model

Of course, enterprises still need to generate income to remain viable and reinvest in their social missions. But growth is pursued by creating genuine value for society rather than extracting it. Sustainable, circular economic models replace those premised on endless consumption and planned obsolescence.

A Radical Yet Possible Vision

Such a world may seem naively idealistic to modern sensibilities, conditioned to accept profit as the prime directive. But is it any more far-fetched than an entrenched global system that relentlessly exploits people and finite resources in pursuit of perpetual economic expansion on a finite planet? By orienting business toward the greater good, as past ethical movements have done, we might create an economy that better serves humanity. This may read as a utopian ideal today, but it has been a reality at various points throughout our history. A world where businesses prioritise society over self-interest may not be inevitable, but it is possible if we dare to imagine and build it together.

Do you have even the briefest five minutes to contemplate how things might be different?

Further Reading

Ackoff, R. L. (2011). The aesthetics of work. In Skip Walter’s blog post retrieved from https://skipwalter.net/2011/12/25/russ-ackoff-the-aesthetics-of-work/

The Spread of Collaborative Knowledge Work

The Power of Collective Intelligence

In more and more scenarios, solving complex challenges often requires much more than just an individual’s expertise. It demands the ability to synthesise diverse perspectives and pool intellectual resources through seamless coordination and collaboration. This emerging paradigm is known as collaborative knowledge work (CKW).

CKW brings together professionals from varied backgrounds to tackle intricate problems that defy siloed approaches. By harnessing the collective brainpower of multidisciplinary teams, organisations can innovate and achieve breakthroughs that may have once seemed unattainable. This collaborative mindset is reshaping various industries and giving rise to new types of roles and career paths.

Professions Embracing the Collaborative Paradigm

Here are some of the professions where collaborative knowledge work is taking centre stage:

Software and Digital Products

From agile squads to distributed open-source collaborations, software creation has become a team sport where developers, designers, and product experts collectively craft digital solutions.

Management Consulting

Rather than individual consultants, firms are assembling cross-functional teams to provide holistic advisory services that span multiple practice areas for their clients.

Product Design and Innovation

User-centred design demands close collaboration between designers, engineers, researchers, and other stakeholders throughout the product development lifecycle.

Scientific Research

Tackling complex scientific inquiries requires coordinated efforts between researchers across institutions, merging expertise from diverse domains.

Healthcare

Providing effective patient care requires seamless cooperation among physicians, nurses, therapists, pharmacists, and other healthcare professionals.

Legal Services

Navigating intricate legal matters, especially those spanning jurisdictions, necessitates integrated teams of lawyers and paralegals from complementary practice areas.

Education and Training

Developing robust educational programmes involves interdisciplinary instructional designers, subject matter experts, and educational technologists working in concert.

Construction and Engineering

Delivering large-scale construction projects relies on integrated teams that bring together architects, engineers, builders and other specialised roles.

Finance and Investments

Managing investment portfolios and analysing risk profiles is increasingly a shared responsibility between quantitative analysts, economists, and other financial experts.

The New Collaborative Mindset

As the complexities of our world continue to grow, the demand for professionals adept at collaborative knowledge work will only intensify. Thriving in these roles requires a unique blend of specialised expertise and the ability to synthesise diverse perspectives through effective communication and coordination. This emerging paradigm presents exciting opportunities for those seeking to make a lasting impact by pushing the boundaries of what is possible through the power of collaboration. I wonder how many of the above truly understand and embrace CKW, and how many remain mired in the category error of treating CWK like traditional forms of work?

The Power of Beliefs

A panel illustrating various major world religions

Montage of the world's largest political parties

The Impact of Ideologies

If you doubt the power of beliefs, just consider the world’s religions and political movements for a moment or two. These ideologies have shaped the course of history, influencing the lives of billions and driving both incredible acts of compassion and unspeakable atrocities. The fervent conviction of their adherents demonstrates the immense impact that belief systems can have on human behaviour and societies as a whole.

Beliefs in the Workplace

And then ask yourself, why would that apply to people’s lives in general, but not to their lives at work?

The truth is, the power of belief permeates every aspect of our existence, including our workplaces. Our assumptions and beliefs about ourselves, our abilities, our colleagues, and our work environment have a profound effect on our performance, motivation, and overall job satisfaction.

The Self-Fulfilling Prophecy

Consider the self-fulfilling prophecy: if we believe we are capable of achieving great things, we are more likely to put in the effort and take the risks necessary to make those beliefs a reality. Conversely, if we doubt our abilities or assume that our efforts will be in vain, we may subconsciously sabotage our own success or fail to seize opportunities for growth and advancement.

The Impact of Beliefs on Collaboration

Moreover, our beliefs about our workplace and colleagues can significantly impact our interactions and collaboration. If we assume that our team members are competent, trustworthy, and committed to a shared goal, we are more likely to foster a positive, supportive work environment that encourages innovation and success. On the other hand, if we harbour negative assumptions about our colleagues or the company itself, we may engage in counterproductive behaviours that undermine morale and hinder progress.

Company Culture: A Shared Set of Beliefs

The power of belief in the workplace extends beyond the individual level. Company culture is essentially a shared set of beliefs, values, and assumptions that guide the behaviour and decision-making of an organisation. A strong, positive company culture can inspire employees to go above and beyond, driving innovation, customer satisfaction, and long-term success. Conversely, a toxic or misaligned culture can lead to high turnover, poor performance, and ultimately, business failure.

Deprogramming: Individual Psychotherapy

To harness the power of belief in our professional lives, we must first become aware of our own assumptions and biases. By consciously examining and challenging our beliefs, we can identify areas for personal growth and development. This process of deprogramming can be likened to individual psychotherapy, where one works to unlearn counterproductive beliefs and replace them with healthier, more empowering ones.

Organisational Psychotherapy: Fostering a Positive Culture

At the organisational level, companies can choose to recognise the importance of fostering a strong, positive culture that aligns with the values and goals of the business. This involves communicating a clear vision, leading by example, and encouraging open dialogue and feedback. By actively shaping and nurturing a culture of belief, leaders can create an environment that inspires people to bring their best selves to work every day. In essence, this process of organisational psychotherapy involves identifying and addressing the collective beliefs and assumptions that may be holding the company back, and working to instil a more positive, growth-oriented mindset throughout the organisation*.

Conclusion

In conclusion, the power of belief is not limited to the realm of religion or politics; it is a fundamental driver of human behaviour and success in all areas of life, including our professional endeavours. By recognising and harnessing the power of our assumptions and beliefs, and engaging in both individual deprogramming and organisational psychotherapy, we can unlock our full potential, build stronger teams, and create thriving organisations that make a positive impact on the world.


*Actually, the emergent mindset may be postive, or negative; growth-oriented, degrowth orients, or other. What emerges is realisation of the role of beliefs. The organisation itself gets to own the direction it takes. The involvement of an organisational psychotherapist does not automatically imply culture change “for the better”.  But it does assist organisations in realising more clarity in surfacing and reflecting upon their beliefs. As Gandhi famously said: “I came to the conclusion long ago that all religions were true and that also that all had some error in them, and while I hold by my own religion, I choose to hold other religions as dear as Hinduism. So we can only pray, if we are Hindus, not that a Christian should become a Hindu; but our innermost prayer should be that a Hindu should become a better Hindu, a Muslim a better Muslim, and a Christian a better Christian.”

The Why of FlowChain: Deliberate Continuous Improvement

In my career, working with hundreds of companies, I’ve almost never seen organisations* take a truly deliberate approach to continuous improvement. It’s nearly always treated as an afterthought or add-on to business-as-usual (BAU). But real transformation requires making continuous improvement an integral and core part of daily work. This is the “why” behind FlowChain – enabling deliberate, in-band continuous improvement.

In other words, applying the same disciplines from product development, delivery, etc. to the business (sic) of delivering continuous improvements  – continuously improving the way the work works.

What Is FlowChain?

So what is FlowChain? At its core, it is a system for managing flow – both the flow of outputs and the flow of improvements to the way the work works, concurrently and by the same means. And by “flow”, I mean the steady progress of work from request to completion through all steps in a process. Flow is optimised when the right work is happening at the right time by the right people. Roadblocks, delays, and waste are minimised or eliminated.

Flow

Optimising flow delivers the following benefits:

  • Increased productivity – less time wasted, more work completed
  • Improved quality – fewer defects, rework minimised
  • Better customer service – faster response times, reliability
  • Higher employee engagement – less frustration, more joy

But achieving flow requires continuous improvement. Problems must be made visible. Waste must be reduced iteratively. Roadblocks must be cleared continuously.

This is why FlowChain incorporates improvement into its regular rhythm. Each cycle follows a deliberate sequence:

  • Plan – Select and sequence the upcoming work.
  • Execute – Complete the work while tackling issues.
  • Review – Analyse completed work and identify improvements.
  • Adjust – Make changes to improve flow.

Unlike most continuous improvement efforts – that are separate from BAU – FlowChain makes improvement an integral in-band activity. The rapid cycles provide frequent opportunities to reflect, gain insights, and act.

Compounding Benefits

Over time, the compounding benefits are immense. Teams develop a “flow habit”, where improving flow becomes second nature. Powerful capabilities like root cause analysis, A3 problem-solving, improvement katas, and change management are honed.

In my experience, this deliberate approach is transformative. Teams gain tremendous agency to systematically improve their own flow. The organisation as a whole cultivates a culture of continuous improvement. And customers experience ever-better service and responsiveness.

The “why” of FlowChain is simple – create focus, visibility, accountability, and agency to drive continuous improvement. The results – ever better flow, reduced waste, and sustainable transformation. Deliberate, in-band continuous improvement stops being an aspiration and becomes a reality.

*Ask me about the exception.