Unleashing the Power of the Antimatter Principle

The Benefits

When it comes to collaborative knowledge work endeavours like software development and product development, the “Antimatter Principle” offers a revolutionary approach that promises to unlock unprecedented levels of engagement, value and effectiveness. By focussing on the psychology of human behaviour and treating people’s needs as the most precious and potent resource, this principle has the potential to transform the way we approach and manage such work.

Fostering a Culture of Mutual Respect and Empathy

At its core, the Antimatter Principle advocates for a deep understanding and prioritisation of the human needs of all stakeholders involved – developers, customers, partners, and anyone else impacted by or contributing to the project. By genuinely listening to uncover everyone’s underlying needs, it fosters an environment of mutual respect, empathy, and a shared desire to contribute one’s best efforts. This nurturing atmosphere empowers individuals to tap into their deepest motivations, unlocking a wellspring of creativity, innovation, and dedication.

Aligning Efforts with What Truly Matters

Traditionally, collaborative work often prioritise metrics like productivity, deadlines, or profits, relegating human needs to a secondary concern. The Antimatter Principle flips this paradigm on its head, advocating for a psychologically aware approach that places people’s core needs at the forefront. By aligning all efforts with what truly matters to those involved, it increases the likelihood of achieving outcomes that resonate deeply and create lasting value.

Maximising Value and Effectiveness

While challenging to implement, the payoff of the Antimatter Principle is immense. By tapping into people’s core needs and motivations, it has the potential to unlock exponentially more value and effectiveness than process optimisation or profit-driven methods. This approach recognises that true success lies not in mere efficiency, but in harnessing the collective power of human potential.

Implementing the Antimatter Principle

Identifying “The Folks That Matter™”

Central to the Antimatter Principle is the concept of “The Folks That Matter™” – a term encompassing all stakeholders with needs inviting attention. This includes developers, team members, customers, users, sponsors, regulators, society at large, and anyone else impacted by or contributing to the project. The first step is to establish a well-reasoned process for determining who falls within this crucial group. It’s this dialogue that brings much of the power to the Antimatter Principle.

Engaging in Deep Listening

Once “The Folks That Matter™” have been identified, and more importantly the policy driving such identification and prioritisation, the next step is to engage in deep, active listening to uncover their underlying needs. This invites an organisation to create safe spaces for open dialogue, fostering trust, and demonstrating genuine empathy and curiosity. By understanding the human factors driving each group’s motivations and expectations, teams can align their efforts to deliver outcomes that resonate profoundly.

Prioritising and Focusing Efforts

With a comprehensive understanding of stakeholder needs, teams can then prioritise and focus their efforts on addressing the most critical and impactful requirements. One complimentary approach involves evaluating the “Cost of Focus” – the impact on desired outcomes from including or excluding certain needs – and making strategic trade-offs when necessary. By aligning resources with the needs that truly matter, teams can maximise their potential for creating transformative value.

Embracing the Antimatter Principle

While the Antimatter Principle may seem counterintuitive or even idealistic at first glance, its potential rewards are profound. By treating people’s needs as the rarest and most potent resource, it offers a path to unlocking unprecedented levels of collaboration, innovation, and success in collaborative knowledge work endeavours. Embracing this mindset requires a paradigm shift – a willingness to prioritise human factors over traditional metrics and to invest in deep listening and empathy. However, those who embark on this journey may discover that the true “antimatter” lies not in some elusive substance but in the limitless potential of human connection and understanding.

See also: Quintessence.

Appendix: The Folks That Matter™

The concept of “The Folks That Matter™” is a central tenet of the Antimatter Principle, referring to all the various stakeholders, team members, customers, users, and anyone else impacted by or contributing to a collaborative project or endeavour. These are the people with needs to be prioritised and attended to.

The “interesting angle” of The Folks That Matter™ is examining how this set of stakeholders gets determined – through consensus, autocracy, cost/impact analysis, or other means. And what consequences result from that examination and emergent dialogue.

With finite resources, difficult trade-offs must be made about whose needs to prioritise versus discount as “Folks Who Don’t Matter™” for a given scope. Note the concept of “Cost of Focus” – communicating the impact on desired outcomes from including or excluding certain stakeholders’ needs. Similar to Cost of Delay for prioritising product features.

The core premise is that until you have a well-reasoned way to determine whose needs to “focus” on (whose needs matter most), other prioritisation efforts like Cost of Delay are moot.

In essence, “The Folks That Matter™” framing reinforces and provides more operational details for implementing the “Antimatter Principle” of truly prioritising understanding and delivering on people’s core needs in collaborative efforts.

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.

The IS of Identity: Exploring the Self through General Semantics

We often take our sense of identity for granted, assuming “me” and “us” is a fixed and unchanging core of who we are. However, the field of General Semantics invites us to challenge these assumptions and engage in deeper reflection on the constructed nature of identity. This perspective holds particular relevance for the practice of Organisational Psychotherapy.

Assumptions and Abstractions

At the heart of General Semantics lies the recognition that we do not experience reality directly. Instead, we create abstractions and maps in our minds to represent the world around us. Our identity, or sense of self, emerges from this process of abstracting.

As the pioneering general semanticist Alfred Korzybski famously stated, “The map is not the territory.” Our self-concept, composed of memories, beliefs, and narratives, is simply our mind’s representation of who we think we are. It is not an inherent, immutable truth.

Language and Identity Formation

Language plays a pivotal role in shaping these abstractions that form our identities. The very act of labelling ourselves with statements like “I am…” imposes artificial boundaries and categories upon our fluid experience.

For instance, saying “I am a manager” reduces the multi-faceted richness of our being to a single role or descriptor. General Semantics encourages us to become more conscious of how language influences and potentially limits our self-perception.

The Organisational “Mega-Self”

Interestingly, organisations themselves can develop a kind of collective identity or “mega-self” that transcends the individual employees. This organisational psyche manifests through shared narratives, cultures, assumptions, beliefs, and behavioural norms.

Just as individuals unconsciously shape their identities through language, organisations reify their mega-self through mission statements, marketing messages, and the stories perpetuated about the company’s history and values. An awareness of General Semantics principles can illuminate how this collectively-constructed identity arises and evolves over time.

The Organisational Self

At an individual level, our personal identities are further moulded by the structures and cultures of the organisations we inhabit. We may unconsciously define ourselves in relation to our job titles, team memberships, or the narratives of the broader organisational mega-self.

An organisational psychotherapist employing a General Semantics lens might invite people to question the implicit assumptions and linguistic traps that constrain how they view themselves within the workplace context. This expanded awareness can open up new possibilities for growth, authenticity, relationships, and systemic change.

Towards Fluidity

