Archive

Actionable Insights

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.

The Personal Upside of Business Improvement

[Or – what’s all this business improvement malarkey, and what’s in it for me?]

Waning Interest Post-Pandemic

As we’ve learned to live with COVID, much has changed in how businesses operate. Remote work is now the norm rather than the exception. Supply chains have been disrupted. Customer behaviours have shifted significantly. In the midst of this turbulence, it feels like interest in business improvement initiatives has waned and taken a backseat.

Survival Mode

The sluggish economy and persistent inflation have put many companies in survival mode, just trying to keep the lights on. Ambitious programmes to reengineer the way the work works, implement new systems, or drive improved effectiveness now feel like costly distractions. After all the chaos of the last few years, who has the bandwidth for that right now?

The Personal Upside

While the economic arguments for deprioritising business improvement are understandable, I think we’re missing something important – the personal upside. Streamlining operations, updating shared assumptions and beliefs, developing better practices, and finding ways to work smarter don’t just benefit the business. They allow each of us to be more successful and fulfilled as individuals.

The Costs of Inefficiency

Think about it – what does bloated, inefficient business activity translate to on a personal level? Wasted time on tedious manual tasks. Constant firefighting and rework thanks to poor ways of working. Headaches and frustrations navigating clunky systems and workarounds. At its worst, organisational dysfunction mentally drains and demotivates employees to the point they burn out or quit.

The Benefits for Individuals

On the flip side, smart business improvements that simplify and optimise how we execute allow us to flow through high-value work with less friction. We spend more time on the energising aspects of our roles utilising our skills and making an impact. Our days feel more productive and purposeful rather than mired in busywork and cleanup. More gets done, with less expended effort.And we learn.

From streamlined reporting that saves hours a week, to improved workflows that reduce costly errors, to delighting customers through superior service – the personal benefits of working at a well-oiled operation are massive in terms of satisfaction, growth, and work-life balance.

The Workplace Attraction Issue

Given the intensely competitive landscape for people, any organisation looking to attract and retain commited and engaged people might choose to prioritise continuous improvement as part of their employee value proposition. When people can channel their energies into engaging, rewarding work day after day, that’s when we build exceptional teams delivering exceptional results.

Don’t Brush It Aside

So don’t just brush business improvement aside as a nice-to-have these days. See it as key driver of personal success and engagement, helping your teams flourish while fuelling joy and delight in the (distributed) workplace.

Let’s Call Software Testing By Its Real Name

The Elephant in the Room

Can we have have an honest discussion about software testing? For many years now, we’ve danced around the real reason we dedicate substantial time and resources to testing software before releasing. It’s time to call a spade a spade – what we refer to as “testing” is actually “status determination”.

Status Determination: Reporting on the Current State

Testing, or status determination as I’ll contentiosly refer to it going forward, serves one key purpose: to report on the current status of the software under development. With each test execution, we’re essentially asking “Where are we at? What’s working as intended and what still needs to be fixed or improved?”

A Reflection of Our Development Approach

The need for rigorous status determination is a reflection of the current state of software development practices. If processes were truly stable and predictable, we would already know the status of the product without having to examine it through testing. But the truth is, our development approaches have instability and unpredictability baked in from the start.

Embracing Status Determination

Instead of deluding ourselves, we might choose to resign ourselves to the humiliating reality that status determination is a crutch upon which our development efforts desperately rely. It is a begrudging acknowledgment that teams simply cannot contend with the inherent complexities involved in crafting modern software systems through process and skill alone.

We lack the capability – the fundamental engineering wisdom – to make any credible predictions about how our systems will ultimately behave until we have fully constructed them and exhaustively probed their functions through test execution. No amount of upfront rigour, no depth of planning, no elite cadre of technical talent can circumvent this embarrassing limitation.

Embracing status determination is an admission that our vaunted processes and highly-skilled practitioners are profoundly inept at the core challenge of developing software systems that accurately model their specified behavior from the outset. We are hopelessly beholden to this retroactive “validation” step, owing to our rudimentary inability to wrangle the demons of complexity upfront through our hubris-laden and woefully inadequate practices.

