Archive

Organisational Therapy

Exploring Shared Assumptions and Beliefs with the Help of an AI Chatbot

Introduction

As businesses strive for innovation and growth, they often find themselves running up against unseen barriers – ingrained ways of thinking and behaving that can severely limit their ambitions and ability to adapt. In many cases, these constraining (shared) beliefs and assumptions live under the surface, making them extremely difficult to identify and uproot.

This sample dialogue (below) aims to illustrate how engaging with an AI chatbot like Claude can provide a fresher, more impartial perspective to help bring those unconscious blockers into the light. By asking probing questions and suggesting reframes, an AI can serve as a cooperative thinking partner to explore the root causes behind an organisation’s collective blind spots.

Let’s take a look at how this conversational process might unfold:
(Note: this is an actual dialogue generated by ClaudeAI)

Overcoming Organisational Blind Spots: A Candid Dialogue

Are Collective Mindsets Holding Us Back?

Business Team: We’re really struggling as a team at work. Our growth and innovation have hit a plateau, and we can’t seem to get over this hump. We feel like there are some underlying assumptions or beliefs that we all unconsciously share that are limiting our thinking, but we can’t quite put our finger on what they are. Any thoughts?

Claude: That’s an insightful observation. Could you elaborate on the areas where your team has faced repeated roadblocks or struggled to adapt? Have you noticed any patterns in how new ideas get instantly dismissed or shut down?

The Perils of Risk-Aversion

Business Team: You know, now that you mention it, we do tend to instinctively shut down ideas that seem too ambitious or radically different from our current model. There’s an assumption that taking big swings is too risky and that we’re better off sticking to incremental innovations.

Claude: I see, so there seems to be an excessive aversion to risk-taking that could be crippling your team’s ability to innovate more boldly. Where might this belief originate from? Perhaps past failures that bred excessive caution within the team?

Overconfidence from Past Successes

Business Team: And you’re right, we may be overly reliant on past glories and successes rather than pushing for true disruption these days.

Claude: Overconfidence and complacency from previous successes is a common pitfall for teams. Have you explored where those constraining beliefs originated within your group? Sometimes they start from overcorrecting after a past failure. Or they take root from excessive short-term focus and risk-aversion in decision making over time.

Business Team: You’ve hit the nail on the head. We can trace the risk-aversion back to a few high-profile product launches that failed a few years ago. And the reverence for our old products stems from the founders still being closely involved, constantly reminiscing about how we initially disrupted the market.

Shattering Ingrained Narratives

Claude: Those do seem like major sources of the limiting beliefs constraining your team’s thinking. But how can you start dismantling and changing those ingrained narratives collectively? Here are some suggestions:

  1. Make the limiting beliefs explicit and discuss them openly together as a team. Bringing these unconscious biases into the light is key.
  2. Have you analyzed instances where those beliefs caused you to miss opportunities and calculated the cost of leaving innovation on the table as a group?
  3. Could you find examples of competitors or companies in other industries who have succeeded by doing the opposite – embracing risks, continuously reinventing themselves? Study how they cultivated a different organizational mindset.
  4. Implement structural changes to counteract the limiting beliefs. For instance, explicitly weighing the cost of inaction, having an “innovation ombudsman” role, or celebrating failed experiments more than static successes.
  5. Bring in fresh perspectives through new hires, industry experts, or even customers who can challenge the status quo assumptions.

The ultimate ambition might be to make curiosity, experimentation, and an appetite for disruption core cultural values for your team and organisation.

Business Team: This is immensely helpful. We have a much clearer picture now of how to diagnose and deliberately shift our unhelpful collective beliefs as a team. Change starts by bringing those unconscious biases into the light through open discussion. We really appreciate you laying out such a detailed framework – we’re energized to start implementing these ideas right away.


Bringing in an Organisational Psychotherapist

Sometimes, even with the best intentions, it can be extremely difficult for a team to identify and overcome their own deep-seated collective assumptions and beliefs on their own. This is where bringing in an outside organisational psychotherapist can be invaluable…

By prompting deeper reflection, offering new perspectives, and designing tailored interventions, an experienced organisational psychotherapist or AI assistant can catalyse the crucial process of surfacing and reflecting upon an organisation’s dysfunctional beliefs and narratives.

While working with a human expert may ultimately be advisable for any complex organisational transformation, this dialogue demonstrates how an AI like Claude can provide a potential first step. Through probing inquiries and analytical detachment, an AI chatbot can shed light on the obscured mental models that might be unwittingly obstructing an organisation’s path to greater innovation and growth.

What Are You Missing Out On?

In any organisation, the beliefs and assumptions that everyone holds in common can have a profound impact on culture, productivity, and overall success. By neglecting shared assumptions and beliefs you may be missing out on harnessing the power of aligning them for optimal performance. But what exactly could this approach unlock for your organisation?

For Executives and Senior Managers

Shaping the Organisational Mindset

As a leader, you set the tone for the entire company’s culture and worldview. However, failing to examine and actively shape the company’s ingrained assumptions can lead to misalignment and hinder performance. Organisational psychotherapy illuminates existing belief systems – a.k.a. the collective mindset – and provides means to cultivate an organisational mindset centered on the things that matter to you, and a unified vision for success.

Transcending Limiting Assumptions

Over time, organisations develop deep-rooted assumptions that act as invisible shackles, limiting innovation, adaptation and achievement of goals. You could be missing out on breaking through these limitations by not exploring the underlying group psyche. Organisational psychotherapy techniques identify and reframe constraining assumptions, allowing you and your peers, and your workforce, to operate from an empowered, possibility-focused perspective.

For Middle Managers

Bridging Misaligned Beliefs

In the pivotal role of middle management, you navigate the shared assumptions of both leadership and frontline teams. Unaddressed, differing beliefs between groups can breed misunderstanding and hinder synergy. Organisational psychotherapy provides a framework for uncovering disconnects and fostering more cohesive, aligned assumptions across all levels.

Fostering Trust and Psychological Safety

Highly effective teams are built on a foundation of trust and the ability to take interpersonal risks. You could be missing out on this key ingredient if psychological barriers rooted in distrustful and deleterious assumptions remain unaddressed. Psychotherapeutic interventions help everyone examine and reshape beliefs around vulnerability, conflict, and collaboration.

For Technical Workers

Unleashing Pioneering Thinking

For technical roles requiring cutting-edge solutions, limiting assumptions around “how things are done” stifle innovation. You may be missing out on radically more effective approaches by not exploring and expanding your team’s collective assumptions about e.g. what is possible. Psychotherapy illuminates blind spots and reframes beliefs to open minds to truely different thinking.

Fostering Knowledge-Sharing

In highly specialised technical domains, knowledge-sharing is critical but often obstructed by entrenched assumptions of competence hierarchies or domain territoriality. Organisational psychotherapy provides means to surface and reflect on these counterproductive beliefs, instead opeing the door to assumptions that celebrate joyful work, collaborative growth and learning.

Summary

Embracing organisational psychotherapy unlocks an often-overlooked yet powerful source of competitive advantage – the shared assumptions and beliefs that underpin an organisation’s culture, communication, and performance. By neglecting this dimension, you may be missing out on by not giving organisational psychotherapy serious consideration as a powerful tool for your toolbox:

For Executives and Senior Managers:
The ability to purposefully shape an organisational mindset aligned with your shared vision and strategic objectives. As well as the opportunity to transcend limiting assumptions that constrain innovation, adaptation, and achievement.

For Middle Managers:
A framework for bridging misaligned beliefs across levels that breed misunderstanding and hinder synergy. And fostering a bedrock of trust and psychological safety that enables teams to take interpersonal risks and collaborate effectively.

For Technical Workers:
Unleashing pioneering, radically different thinking by reframing beliefs around “how things are done.” And cultivating knowledge-sharing by dispelling assumptions of competence hierarchies and domain territoriality.