Ultimately, General Semantics does not advocate for the elimination of identity altogether. Rather, it encourages a more flexible and enquiring relationship with our sense of self – one that recognises its constructed and mutable nature.

By embracing the core principles of this field, we can learn to hold our identities lightly, remaining open to revision and evolution as our experiences and contexts shift. In doing so, we cultivate greater agency, adaptability, and presence in our lives and work.

At an organisational level, this fluid stance towards identity allows for increased agility and responsiveness. Rigid attachments to how a company defines itself can blind an organisation to changing customer needs or environmental pressures. Applying General Semantics thinking can facilitate an organisational identity that is resilient and dynamically co-created by its members.

Leadership’s Labour Arbitrage Addiction

Introduction

Labour arbitrage refers to the practice of hiring workers who will accept lower wages, fewer benefits, and less favourable employment terms compared to others doing similar work. The goal is ruthlessly simple – reduce overall labour costs to inflate profits. But behind this seemingly rational business tactic often lurks a more insidious agenda – catering to the psychological needs of managers rather than the organisation’s long-term interests.

A Losing Game

On paper, labour arbitrage might seem an easy win. Replace highly compensated staff with lower-cost alternatives through outsourcing, offshoring, or hiring marginalised demographics. In the short run, it trims expenses and pads the bottom line.

But this myopic focus on cost-cutting comes at a steep price. Organisations pursuing such strategies to an extreme risk losing their technological edge, innovative capabilities, and ability to attract top talent. They become trapped in a race to the bottom, deskilling their workforce and deinvesting in the advanced tools that drive productivity gains.

Enshitification Paradox

The paradox, of course, is that labour arbitrage aimed at inflating profits inevitably leads to enshitification – the gradual degradation of product and service quality over time. As underinvestment in human capital compounds, outputs become commensurate with the low-skilled labour producing them – shoddy, unreliable, and unable to evolve with changing markets.

The annals of business are littered with former giants, such as Nokia and now Boeing, hobbled by this self-destructive spiral. From iconic tech brands to venerable manufacturers, their relentless pursuit of lower labour costs proved a Faustian bargain that hollowed them from within.

Maslow’s Folly

So why this obsessive focus on labour arbitrage when its pitfalls are so apparent? The answer lies in Maslow’s hierarchy of human needs. For managers, slashing headcount satisfies cravings for credibility, control and esteem. Hunting efficiencies through payroll reductions, offshoring or automation provides a deceptive dopamine hit of achievement.

These ego-driven impulses, coupled with the lure of short-term personal gain like padded compensation, cloud better judgement. Long-term organisational impacts get handwaved in favour of catering to individual psychological needs in the here and now.

Sustainable Practices

The true failing in labour arbitrage as a strategy lies in allowing it to become an end in itself, an obsessive panacea for cost control that cannibalises an organisation’s future.

Real leaders approach such a strategy with sober pragmatism. Is this move prudent for enduring competitiveness and growth? Or merely gratifying managerial egos while eroding the bedrock of skilled labour and innovation?

Cultivating this self-awareness, while emphasising investments in skills, tools, and R&D on par with responsible cost management, is the path toward sustainable labour practices. It insulates organisations from enshitification’s inevitable decline and keeps them sailing confidently toward future horizons.

Stripping the Antimatter Principle for Useful Parts

I’ve long believed in the Zen-like principle that there is profound wisdom in simplicity. The Antimatter Principle, a mere four words long, encapsulates a powerful paradigm that has the potential to transform our relationships, our communities, our organisations, and ultimately, our world. As we explore this elegant concept, let’s unpack its depth, adaptability, and profound implications.

The Antimatter Principle In Four Words

At its essence, the Antimatter Principle states: “attend to folks’ needs”. Just four straightforward words, yet they encapsulate a powerful paradigm with far-reaching implications. As Hillel Wayne so eloquently and recently put it, “useful paradigms are those we can strip for parts” – and this principle is open to that notion exquisitely.

Unpacking The Profundity

While the wording may be simple, the underlying philosophy is profound. By actively attending to the needs of others, we cultivate an outward-looking perspective that transcends selfish impulses. It demands that we develop empathy, emotional intelligence, and a genuine concern for the well-being of those around us.

This principle extends far beyond mere pleasantries or superficial gestures. It challenges us to truly understand the unique circumstances, desires, and struggles of our fellow human beings – and to respond with compassion, support, and tangible assistance wherever possible.

Stripping The Paradigm For Parts

The beauty of the antimatter principle lies in its versatility and adaptability. It can be applied to virtually every facet of life, from personal relationships to professional endeavours, from local communities to global initiatives.

In our personal lives, attending to the needs of loved ones can deepen bonds, foster understanding, and create a nurturing environment for growth and fulfillment.

In the workplace, this principle can enhance collaboration, boost morale, and ultimately drive success by ensuring that the needs of colleagues, customers, and stakeholders are consistently met.

On a broader scale, attending to the needs of marginalized or underprivileged communities can help address systemic inequalities, promote social justice, and work towards a more equitable and humane society.

The Ripple Effect

Ultimately, the Antimatter Principle has the potential to catalyse a ripple effect of positive change. When we attend to the needs of others, we inspire them to pay that kindness forward, creating a virtuous cycle of empathy, compassion, and collective progress.

In a world often consumed by self-interest and divisiveness, this simple paradigm serves as a powerful reminder of our shared humanity and the profound impact we can have by prioritising the well-being of those around us.

To Debate or Prototype? That is the Question

We’ve all been there – I certainly have – the team meetings that seemingly go on forever, dissecting every tiny detail of a proposed approach. Every potential issue is discussed ad nauseam. Opposing viewpoints are vigorously debated until faces are red and tensions are high. And at the end of it all, a week has gone by without a single line of code written.

These are the perils of analysis paralysis – the tendency to over-analyse a situation and get bogged down in discussions rather than actually making progress. It often stems from a fear of making the wrong choice, but paradoxically, it can lead to inertia that is far worse than any individual misstep.

For teams, a conundrum arises again and again: Is it better to spend a week rigorously debating and analysing the optimal approach for tackling a piece of work? Or is it more useful to rapidly build an exploratory prototype during that same week to validate ideas, hands-on?

The Endless Analysis Trap

There’s no denying the allure of the former approach. By thoroughly discussing every potential issue and considering all perspectives, surely the team can devise a near-perfect strategy, right? Wrong. Too often, this road leads to analysis paralysis – a state of inertia caused by bikeshedding hypothetical scenarios.

The Prototype-Driven Path

In stark contrast is the alternative of rapid prototyping. Instead of prolonged theoretical debate, a barebones working version of the software or a trial of the approach is built from the outset. This exploratory prototype serves as a proof of concept to validate the underlying ideas and assumptions through real implementations.