Status determination stands as an unavoidable, perpetual reminder that for all our pontificating about engineering maturity and advancing the software discipline, we remain disappointingly crude in our approaches. It is the ceaseless tax we pay for failing to evolve more predictable, more reliable development techniques befitting a truly modern, professional field.

The Path Forward

Does this mean our development practices are fatally flawed? Pretty much. It means we have to allocate appropriate time and resources to status determination as a key part of our delivery lifecycle. We might better choose to strive to improve our processes. Let’s call software testing what it is – “status determination” – and double down on getting better at no longer needing it.

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.

Metacluelessness is Not a Criticism, It’s a Lament

Metacluelessness: The Plight of Being Unaware

What is metacluelessness? Simply put, it refers to the lack of awareness about one’s own lack of awareness or knowledge. In other words, metacluelessness is a state of being clueless about being clueless. It’s a predicament that plagues us all to varying degrees, cutting across boundaries of education, intelligence, and experience.

The Dunning-Kruger Effect

This phenomenon is closely tied to the Dunning-Kruger effect, a cognitive bias that causes people to overestimate their abilities and knowledge in areas where they are, in fact, incompetent. Named after the psychologists David Dunning and Justin Kruger, this effect explains why the least skilled individuals often have an inflated sense of their expertise, while the truly knowledgeable tend to underestimate their capabilities.

The Perils of Metacluelessness

Metacluelessness can have far-reaching consequences, both personal and societal. On an individual level, it can lead to poor decision-making, missed opportunities, and stagnation. When we are unaware of our own blind spots, we fail to seek the guidance or education that could help us grow and improve.

In a broader context, metacluelessness can contribute to polarisation, conflict, and the spread of misinformation. Those who are metaclueless about their lack of knowledge on complex issues may cling to their beliefs with stubborn certainty, dismissing contrary evidence and fuelling divisiveness.

A Lament, Not a Criticism

It’s important to note that metacluelessness is not a personal failing or a character flaw. It’s a universal human condition, a byproduct of our cognitive limitations and biases. Recognising and acknowledging one’s metacluelessness is, in fact, a sign of wisdom and humility – a willingness to admit that there is always more to learn.

The Path to Self-Awareness

So, how can we combat metacluelessness? The first step is to cultivate self-awareness and intellectual humility. We might choose to embrace the fact that our knowledge and understanding are inherently limited, and remain open to new information and perspectives. Reading widely, in depth, and outside of a narrow field helps too. I’d recommend in particular the works of notable psychotherapists including R.D. Laing, Marshall Rosenberg, Virginial Satir, Viktor Frankl, and Carl Rogers.

Surrounding ourselves with diverse viewpoints and seeking out constructive feedback can also help us identify our blind spots. By engaging in respectful dialogue and actively listening to others, we can gain insights into areas where our understanding may be lacking.

Lastly, we might choose to foster a culture of lifelong learning, recognising that education is an ongoing process, not a finite destination. Whether through formal education, self-study, or simply keeping an open and curious mind, we can chip away at our metacluelessness, one lesson at a time.

In the end, metacluelessness is not a criticism or a judgement – it’s a lament, a recognition of the inherent limitations of the human condition. By embracing this reality with humility and a commitment to growth, we can navigate the complexities of our world with ever greater wisdom and understanding.

Taking Responsibility for Our Emotions

The Harsh Truth

One of the most transformative realisations I’ve had from years of studying many schools of therapy is that our emotional responses are solely our own responsibility. No matter what someone else says or does, we alone are responsible for how we internalise their words or deeds, and react, emotionally.

This is a difficult pill to swallow, as we’re conditioned from a young age to blame others for “making” us feel certain ways*. If a co-worker is rude or our boss lays into us, it’s easy to mentally check out and go numb – as a self-defense mechanism – feeling angry at them for causing us distress. But the reality is, no one can make us feel any particular way without our permission.

The Source of Our Emotions