At every level of an organisation, insidious assumptions and beliefs can act as unseen forces, obstructing potential and stalling progress. You could be missing out on dismantling these forces and instead harnessing the power of shared vision, alignment of mindsets, and collaborative beliefs.

Organisational psychotherapy provides the insight and means to illuminate, examine, and reflect on the collective beliefs and assumptions influencing your organisation’s culture and performance. Is it yet time you explored how to unleash this underutilised power and stop missing out on achieving new heights of success?

What Don’t You Know?

The Known Unknowns

As software developers, we inevitably encounter knowledge gaps – areas where we are certifiably clueless. Perhaps we’ve never worked with databases, so we recognise terms like “schema” and “queries” as complete unknowns we’d need to study.

These are the “known unknowns” – subjects we can identify as unfamiliar terrain, even if we can’t articulate precisely what lies in that territory. While frustrating, known unknowns at least make the gaps in our understanding visible.

The Invisible Unknowns

Far more insidious is the state we call metacluelessness – being unaware of unknown domains altogether. These are the invisible “unknown unknowns” – entire domains of knowledge and skill whose existence we fail to even comprehend.

For us developers, metacluelessness blinds us to whole realms of critical concepts and practices. We may be experts in shipping web apps, but oblivious to vital DevOps disciplines like infrastructure-as-code, monitoring, or chaos engineering. Or talented backend coders who have never conceived of cutting-edge frontend paradigms like WebAssembly or Jamstack. And then there’s the whole raft of invisibles related to the way the work works – not necessarily an issue for micromanaged developers, but for self-managing teams, crucial.

These aren’t just knowledge gaps – they’re unknowns we don’t know exist. Unfathomable blind spots preventing us from recognising what we’re missing.

The Illusion of Mastery

Metacluelessness is pernicious because it breeds complacency and over-confidence in our ranks. When we’re unaware of the boundaries of our mastery, it’s easy to succumb to arrogance about our depth of experience.

Without recognising our blind spots, we assume comprehensive expertise simply because we’ve never glimpsed the unknown territories. This false mastery mindset leaves us closed-off to growth, unable to even ask the questions that would identify new areas for development.

Shattering the Illusion

The antidote to our metacluelessness is shattering the illusion that our knowledge has no limits. It’s the humble admission that our expertise, however vast, is circumscribed by invisible domains we cannot fathom.

This isn’t easy – it requires us to continually question the limits of our understanding. To surround ourselves with new perspectives and domains. To listen for obscure terminology that hints at whole schools of thought we’ve never apprehended.

Only by identifying the realities of our metacluelessness can we begin addressing it. Grappling with unknown unknowns, if only to clarify what they are, not comprehend them fully. It’s an endless process of mapping the boundaries of our ignorance.

The Never-Ending Terrain

For us developers, pushing past metacluelessness is an infinite game. The leading edges of the intersection of software, work and business are so vast and emergent, there will always be new blind spots blocking our peripheral vision.

As we shed light on one enclave of metacluelessness, it reveals dozens more shadows where blind spots reside. It’s a perpetual cycle of overcoming the limitations of our expertise, only to uncover new frontiers of ignorance.

But embracing this cycle, and the inherent metacluelessness that comes with being human, is the path to true mastery. We cannot eliminate blind spots entirely, but we can develop the self-awareness to recognise their existence – and the curiosity and humility to keep exploring.

Deming’s 95/5 Principle Negates Individual Coaching

In the world of organisational improvement and performance enhancement, W. Edwards Deming’s principles have had a profound impact. One of his most famous principles, the 95/5 rule, suggests that 95% of performance issues are attributable to the system and processes, while only 5% are due to the individual worker. This principle has however not led many organisations to prioritise systemic changes over individual development initiatives. So does Deming’s 95/5 principle entirely negate the value of individual coaching? Let’s explore.

The 95/5 Principle: Putting Systems First

According to Deming’s 95/5 principle, the vast majority of performance problems stem from flawed organisational systems, processes, and cultures. Focusing on individual skill development or coaching would be akin to treating the symptoms without addressing the root cause. Deming advocated for a systems thinking approach, wherein organisations critically examine and optimise their practices, policies, and culture to create an environment conducive to success.

In the context of collaborative knowledge work, this principle suggests that individual coaching efforts will have limited impact when the underlying organisational systems and processes are not optimised for effective collaboration, knowledge sharing, and collective problem-solving.

The Shortcomings of Individual Coaching

Proponents of Deming’s philosophy argue that individual coaching alone is insufficient in addressing performance issues within collaborative knowledge work environments. Even if individuals receive coaching to enhance their communication, teamwork, or creative thinking skills, these efforts will be undermined or rendered ineffective when the systems and culture within which they operate are counterproductive or siloed.

For example, imagine a scenario where knowledge workers receive coaching on effective knowledge sharing practices, but the organisation lacks a robust knowledge management system or has rigid hierarchical structures that discourage cross-functional collaboration. In such cases, the individual coaching will yield limited results due to systemic barriers.

Organisational Transformation: The Key to Collaborative Success

According to Deming’s principle, our primary focus should be on transforming organisational systems and culture to foster an environment conducive to collaborative knowledge work. This could involve:

  • Optimizing communication channels and knowledge sharing platforms
  • Breaking down departmental silos and promoting cross-functional collaboration
  • Fostering a culture of continuous learning and improvement
  • Implementing agile and flexible processes that adapt to changing needs
  • Establishing clear roles, responsibilities, and accountability mechanisms
  • Organisational psychotherapy – enabling the organisation to surface and reflect on its shared assumptions and beliefs

By prioritising systemic changes, organisations create an enabling environment where individuals can thrive and collaborate effectively, minimising the need for extensive individual coaching.

The Verdict: Individual Coaching Has Limited Value

While individual coaching may provide some marginal benefits, Deming’s 95/5 principle suggests that it has limited value in the grand scheme of enhancing collaborative knowledge work. Organisations that solely rely on individual coaching initiatives without addressing the underlying systemic issues will experience suboptimal results and inefficiencies.

The path to success lies in embracing a systems thinking approach, transforming organisational assumptions and beliefs, structures, and culture to create an environment that fosters collaboration, knowledge sharing, and collective problem-solving. Only then can organisations unlock the full potential of their knowledge workers and achieve sustainable performance improvements.

In conclusion, Deming’s 95/5 principle entirely negates the value of individual coaching as a standalone solution for enhancing collaborative knowledge work. Instead, it calls for a fundamental shift towards organisational transformation, where systemic changes wrought through i.e. organisational psychotherapy take precedence over individual development initiatives.

How “Constant State of Ship” Drives Transformative Practices

Introduction

In the relentless pursuit of delivering value to customers, with unparalleled speed and reliability, the software development world has yet to widely embrace a revolutionary principle – the “Constant State of Ship”. This state, where software artefacts and products are perpetually poised for release into production environments within just 15 minutes’ notice, has emerged as a driving force behind best practices that enable true continuous deployment. Remarkably, this groundbreaking concept formed the foundation of the pioneering “Javelin” software development approach, a visionary approach conceived by FlowChainSensei (Bob Marshall) at Familiar circa 1996 and onwards, foreshadowing the industry’s even-now-yet-to-be-realised embrace of these practices.

The Power of “Constant State of Ship”

The “Constant State of Ship” serves us as an unyielding forcing function, inviting teams to adopt and adhere to a comprehensive set of best practices that catalyse the seamless flow of software into production. Let us explore how this principle reinforces each of thirteen fundamentals of Continuous Delivery (hat tip to Dave Farley):