The virtues of this hands-on approach are numerous:

• It forces ambiguous debates into concrete ways of working
• Design and technical flaws are exposed early
• Stakeholders can review actual working software, not just abstract plans
• Time is not wasted overthinking issues that may never materialise

Striking the Right Balance

Of course, both extremes have their pitfalls. Some thoughtful upfront planning can sometimes help chart a general direction. But the most elite software teams recognise the limits of bikeshedding and paralysis by analysis. They favour iterative cycles – short bursts of planning, followed by prototyping, reviewing, refining, and repeating. A.k.a. PDCA (the Shewhart Cycle, popularised by Bill Deming)

By building tangible working software from the outset, even if rudimentary, teams avoid getting bogged down in theoretical tar pits. This practical feedback loop between talking and doing ultimately leads to better outcomes.

So for your next piece of work, might you choose to resist the urge to spend weeks analysing in the abstract? Roll up your sleeves, get building, and let the prototype guide your path forward.

What Does Your Team Prefer?

Every team has their own style. Some teams like to talk things through a lot before building anything. Others prefer to start building right away, maybe planning as they go.

Which approach does your team take more often? Do you find yourselves getting stuck in discussions without moving forward? Or does your team start building prototypes from the get-go?

There’s no one right answer for every situation. But it’s important to know your team’s natural habits. If you tend to over-discuss, consider setting time limits and forcing yourselves to start building. If you build prototypes yet find soem of that build time is wasted through e.g. misalignment or lack of clarity, consider spending some time getting aligned, upfront.

Being aware of these tendencies will help a team strike the right balance between discussing ideas and putting them into practice through prototyping. Finding this balance will lead to smoother execution.

Think about what your team typically does. This self-awareness can help you adjust to use the right mix of debating and prototype building.

Dissent: A Catalyst for Innovation

The Path Least Questioned

Businesses and software teams often find themselves entrenched in established practices and ideologies. Processes become routines, and routines turn into unquestioned norms over time. In such environments, conformity reigns supreme, and innovation is stifled. However, true progress lies in the disruption of these norms – the willingness to challenge the status quo through calm yet forceful dissent.

The Importance of Differing Perspectives

One key ingredient that is frequently overlooked when striving for innovation is the role of dissent – offering alternative viewpoints that diverge from the dominant narrative. When differing perspectives are encouraged and thoughtfully considered, businesses and teams can reap substantial benefits.

The Benefits of Constructive Disagreement

While dissent may initially seem disruptive or uncomfortable, it is essential for driving progress. When differing viewpoints are encouraged and respectfully considered, it can lead to:

1. Rigorous Evaluation of Ideas: Contrary opinions invite teams to thoroughly examine their assumptions and beliefs, and critically assess the merits and drawbacks of their proposals, resulting in more robust and well-rounded solutions.
2. Identification of Blind Spots: Individuals or groups often become entrenched in their own biases and perspectives, making it challenging to recognise potential pitfalls or oversights. Dissenting voices can help uncover these blind spots and mitigate risks.
3. Increased Creativity: By challenging the status quo, dissent can spark new lines of thinking and encourage teams to explore alternative approaches, fostering an environment of creativity and innovation.

Creating a Culture of Open Discourse

Fostering an environment where dissent can thrive requires a concerted effort from everyone. Here are some strategies to consider:

1. Lead by Example: Teams can choose to demonstrate a willingness to listen to and consider differing viewpoints, even when they contradict their own beliefs. This sets the tone for the entire organisation.
2. Establish Safe Spaces: Create designated forums or channels where folks can freely express their opinions without fear of repercussions. This could include regular brainstorming sessions, anonymous feedback mechanisms, or open discussions during meetings.
3. Promote Cognitive Diversity: Actively seek out individuals with diverse backgrounds, experiences, and perspectives to contribute to projects and decision-making processes. This diversity of thought can be a catalyst for both dissent and innovation.
4. Provide Constructive Feedback: When dissenting views are expressed, respond with supportive and constructive feedback. Invite folks to address the substance of the dissent, rather than dismissing or belittling the dissenting individual.

Embracing Dissent as a Competitive Advantage

In competitive business situations, the ability to adapt and innovate is a crucial differentiator. By cultivating an environment where dissent is not just tolerated but actively encouraged, businesses and software development teams can tap into a wealth of diverse perspectives and ideas, ultimately driving progress and gaining a competitive edge.

While embracing dissent often feels uncomfortable or disruptive, it’s a necessary catalyst for challenging complacency and fostering a culture of innovation. By fostering open discourse and constructive disagreement, organisations can unlock the full potential of their people and stay ahead of the curve.

The Path to Optimal Solutions Lies in Applying Systems Thinking Conjointly with the Antimatter Principle

This post outlines two key components required to reach truly optimal solutions in e.g. product development, software development, operational processes, etc.:

1. Applying Systems Thinking
   This refers to taking a holistic, interconnected view of the entire system or challenge. It means analyzing all the interrelated parts, perspectives, and dependencies rather than looking at any piece in isolation. Systems thinking allows you to understand how different elements influence and are constrained by each other within the larger environment.
2. Attending to All Relevant Needs
   In conjunction with the systems approach, the title emphasises the critical importance of comprehensively accounting for the needs of all the Folks That Matter™. It’s about diligently mapping, understanding, and addressing the priorities, constraints, and requirements across every impacted group – not just taking a narrow view.

The Fusion of Holistic Thinking and Stakeholder Attention

Here I suggest that optimal solutions cannot be reached solely by systems thinking alone nor by piecemeal consideration of some folks and some needs. Rather, it requires the combined application of:

1. Holistic systems thinking to understand interdependencies and potential trade-offs
2. Meticulous attention to the needs of all the Folks That Matter™ and perspectives involved

Only through applying these two principles conjointly and harmonising both the systems view and the full scope of relevant needs can we align on an overarching solution that proves genuinely optimal. It’s not, however , a binary choice. The more we take a holistic view, and the more we atten to folks’ needs, the closer we can approach an optimal solution.

In essence, it captures the balanced mindset of both broad systemic comprehension and depth of stakeholder-centricity required to find answers that are comprehensively optimized.

While simply attempting to attend to every single need does not automatically yield an optimal solution, adjusting partial solutions for each group’s needs in harmony with others is what gets us there. It’s a nuanced process of systems thinking.

The Art of Balancing Needs

How do we balance needs when seeking solutions?

Consider the development of a public park, which involves various stakeholder groups such as families with children, teenagers, seniors, environmental advocates, local government, public safety, and surrounding neighbourhoods. An optimal park plan doesn’t simply cater to each group’s demands in isolation.