Our emotional responses are fuelled by our thought patterns, beliefs, prior experiences, and state of mind in that moment. Someone’s unskillful behaviour can act as a trigger, but we alone control whether we react with anxiety, defensiveness, anger, or remain grounded. This is where the work comes in.

So few people realise this responsibility is theirs, let alone take it to heart. It’s much easier to play the victim and blame others. But true emotional maturity comes from internalising that our emotions originate from within us, not from other people..

Empowerment at Work

In a workplace context, this philosophy is incredibly empowering. If we have a chronically negative or harsh manager or colleague, we get to decide whether their behaviour sends us into an emotional tailspin or if we react with non-judgement and detachment. Not getting hung up on the emotions of the moment allows us to respond skilfully in misunderstandings and avoid escalations.

A co-worker’s words and actions are about them, not about us. Our colleagues’ unconscious behaviours don’t have to dictate our experience. We get to consciously choose our mindset and emotional state in any situation.

The Greatest Gift

This paradigm shift takes practice, but it’s one of the greatest gifts we can give ourselves. No longer feeling like helpless victims to others’ emotional outputs. Owning our emotional adulthood and self-accountability. True inner freedom.

It’s available to anyone, but so few people live it. We can choose to do the work to take radical responsibility for our emotions, no matter what others do. We’ll be rewarded with choice and peace in the face of conflict, instead of being unconscious reactors.


*One root of the Myth of Redemptive Violence

Cop

The Executive Fuckups Crippling Software Development

Let’s be honest, executives and seniors managers are forever fucking up their organisations’ software development efforts, big time.

Category Error

The Crux of the Problem

Let’s be honest, successfully executing software development initiatives is no easy feat for executives and senior managers. As the Harvard Business Review aptly states,

“The greatest impediment [to effective software development] is not the need for better methodologies, empirical evidence of significant benefits, or proof that agile can work – it’s the behaviour of executives.”

At the root of these struggles lies a fundamental “Category Error” – the failure to recognise collaborative knowledge work (CKW), such as software development, as a distinct category from other types of work.

Applying the Wrong Lens

Whilst leadership plays a crucial role in complex projects, executives often fuck up development big time by attempting to manage software development through the same lens as:

  • Factory work
  • Manufacturing
  • Traditional office work
  • Service work (e.g. call centres, help desks)
  • Individual knowledge work

However, collaborative knowledge work demands a radically different approach. Imposing management practices from other categories inevitably leads to “management monstrosities” – dysfunctional, ineffective tech organisations.

The Pitfalls of Misclassification

  1. Disconnect Between Business and CKW
    Executives struggle to bridge the gap between business objectives and CKW realities when software development is treated as akin to factory work or manufacturing.
  2. Unrealistic Expectations
    Viewing software development through the lens of production lines and factory work breeds cultural mismatches, unrealistic timelines and quality compromises.
  3. Resistance to Change
    Legacy systems persist due to inertia from treating CKW like the more understood office work.
  4. Resource Misallocation
    Without recognising development as collaborative knowledge work, resources for talent, tools and infrastructure are inadequate.
  5. Micromanagement
    An authoritarian command-and-control ethos stifles the autonomy and collaboration that development teams need.

The Crux of the Issue

The HBR quote exposes this truth – executives’ mindsets, shaped by misunderstanding the category of work, undermine methodologies and processes.

Unlocking True Potential

Overcoming “management monstrosities” requires understanding software development as collaborative knowledge work. This shift allows:

  • Fostering cultures of learning and evolution.
  • Embracing self managing, autonomous team models.
  • Aligning resources for teams of knowledge workers.
  • Building bridges between business and CKW domains.

With the right categorisation and mindset, executives can transform organisations into innovative powerhouses (fat chance of that happening in our lifetimes).

The Path Forward

The key lies in shedding industrial-era management thinking (they do think, don’t they?) and nurturing environments suited to this distinct category of work.

Open communication, adaptability and appreciating the complexities of collaborative development are vital. Escaping the “Category Error” unlocks outstanding delivery of software solutions and delight for all the Folks That Matter™.