The 13 Fundamentals Enabled

  1. A Repeatable, Reliable ProcessWith the ever-present possibility of an imminent release, teams may choose to establish a well-defined, automated pipeline for building, testing, and deploying their software. This process needs to be repeatable and reliable, minimising the risk of human error and ensuring consistency across releases.

    The “Constant State of Ship” mindset suggests that teams have a streamlined, automated release pipeline that can be triggered at any moment. Manual steps and ad-hoc and emergency exception procedures become liabilities, as they introduce variability and increase the chances of mistakes during deployment.

    To achieve this repeatability and reliability, teams are supported to invest in build automation tools, automated testing frameworks, and deployment automation pipelines. Every step of the release pipeline can be codified, documented, and thoroughly tested to ensure predictable outcomes each time.

    Moreover, the “Constant State of Ship” principle fosters an environment of continuous learning and improvement. Any failures or issues encountered during a release are promptly analysed, and the release process is refined to prevent future occurrences. This cycle of continuous feedback and optimisation ensures that the release pipeline remains reliable and efficient, even as the codebase and systems evolve over time.

    By operating in a “Constant State of Ship” mode, teams are invited to treat the release pipeline as a critical component of their software development lifecycle, investing the necessary resources and effort to make it repeatable, reliable, and capable of delivering changes to production environments at a moment’s notice.

  2. Automate All the ThingsIn a “Constant State of Ship” paradigm, manual interventions become significant bottlenecks and risks, hindering the required velocity and reliability. Automation becomes imperative, spanning every aspect of the delivery pipeline, from code compilation to infrastructure provisioning. The threat of an imminent release leaves no room for error-prone manual processes that could delay or derail a deployment. Teams must automate build processes, test execution, environment provisioning, deployment steps, and release orchestration to ensure consistency and minimise the risk of human error.
  3. Maintain a Releasable StateThe core tenet of “Constant State of Ship” requires that the codebase and associated artifacts remain in a perpetually releasable state. This principle invites teams to address issues promptly, maintain a high level of code quality, and vigilantly consider the accumulation of technical debt. Any defects, bugs, or instabilities in the codebase could potentially disrupt an imminent release, leading to costly delays or failures. Teams must adopt practices like continuous integration, automated testing, and ensemble programming to ensure that the codebase remains in a stable, deployable state at all times.
  4. Focus on Robust (Real) Quality Assurance

    In the “Constant State of Ship” paradigm, where the possibility of demand for an immediate release is ever-present, quality assurance cannot be treated as an afterthought. “Constant State of Ship” invites the integration of quality practices throughout the entire development lifecycle, ensuring that quality is baked into the software from inception to deployment.

    While testing plays a role, it is merely one facet of a comprehensive quality assurance strategy. Teams may choose to adopt a holistic approach that emphasises quality as a continuous, pervasive practice woven into every aspect of the development approach.

    This begins with cultivating a culture of quality-driven development, where every team member participates in collective ownership and responsibility for the quality of their work. Practices such as clarity of (quantified a la Gilb) requirements, ensemble programming, peer code reviews, adherence to coding standards, and continuous static code analysis can help identify and mitigate potential issues early in the development cycle.

    Furthermore, “Constant State of Ship” invites teams to embrace principles of iterative and incremental development. By breaking down complex features into smaller, manageable, well-bounded increments, teams can more effectively manage quality risks and ensure that each increment and subsystem meets the required quality criteria before progressing to the next.

    Continuous integration and deployment pipelines play a pivotal role in this quality assurance strategy, enabling teams to continuously validate and verify the software’s functionality, performance, and stability with each incremental change. These pipelines automate the execution of various quality checks, including unit tests, integration tests, and performance tests, providing real-time feedback and enabling teams to address issues promptly.

    However, quality assurance extends beyond mere testing alone. Teams have the opportunity to adopt a holistic approach that encompasses design practices, architectural decisions, and operational readiness. By considering quality implications at every stage of the software development lifecycle, teams can proactively identify and mitigate potential risks, ensuring that the software remains in a releasable state at all times.

    “Constant State of Ship” elevates quality assurance to a core discipline that permeates every aspect of the software development effort. By fostering a culture of quality-driven development and adopting continuous quality practices, teams can attend to the needs of all the Folks That Matter™, with confidence, knowing that their software meets the highest standards of reliability, stability, and performance.

  5. Implement Robust Deployment PipelinesAchieving a “Constant State of Ship” necessitates the implementation of robust deployment pipelines. These pipelines automate the entire process of building, testing, and deploying software changes, ensuring consistency and minimizing the risk of errors. With the ever-present possibility of an imminent release, teams cannot afford manual, error-prone deployment processes. Automated deployment pipelines provide a standardised, repeatable path to production, reducing the likelihood of failed or inconsistent deployments.
  6. Monitor the PipelineRegular smoke testing of the deployment pipeline is crucial in a “Constant State of Ship” mode. This practice helps catch issues early, before they can impact production environments, ensuring the pipeline’s reliability and preventing costly downtime. The possibility of an imminent release amplifies the importance of having a thoroughly validated deployment pipeline. Smoke tests act as a safety net, verifying the integrity of the pipeline and identifying any potential issues that could disrupt a deployment.
  7. Integrate ConstantlyThe “Constant State of Ship” mindset encourages teams to integrate their changes frequently, often multiple times per day. This practice surfaces issues early, reduces merge conflicts, and ensures that the codebase remains in a releasable state, ready for deployment at any given moment. Infrequent integration can lead to divergent codebases, making it harder to identify and resolve conflicts, which could potentially disrupt an imminent release. By integrating frequently, teams can maintain a stable, unified codebase that is always primed for deployment.
  8. Evolve the ArchitectureMaintaining a “Constant State of Ship” over time invites the continuous evolution of the system’s architecture (see also: Reverse Conway). Are teams prepared to refactor and adapt their architectures to accommodate new requirements, technologies, and scaling needs, without compromising the ability to release rapidly and reliably? As products grow and evolve, architectural decisions made early on may become hindrances to continuous deployment. The “Constant State of Ship” principle invites teams to proactively evaluate and evolve their architectures, ensuring that they remain flexible, scalable, and conducive to rapid releases.
  9. Leverage Data EnvironmentsWith the constant possibility of an imminent release, the ability to provision and manage data environments becomes critical. Teams may choose to adopt practices like database versioning, data seeding, and data masking to ensure consistent and reliable testing and deployment across environments, minimising the risk of data-related issues in production. The “Constant State of Ship” mindset invites a robust data management strategy that enables seamless and repeatable deployments, regardless of the data complexities involved.
  10. Mirror Production EnvironmentsTo minimise the risk of issues arising from environmental differences, teams operating in a “Constant State of Ship” mode may choose to ensure that their development, testing, and staging environments closely mirror production environments in terms of configuration, data, and infrastructure. This practice helps identify and address potential issues before they impact the live production system. The possibility of an imminent release heightens the importance of having production-like environments, as any discrepancies could lead to unexpected behavior or failures during deployment.
  11. Codify InfrastructureManually provisioning and configuring infrastructure for each release becomes a significant bottleneck when operating in a “Constant State of Ship” mode. Adopting Infrastructure as Code (IaC) practices, where infrastructure is defined and managed through code, enables teams to provision and tear down environments rapidly and consistently, minimising delays and reducing the risk of configuration drift. The “Constant State of Ship” principle invites a high degree of automation and repeatability in infrastructure management, making IaC a beneficial practice for ensuring rapid, reliable deployments.
  12. Foster Collaborative OwnershipAchieving a “Constant State of Ship” invites a high degree of collaboration and shared ownership among team members. Siloed responsibilities and knowledge become obstacles to rapid delivery. Teams may choose to adopt practices that promote collective code ownership, cross-functional collaboration, and shared understanding of the codebase and delivery processes. The “Constant State of Ship” mindset invites a culture of collective responsibility, where all team members are empowered to contribute to and understand the entire delivery process, enabling seamless and efficient releases.
  13. Continuous ImprovementOperating in a “Constant State of Ship” mode exposes inefficiencies and bottlenecks in the delivery pipeline and processes with uncompromising clarity. Teams may choose to embrace a culture of continuous improvement, regularly reviewing their practices, identifying areas for optimisation, and implementing changes to enhance their ability to deliver value rapidly and reliably. The constant presence of imminent releases acts as a driving force for continuous improvement, encouraging teams to continuously refine their processes, tools, and practices to achieve higher levels of velocity and quality. FlowChain was designed to systematise this very purpose.