It requires intelligently integrating common elements to meet multiple groups’ core needs simultaneously while making thoughtful adjustments to reconcile competing needs. For instance, increasing lighting can create safe evening spaces for families while addressing public safety concerns. Repositioning the park entrance can improve neighbourhood flow without compromising desired landscapes.

It requires intelligently integrating common elements that achieve several groups’ core needs simultaneously, while making thoughtful adjustments to reconcile competing needs in a balanced way. Perhaps increasing lighting implements both creating safe evening spaces for families while assuaging public safety concerns. Repositioning the park entrance eases neighborhood flow while allowing desired landscapes.

The strongest solutions emerge through this iterative systems approach of understanding how pieces interrelate, continuously harmonising and refining to appropriately serve all key stakeholder needs within realistic constraints. It’s an ongoing process of holistic refinement and balance.

Upholding the Systems Mindset

As we tackle multi-stakeholder challenges, we can choose to embrace this nuanced systems mindset. Simply checking boxes leads to conflicted or discordant solutions. The optimal path forward arises from diligently mapping then interconnecting and harmonising the intricate web of needs and priorities across all impacted groups and individuals.

The more thoroughly we consider and blend various factors into a unified solution, the better it can achieve lasting success amid complex challenges.

The “Good Enough” Sweet Spot

[Tl;Dr: “Good enough” means optimising for best meeting all the needs of the Folks That Matter™]

The Perils of Over-Engineering

In our quest for excellence, it’s tempting to over-engineer solutions, pouring needless resources into perfecting every tiny detail. However, this pursuit of flawlessness often comes at a steep price. Over-engineering can lead to diminishing returns, where the marginal benefits of additional effort become negligible. It can also result in unnecessary complexity, making systems harder to maintain and adapt.

The Pitfalls of Under-Engineering

On the flip side, under-engineering can be equally detrimental. Cutting corners or settling for subpar solutions may seem like a shortcut to efficiency, but it often leads to technical debt, compromised quality, and long-term sustainability issues. Under-engineered products or processes are more prone to failure, necessitating costly reworks or replacements down the line.

Striking the “Good Enough” Balance

Between these two extremes lies the “good enough” sweet spot – a delicate balance that maximises value while minimising waste. Embracing the “good enough” mindset means understanding when to invest resources and when to call it a day. It’s about recognising that perfection is an asymptote that can never be reached, and that diminishing returns inevitably set in.

The “Good Enough” Approach

Adopting a “good enough” approach involves setting realistic goals and prioritising the most critical aspects of a project or product. It means focusing on core functionality and user needs, rather than getting bogged down in superfluous features or tiny optimisations. By identifying the minimum viable product (MVP) and iterating from there, teams can meet folks’ needs faster and adapt more readily to changing requirements.

Quantifying the “Good Enough” Threshold

Of course, to deliver just what’s good enough, we have to know what’s good enough. Choosing to quantify the qualitative aspects of deliverables can help (Cf. Gilb).

Quantifying the Qualitative

Defining “good enough” can be challenging, especially when dealing with qualitative aspects such as user experience, design aesthetics, or customer satisfaction. However, by quantifying these qualitative elements, teams can establish more objective criteria and benchmarks for what constitutes “good enough.”

Leveraging Data and Metrics

One approach is to leverage data and metrics to measure and track qualitative aspects. For example, user testing and feedback can provide numerical scores for usability, intuitiveness, and overall satisfaction. Analytics data can reveal user behavior patterns, highlighting areas of friction or success. Even design aesthetics can be quantified through techniques like preference testing or eye-tracking studies. (See also: Gilb: Competitive Engineering).

Defining Acceptance Criteria

Another powerful tool is setting clear acceptance criteria upfront. By collaborating with stakeholders and subject matter experts, teams can define specific, measurable criteria that must be met for a deliverable to be considered “good enough.” These criteria can encompass functional requirements, performance benchmarks, accessibility standards, and qualitative thresholds based on user feedback or industry best practices.

Prioritising and Iterating

Once acceptance criteria are established, teams can prioritize the most critical aspects and focus their efforts on meeting those thresholds. By adopting an iterative approach, they can continuously refine and enhance the deliverables, incorporating feedback and adapting to evolving needs while maintaining a “good enough” baseline.

Embracing a Quantification-Driven Approach

Quantifying qualitative aspects requires a data-driven mindset within the organisation. Teams must be equipped with the tools, skills, and processes to collect, analyse, and act upon relevant data. Additionally, fostering a culture of continuous learning and experimentation can help, allowing for ongoing refinement and optimisation based on empirical evidence.

By quantifying qualitative aspects and establishing objective criteria, teams can more effectively arrive at the “good enough” sweet spot. This approach ensures that resources are allocated judiciously, core needs are met, and a solid foundation is established for ongoing iteration and improvement.

Embracing Iteration and Continuous Improvement

The beauty of the “good enough” philosophy is that it doesn’t preclude ongoing improvement. In fact, it embraces iteration and continuous refinement. By shipping a “good enough” initial version and gathering real-world feedback, teams can identify areas for enhancement and prioritise future efforts accordingly. This approach allows for more efficient resource allocation and greater responsiveness to the evolving needs of all the Folks That Matter™.

Fostering a “Good Enough” Culture

Cultivating a “good enough” culture requires a shift in mindset – one that values pragmatism, efficiency, and attending to folks’ needs over perfection. It means fostering an environment where team members feel empowered to make trade-offs and prioritise based on business impact. Teams play a crucial role in setting the tone, celebrating progress, and encouraging a bias towards action over analysis paralysis. Good enough applies to not only the product(s) but to the way the work to produce and support them works, too.

In essence, the “good enough” sweet spot is about striking the right balance – investing enough effort to deliver quality solutions that meet core needs, while avoiding the pitfalls of over- or under-engineering. By embracing this mindset, teams can optimise their resources, better address folks’ needs (but no better than good enough!) and foster a culture of (good enough) continuous improvement and adaptation.

Note to self: Mention the Kano Model, the Taguchi Loss function, and e.g. muri, mura and muda.

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.

The Spectre of Stochastic Parrots

AI and the Human Condition

As large language models (LLMs) continue their meteoric rise, their eerie ability to mimic human communication grows ever more sophisticated. However, we must keep a level head about the inherent limitations and potential pitfalls of these stochastic parrots trained on the endless babble of the internet.

The Faustian Bargain

LLMs are not innately intelligent. Rather, they are highly complex statistical engines, ingesting and regurgitating patterns from a colossal corpus of human-generated text (and more and more, from AI-generated text too). This digital ouroboros inevitably encapsulates the flaws, biases, and misinformation that tarnish so much of our online discourse.