Metacluelessness – The Competence Blind Spot Plaguing Organisations

The Danger of Overconfidence

As a manager, having confidence in your abilities is certainly important for leading teams and making critical business decisions. However, there is a fine line between self-assurance and falling victim to a dangerous cognitive bias called metacluelessness – a lack of awareness about the boundaries of your own competence.

Clifford’s Ethics of Belief

Philosopher William Kingdon Clifford highlighted the ethical importance of not allowing ourselves to remain in a state of false beliefs or delusions. In his essay “The Ethics of Belief,” Clifford argues it is wrong, whenever the occasion arises, to believe something on insufficient evidence. To do so is to erect a “scorner’s chair” for truth and to fail to uphold our fundamental duty as human beings to pursue truth diligently.

Metacluelessness as Unethical Delusion

Metacluelessness directly violates this duty that Clifford lays out. It causes managers to grossly overestimate their skills, knowledge, and overall managerial competence based on delusional confidence rather than objective assessment of the evidence of their understanding. Managers suffering from metacluelessness erect their own “scorner’s chairs” for truth in their areas of responsibility.

They think they have a solid handle on principles, best practices, people, psycvhology, emerging trends, and the complexities involved, when in reality there are gaping holes in their grasp that they fail to acknowledge. Suffering from metacluelessness, managers operate under a false sense of mastery over critical management disciplines. They are clueless about the true extent of their cluelessness and knowledge gaps. This creates disastrous blind spots in their judgment and decision-making.

The Root of Managerial Arrogance

As Clifford states, “The source of all the miserable self-idolatries…the despicable vices…is nothing other than a persuasion existing in men’s minds not based on fair reasoning and evidence.” Metacluelessness breeds overconfidence based on delusional beliefs about one’s true competence. It is the root of managerial arrogance, close-mindedness, dismissal of risks, and poor strategic vision.

Catastrophic Consequences

The consequences can be catastrophic – flawed strategies, missed opportunities, sunk costs from failures, poor leadership examples set for teams, and more. Entire companies have met their demise because executive leadership teams suffered from the “miserable self-idolatry” of individual and collective metacluelessness in critical areas.

Cultivating True Competence

Combating metacluelessness requires cultivating true competence – an awareness of what you don’t know and diligence in addressing those shortcomings. It starts with the intellectual humility that Clifford upheld as critical for a responsible pursuit of truth and knowledge. Admit the limits of your expertise without feeling inadequate. As Clifford wrote, “A generous admission of knowledge gaps is the condition of all real progress.”

The Best Never Stop Learning

Recognise that as a manager, you supervise teams filled with specialised knowledge you cannot possibly match in every domain. True competence means knowing when to rely on the wisdom of others with deeper mastery and looking for opportunities to expand your own understanding through fair reasoning and examination of evidence. It’s about embracing a habit of perpetual learning to strengthen beliefs in alignment with evidential proof.

The best managers never stop questioning their grasp of important principles and best practices based on the ethics of belief laid out by Clifford. Don’t let the “despicable vice” of overconfident metacluelessness derail your judgment through beliefs detached from rigorous evidentiary standards. Proactively identify and confront the boundaries of your competence. Only then can you become a more complete, ethically sound, and effective manager capable of leading teams and companies to success built on a foundation of diligently pursued truths.

The Power of Reflective Questions

The Impact of Our Questions

When it comes to understanding employee satisfaction and well-being, the questions we ask hold immense power. They shape the depth of insight we receive and the degree of self-reflection they prompt in others.

Simple vs. Reflective Questions

Consider these two contrasting questions:

  1. “Do you feel happy in your work and workplace?”
  2. “What factors contribute to making you feel happy or sad about your work and workplace?”

The first question stands broad and surface-level. A simple yes/no response fails to encourage any deeper self-reflection on the part of the employee. While they may respond truthfully, that single word provides no window into the nuanced drivers behind their feelings. Some might describe this as a “closed” question.