The Visionary “Javelin” Approach

The “Javelin” approach (initally named “Jerid”) pioneered by me and my teams at Familiar from 1996 onward, was truly ahead of its time, recognising the transformative power of the “Constant State of Ship” mindset. By enshrining this principle as a cornerstone from its inception, “Javelin” has paved the way for the modern continuous deployment practices that have since become poised to gain industry standard status. This pioneering approach, along with FlowChain and e.g. Prod•gnosis, Flow•gnosis, Product Aikido, etc. exemplifies the spirit of continuous improvement intrinsic to the “Constant State of Ship” principle, ensuring its enduring relevance and impact.

Deep Cultural Implications

Reshaping the Culture and Mindset

Adopting the “Constant State of Ship” principle suggests a profound transformation that extends way beyond technical practices and processes – it hints at a seismic shift in the culture and mindset of software development teams and their parent organisations. This metamorphosis permeates every aspect of the organisation, reshaping shared assumptions, beliefs, and ways of working. However, navigating such a profound cultural shift can be a daunting challenge, often met with resistance and inertia.

This is where the discipline of organisational psychotherapy plays a pivotal role. By applying principles from psychotherapy, sociology, and group dynamics, organisational psychotherapy facilitates teams’ cultural and mindset shifts required to embrace the “Constant State of Ship” paradigm smoothly and effectively.

A Culture of Ownership and Accountability through Empowerment

The “Constant State of Ship” mindset fosters a culture of collective ownership and accountability. Organisational psychotherapy techniques, such as participative decision-making and fellowship, empower team members to take responsibility for the quality, stability, and deployability of the codebase and overall product. This sense of empowerment cultivates a culture of shared ownership, where individuals proactively address issues, collaborate across boundaries, and collectively strive for continuous improvement.

Embracing Transparency and Trust

Maintaining a “Constant State of Ship” requires a high degree of transparency and trust among team members. Organisational psychotherapy practices, such as surfacing shared assumptions and beliefs, encourage open communication and facilitate the identification of problems and risks early. By fostering an atmosphere where team members feel comfortable expressing concerns, sharing mistakes, and seeking help, a culture of transparency and trust emerges, enabling teams to collectively address challenges and ensure the software remains in a releasable state.

Prioritising Continuous Learning

The “Constant State of Ship” principle instills a mindset of continuous learning and improvement. With each release, teams gain valuable insights into their processes, tools, and practices. Embracing new shared assumptions becomes essential, as teams must continuously refine and adapt their approaches based on feedback and lessons learned. This culture of continuous learning fosters an environment of experimentation, where failures are embraced as opportunities for growth, and success is measured by the ability to deliver value rapidly and reliably.

Aligning Towards a Common Goal

Ultimately, the “Constant State of Ship” principle unifies teams around a common goal: meeting the needs of all the Folks That Matter™ with unparalleled speed and reliability. This shared mission transcends individual roles, responsibilities, and technical disciplines. It creates a sense of collective purpose, where every team member’s contribution, regardless of their specific function, is valued and recognised as essential to achieving this overarching objective.

By leveraging organisational psychotherapy techniques, organisations can accelerate and streamline the cultural and mindset shifts required to embrace the “Constant State of Ship” paradigm. This discipline not only makes the transition quicker and easier but also more cost-effective, as it addresses the root causes of resistance and inertia, facilitating a smoother and more sustainable transformation.

By reshaping the culture and mindset of software development teams, the “Constant State of Ship” principle cultivates an environment conducive to continuous deployment success. It fosters a sense of collective ownership, transparency, continuous learning, and shared purpose – traits that are indispensable in today’s rapidly evolving software landscape.

Embracing the Future

When the ability to swiftly adapt and innovate is paramount, the “Constant State of Ship” principle emerges as a beacon, guiding software development teams towards a future of quiet competence and competitiveness. By embracing this mindset, as exemplified by the visionary “Javelin” approach, teams can unlock the power to attend to folks’ needs with unprecedented speed, reliability, and quality – solidifying their organisation’s position as industry leaders in the software development arena.

Effective Regulation

Within business organisations, the discourse around effective regulation often becomes polarised, oscillating between the extremes of rigid compliance and laissez-faire approaches. Compliance, typically understood as strict adherence to rules and procedures, can foster an environment of micromanagement that stifles innovation. On the other hand, a laissez-faire attitude, characterised by minimal oversight, can lead to chaos, unethical practices, and a lack of accountability.

However, true effective regulation does not reside on this spectrum between micromanagement and laissez-faire. Rather, it represents a fundamentally distinct “third way” – a holistic approach that transcends the limitations of these two extremes, fostering a culture of responsibility, continuous improvement, creativity, and autonomy.

Redefining Regulation as Principled Action

The third way redefines regulation not as a checklist of rules to be blindly followed, but as a commitment to upholding core ethical principles and standards aligned with the organisation’s mission. This paradigm shift requires:

  1. Clearly articulating the organisation’s shared assumptions and beliefs, including its guiding purpose, principles and values.
  2. Engaging employees in embodying these principles through e.g. dialogue.
  3. Revising policies to reinforce the principles, not merely enforce rules.
  4. Nurturing critical thinking over box-ticking compliance.

By empowering individuals to internalize and live these principles, a sense of ownership and genuine accountability is cultivated.

Organizational Psychotherapy: Fostering Shared Responsibility

Central to the third way is a culture where every member is invested in upholding ethical practices and sustainable growth. Organisational psychotherapy can be a powerful tool in nurturing this culture by:

  1. Facilitating open dialogues to surface underlying shared attitudes and beliefs.
  2. Identifying systemic issues impacting trust and accountability.
  3. Developing tailored interventions to address dysfunctional group dynamics.
  4. Providing a safe space for honest feedback and conflict resolution.
  5. Make attending to folks’ needs a central plank.

Through this therapeutic process, organisations can heal dysfunctional patterns, rebuild trust, and instill a genuine sense of shared responsibility that transcends the compliance-laissez-faire dichotomy.

Continuous Learning: An Organisational Ethos

The third way recognises that effective regulation is an ever-evolving process, requiring a steadfast commitment to continuous learning and improvement as an organisational ethos:

  1. Encouraging the continuous development of improved abilities and intelligence, by reframing failures as learning opportunities.
  2. Implementing substantive, regular dialogue on emerging best practices.
  3. Facilitating cross-functional knowledge sharing and mentoring.
  4. Gathering feedback from all the Folks That Matter™ to identify areas for development.

By making attending to folks’ needs a core value, organisations can remain agile, adaptive, and always improving their approach to regulation and governance.

Ethical Leadership and Collaboration

Effective regulation invites exemplars who embody the principles the organisation aims to instill, proselytising ethical conduct through their actions and decisions. Organisations can champion the third way by:

  1. Exemplifying ethical behaviour in all things.
  2. Openly acknowledging mistakes and pivoting course when needed.
  3. Prioritising ethical decision-making in all communication and conduct.
  4. Actively listening and incorporating feedback from across the organisation.
  5. Fostering cross-functional collaboration on key initiatives.

This ethical behaviour, amplified by collaboration, inspires others to genuinely embrace the third way of effective regulation.

Summary