We open a Pandora’s box when we uncritically accept an LLM’s outputs as gospel. Their responses are at best reflections of human knowledge – and at worst, amplifications of our worst impulses and untruths.

Towards a Nuanced Understanding

Does this mean we must reject the promise of AI? Not at all. But we can choose to adopt a nuanced, skeptical perspective when evaluating its responses. LLMs can be powerful aids, but never a substitute for human reason, wisdom and ethical judgement.

We are in an era of revolutionary yet unpredictable technological change. Maintaining a tight embrace of our core values and rationality is the only way to navigate these roiling waters. Let’s ride the rising tide of AI potential while never forgetting to remain vigilant against the flaws and distortions inherent in the data streams that birthed these technologies.

Why Corporate Software Developments Fail

The Graveyard of Good Intentions

I’ve seen wayyy more than my fair share of corporate software development efforts, up close and personal, over the years. From bright-eyed startups to lumbering enterprise behemoths, they all had one thing in common – they failed. And shockingly, they all failed for essentially the same reason – the collective assumptions and beliefs held by the management in charge of the efforts.

An Epidemic of Misguided Thinking

Time and again, I’ve witnessed management fall victim to a set of deeply flawed assumptions and beliefs that doom their initiatives from the start. These misguided beliefs act like a virus, infecting decision-making at every level and leading teams inexorably down the road to ruin.

Some of the most pernicious offenders:

• The assumption that more money and resources will accelerate progress linearly
• The belief that their bespoke requirements are genuinely unique
• Insisting that their internal talent is superior to readily available outside expertise
• Naively trusting that adopted methodologies like Agile or Lean will be a panacea

(You can find a full collection of some 70+ of these collective assumptions and beliefs set out in my books Memeology and Quintessence.)

Cycles of Failure and Denial

The saddest part is watching this cycle of failure and denial play out over and over. At first, there is optimism and confidence that this time will be different. Budgets are generously allocated, grand plans are hatched. But as delays mount and budgets are inevitably exceeded, the blame game kicks into high gear.

It starts with shooting the messenger – dismissing or discrediting any Cassandras who warn of impending disaster. When that doesn’t stem the bleeding, people turn on each other – management backstabbing, scapegoating external suppliers, and eternal damnation for any entreprenurial independent software vendor (ISV) unlucky enough to get caught in the crossfire.

An Ounce of Prevention

If I’ve learned anything from these myriad spectacles of self-immolation, it’s that taking proactive preventative measures is far more valuable than trying to fight an uphill battle after problems have already arisen. Before embarking on an ambitious development programme, management might choose to first confront their own biases and assumptions head-on:

• Accept that their requirements are not special; proven off-the-shelf solutions likely exist
• Look for and bring in highly skilled outside workers (and listen to them!) rather than sticking only to hiring people you already know.
• Adopt a mindset of humility, transparency and accountability from the top down

The path to success begins with honestly assessing one’s own limitations and tendencies for self-delusion. Those unwilling to engage in such introspection are doomed to keep repeated the same ruinous mistakes again and again.Mistakes for which we all pay.

The Instincts of the C-Suite are Way Off Base

In industries where collaborative knowledge work is key – software development, product design and the like – those at the top often have deeply flawed instincts about what drives productivity and creativity. Their assumptions about what motivates people and maximises value are frequently undermined by research and real-world results.

Conflating Activity with Productivity

A common managerial blind spot is the belief that more hours in the office equates to more productive output. Stemming perhaps from an industrial era mindset, executives often implement policies aimed at maximising “bums on seats.” Open plan officing, strict monitoring of attendance, limiting work-from-home – these are championed as means of fostering focus and accountability.

However, studies consistently show that knowledge workers are not production line operatives. Their optimal productive hours are limited and their cerebral tasks demand periods of distraction, refocusing and recharging. Trying to squeeze every possible minute out of them is counterproductive. Strict activity monitoring simply promotes insincere behaviour – employees pretending to be working while daydreaming or cyberloafing.

The Mythology of Keeping Them on a Tight Leash

Another frequent executive instinct is the desire for control and direct oversight. There is a notion that people must be micro-managed and kept on a tight leash lest they become complacent or distracted. Draconian monitoring of tasks, delivery and deadlines is viewed as essential in driving progress.

Yet autonomy has been shown time and again to be a powerful and essential motivator for collaborative knowledge workers. These are people who can be trusted to manage their own workflow within flexible guidelines. Injecting needless stress through oppressive oversight actively hampers productivity and alienates. The most engaged and high-performing teams are those afforded autonomy in executing their responsibilities.

Misunderstanding Intrinsic Motivation

Perhaps the most egregious executive blindspot relates to motivation itself. The traditional management view is that people are primarily motivated by money and status. The pursuit of higher salaries and promotions is seen as the catalyst that drives them.

While fair compensation and opportunities for growth are certainly baseline factors, study after study demonstrates the key drivers of motivation for knowledge workers are:

1. The inherent interest and enjoyment of the work itself
2. The opportunity to learn and develop mastery
3. A sense of purpose in creating something valuable

Environments injecting excessive financial rewards or top-down pressures to produce actively dampen these powerful intrinsic motivators. Meanwhile, cultivating working conditions that promote autonomy, mastery and purpose is proven to amplify productivity. And Cf. Dan Pink’s Drive).

Misunderstanding Collaborative Knowledge Work Itself

At a more fundamental level, many executives fail to grasp the very nature of collaborative knowledge work. They incorrectly view it as a assembly line process with discrete tasks to be delegated and combined into final deliverables. In their minds, software is built by having teams of coders each complete coding assignments that are integrated together. New products arise from different designers, analysts and specialists fulfilling their prescribed roles.

In reality, fields like software development and product design involve dynamic problem-solving where roles are fluid and team situations evolve rapidly. The work is fundamentally exploratory, requiring cycles of trial, testing, and incorporated learnings. Solutions emerge iteratively through interdisciplinary collaboration across all roles.

Trying to impose rigid, segregated workflows is antithetical to this reality. Successful collaborative knowledge work demands organisational models that are adaptive and non-siloed. People must be able to fluidly cross roles and swarm around emerging problems or opportunities as a cohesive team. Excessive process formality and, especially, hierarchy only gums up the works.

In Closing

While difficult to shed, executive instincts around managing collaborative knowledge work are often diametrically opposed to evidence-based best practices. What those at the top intuit rarely enhances outcomes – rigidly controlled activity, draconian oversight, and financial or status-based motivators actively undermine outcomes. True high performance comes from nurturing inherent motivation, respecting folks’ autonomy and needs, affording flexibility around working practices, and enabling an adaptive team-based model of execution.