The second question, however, demands thoughtful introspection. It pushes the employee to pinpoint the root causes and specific elements that amplify or detract from their workplace fulfillment and positive sentiments about their role. Some might describe this as an “open” question.

The Value of Self-Reflection

An insightful response might go:

“I find happiness in this role’s meaningful work and growth opportunities. However, the long hours, lack of work-life balance, and poor management communication leave me frequently stressed and discouraged.”

This level of self-reflection yields far richer insights for the employer and embloyee, both. They gain a holistic view into not just the employee’s mood, but the underlying factors and pain points shaping their experience each day.

Fostering Authentic Understanding

The quality of the questions we ask directly impacts the quality of self-reflection. When we ask binary, closed-ended questions about complex issues like happiness, we restrict the potential for enlightening personal contemplation, and meaningful dialogue.

In contrast, open-ended exploratory inquiries serve as prompts for valuable self-reflection. They require respondents to purposefully examine their emotions, motivations, and the nuanced elements influencing their attitudes and engagement levels.

As employers, if we seek authentic understandings rather than superficial sentiments, we must create room for self-reflection through our questions. Instead of asking “Are you happy?”, we might choose to frame inquiries that facilitate thoughtful exploration: “What brings you a sense of meaning and fulfillment in your work? What factors leave you feeling dissatisfied or burnt out?”

The Path to Better Connection

When we invite this level of self-reflection, we don’t just understand an employee’s current state. We gain powerful insights into the roots of their experiences – both positive and negative. Armed with that deeper awareness, we can enact changes, reinforce strengths, and directly address issues eroding engagement and achievement, and sucking joy.

In the quest for connection, self-reflective questions are an under-utilised superpower. They enable not just data collection, but a purposeful exploration of the human experience we’re aiming to improve. Let’s craft questions that illuminate richer truths and inspire more fulfillment.

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 Needs of Employees: What’s at Stake for Businesses

Employees are the backbone of any successful business. Their performance and satisfaction directly impacts a company’s bottom line. This means businesses have a vested interest in attending to the needs of their workforce. However, doing so requires commitment and resources. What exactly is at stake when it comes to meeting employee needs? Let’s explore the potential risks and rewards underpinning the Antimatter Principle.

What Businesses Stand to Lose

Ignoring employee needs can be costly for companies in many ways:

  • Reduced productivity and performance: Employees who feel their needs aren’t being met are less motivated, engaged, and productive at work. This negatively impacts the quality and efficiency of their output.
  • Higher turnover: Dissatisfied workers are more likely to leave their jobs in search of better opportunities. High turnover disrupts operations and incurs substantial replacement costs.
  • Damaged employer brand: News of poor working conditions and unmet needs spreads quickly. This damages a company’s reputation as an employer, making it harder to attract and retain top talent.
  • Litigation risks: Disgruntled employees may take legal action over issues like discrimination, harassment, unsafe working conditions, privacy, or wage violations. Lawsuits are both expensive and damaging PR-wise.
  • Toxic culture: Ignoring needs can breed negativity, resentment, and low morale among staff. This creates a stressful, unmotivated culture that further reduces productivity.

What Businesses Stand to Gain

On the flip side, making employee needs a priority and attending to them a intrinsic part of BAU can pay off tremendously:

  • Improved recruitment and retention: Employees are drawn to supportive companies with great benefits, culture, and working conditions. Catering to needs helps attract and retain top talent.
  • Higher productivity: Employees who feel their needs are met work more effectively and deliver better results. A happy, healthy workforce is a productive workforce.
  • Enhanced loyalty and engagement: When companies show they care, employees respond with greater commitment, passion, and loyalty. This directly fuels performance.
  • Better customer service: Needs like training and empowerment equip staff to deliver exceptional service that keeps customers happy and loyal.
  • Reduced risks: Addressing needs like safety and wellness protects staff while minimising potential injuries, lawsuits, and PR crises.
  • Employer brand building: Exceptional benefits, culture, and practices earn rave reviews from staff. This builds a company’s reputation as a premier employer.