The third way represents a distinct approach that transcends the micromanagement-laissez-faire spectrum, offering a holistic, principled path centered on shared responsibility, continuous learning, and collaborative ethical leadership. By leveraging tools like organisational psychotherapy, mindset shifts, and genuine organisational commitment, businesses can cultivate an environment that upholds ethical conduct, innovation, sustainable growth, and the highest standards of accountability and integrity.

The Seductive Allure of Command-and-Control

Defining Command-and-Control

In the context of business organisations, command-and-control refers to a top-down, highly centralised management approach. It is characterised by strict hierarchies, rigid processes and procedures, and a focus on enforcing compliance through rules and policies set by senior management.

Under a command-and-control model, strategy and decision-making flow vertically downwards, from the top, with managers and executives dictating priorities and objectives that must be executed down the chain of command. Employees have little autonomy or latitude for questioning directives from above.

The Lure of Execution

We all want to get things done effectively and efficiently. As humans, there’s a deep satisfaction in seeing our efforts translated into concrete results. Whether it’s getting that big project shipped, launching a new product, or just ticking items off our personal to-do list, achievement feels good.

However, in many organisations, the primacy placed on “getting things to work” can blind us to deeper systemic forces at play. All too often, the siren song of efficiency and execution drowns out more fundamental questions about whether we’re even working on the right things in the first place (a.k.a. effectiveness).

Institutional Inertia

The truth is, large organisations are complex systems governed as much by unspoken assumptions, ingrained beliefs, and social incentives as any official policy or executive mandate. The very rubrics we use to measure success – be it revenue targets, user growth, or other metrics – emerge from a particular culturally-entrenched worldview.

Within this context, a command-and-control narrative reigns supreme. We optimise for top-down directives, vertical hierarchies, and centralised decision-making. Goals get cascaded down, while accountability and compliance permeate back up the chain. Efficiency and order and managers’ wellbeing are prioritised above all else.

The system effectively hard-wires this command-and-control mentality. Being a “team player” often means deferring to established processes, not rocking the boat, and falling in line with conventional thinking. Those who push back or challenge assumptions are frequently sidelined as “not pragmatic” or “not working towards the same priorities.”

The Costs of Control

Things get done, to be sure. But at what cost? A singular focus on execution often means unquestioningly working towards the wrong objectives in the first place. It breeds an insular, institutionalised mindset that is exquisitely efficient…at preserving the status quo.

Perhaps more importantly, a command-and-control culture discourages the very creativity, critical thinking, and experimentation needed for an organisation to truly adapt and evolve over time. After all, what incentive does anyone have to question the deepest assumptions that underlie day-to-day work when doing so could threaten their standing, compensation, and career prospects?

Catalysing Change

True change requires creating space for fundamentally rethinking and reimagining what an organisation is optimising for in the first place. It means giving voice to diverse perspectives, nurturing a willingness to exploit fleeting opportunities and take calculated risks, and embracing a degree of productive failure.

Dismantling existing systems is hard, uncomfortable work. Doubly so for dismantling entrenched assumptions and beliefs. It inevitably encounters inertia and opposition from those who are vested in maintaining the current order. But simply getting things done is not enough – we must wrestle with whether we’re even pulling the right levers to begin with.

To catalyse genuine innovation and transformation, we might choose to move beyond blind adherence to the siren song of pure execution. We must create the conditions for all voices to be heard, for first principles to be questioned, and for fundamentally new visions and possibilities to emerge. Only then can we achieve meaningful change.

Further Reading

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

The Power of Beliefs

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.”

That Weird Feeling When Someone Attends to Your Needs

There is often subtle unease or vulnerability when another person identifies and attends to your emotional or practical needs before you ask. Even as they are attending to you, why might you feel strangely rattled or intruded upon by having your underlying feelings anticipated and met in this way?

Expectations

Part of the strangeness seems to be linked to our expectations around emotional autonomy in relationships. It might be because we assume we must self-manage feelings, not burden others unprompted, and disguise any weakness. So when someone sees through our façades and reaches out with support, it can feel jarringly unfamiliar. There is awkwardness adjusting to a new way of relating where masking distress is no longer accepted or expected.

Self-Image

Additionally, admitting needs may endanger our own resourcefulness or positive self-image. To remain strong and unaffected is easier than acknowledging where we genuinely need empathy or assistance. Conceding our emotional gaps confronts us with difficult realities about ourselves. Having someone respond caringly can dredge up shame before that nurturing registers as comfort. It takes time to overcome our reflexive impulse to deny needs that contradict the identities we aspire to.

Psychological Safety

Beneath the discomfort may also lurk trust issues around vulnerability. Emotions expose our innermost selves. Letting someone in to perceive and attend to that sensitive dimension means lowering barriers and giving up some degree of control. Psychologically, it signals dependence on their benevolence versus total self-sufficiency. With support inevitably comes some loss of authority over how we might want to be perceived. Even caring assistance can seem invasive before safety takes root.

While emotional caretaking intends to heal and bond, the path to welcoming nurture over isolation is not always smooth or instant. The vulnerability of relinquishing façades, acknowledging needs, and opening up to help all disrupt our status quo. By naming these sources of weirdness, perhaps the tensions around receiving compassionate support become less of a bewildering hurdle. Gradually, we learn to receive grace and attend to one another’s emotions without threatening inner resolve or identity. The discomfort slowly fades as emotional interdependence replaces sole self-reliance.

Summary

In essence, the discomfort we may feel when someone attends to our emotional needs often stems from unfamiliarity with true interdependence, unwillingness to show vulnerability, and a cultural overemphasis on extreme self-reliance. We expect to conceal any weakness, deny needing support, and handle distress alone without imposing on others. So when another person perceptively senses unvoiced feelings and reaches out to care for our inner experiences, it can feel weirdly intrusive. Even compassionate emotional caretaking jars notions of autonomy and challenges our reflexes to hide perceived flaws or shortcomings behind façade of capability. Yet suppressing needs creates isolation, and makes it so much more likely our needs will go unmet. Perhaps by better understanding the common strangeness behind receiving others’ attention, we can grow into truer communities where attending to one another’s unspoken needs and hopes is simply what love requires.

Probing the Collective Mind: Organisational Psychotherapy

Organisations, like human beings, have a complex psyche. This collective psyche transcends individual perceptions, emerging from the interactions of members. Just as our minds have conscious and subconscious parts, so too organisations develop collective ways of perceiving, operating and relating that often remain unspoken or unobserved.

Identifying and settling tensions within the organisational psyche can facilitate growth, resilience and better commitment to purpose – the domain of organisational psychotherapy. I work as a consultant to companies, charities, public sector bodies and community groups to evaluate and nurture organisational mental health by helping them surface and reflect on shared consciousness.

Some key questions we explore through Organisational Psychotherapy:

  • What visible and invisible narratives shape this organisation’s culture and choices?
  • Where might discordant group emotions or motivations cause strain?
  • How equitable and inclusive are existing customs and systems? Do they fully utilise organisational diversity?
  • How do past shared experiences or traumas continue to affect organisational patterns?

I employ methods including extensive stakeholder interviews, observation of gatherings and operations, surveys, communication pattern analysis and existing research on the organisation.

I then provide perspective on the organisational psyche identified through discovery – covering areas from conflicts between principles and practices to the impact of founder stories on current aims. My observations seek to help organisations consciously evolve their psyche for mutually positive outcomes rather than reacting only to surface performance indicators.

In developing insights into organisational psyche, I incorporate models like Edgar Schein’s levels of organisational culture. This identifies artifacts, espoused beliefs, and shared underlying assumptions that together form the collective mindset. By probing beyond visible structures into deeper assumptions groups hold about themselves and wider reality, organisational psychotherapy can advocate for purposeful evolution rather than being locked in to habitual patterns or beliefs.

Just as personal therapy provides individuals support for self-knowledge and growth, organisational psychotherapy offers this at the collective level. My calling is helping groups access healthy psyches tuned to members’ shared humanity, their collective needs, and the greater social good.