The Myth of Redemptive Labour

The Working Class Confidence Trick

We’re taught from an early age that work is virtuous and ennobling. A puritan ethic extolling the moral value of working for a living has been deeply woven into our cultural fabric. We internalise the idea that through the sweat of our brows, we redeem ourselves and find meaning and self-worth.

But I’m going to let you in on a secret – this is a con game perpetrated by the capitalist ruling class. The notion of redemptive labour is a confidence trick, a way to get the working masses to willingly participate in their own exploitation.

The Capitalist Bourgeoisie’s Game

Think about it – who really benefits from this ethos of endless toil and self-sacrifice through work? It’s not the workers whose bodies and minds get ground down from incessant labour. No, it’s the patrician class of owners and investors who can sit back and watch the surplus value get extracted from the efforts of the working class.

By convincing everyone that work is intrinsically virtuous, the capitalist bourgeoisie naturalises what is essentially a system of wealth extraction. Workers are taught to equate their self-worth with their productivity in service of those who own the means of production. This psychological subjugation pacifies the masses and staves off working class consciousness.

The Mandated Indentured Servitude

The hard truth is that for most, work under capitalism is not a source of fulfilment or liberation, but rather a mandated form of indentured servitude. We sacrifice our finite time and energy not for our own benefit, but to generate profits that accumulate to a minority at the top. The redemptive labour myth tricks us into embracing this asymmetric relationship as noble and righteous. Sheesh.

Deprogramming Ourselves

So how about we start to deprogram ourselves from this ideological con. Work does not have inherent sanctity – it is a constructed system of exploitation designed to undermine our collective self-interest as workers. Until we can shake off these mental shackles, true emancipation will never be possible. UBI (Universal Basic Income) promises a way forward. And maybe that’s a reson why it’s so opposed by the exploting elites.

The Misunderstood World of Quality Assurance

What is Quality Assurance?

Quality Assurance (QA) is a term that gets tossed around quite frequently in the business world, particularly in the realms of product development and software development. However, despite its widespread usage, QA remains one of the most misunderstood and misused terms out there. Many conflate it with quality control, when in reality, QA is a separate and far more comprehensive approach that we might choose to see permeate every aspect of a business’s operations.

Separating QA from Quality Control

A fundamental misconception is viewing QA and quality control as one and the same. This could not be further from the truth. Quality control refers to the specific processes and techniques used to identify defects or non-conformances in products or services. It is a reactive measure, taken after a product or service has been created.

Quality Assurance, on the other hand, is a proactive and all-encompassing mindset, focused on implementing principles, processes, and activities designed to achieve the goal of “ZeeDee” – Zero Defects. When effective QA practices are in place, the need for extensive quality control measures – a.k.a. inspections, testing – becomes largely unnecessary.

The Holistic QA Approach

In the context of product development, we might choose to see QA integrated into every phase, from conceptualisation to final delivery and beyond. This involves establishing clear quality objectives, defining measurable criteria, implementing robust preventive measures, and continuously monitoring and improving based on feedback and data.

Similarly, in software development, we may choose to regard QA as crucial throughout the entire lifecycle, ensuring functionality, reliability, and an optimal user experience – not through testing, but through activities like risk management, all geared towards the Zero Defects goal.

Prevention over Correction

The true power of Quality Assurance lies in its ability to prevent issues before they arise, rather than correcting them after the fact. By implementing comprehensive QA strategies with e.g. ZeeDee as the guiding star, organisations can significantly reduce or eliminate the need for resource-intensive quality control processes (inspections and the like), resulting in increased efficiency, cost savings, and a superior end product or service.

An Organisational Culture

Ultimately, Quality Assurance is not merely a set of tools and techniques; it is a mindset and a culture that must be embraced by every member of an organisation. From top management to front-line employees, everyone must understand the importance of quality and take ownership of their role in ensuring that products and services consistently meet the needs of all the Folks That Matter™, with Zero Defects as the guiding principle.

Conclusion

In a world where businesses strive for excellence and customer satisfaction is paramount, Quality Assurance as defined here is not a luxury; it is a necessity. By recognising the true scope and significance of QA, its distinction from quality control, and its pursuit of ZeeDee (Zero Defects), organisations can unlock the full potential of their products and services, foster a culture of quality, and ultimately, achieve sustainable success in an increasingly competitive marketplace.

Embracing Irrelevance

The Harsh Reality

There I was again, sitting in yet another meeting, trying to share perspectives honed over decades of leading software teams and driving development efforts. I knew the challenges they were facing, and had wrestled with similar issues countless times before. I metaphorically raised my hand and began outlining a potential path forward, drawing upon hard-won knowledge and experience.

But I could see the glazed looks from the fresh-faced engineers before me. The furtive glances at phones and laptops. I was bombarded by the deafening silence of irrelevance.

It’s a harsh reality that many experienced technology professionals eventually need to confront. The industry moves at a blistering pace, with new languages, frameworks, and methodologies materialising every few years. Management fads come and go in eerily predictable cycles. The young zealots who embrace each new trend inevitably become the cranky stick-in-the-muds insisting, “We’ve always done it this way, and it works just fine.”

A Joyful Choice

It can be incredibly disheartening to find your deep institutional knowledge rapidly becoming irrelevant, proverbially screaming wisdom into an unheeding void. You watch in dismay as the same mistakes you learned from get repeated over and over. You furiously take notes during meetings, composing verbose emails that seemingly disappear into purgatory.

At some point, you’re left with two choices – endlessly rage against the machine of disruption and alienate those around you, or embrace your newfound irrelevance. I’ve joyfully chosen the latter.

The Therapeutic Stance

Trying to force your experiences on those unwilling or unable to receive them is incredibly unfulfilling, not to mention pointless. It simply results in frustration for all involved. Instead, I’ve learned to share my perspectives selectively with those who actively seek my counsel. I’ve let go of the need to be heard. And it’s a major reason for my current “therapeutic” stance – eschewing advice in favour of empathetic listening, non-judgement, and facilitating others’ self-discovery.

A Tremendous Liberation

In many ways, it’s a tremendous and joyful liberation. Any pressure to have all the answers dissipates. You’re free to sit back, listen, and learn from those with fresh ideas and energy. You can empathise and support when asked without putting your entire self-worth on the line.

Most importantly, you gain the ability to focus on what truly matters – making life more wonderful rather than feeding your own ego. Finding relevance in being helpful to others, not in forcing them to accept your specific brand of help. Semper mirabilis!

Unshackling Yourself

So I embrace irrelevance. I recognise that skills atrophy over time. I accept that the march of technology will inevitably leave us behind in some areas.