The Takeaway

While it requires investment, making employee needs a priority provides significant upside for businesses. On the other hand, ignoring needs exposes companies to major risks and hidden costs. The message is clear: by taking care of the needs of employees, businesses also take care of their own interests. The potential rewards of meeting needs make it a win-win proposition.

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.

Management Shortchanges Employees At Every Turn

In many companies, management imposes policies and practices that end up costing employees in major ways. Despite no clear business benefits, executives and middle management, both, make decisions and pursue approaches that hurt workers’ wallets, productivity and well-being.

Can we ever expect a healty, productive and mutually beneficial community of relationships to emerge from a foundation of naked exploitation?

Example: RTO

One example is Return to Office mandates after COVID, but this is just a symptom of a broader issue – management making decisions without considering employees’ needs and blythe ignorance of the consequences. (Or is it mendacity? For example, Wage Theft – estimates suggest wage theft costs U.S. workers $15-50 billion per year, more than is lost to robbery and theft combined.).

Shall We Count the Ways?

“How do I love thee?
Let me count the ways.
I love thee to the depth and breadth and height
My soul can reach, when feeling out of sight
For the ends of being and ideal grace.”

~ Elizabeth Barrett Browning

Other common ways managers financially and personally cost staff include:

  • Stagnant wages and lack of raises, even despite rising costs of living
  • Minimal spending on employee training and career development
  • Avoiding the costs of effective health and safety and wellness programmes
  • Mandating outdated tools, working practices, organisational structures, and systems, that hinder productivity vs new approaches
  • All talk, no action on diversity, equity and inclusion initiatives – “DEI Theatre”
  • Ever rising C-suite salaries, bonuses and perks while rank and file see ever-shrinking benefits
  • Lack of flexibility for work-life balance, leading to workers’ lives and earnings being disrupted by having to change jobs

Many companies view workers as nothing more than a cost to be minimised. Executives are disconnected from the employee experience. They pursue shareholder value at the expense of the workforce.

But organisations suffer when employees are not valued. Disengagement, burnout and high turnover follow. Customer satisfaction dips as unhappy employees deliver poor service. Innovation and performance decline.

Conclusion

The poor treatment of employees by management seems deeply ingrained in corporate structures and business school teachings. But are there solutions, or is management simply an irredeemable concept?

Some argue that these problems can be addressed through better laws and regulations, such as higher minimum wages, stronger health and safety protections, limits on executive compensation, and empowering workers’ rights to organise. Management training programs could also be reformed to prioritise employee wellbeing over short-term profits.

However, others contend that management by its very nature is exploitative. The hierarchical structure gives disproportionate power to executives and shareholders beholden to capitalism’s pursuit of power-holders’ wellbeing, efficiency, and profit maximization. Workers will always be squeezed under the management yoke

Radical solutions propose democratising the workplace through cooperatives, employee representation and ownership, worker representation on boards, and decentralised decision-making. But can these ideas scale successfully?

Perhaps the answer lies in a mixed approach. Pragmatic reforms to improve life for workers within current corporate models, paired with incubating alternative organisational structures that give workers an equal voice, or even the whip hand (Cf. servant leadership).

There are no easy solutions, but can we continue to accept the status quo of management blatantly and egregiously exploiting employees? Can we find a system that upholds dignity, justice and shared prosperity? Workers are assets to invest in, not costs to cut. Might we have faith that through insight, integrity and innovation, business can empower rather than extract from the workforce? The path will not be quick or easy, but progress remains possible through partnership across sectors and persistence despite setbacks.

For a model of how such an oganisation might look like – and feel like from both the workers’, managers’, and customers’ perspectives – you might like to read my latest book “Quintessence“.

Afterword

What practices have you seen, good or bad, that reveal how a company truly views its employees? Share your thoughts on when management’s decisions cost or benefit workers.

The Why of FlowChain: Deliberate Continuous Improvement

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

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

What Is FlowChain?

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

Flow