Questioning Workplace Culture

As we explore new ways to improve how organisations function, some suggest looking at the concept of a “collective psyche.” This means recognising shared ways of thinking and acting that develop in work cultures over time.

Do you see evidence that workgroups adopt common outlooks and responses based on past experiences? Have you noticed certain “vibes” or unwritten rules shaping your workplaces? Things like what gets talked about or whose voices carry weight? If so, you may have witnessed signs of the organisational psyche.

My experience shows that often these cultural patterns go unexplored, even as they limit a company’s success or employee happiness. There may be ingrained ways of excluding people or communicating that uphold old biases. Or deep wounds from events such as layoffs that linger silently for years, killing morale and trust.

Unpacking this organisational “baggage” requires openly examining the collective psyche – facilitating honest reflections on workplace culture by those within it. This can uncover why teams act in contradictory or counterproductive ways despite stated values or policies.

While some dispute whether organisations have a “mind” beyond individuals, I frequently see signs that they do develop shared ways of thinking, passed down over the years. These may include unspoken rules about conflict, success measures valued over ethics, or tendencies to privilege certain groups’ ideas.

My message is simply that by talking openly about these cultural patterns as part of improving workplaces, companies have much to gain. There are always more positive, equitable ways for employees to coexist and collaborate. Organisations can choose to commit to ongoing self-reflection and evolution to make this a reality.

So may I invite you to notice group dynamics in your workplace. And consider advocating for culture introspection aimed at growth rather than judgment or blame. There is promise in recognising companies as having complex collective psyches inviting continuous care beyond restructuring initiatives. Perhaps it takes a village* to raise an organisation, too.

Note:

“Perhaps it takes a village to raise an organisation too” – is a play on the phrase “it takes a village to raise a child.” The idea behind that phrase is that no parent can single-handedly provide everything a child needs to mature into a well-adjusted adult. Successful upbringing requires an entire supportive community or “village” of people – parents, teachers, mentors, friends etc. – continually nurturing the child’s development.

Here we extend this metaphor to apply to organisations and workplaces as well. Just as a child needs whole communities of support, so too may organisations require more holistic “villages” iaround them to sustain positive cultural change. Relying solely on the efforts of leaders or executives is unlikely to transform entrenched workplace dynamics on its own.

True shifts in organisational psyche need to involve people at all levels engaging in self-analysis and reflection, speaking up on needed changes, building trust, and continuously evolving interpersonal habits and norms. It can’t and won’t be driven through top-down mandates or policy tweaks. The entire workplace community, including customers, partners etc., can become a village dedicated to positive organisational development, health and maturation over time.

In essence, systemic transformation requires engagement and ownership across an entire “village”. Just as healthy childhood development is a communal process, so too may be nurturing organisational culture. It is ambitious and complex work demanding community-driven change rather than quick fixes. But this holistic, village-focused approach holds real promise for creating more conscious, equitable and purpose-driven workplace cultures.

So in summary, I aim to invite readers towards this more collective understanding of organisational development – recognising it as long-term cultural evolution requiring supportive communities, not temporary quick fixes. The organisational village, so to speak, is instrumental in liberating the organisational psyche to realise its full potential.

 

You May Find This Disconcerting

Organisational psychotherapists have an unusual approach to helping people that some might find quite disconcerting. When advising on jobs, relationships, or life decisions, we don’t just take requests at face value. Instead, we dig deeper using the Antimatter Principle.

The goal is to aid people in surfacing the hidden motivations underlying what people say they need. We often ask “Why?” to expose emotional needs and deeper values driving behaviour. And admittedly this persistent probing makes many uncomfortable, at least initially.

We find ourselves constantly asking “Why?” Not just once, but repetitively, until our clients get to the heart of the matter. We’re looking for folks to understand their underlying motivations – the fundamental emotional, psychological or values-based drivers behind their stated wants and requests.

For example, say someone asks for advice on finding a new job with better pay. We could just look at open positions and salaries, making recommendations based on those factors.

But instead, we might ask “Why?” in an attempt to surface their assumptyions and beliefs, and to help them uncover their motivations.

Perhaps they want higher pay because they feel unappreciated in their work. Maybe it’s about financing kids’ education. Or it could be dreaming of a new house. There may even be a desire to boost self-esteem or a sense of self-worth tied to income level.

These motivations are powerful drivers of the stated need. Ttruly helping people requires understanding those underlying emotional needs and values behind the surface-level request.

So we might continue asking “Why?” until their motivation reveals itself to them. With that understanding, we’re able to reflect on jobs or other solutions that may work far better than just chasing higher pay. We uncover approaches that align with their deepest needs, not just the transactional request.

Clearly, repetitively asking “Why?” in attempts to unearth hidden motivations is an unusual approach. And yes, some may understandably find this probing style uncomfortable or disconcerting at first. (Clean Language can help)

But time and again I’ve seen the aha moments this approach delivers as people’s motivations come to the surface. And it’s helped friends, family and clients find outcomes better tailored to their previously unstated and unconcious needs.

That ability to uncover and serve people’s underlying emotional drivers we call the Antimatter Principle. These hidden motivations power much of human behavior. Bringing them to the surface releases energy capable of transforming outcomes in positive ways.

So if in working with an organisational psychotherapist you ever feel we’re responding oddly or asking too many follow-up “Why’s,” this principle likely explains it. We simply believe that to truly help people, we must do the work of supporting the discovery of their deeper motivations and needs.

A Message For the Media

News of Organisational Psychotherapy will captivate your audience and sell headlines. The work reveals innovative ways to strengthen communities, unlock human potential, and pave the path to a brighter future. By covering this topic, you provide your readers with hope and help spread ideas that could change millions of lives for the better. This research offers clear guidance to improve workplaces, and society at large too.

Your reporting and analysis will empower people to implement the findings in their own lives and communities. Be at the forefront of spotlighting a roadmap to prosperity and social cohesion. Set the agenda for constructive change by making this field accessible through your platform. The public needs to know how they can create positive change. When people are informed and inspired, they will rise up and put these ideas into action.

This is your opportunity to tell an uplifting story that sticks with readers and spurs real impact.

Time Yet for Organisational Psychotherapy?

The Software Crisis is but a Symptom

The “software crisis” plaguing the tech industry for more that 50 years reflects a broader crisis spanning business, society, and our species. At its core is our inability as a species to fully grasp and manage rapidly change and wicked problems, both. But this crisis manifests in different ways across multiple levels of human endeavours.

The Business Crisis Begets the Software Crisis

In business, intense competition, shifting customer demands, changing social expectations, and disruption make consistent success an elusive goal. In society, we face polarisation, inequality, and loss of social cohesion. As a species, our advanced civilisation has exceeded our innate cognitive capacities. We are overwhelmed by the world we’ve created.

The Societal Crisis Begets the Business Crisis

The software crisis is just a symptom of crises in business, society, and our human systems as a whole. To truly address it, solutions are needed at each level. Organisational psychotherapy can help provide a framework for shared reflection and treatment.

Business operates within a broader social context beset by polarisation, inequality, and eroding social cohesion. Society’s challenges become business’s challenges.

When society tacitly promotes individual gain over collective well-being, so does business. When civil discourse and trust decline, companies struggle to collaborate. When opportunity is not distributed broadly, markets suffer.

Business could help lead society forward. But first, society must create conditions where ethics and human dignity come before efficiency and profits. By reflecting society’s imbalances, business contributes to the social crisis.

Organisational Psychotherapy Offers a Way Forward

Just as individual psychotherapy helps people gain self-understanding to heal, organisational psychotherapy facilitates collective self-reflection to foster change in groups, companies, systems, societies and the species. It surfaces the dysfunctional patterns that maintain the status quo.

Applications