Might I suggest using the precious time you have left to unshackle yourself from the burden of universal relevance. Pour your efforts into making an impact where you still can. You may find more fulfilment in your later years than you ever did being the irreplaceable expert.

 

Why Your Brain Lies to Itself: A Mind-Changing Look at “How Minds Change”

I started out reading David McRaney’s “How Minds Change” wanting to hate it. Just another pontificating intellectual, I thought. But then as I got into it, my mind changed. And although about individuals, the relevance to Organisational Psychotherapy became clear. Even if the answer to “…how do collective minds change” has not become entirely clear as yet.

The Desire for Consistency Deludes Us

One of the book’s great strengths is how approachably McRaney conveys complex concepts through compelling real-world examples anyone can relate to. He deftly illustrates how our innate desire to seem consistent frequently causes us to rationalise away contradictory information. We meet people who have gone to extraordinary lengths to cling to conspiracy theories, fanciful identities, and quack medical treatments despite overwhelming opposing evidence.

Online Echo Chambers Reinforce Our Delusions

McRaney also delves into the polarising effects of internet echo chambers, highlighting how we gravitate towards online sources that reinforce our views – likely contributing to rising societal divides. He makes a persuasive case that we are beautifully equipped for detecting patterns but ill-suited for changing our minds about them once beliefs have formed.

Tools For the Job

The book also sheds light on the tools we might use to change our minds – and the minds of others (if they’re so willing) – on specific issues. For example, “Deep Canvassing*” with its opening questions:

• “Where or from whom did you first hear about this issue?”
• “Do you know of anyone that has been personally affected by this issue?”

Cultivating an Open Mind

While How Minds Change paints a sobering picture of human stubbornness, it provides insights into approaches for becoming more open-minded. Developing humility, seeking differing perspectives, empathising, listening, and questioning our motives can help overcome our resistance to belief revision.

An Elegant Wake-Up Call

This superbly researched and engagingly written book is an illuminating look at how our minds so readily convince us of untrue things. How Minds Change is a must-read for understanding complexities of reasoning, cognition, and our self-deceptions. Crucially, it offers invaluable guidance for learning how to re-evaluate our most steadfast notions with an open mind.

What began as skepticism towards yet another intellectual piling on, quickly transformed into an eye-opening journey into the depths of my own mind’s resistance to change. Engaging stuff.

---

* Deep Canvassing

Deep canvassing is a method of door-to-door political campaigning that aims to have longer, deeper conversations with voters in order to try to change their minds on particular issues rather than just persuading them how to vote.

The key principles of deep canvassing are:

1. Using active listening and open-ended questions to have an in-depth, two-way conversation rather than just delivering scripted talking points.

2. Focusing on trying to understand the root motivations, experiences, and values that underlie a person’s stance on an issue.

3. Sharing personal narratives and trying to find common ground while also respectfully bringing up counterpoints.

4. The goal is not just to win a voter over in that moment, but to plant seeds that could lead them to re-evaluate and potentially change their stance – and minds – over a longer period of time.

Deep canvassing was pioneered in the United States by the LGBTQ rights organization LBGT Action in the lead up to same-sex marriage ballots. Their deep canvassing approach was found to be remarkably effective at shifting voter attitudes compared to traditional persuasion canvassing.

While more time-intensive, deep canvassing recognises that people’s views on controversial issues are often deeply rooted and simply dismissing or arguing against them directly is ineffective. By facilitating open-ended conversations that chip away at preconceptions over time, it aims for more durable opinion shifts.

Change is a Social Phenomenon

It is often said that Man is a social animal, meant to live in communities and derive meaning from interactions with others. We are fundamentally shaped by the social structures and relationships around us from birth. Our beliefs, assumptions, values and behaviours are heavily influenced by the culture, norms and people we grow up around. (And don’t overlook pets and other flora and fauna).

Just as our individual psyches are moulded by social forces, so too is change itself a profoundly social phenomenon. True shifts in mindsets, behaviours and beliefs rarely happen in isolation. They tend to arise organically from the interplay of ideas, the cross-pollination of perspectives, and the prevailing Zeitgeist of the times. People’s views evolve through conversations, observations of others, ingoup vs outgroup influences, and the gradual reframing that comes from immersion in new environments.

The Power of the Group

This underscores the potential power of groups and organisations in catalysing change. When people come together around common goals or experiences, there is a meaningful interaction of minds. Assumptions are challenged, new syntheses arise, and space is created for evolution of thought. Just as individuals can undergo therapy to overcome unhealthy patterns, so too can groups undergo a kind of psychotherapeutic process to overhaul outmoded and dysfunctional paradigms.

Organisational Psychotherapy

This is the premise behind the emerging field of organisational psychotherapy. Just as individual therapy provides a container for people to explore their inner landscapes in order to grow, organisational psychotherapy involves creating facilitated spaces for teams, companies or communities to engage. Using insight from psychology, group dynamics and systems thinking, trained practitioners can help organisations gain self-awareness around dysfunctional patterns, beliefs and behaviours that may be holding them back. From this raised vantage point, new narratives and ways of operating can emerge organically.

The Group as Crucible

Organisations and teams are microcosms where the full spectrum of human behaviour and group dynamics are constantly playing out. As such, they become rich territory for exploring how change actually happens. Real transformation happens not through rigid policies or top-down mandates, but through people-led shifts in culture, mindsets and relationships. The group itself acts as a crucible for these new ways of being to gestate and be stress(!) tested. In being witnessed and worked through collectively, outmoded mindsets can be let go of, making space for what needs to emerge.

In this way, organisational psychotherapy is not just about imparting new models or frameworks, but about harnessing the innately social and emergent nature of how humans actually change and evolve. It is a way of working with the group mind itself as the catalyst for transformation.

The Agile Paradox: When Founders Fail Their Own Manifesto

The Incongruous Origins

The Agile Manifesto threw the software world into disarray when introduced in 2001. With its emphasis on individuals over processes, it promoted radical values like customer collaboration, embracing change, and empowering motivated teams.

However, over 20 years on, there is a glaring disconnect between the values espoused and how some of the founders themselves behave, according to the thought-provoking critique by @davenicolette. It’s a harsh charge – that the very people birthing the Agile revolution violate its core tenets through arrogant, domineering attitudes antithetical to the spirit of empathy and humility they advocated.

A Cultural Blind Spot

This paradox may stem from the homogeneity of the Manifesto authors as middle-class white males from individualistic Western cultures. @davenicolette posits that the teamwork and self-organisation urged by Agile were unnatural in such environments, hence the need for a “grand statement of the obvious.”