Optimising flow delivers the following benefits:

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

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

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

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

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

Compounding Benefits

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

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

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

*Ask me about the exception.

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.

Improving Human-to-Human Communication Through AI and Chatbots

For God’s sake, there is truly no longer any excuse for typos, misspellings, and grammatical errors in your posts, articles, and other writings.

Artificial intelligence (AI) and chatbots are transforming how we communicate. When integrated thoughtfully, this technology can optimise and enhance written communication between people. In this post, I’ll discuss some ways AI and chatbots can improve messaging, email, documentation, and other word-based interaction between humans.

Automated Proofreading and Editing

AI-powered writing tools already help by providing grammar and spelling checks. But newer capabilities can now also flag unclear phrasing, verbose language, overused words, and overly complex sentences. This aids writers in simplifying and refining their messaging before sending to a recipient. Readability statistics further help authors match their tone for the intended audience.

Summarisation and Translation Features

For long-form writing like reports or manuals, AI can generate a concise summary highlighting key facts, main takeaways, or action items. This allows collaborators or stakeholders to quickly grasp the essence before diving into the details. Meanwhile, instant translation functionality enables clear communication across language barriers.

Interactive Books

AI is also enhancing books through interactive elements powered by chatbots. Platforms like Ainklings.com allow authors to insert quizzes, discussion questions, exercises and other engaging features directly into the book text (or via sidecars). Readers can further highlight passages and interact with supplementary content related to the main narrative, enriching the reading experience.

Content Recommendations and Insights

Smart suggestions can enable more meaningful interactions through personalised recommendations. By analysing past correspondence as context, AI can prompt authors to include certain missing information, helpful examples, or reminders based on what the recipient would find useful. Language pattern analysis can also reveal insights for improving future discussions.

Automated Meeting Summaries and Notes

While AI currently struggles to match the creativity of human writing, it excels at capturing the salient points from meetings and presentations. Automated summaries of video sessions or collaborative spaces can save meeting participants time while ensuring everyone understands the key decisions or action items.

With thoughtful application, AI and chatbot tools can enhance understanding and engagement between people through better writing assistance, translation, summarisation, and recommendations. As these capabilities continue advancing, keeping the human audience at the center will be key to success.

The Great British Worker Shortage: Flogging a Dead Horse

Recent headlines bemoan a British workforce apparently lacking motivation as employee shortages plague UK companies. But rather than dusting off the same stale carrot-and-stick strategies aimed at driving disengaged worker horses, a radical shift may be in order. What if leading organisations reinvented their entire mindset and systems to inspire authentic engagement?

Outmoded Assumptions

This seismic reinvention starts with rethinking assumptions:

  • Are tired coercion tactics truly the only solution, or are there unmet needs amongst our people?
  • Could under-tapped passions and purpose be awakened to fuel commitment?
  • What kind of workplace reimagining could kindle individual and collective potential?

Rather than tread the same dead paths, today’s visionary organisations are poised to pioneer reinvention rooted in understanding these human truths. Work can inspire meaning, camaraderie and self-actualisation towering far above merely showing up for a wage. But aspiting to these heights requires a fundamentally fresh lens.

Are we ready to reshape the canvas? What possibilities might emerge through a relationship-based reset? Read on to explore dead-end strategies of the past contrasted to pathways to engagement and symbiotic thriving…

Reinventing the Disengaged British Workforce