Applied to the software crisis, organisational psychotherapy invites examination of the beliefs, behaviors, and power dynamics across the tech industry that contribute to the many and perrenial chronic failures. It enables new understandings and behaviors to emerge.

Similarly, organisational psychotherapy addresses dysfunctional aspects of business culture and society that exacerbate our challenges and frustrates our needs. It helps groups align around shared purpose, and adapt.

Ultimately, organisational psychotherapy a.k.a. collective psychotherapy is about creating the conditions for species learning. As we confront crises across business, society, and our species, we might benefit from the capacity for honest inquiry, collective problem-solving, and continuous learning. Organisational psychotherapy can guide that evolutionary process. The software crisis and beyond provide an opportunity for our organisations, businesses, societies, and species to increase our enlightenment. But we must be willing to courageously examine ourselves along the way.

Outdated Beliefs Get in the Way

Many organisations today seem stuck in a pattern of missed opportunities and mediocrity. They work hard, but never achieve their potential for dignity, joy, and shared prosperity.

The key reason is that most organisations cling to outdated assumptions and beliefs about the world of work – assumptions and beliefs that hold them back. Their mental models of how business works are based on premises that were, maybe, relevant decades ago but have long since become obsolete.

For example, a common outdated belief is that decision quality is higher when decisions flow through strict organisational hierarchies, when flatter structures often foster faster innovation and improved decison quality, both.

Another toxic belief is that loyal, long-term employees are an organisation’s greatest asset. But in the modern workplace, it’s the relationships between employees that promotes prosperity and fresh thinking.

The world moves fast today. What made an organisation dominant 10 or even 5 years ago no longer guarantees success. The leaders and companies that dump outdated assumptions and beliefs about how things work are positioned to achieve their aspirations.

By continually questioning their premises and mental models, organisations can recognise where staus quo wisdom no longer applies. They can pivot rapidly rather than being mired in he past. And they can pursue innovative opportunities for atteding to folks’ needs, instead of sticking to familiar but lame and dysfuntional practices.

Shedding outdated beliefs at all levels is the only reliable way for an organisation to keep achieving extraordinary results in a world of accelerating change. The companies that realise this will be poised for progress in the years ahead.

Should We Adopt Agile?

Following on from my previous post concerning surfacing and reflecting on shared assumptions and beliefs about work, here are ten reflective questions for an executive considering flexible software development approaches:

  1. What are our priorities – speed, adaptability, innovation, quality, predictability? How should our processes align*?
  2. Do our teams thrive with more autonomy, or require structure from leadership?
  3. Are staff skills best leveraged through specialisation or multi-skilling and cross-functional collaboration?
  4. How much do we value rapid delivery versus long-term planning and building of long-term capabilities?
  5. Can our culture accept constant change versus needing firm commitments to e.g. delivery dates, feature sets, etc?
  6. Is our leadership comfortable ceding some control over how work gets done?
  7. Do our metrics reflect outcomes, outputs, value delivered, or needs met? Should we measure differently?
  8. Is transparency into work progress more valuable than formal milestones?
  9. Do we believe in Minimal Viable Products over Big Design Up Front?
  10. Are we open to new ideas or convinced our current ways of working work best? How much research have we done?

*I.E. What approach will best ensure our organisation’s processes, systems and structures are optimally configured to support our priorities and goals, around both software development and our wider business?

 

Note: Many more than these ten questions could be relevant to the headline topic. I encourage and invite you to try asking your favourite chatbot for more questions to consider.

Also note: Given the preponderance of proselytisation for the Agile approach currently found on the Internet, I would not recommend asking your chatbot “Should we adopt Agile?” directly. Unbiased and considered advice will NOT be forthcoming.

What Do You Believe?

[Tl;Dr Ten questions for the busy executive to prompt self-examination]

By way of illustrating the intersection between current AI and Organisational Psychotherapy, here are ten AI-suggested* reflective questions for the business executive related to collective assumptions and beliefs about work:

  1. What core assumptions do we hold about what motivates employees? How might those impact our leadership style and company culture?
  2. Do we believe work should primarily be about productivity or fulfillment? How does that shape our policies around work-life balance?
  3. What are our beliefs around hierarchy and top-down leadership? Could a more collaborative model unlock more creativity?
  4. Are we open to re-examining traditional perspectives on things like remote work, flexible hours, or results-focused goals?
  5. Do we view employees as expendable assets or vital stakeholders? How does that perspective influence retention and turnover?
  6. Do we believe work requires oversight and control to be done well, or that autonomy drives better outcomes?
  7. Do we assume all employees are motivated by the same things like money or status? How could we better incorporate individual motivators?
  8. Are we clinging to any outdated models of what a successful workplace looks like? What new data or examples contradict our assumptions?
  9. Do we recognise generational differences in perspectives around things like work ethic, loyalty, and fulfillment?
  10. Are any of our beliefs around hard work or merit holding back disadvantaged groups? What biases might we recognise and rethink?

With help from any of the now numerous AI chatbots*, the busy executive can easily and quickly generate such questions to assist in e.g. collective self-reflection.

*The above list was generated via ClaudeAI

The Urge to Keep People Busy (And Why It Doesn’t Work)

In many workplaces, there is an underlying pressure to keep employees constantly busy. The thinking goes that if people have any downtime at work, that time is wasted and money is being left on the table. This leads managers and leaders to pile more and more work onto employees’ plates in an effort to extract maximum productivity. However, this approach is actually counterproductive.

Software companies tend to be prime examples of this misguided busywork culture. There is often intense pressure to continually release new features and upgrades to products. The development team is expected to churn out a steady stream of product increments to show that they are adding value. However, much of this activity becomes useless busywork after a certain point.

Queueing Theory 101

This phenomenon can be explained by queueing theory – the mathematical study of waiting in lines. As Tom DeMarco wrote in “Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency”, workers and tasks in a company form a queueing system. If all workers are 100% utilised, queues grow infinitely long and lead times stretch without bound. Companies need slack resources to absorb variation. Trying to keep everyone 100% busy all the time is thus self-defeating.

The Human Dimension

Studies have also shown that human cognitive resources are finite. We all have a limited capacity for productive focus and good decision making each day. Piling on more and more tasks leaves less mental energy for each task. Workers become ineffective at judging what activities are truly important versus those just designed to fill time. The quality of output suffers even as teams scramble to check more boxes.

Additionally, constant busyness leads to burnout over the long run. Workers never get the chance to recharge because they jump from one urgent task to the next. The resultant stress and exhaustion eventually sap motivation and creativity.

Alternative: Focus

Instead of keeping people busy for the sake of looking productive, organisations might choose to create focus. When clear priorities are set, teams have the space to deeply engage with tasks that really further core goals and objectives. Quality output that moves the needle earns more than quantity of output or hours logged.

Rather than endlessly generating and implementing new product features, software teams can choose to carefully consider business objectives and what features will have the biggest impact. Saying “no” to nonessential work is often healthier than taking it on just to keep programmers coding around the clock. Less can truly be more when it comes to productive and innovative software teams.

The Benefits of Downtime

In knowledge economy workplaces, ongoing learning uplifts both individual and organisational success. However, prioritising constant busyness leaves little room for employees to actively absorb new information or develop additional skills. Building protected time for learning into work schedules is thus hugely beneficial compared to attempting to eliminate all downtime.

Sufficient breathing room between intensive assignments provides cognitive space for individuals to deeply internalize and contextualise what they have already worked on. Lessons sink in better when folks have moments to pause and reflect on how the dots connect. Such periodic integration of experiences builds flexible knowledge that better transfers to future contexts.

Dedicated downtime also makes room for individuals to proactively seek out cutting edge knowledge in their domain. Workers use the time to read journals, take online courses, attend conferences, engage mentors and collaborate with peers in the field. Through these networks, they rapidly update understanding and hone best practices awareness. Organisations thrive when individuals return to apply these learnings to internal initiatives.