In more collectivist societies, these human-centric principles were ingrained, making much of the “Agile industry” of training and certifications more or less irrelevant. The coaching, tools and jargon were unnecessary “grabs for attention” in individualistic contexts.

Heroes to Humans

A core Agile principle was rejecting the old “hero-god” mentality of software development, instead fostering self-organising teams of empowered peers. Tragically though, @davenicolette finds some founders exhibiting that very domineering behaviour they aimed to dismantle.

In a striking role reversal, these “hero-gods of Agile” reportedly collaborate poorly, fixating on their own perceived wisdom over cultivating curiosity about others’ perspectives. A far cry from the humble facilitation prescribed by their own teachings.

The Agile Evolution: Organisational Psychotherapy

As Agile principles continue being applied beyond software, the future increasingly points toward an organisation-wide psychotherapeutic approach to workplace development and improvement.

Organisational Psychotherapy (OP) seamlessly blends the human-centric principles at Agile’s core with a holistic focus on group dynamics, emotional intelligence and cultivating synergistic team cultures. It’s a natural progression from the Manifesto’s original emphasis on prioritising individuals and interactions over processes.

In this sense, organisational psychotherapy represents the next evolutionary wave – taking the ideals of empathetic, self-aware collaboration and expanding them into a comprehensive intentional approach for nurturing the human elements that allow organisations to truly flourish.

As @davenicolette expresses, the fundamental “agile thing” boils down to simply allowing and enabling people to work in a manner innate to our species. Organisational psychotherapy provides a framework for manifesting that ideal across all kinds of organisations, while helping address cultural hang-ups and institutional obstacles.

By fusing the original humanist values with a strategic organisational focus, this approach can help transcend the personal contradictions of the founders and realise their full transformative potential across all industries. It’s the embodiment of “individuals and interactions” writ large.

The Multicultural Counter-Example

Contrasting this, @davenicolette shares an uplifting tale of coaching a diverse, multicultural team comprising six nationalities. Despite no native culture in common, they smoothly embodied teamwork and continually improved their approach – all with minimal resistance or guidance required.

This team’s seamless discovery and embracing of the ideas the Manifesto fought so hard to establish perhaps reveals the broader cross-cultural resonance when people transcend societal biases around individualism.

Simple Wisdom Lost

As Agile pervaded the corporate sphere, the original straightforward vision of “working naturally as humans” became increasingly obscured. Corporatisation, commodification of training, and standardisation into rigid processes corrupted and diluted the elegant simplicity at its core.

Organisational Therapy: The Next Level

Organisational Psychotherapy takes the Manifesto’s people-first philosophy to the next level. It blends prioritising individuals with cultivating healthy group dynamics, emotional intelligence, and vibrant team environments. It further evolves the idea of valuing interactions over processes.

The holistic approach helps us grow as individuals while optimising how we work collectively to achieve more together than we could alone. By applying psychological insights through an organisational lens, it charts an expansive path for making the Manifesto’s ideals a reality across organisations.

The Fruitful Future

From this perspective, the future feels absolutely brimming with creative potential. We can combine our skills, remove limits holding us back, and build supportive environments that increase what we’re able to do while appreciating our human nature.

It’s a wide-open opportunity awaiting trailblazers willing to forge an inclusive, self-aware path like Agile’s founders did. We stand poised to discover new ways to collaborate and unleash our collective genius to everyone’s benefit.

The Human Revolution Continues

With OP illuminating the way, we can realise more of our ambitions. This human-honouring revolution can now reshape the very core of how organisations operate – tapping into our need for continual growth and flourishing teams to build a perpetually evolving, thriving future together.

Ultimately, @davenicolette posits, the Manifesto’s powerful ideas may be best appreciated by disassociating them from the personal shortcomings of their originators. While honouring their revolutionary contribution, separating the philosophy from its founders’ “peculiar incongruities” allows its value to shine through – untarnished by human contradictions.

In its essence, Organisational Psychotherapy is a call to harness our truest, most collaborative selves through self-awareness, teamwork, continual introspection, and shunning of dogmas. A clarion call to humanise the workplace that likely resonates most purely when its ideas transcend the limitations of the Manifesto’s origins. How about we use the Manifesto as a stepping stone to better things?

Deliver Value by Addressing the Customers’ Crucial Needs

[Tl;Dr: Optimal value to customers means helping them address their active constraint]

The Paradox of Customer Needs

In the context of organisations which develop software, understanding customer needs is paradoxically both straightforward and complex. On the surface, the goal seems clear – create software that meets the expressed requirements and desires of the customer. However, these articulated wants often fail to accurately capture the customer’s genuine, underlying need.

The Theory of Constraints Insight

Eliyahu M. Goldratt’s Theory of Constraints offers a powerful lens through which to view and resolve this paradox. According to Goldratt, at any given time, an organisation faces a single constraint – a bottleneck – that limits its progress toward its goal(s). This constraint represents the pivotal need that, if addressed, would unlock new levels of progress and value for the organisation.

Needs Manifest as Constraints

Through this framework, we can redefine the concept of customer needs in software development: the customer’s crucial need is to identify their current organisational constraint and see it addressed. While customers may articulate a multitude of wants, their fundamental need remains anchored in alleviating the bottleneck that is holding them back from achieving their broader goals.

Continuous Adaptation to Evolving Needs

However, just as individual human needs evolve over time, so too do an organisation’s constraints. As one bottleneck is addressed, a new constraint inevitably emerges, creating a cycle of perpetually evolving needs. This necessitates an iterative, adaptive approach to software development, where efforts are continuously re-aligned to tackle the customer’s current constraint as it shifts.

Fostering Deep Organisational Understanding

To effectively identify and address these pivotal customer needs, a deep understanding of the customer’s organisation is essential. This requires going beyond surface-level requirements gathering and actively engaging with all the Folks That Matter™, observing processes, and immersing oneself in the organisational culture (a.k.a. shared assumptions and beliefs). Only through such immersion can one gain the insights necessary to pinpoint the root constraint and develop targeted solutions.

Delivering Continuous Value

By embracing this perspective – that customer needs manifest as organisational constraints – software development becomes an ongoing journey of value delivery. Each cycle of identifying and addressing the current constraint provides tangible value to the customer, propelling their organisation forward. And as new constraints emerge, the cycle repeats, ensuring that solutions remain relevant, impactful, and aligned with the customer’s evolving needs.

Conclusion

True value in delivering solutions to customers lies in addressing customers’ crucial needs, which are inextricably tied to their in-the-now operational constraints. By adopting a constraint-focused, iterative approach and fostering deep understanding of customers’ needs vis their constraint, solutions can continuously meet customers’ fundamental needs, unlocking new levels of service, customer satisfaction, and mutual success.