Here are 12 strategies often used by companies who find themselves riding a dead horse:

  1. Change riders: For example, appoint new managers. But rather than simply swap managers, why not build engagement teams to deeply enquire of unmotivated staff on their true passions and purposes?
  2. Buy a stronger whip: But harsher penalties or coercive measures usually backfire. Could tailored incentives that speak to intrinsic worker values be more sustainably motivating?
  3. Harness several dead horses together: Attempting to harness disengaged teams rarely breeds vitality. Should clarifying individual purpose come first before teaming to ignite motivation?
  4. Emulate the best practices of other dead horse riders: Trendy gimmicks gaining traction elsewhere may entertain briefly, but authentic and lasting motivation lives in practices tailored for your people.
  5. Outsource the ridership: Handing rein over to outsourced managers who lack connection to internal teams can further dissolve rapport and purpose. Regular grassroots engagement from the organisation can rebuild relationships.
  6. Affirm that “this is the way we have always done things”: Preserving status quo processes may provide familiarity but squelches the innovation and empowerment today’s workforce expects. Could reinvention around the human dimension stir engagement?
  7. Change the requirements, declaring “This horse is not dead”: When workplace reality conflicts unsustainably with output expectations, organisations able to accept reality and reinvent accordingly tend to thrive.
  8. Perform cost analysis to see if contractors can ride cheaper: Analysing staff as expenses rather than assets risks missing their fullest potential value. How could we reboot to showcase their upside?
  9. Promote the dead horse to a management position: Rather than reward fancy titles over real contribution, what if meaningful advancement tied directly to the ability for motivating and uplifting others?
  10. Sue the horse manufacturer: Playing the blame game often wastes energy better directed toward understanding real needs and reinventing uninspiring systems. What does that reinvention vision entail?
  11. Claim “the horse was always dead”: Whether motivation issues worsened gradually over time or not, forward-thinking leaders take full responsibility today. Authentic reinvention must start now.
  12. Hire in foreign riders known for their ability to ride dead horses.

The Antimatter Principle reminds us that inspiration sparked by deeply attending to human emotional needs will always outpace coercion. Will UK companies discover how to truly engage the 21st century British worker by fully reinventing the workplace experience? I boubt it. And yet, The potential awaits fresh thinking!

What is Rigour?

Rigour refers to the strict precision and accuracy with which work is executed in fields like software engineering and collaborative knowledge work (CKW). It entails adherence to standards and best practices for needed outcomes.

The Importance of Getting it Right

Attentive rigour matters because carelessness breeds mistakes. Flaws in logic or bugs in code stem from a lack of rigour. This introduces unwanted surprises, and failures down the line. Rigour is an attitude of mind that zeroes in on getting things right the first time Cf. Crosby, ZeeDee.

The Perils of Getting it Wrong

However, the quest for rigour can go awry when imposed hastily or mindlessly. Establishing rigorous frameworks like requirements analysis, peer review etc. does carry overhead. Teams can get so bogged down chasing perfection that creativity, productivity and morale suffer. Or so much time is spent eliminating small defects that bigger picture progress slows. Like most things, balance is warranted.

The Laissez-Faire Extreme

At the other end of the spectrum from rigour lies the laissez-faire attitude. This French phrase meaning “let it be” encapsulates a laid-back approach where participants have broad freedom to work in whatever manner they choose.

In software and knowledge work contexts, laissez-faire environments feature very few enforced policies, protocols, or mechanisms for ensuring quality. Creativity and unhindered workflow takes priority over rigour. Peer reviews, quality assurance, and documentation are optional. Teams self-organise organically without work standards.

This spontaneity can spark innovation but has pitfalls. Lack of rigour tacitly permits cut corners, gaps in logic, unfinished ideas and sloppy execution. With an easy-going approach, easily preventable flaws accumulate and undermine end results.

In applied contexts like commercial software development, laissez-faire practices practically guarantee shoddy work products riddled with defects. User needs demand rigour not as an obstacle, but as an enabler of excellence. Finding the right balance is key.

The absence of rigour embodied in laissez-faire philosophies may promote freedom. But the ensuing chaos leaves the fruits of hard work easily compromised. Some structure and rigour ultimately serves applied collaborative knowledge work better in the long run.

While cutting corners is not an option, forced rigour without context can mean marginal gains at disproportionate cost. Rigour must enable, not encumber, the pursuit of excellence. Teams that foster a culture where rigour flows from all participants, intrinsically and voluntarily, tend to find the sweet spot. Getting there requires clarity of purpose, patience, and care. Do that and rigour lifts the quality of collaborative knowledge work substantially over time.

What does rigour mean to you and your team?