Importantly,downtime allows employees to pursue self-directed skill building aligned to their own person al and career needs, not just immediate organisational requirements. When individuals direct their own learning, intrinsic motivations energise mastery far beyond what imposed trainings can deliver. Carving space for self-improvement helps attract and retain top talent as well.

Of course, workers also benefit from downtime that simply allows their brains to recharge after intense problem solving. Neural networks expend significant energy forming new connections demanded by complex tasks. Regular periods of low external stimuli are crucial for restoring the actual physical infrastructure enabling learning in the first place.

Rather than something to eliminate through added busywork, downtime facilitates ongoing renewal that powers future performance. Knowledge workers’ most precious asset is the human capacity for rapidly acquiring and applying new understanding. Protecting time and space for learning may thus provide the highest organizational return on investment of any activity, busy or not.

Finally, downtime provides the space to surface and reflect on both personal and shared assumptions and beliefs about the way the work works (i.e. the opportunity for organisational psychotherapy, whether facilitated or self-directed).

Summary

The impulse to minimise any workspace downtime is understandable but misplaced. Workers and companies both thrive when space is made for deliberate thinking, creative ideation, restoration, reflection, and collaboration. The busiest person in the office is rarely the most productive or effective. Organisations migh better choose to create focus for employees rather than frenetic stimulation. Whether explained through queueing theory or basic human psychology, purposeful work will always trump mindless busyness.

Individual Mindsets vs. Collective Mindsets

We often talk about the need for individuals to change their mindsets – their assumptions, beliefs, and attitudes – in order to create positive change. But as human beings, we don’t exist in isolation. As the saying goes, we are social animals, shaped by the groups and cultures we are part of. So perhaps we might choose rather to shift more of our focus to addressing collective mindsets rather than just individual ones.

Schein On

Organisational psychologist and author Edgar Schein argues that culture stems from a group’s shared basic assumptions and beliefs. These collective ways of thinking and being manifest in organisational policies, processes and behaviors. If the culture has dysfunctional aspects, it perpetuates dysfunction. Merely helping individials adopt more productive mindsets without addressing the surrounding culture is an uphill battle.

For Example

Take a common example – trying to promote more innovative thinking in a risk-averse bureaucratic workplace. Telling individuals to “be more innovative” often backfires. When people attempt new ways of doing things, they get pushback for not following protocols. and Interesting ideas get shut down quickly by naysayers. There are no systems or incentives to support innovation. So you end up with frustrated employees, not actual innovation.

Organisational Psychotherapy To The Rescue

In contrast, #OrganisationalPsychotherapy seeks to invite folks into uncovering and transforming collective assumptions and beliefs – the mental models that shape systems and culture. By facilitating more awareness of existing culture and defining desired culture, interventions get better traction. Collective mindsets shift to be more supportive of stated goals, like innovation, making it easier for individuals to adopt those productive mindsets as well.

Summary

The key insight is that individual mindsets are downstream of collective mindsets. Without addressing dysfunctional aspects of culture and systems, individual change efforts face resistence from the surrounding ecosystem. This highlights the need to focus on group mindset factors first and foremost. Of course, individuals still have agency in driving any kind of change. But we’d do well to spend more time examining and evolving the shared beliefs and assumptions on which any organisation is built. For cultural transformation, that’s likely the most high-leverage point of intervention.

Postscript – Donalla Meadows’ Twelve Points of Leverage

In her influential article “Leverage Points: Places to Intervene in a System,” systems thinker Donella Meadows articulated 12 places within complex systems where a small shift can lead to fundamental changes in the system as a whole. Her framework offers guidance on how to approach system-level transformation, whether in organizations, societies, or beyond.

Meadows proposes 12 leverage points ranked in order of effectiveness, with the most high-leverage interventions at the top. The higher the leverage point, the easier it is to make major improvements to the system with minimal effort. Her list starts with more superficial leverage points around details like subsidies and incentives, then moves deeper into the fundamental goals, paradigms, and transcending purpose that underpin why a system exists in the first place.

The most powerful leverage points require a deeper, more courageous transformation. But they allow us to redefine the very reason a given system exists, enabling revolutionary redesign rather than incremental improvements. Meadows urges change agents to have the wisdom and patience to address the deeper paradigms, values, and purpose driving systemic behavior. As she concludes, “People who have managed to intervene in systems at the level of paradigm have hit a leverage point that totally transforms systems.”

In examining Meadows’ hierarchy of leverage points, we gain an appreciation for the depth of change required for true systems transformation. It inspires a more radical reimagining of what’s possible. The framework continues to provide guidance to sustainability leaders and organizational change agents seeking to effect large-scale improvements in business, government, technology, education and beyond. In this critical era facing many complex, planetary-scale challenges, Meadows’ words ring truer than ever as we work to create fundamental shifts towards more just, resilient and life-affirming systems.

Pronouncing “Quintessence”

If you’ve come across the word “quintessence” while reading English texts, you may have wondered about the correct pronunciation and actual meaning of this rather unusual word. As a non-native speaker, the pronunciation can seem tricky at first. Read on for a quick guide on how to say “quintessence” properly and what this interesting word signifies.

Breaking Down the Pronunciation

Quintessence is pronounced “kwin-tess-uhns” in British English. Let’s look at each syllable:

“Quin”: The “qu” sounds like a hard “c” or “k”, as in words like “queen” or “quick”. Say the “kwin” syllable.

“Tes”: This syllable rhymes with words like “test” or “best”. Say “tess”.

“Ence”: Here the “e” becomes a schwa sound – the neutral “uh”. Think words like “enhance”, and say the schwa “uh” sound.

Put together, the full pronunciation is: kwin-tess-uhns. The stress is on the second syllable, “tess”. Say the word a few times out loud, stressing that middle portion, to get comfortable with the pronunciation.

Alternatively, you might choose to pronounce it “quint” + essence”.

The Meaning of Quintessence

So now that you know how to say it properly in your best spoken English accent, what does “quintessence” actually mean? Quintessence signifies the purest, most perfect or concentrated essence of something. For example, you could describe a breathtaking landscape as “the quintessence of natural beauty”. Or for an organisation that has everything sorted, all its ducks lined up, and firing on all cylinders, we might choose to call that a “Quintessential organisation”.

Etymology

The word originates from medieval philosophy, derived from the Latin “quinta essentia”, meaning the “fifth essence“. This referred to what was thought to be the pure substance making up heavenly bodies, beyond the four basic earthly elements of fire, water, air and earth.

In Modern Physics

In modern physics, “quintessence” refers to a hypothetical form of dark energy postulated to explain the observed acceleration of the expansion of the universe. Based on astronomical observations, scientists have determined that some unknown form of energy, termed “dark energy,” makes up about 68% of all the energy in the observable universe. This mysterious dark energy is causing the expansion of the universe to speed up over time. To explain this phenomenon, physicists have proposed that quintessence – an extremely light and slowly-varying scalar field – may account for the observed behavior of dark energy and the accelerating cosmic expansion. Quintessence would have negative pressure, offsetting normal attractive gravity and driving galaxies apart at an ever-faster rate. If confirmed, the quintessence scalar field would be the “fifth element” driving cosmology, alongside ordinary and dark matter. Though still unproven, quintessence remains a leading contender for explaining one of the biggest mysteries in modern physics and astronomy. Further experiments and astrophysical observations may shed more light on this proposed fifth essence permeating the universe.

Summary

So next time you come across this unique word, you’ll know the proper English pronunciation and understand its meaning related to a pure, perfect embodiment of something. With your new knowledge, use “quintessence” to impress your English friends and teachers!

Further Reading

Marshall, R.W. (2021). Quintessence – An acme for software development organisations. https://leanpub.com/quintessence