Archive

Community

From Suffrage to Software Development

Courage Calls to Courage Everywhere

How Millicent Fawcett’s rallying cry for women’s suffrage speaks to everyone fighting for organisational change


‘Courage calls to courage everywhere, and its voice cannot be denied.’

These words, spoken by Millicent Fawcett in 1920 following the death of fellow suffrage campaigner Emily Davison, echo through time with remarkable relevance. Davison had died seven years earlier when she was struck by the King’s horse at the Epsom Derby in a protest that shocked the nation. Whilst Fawcett was rallying women to demand their fundamental right to vote, her message speaks to anyone who has ever stood up against entrenched systems that resist needed change.

Fawcett’s call resonated because it captured something already stirring in the collective consciousness of her era—a growing recognition that democratic ideals demanded broader participation. Today’s developers find themselves in a fascinating position: whilst they often push against immediate organisational cultures that prioritise speed over sustainability, they’re simultaneously tapping into a broader societal zeitgeist—one increasingly driven by generational values around fairness, meaning, and long-term thinking over short-term extraction.

The Courage to Challenge the Status Quo

Just as the suffragettes faced a political establishment that insisted women didn’t need the vote, developers often encounter organisational inertia that dismisses their concerns about autonomy, technical debt, poor tooling, or unsustainable practices. ‘We’ve always done it this way’ becomes the modern equivalent of ‘women don’t understand politics’. More fundamentally, developers often encounter business attitudes that denigrate the very concepts of autonomy, mastery, and purpose—treating skilled people as interchangeable resources rather than recognising the human need for meaningful, well-crafted work.

Both movements require individuals to risk their standing—suffragettes faced imprisonment and social ostracism, whilst developers risk their careers and livelihoods when they push back against unsustainable practices, challenge poor decisions, or refuse to compromise on quality standards.

Yet in both cases, the courage of one person to speak up creates permission for others to do the same. When a senior developer finally says ‘This pace isn’t sustainable—we’re going to lose good people if we keep pushing these deadlines’ in a sprint retrospective, they’re echoing Fawcett’s call—courage calling to courage.

The Systemic Nature of the Problem

The suffragettes understood that individual voting rights were symptoms of a broader systemic issue about women’s place in society. Similarly, declining engagement, lost motivation, and the absence of joy in work aren’t isolated problems—they’re symptoms of a broader systemic issue about developers’ place in business.

Both movements recognise that meaningful change requires more than individual heroics. It demands shifting entire systems of thought and practice.What is often refer to as collective assumptions and beliefs.

Building Coalitions for Change

Fawcett’s genius wasn’t just in inspiring individual courage, but in building a movement. She understood that isolated voices, however brave, could be dismissed or marginalised. But a chorus of voices demanding change becomes impossible to ignore.

Here, the parallel breaks down somewhat. Smart developers understand this lesson intellectually, yet the industry still lacks the kind of organised movement Fawcett built. The lone engineer railing against poor practices in isolation rarely succeeds, and whilst developers occasionally band together within teams or companies, there’s little of the sustained, cross-organisational coalition that the suffrage movement achieved.

Perhaps this is the missing piece. Individual courage, however admirable, may not be enough. The question becomes: what would a developers’ movement actually look like?

The Long Game of Reform

The suffragette movement spanned decades. Fawcett herself campaigned for over 50 years before seeing women gain the vote. This persistence in the face of setbacks offers profound lessons for developers advocating for organisational change.

Meaningful transformation of development practices doesn’t happen overnight. It requires sustained advocacy, continuous education of stakeholders, and the patience to make incremental progress. Every meeting where developers’ voices are genuinely heard, every deadline that considers human needs, every decision that asks ‘how will this affect our people?’—these are the small victories that accumulate into systemic change.

Moral Authority

The suffragettes derived their power from moral authority—the undeniable rightness of their cause. Developers fighting for better practices have a similar advantage: authority grounded in lived experience. When teams burn out from unsustainable pace, when poor decisions create chaos that developers must navigate daily, when short-term thinking creates long-term suffering—the evidence for change might be compelling, yet organisations often find ways to dismiss, rationalise, or minimise these warning signs.

This aligns with what mathematician William Kingdon Clifford argued in his 1877 essay ‘The Ethics of Belief’—that we have a moral obligation to base our beliefs and actions on sufficient evidence rather than convenient fictions. Both suffragettes documenting systemic disenfranchisement and developers documenting organisational dysfunction aren’t merely being strategic; they’re fulfilling an ethical duty to confront uncomfortable truths about systemic injustices.

The challenge, as with the suffragettes, is making this authority visible to those in power. This requires not just technical expertise, but the communication skills to translate technical consequences into business impact. Note: Don’t throw yourself under a horse!

Courage for Modern Developers

So how do we answer Fawcett’s call in our daily work? Here are some ways developers can channel suffragette-style courage:

Start with documentation. The suffragettes were meticulous record-keepers, documenting injustices and building evidence for their cause. Developers can similarly document the impact of poor practices—the hours lost to debugging, the features delayed by technical debt, the security vulnerabilities introduced by rushed code. God knows there are enough tools to share such documentation and build a portfolio. Google Docs springs to mind.

Find your allies. Identify others who share your concerns. Build coalitions across teams and departments. Remember: courage calls to courage everywhere, but it helps when it’s calling to people who are listening.

Speak in business language. The suffragettes learnt to frame their arguments in terms that resonated with their audience. Developers can learn to translate technical concerns into business impact—lost revenue, increased risk, reduced competitiveness, staff engagement and turnover.

Celebrate incremental progress. Every small improvement, every tool adopted, every collective assumption and belief surfaced is a victory worth acknowledging. The suffragettes celebrated partial victories whilst continuing to push for the whole nine yards.

Stay professional but persistent. Maintain credibility whilst refusing to be silenced. The suffragettes largely mastered this balance, though not without tactical missteps that sometimes undermined their cause. The key was learning from setbacks whilst maintaining unwavering determination.

Embrace what women accomplished. Brogrammers can be dismissive of women in general and their achivements in particular.

The Voice That Cannot Be Denied

When developers across an organisation begin advocating for better, when they support each other’s proposals for improvement, when they consistently demonstrate the value of e.g. quality over speed—they create something powerful. They create a voice that, as Fawcett knew, cannot be denied.

The courage of the suffragettes didn’t just win women the vote; it demonstrated that ordinary people could challenge seemingly immutable systems and win. For developers feeling frustrated by organisational resistance to needed change, this history offers both inspiration and a roadmap.

Every time we advocate for quality, push back against impossible deadlines, or champion users over features, we’re answering Fawcett’s call. We’re demonstrating that courage truly does call to courage everywhere—and in the end, that voice cannot be denied.

The suffragettes transformed society by refusing to accept that ‘this is just how things are’. Software developers have the same opportunity to transform their organisations, one courageous conversation at a time.

Courage calls to courage everywhere. The question is: are you ready to answer?


Further Reading

(Note the dearth of publications on the topic of tech worker organising)

Benjamin, R. (2019). Race after technology: Abolitionist tools for the new Jim Code. Polity Press.

Crawford, E., & Terras, M. (Eds.). (2022). Millicent Garrett Fawcett: Selected writings. UCL Press. https://doi.org/10.14324/111.9781787359444

Gray, M. L., & Suri, S. (2019). Ghost work: How to stop Silicon Valley from building a new global underclass. Houghton Mifflin Harcourt.

Saghafian, M., Laumann, K., & Skogstad, M. R. (2021). Stagewise overview of issues influencing organizational technology adoption and use. Frontiers in Psychology, 12, 630145. https://doi.org/10.3389/fpsyg.2021.630145

Talking About Organisations

There’s a common assumption that the word ‘organisation’ refers primarily to companies, corporations, and commercial enterprises. Whilst this isn’t entirely wrong, it represents a remarkably narrow view of what organisations actually are. In fields like organisational psychotherapy, sociology, and systems thinking, the term encompasses a much richer and more diverse landscape of human collective structures.

What Is an Organisation, Really?

At its core, an organisation is any more-or-less structured group of people who come together around shared purposes, goals, or functions. It’s a social system with defined relationships, roles, and processes that enable collective action. This definition opens up a world far beyond the boardroom and balance sheet.

Think about it: every day, you likely interact with multiple organisations without even realising it. The family unit organising dinner, leisure, recreation and household responsibilities. The neighbourhood watch group coordinating community safety. The sports team working towards a championship or social purposes. The religious congregation gathering for worship, identity and mutual support. Each of these represents a distinct organisational form with its own dynamics, hierarchies, and psychological patterns.

The Rich Tapestry of Organisational Life

Organisations exist across virtually every domain of human experience:

Family Systems represent perhaps our first and most fundamental organisational experience. Families develop roles (the caretaker, the rebel, the peacemaker), hierarchies (parent-child relationships), and shared goals (everything from survival to celebrating traditions). Family therapy (Cf. Virginia Satir) has long recognised that dysfunction often stems from organisational issues rather than individual pathology.

Educational Institutions create complex webs of relationships between students, teachers, administrators, and communities. Schools and universities are organisations with their own cultures, power structures, and psychological dynamics that profoundly shape learning and development.

Religious and Spiritual Communities organise around shared identities, beliefs and practices, creating hierarchies of spiritual authority, systems of mutual support, and collective rituals. Churches, mosques, synagogues, temples, and other houses of worship represent some of the most enduring organisational forms in human history. Churches, in particular, often function as complex organisations with pastoral leadership, congregational governance, volunteer committees, youth programmes, and community outreach initiatives. These organisations provide meaning, identity, and belonging that extend far beyond formal religious observance, often serving as social hubs and support networks for entire communities.

Community Groups and Associations emerge around shared interests, needs, or geographic proximity. From book clubs to neighbourhood associations to advocacy groups, these organisations fulfil human needs for connection and collective action.

Sports Teams and Clubs create intense organisational experiences around competition, skill development, social purpose, and team identity. The psychology of team dynamics, leadership, and performance under pressure offers rich insights into organisational behaviour.

Healthcare Systems represent complex organisational networks involving patients, practitioners, administrators, and families, all navigating issues of care, authority, and healing within structured environments.

Military and Defence Organisations encompass a diverse range of organisational structures built around coordination and collective action under extreme conditions. Whilst traditional armies and navies often feature highly structured hierarchical systems with clear chains of command, other military units operate very differently. Some organisations like the U.S. Marine Corps blend hierarchical structure with cultures emphasising individual initiative, small unit leadership, and adaptability—maintaining clear command structures whilst fostering autonomous decision-making at lower levels. The German concept of auftragstaktik (mission-type orders) represents another organisational approach, where commanders provide clear objectives but grant subordinates significant autonomy in determining how to achieve them, creating a culture of initiative within a formal structure. Special forces like the SAS, Navy SEALs, and similar elite units function with even flatter structures, greater individual autonomy, and team-based decision-making that emphasises rapid response and improvisation.

Governmental and Political Entities organise society itself, from local councils to national governments, creating frameworks for collective sense-making and resource allocation.

Non-Profit and Advocacy Organisations mobilise around social causes, creating structures for collective action towards social change.

Cultural and Artistic Groups from orchestras to theatre companies to art collectives organise creative expression and cultural production.

Companies: Just One Player in a Larger Game

Against this backdrop, commercial organisations—the companies and corporations we typically think of—represent just one subset of organisational life. Yes, they’re often large, visible, and economically powerful, but they’re far from the whole story.

Even within the commercial sphere, the variety is enormous: family businesses operate very differently from multinational corporations. Worker cooperatives function differently from traditional hierarchical companies. Start-ups have completely different organisational dynamics than established institutions.

Why This Matters in Organisational Psychotherapy

Understanding this broader landscape becomes crucial when we consider organisational psychotherapy. People don’t exist in isolation—they’re embedded in multiple organisational contexts simultaneously. Someone might be a parent in a family system, a volunteer in a community organisation, a member of a religious congregation, and an employee in a company, all at the same time.

The psychological patterns, relationship dynamics, and systemic issues that emerge in one organisational context often mirror or influence what happens in others. A person struggling with authority in their workplace might also be navigating similar issues in their family or community roles. Understanding organisations as interconnected and overlapping systems rather than isolated entities provides a more complete picture of human psychological and social experience.

Moreover, the skills and insights that apply to organisational health—communication patterns, power dynamics, role clarity, shared purpose, conflict resolution—are relevant across all these contexts. The family learning to navigate adolescent independence has much in common with the community group managing volunteer burnout or the sports team dealing with personality conflicts.

How Organisational Beliefs Travel and Transfer

One of the most fascinating—and often problematic—aspects of our organisational lives is how beliefs and expectations formed in one type of organisation inevitably travel with us into others. We develop what organisational psychologists call ‘mental models’ about how organisations should function, and these models are powerfully shaped by our earliest and most intense organisational experiences such as school, or the family.

Consider someone raised in a highly authoritarian family structure who enters the workplace expecting rigid hierarchies and unquestioning obedience to authority. They may struggle in organisations that value collaborative decision-making or feel anxious in flat organisational structures where they’re expected to show initiative. Conversely, someone from a family that operated through consensus and negotiation might find traditional corporate hierarchies stifling or illegitimate.

Military personnel transitioning to civilian organisations often experience this transfer effect acutely. The clear command structures, explicit procedures, and mission-focused culture of military organisations can clash dramatically with the ambiguity and consensus-building approaches common in many civilian workplaces. Similarly, executives accustomed to the profit-driven logic of corporate environments may find themselves frustrated when trying to apply purely business thinking to community organisations or religious groups, where different values and decision-making processes prevail.

Religious and spiritual communities create particularly strong organisational templates. Someone whose primary organisational experience has been in churches emphasising collective worship, shared values, and pastoral authority may bring expectations of moral leadership and spiritual purpose to secular organisations—sometimes leading to disappointment when colleagues seem motivated purely by self-interest or autonomy, or when leaders fail to embody higher principles.

Even our experiences in sports teams, schools, or community groups create lasting imprints. A person whose formative organisational experience was on a high-performing sports team may expect all subsequent organisations to operate with the same intensity, clear role definitions, and shared commitment to winning. They might struggle in organisations where collaboration is more important than competition, or where success is measured differently, or not at all.

These transferred beliefs aren’t inherently good or bad—they represent the natural human tendency to apply acquired assumptions to new situations. However, they become problematic when we assume that all organisations should function like the ones we know best, or when we fail to recognise that different organisational contexts invite different approaches to authority, decision-making, communication, and purpose.

Understanding these transfer effects is crucial for anyone working across multiple organisational contexts. It helps explain why changing organisational cultures is so difficult (people carry their previous organisational experiences with them), why some individuals thrive in certain environments but struggle in others, and why effective organisational development often benefits markely from helping people surface and reflect on their collective assumptions and beliefs.

Expanding Our Organisational Imagination

Recognising the full spectrum of organisational life invites us to think more creatively about human collective behaviour. It suggests that insights from family therapy might inform business consulting, that lessons from sports psychology could enhance community organising, and that understanding religious community dynamics might shed light on corporate culture.

This broader view also highlights how much of our lives is bound up with organisations. We’re constantly creating, participating in, and being shaped by organised collective structures. Rather than seeing organisations as external entities we occasionally interact with, we can recognise them as fundamental features of our human social existence.

In a world facing complex collective challenges—from climate change to social inequality to technological disruption—this expanded understanding of organisations becomes even more useful. Solutions to these challenges require not just better companies, but healthier families, more effective communities, more resilient institutions, and more adaptive organisations of all kinds.

The next time someone mentions ‘organisational psychotherapy’ or ‘systems thinking’, remember: they’re talking about the full richness of human collective life, not just what happens in corporate conference rooms. Understanding organisations means understanding ourselves as the deeply social, systemically embedded beings we actually are.

Understanding the psychology of organisations—in all their forms—offers a window into some of the most fundamental questions about human cooperation, creativity, and collective flourishing.


Further Reading

Books

Bowen, M. (1978). Family therapy in clinical practice. Jason Aronson.

Minuchin, S. (1974). Families and family therapy. Harvard University Press.

Schein, E. H. (1988). Organizational psychology (3rd ed.). Prentice-Hall.

Schein, E. H. (2010). Organizational culture and leadership (4th ed.). Jossey-Bass.

Senge, P. M. (2006). The fifth discipline: The art and practice of the learning organization (Rev. ed.). Doubleday. (Original work published 1990)

Journal Articles and Academic Sources

Bakker, A. B. (2011). An evidence-based model of work engagement. Current Directions in Psychological Science, 20(4), 265-269.

Brown, J. (2024). Bowen family systems theory and practice: Illustration and critique revisited. Australian and New Zealand Journal of Family Therapy, 45(2), 203-220.

Senge, P. M., & Sterman, J. D. (1992). Systems thinking and organizational learning: Acting locally and thinking globally in the organization of the future. European Journal of Operational Research, 59(1), 137-150.

Academic Journals

Annual Review of Organizational Psychology and Organizational Behavior. (2014–present). Annual Reviews. ISSN 2327-0608. https://www.annualreviews.org/content/journals/orgpsych

Industrial and Organizational Psychology: Perspectives on Science and Practice. (2008–present). Cambridge University Press on behalf of Society for Industrial and Organizational Psychology. ISSN 1754-9426 (print), 1754-9434 (electronic). https://www.cambridge.org/core/journals/industrial-and-organizational-psychology

Journal of Occupational and Organizational Psychology. (1922–present). Wiley-Blackwell on behalf of British Psychological Society. ISSN 0963-1798 (print), 2044-8325 (electronic). https://bpspsychub.onlinelibrary.wiley.com/journal/20448325

Organizational Psychology Review. (2012–present). SAGE Publications in partnership with European Association of Work and Organizational Psychology. ISSN 2041-3866 (print), 2041-3874 (electronic). https://journals.sagepub.com/home/opr

The Antimatter Principle: Why Nobody Needs Their Needs Attended To

How attending to people’s needs might be the key to everything

The antimatter principle is deceptively simple:

“Attend to folks’ needs”

Just that.

A Brief Introduction: A Clarification After Fifteen Years

I first articulated the Antimatter Principle some fifteen years ago and have been writing about it regularly ever since. But with Claude’s help, I’ve just realised something significant: many people might be misunderstanding what the principle is actually about.

When I say ‘attend to folks’ needs’, I suspect some readers might focus on the ‘needs’ part. They start cataloguing what people might need, developing frameworks for identifying needs, or creating systems for meeting various requirements. But that’s not what the principle is fundamentally about.

The magic word isn’t ‘needs’—it’s ‘attend’!

I chose this word very deliberately. Compare it with ‘meet’ folks’ needs. ‘Meeting’ needs implies taking action, providing solutions, filling gaps. But ‘attending’ to needs is fundamentally different—it’s about presence, recognition, witnessing what’s actually there.

As a long time organisational psychotherapist (and student of Rogers, Rosenberg, and others), the power of ‘attend’ is embedded in my subconscious. But I now realise that for many readers, this distinction might not be immediately obvious. There’s also the social and relationship dimension: the very act of attending builds bonds in ways that meeting needs often doesn’t. When you attend to someone, you’re creating connection through presence rather than transaction. And there’s the reciprocity principle—when you truly attend to someone’s needs (in the way this post explains), they’re more likely to begin attending to your needs and the needs of others. Attention begets attention. This social phenomenon is especially profound in organisational, community and even nation-state contexts.

The Antimatter Principle isn’t about becoming an expert in human needs or developing sophisticated ways to meet them. It’s about the quality of attention you bring to people. It’s about really seeing them, being genuinely present with their experience, and offering the kind of attention that allows them to be fully themselves.

This distinction matters enormously. Focus on needs, and you become a problem-solver, a fixer, someone constantly scanning for deficits to address. Focus on attending, and you become something much more valuable: someone who can be truly present with another human being.

When I defined the Antimatter Principle as “attend to folks’ needs”, both elements were intentional. Needs matter—but the transformative power lies in the quality of attending. This balance between recognising real human needs and offering genuine attention without agenda has been baked in to the principle from its inception.

But here’s the paradox: when you actually attend to people’s needs—really attend to them—you discover that nobody needs their needs attended to — in the way we usually think about it.

Needs are Mostly Subconscious

Most people have very little conscious awareness of what they actually need. They’re just living their lives, dealing with whatever comes up, focused on work, relationships, daily tasks—if they’re focused on anything at all. The whole framework of ‘meeting needs’ often misses how people actually function.

Yet when you genuinely attend to someone—crucially, without any agenda to fix them or solve their problems, but simply to be present with what’s actually happening for them—something remarkable occurs. The very act of real attention, freed from the burden of trying to improve or change someone, often dissolves the sense that anything needs to be fixed or met. It’s precisely the absence of agenda that makes the attention so powerful.

Rogers and Frankl: Foundations for Understanding Attending

Carl Rogers discovered something similar in his therapeutic work. He found that when he could be genuinely present with clients—accepting them completely as they were without judgment or conditions—they often found their own capacity for growth and healing. Rogers’ revolutionary insight was that the quality of attention and acceptance mattered much more than specific techniques or interventions. People seemed to have an innate ability to move towards wholeness when given the right relational conditions.

Viktor Frankl added another crucial dimension to this understanding. Through his work with concentration camp survivors and later patients, Frankl discovered that the need for meaning—to feel that their experience matters, that their struggles have significance, that they’re connected to something larger than themselves—is often people’s most fundamental need. When you attend to someone’s need for meaning rather than just their surface-level complaints, you’re often addressing what they most fundamentally require. Frankl showed that people can endure almost anything if they can find meaning in it, demonstrating that this need for significance is as real and vital as any physical need.

Let’s explore how the Antimatter Principle works using the T-Squad five thinking patterns that reveal why this simple approach is so powerful.

Transform Constraints Into Advantages: Why Our Resistance to Attending Is Actually Wisdom

The obvious constraint is that attending to people’s needs seems demanding, time-consuming, and emotionally draining – both for the attendant and the attendee. Most people resist the idea because they imagine it means becoming everyone’s unpaid therapist or getting overwhelmed by others’ problems.

But here’s the transformation: when you actually attend to people properly—without trying to fix or solve anything—it’s often less demanding than the alternatives.

Think about how exhausting it is to constantly deflect, avoid, or half-listen to people. Or to engage in the endless cycle of giving advice that doesn’t work, then feeling frustrated when people don’t take it. Real attending—just being genuinely present with someone’s actual experience—often requires less energy than these defensive strategies.

The constraint becomes an advantage when you realise that attending doesn’t mean taking responsibility for outcomes. You’re not signing up to solve anyone’s problems. You’re simply offering the quality of attention that allows people to be fully themselves, which often enables them to find their own solutions.

Most people who resist attending to needs are actually protecting themselves from the burden of trying to fix everyone. But the Antimatter Principle isn’t about fixing—it’s about attending. And attending, paradoxically, often reduces the total emotional labour in your relationships rather than increasing it.

Systems-Level Perception: How Attending Creates Ripple Effects

Look at what happens to the whole system when someone consistently applies the Antimatter Principle.

In relationships, the dynamic shifts from transactional to generative. Instead of people keeping score of who’s giving and who’s receiving, attention becomes abundant. When someone knows their experience genuinely matters to you, they’re more likely to attend to others in the same way.

In families, the emotional climate changes. Children who feel truly seen develop better self-regulation. Partners who experience real attention become more generous with each other. The quality of attending spreads through the system like a beneficial virus.

At work, teams that practise the Antimatter Principle often become more resilient and creative. When people feel their actual experience is acknowledged—not dismissed or ignored—they’re more willing to share problems early, more likely to collaborate authentically, and less likely to waste energy on interpersonal drama.

But here’s the systemic insight: attending to needs actually reduces the total number of unmet needs in the system. When people feel genuinely seen and understood, many of their surface-level needs simply dissolve. The need for constant reassurance, the need to prove themselves, the need to defend their position—these often evaporate when the deeper need for recognition is met through quality attention.

The Antimatter Principle creates a positive feedback loop: the more you attend to people’s real needs, the fewer needs there are to attend to.

Generate Unexpected Connections: The Pattern Across Domains

The Antimatter Principle appears in surprising places once you know what to look for:

In medicine: The most effective doctors often aren’t those with the most technical knowledge but those who can attend to patients as whole people. Cf. Compassionomics. When patients feel truly seen and understood, their healing often accelerates in ways that can’t be explained by treatment protocols alone.

In education: Students learn best from teachers who can attend to where they actually are rather than where the curriculum says they should be. The attention to their real state of understanding often matters more than the quality of instruction.

In teambuilding: The highest-performing teams often have folks who attend to what’s actually happening rather than what should be happening. When people feel their real challenges and constraints are understood, they become more resourceful and creative.

In customer service: Companies that train staff to attend to customers’ actual experience rather than just solving problems often create deeper loyalty and fewer repeat complaints.

In activism: Social movements that attend to people’s real lived experience rather than telling them what they should think or feel often create more lasting change.

The pattern reveals something profound: in every domain, attending to what’s actually present rather than what you think should be present unlocks human potential in ways that direct intervention often can’t.

Develop Metacognitive Awareness: Thinking About How We Think About Needs

Most people have never examined their own patterns around needs and attending. Start noticing:

Your attending quality: When someone shares something important with you, where does your attention actually go? Are you listening to understand their experience, or are you scanning for how to respond? Are you present with what they’re saying, or are you already formulating advice?

Your need-meeting assumptions: When you think about helping someone, what do you automatically assume they need things? Do you listen for their actual experience, or do you project your own solutions onto their situation?

Your resistance patterns: What makes you want to avoid attending to someone? Is it fear of being overwhelmed? Worry that you won’t know what to do? The belief that their problems are their responsibility? Misanthropy? Understanding your resistance helps you recognise when the antimatter principle might be most needed.

Your agenda-detection: Notice when you slip from paying attention to someone’s actual experience into trying to change their experience. This shift from presence to agenda often happens unconsciously but dramatically changes the quality of interaction.

The metacognitive insight is that most people think attending to needs means taking on burdens, when it actually means offering a quality of presence that often lightens burdens—for both people involved.

Build Comprehensive Mental Models: How the Antimatter Principle Actually Functions

To apply the Antimatter Principle effectively, you need to understand the way it operates:

The Recognition Layer: Most human suffering comes from feeling unseen or misunderstood. When you attend to someone’s actual experience without trying to change it, you provide recognition that often addresses the root of their distress rather than just the symptoms.

The Safety Layer: Real attending creates psychological support—the sense that it’s okay to be exactly as you are right now. This support often allows people’s natural resilience and problem-solving capacity to emerge.

The Meaning Layer: When someone attends to your experience, they’re communicating that your experience matters—that you matter. This addresses Frankl’s fundamental need for significance, which often underlies surface-level complaints.

The Agency Layer: Attending without trying to fix preserves people’s sense of agency. You’re not taking over their problems; you’re simply witnessing their capacity to handle their own experience.

The Connection Layer: Quality attention creates genuine connection that doesn’t depend on problem-solving or advice-giving. This connection itself is often what people most need, even when they think they need something else.

The Efficiency Layer: Paradoxically, attending to needs often resolves them more quickly than trying to meet them directly. When people feel truly seen, they often discover their own solutions or realise that what they thought they needed isn’t actually what they needed.

The Practical Application

The Antimatter Principle isn’t about becoming everyone’s counsellor. It’s about recognising that in your daily interactions—with family, colleagues, friends, even strangers—the quality of your attention always matters more than the content of your response.

When someone shares a difficulty, instead of immediately offering solutions, maybe try attending to their actual experience: ‘That sounds really challenging’ or ‘I can see why that would be frustrating’ or simply ‘Tell me more about that.’

When someone seems upset, instead of trying to cheer them up or solve their problem, try attending to where they actually are: ‘This seems really important to you’ or ‘I can see this is affecting you deeply.’

The shift is subtle but profound: from ‘How can I fix this?’ to ‘How can I be present with this?’ From ‘What should I do?’ to ‘How can I attend to what’s actually happening here?’

Why This Works

The Antimatter Principle works because it addresses what people most fundamentally need: to know that their experience matters to someone else. When you attend to someone without trying to change them, you meet this deepest need completely.

Most of our surface-level needs—for advice, solutions, comfort, reassurance—are often proxies for this deeper need to be seen and understood. When the deeper need is met through quality attention, the surface needs often dissolve naturally.

Nobody needs to have their needs attended to—because when someone truly attends to you as you are, you discover that what you most needed was simply to be seen, understood, and recognised as mattering. The attending itself completes something that no amount of problem-solving or advice-giving ever could.

What Is This Blog About? Making Work Joyful!

My thanks to all those readers who find things of value here. At its heart, this blog is about one essential question: How do we make our time at work more joyful?

Not just tolerable. Not just productive. Joyful.

Semper mirabilis — making life more wonderful. That’s the mission that drives everything I explore here, and work, being such a significant part of our lives, deserves that same wonderful transformation.

What You’ll Find Here

Each post I write approaches this central theme from a different direction. You might read about the team that discovered how vulnerability transformed their collaboration, or the office that revolutionised their dynamic with a simple change to how they run meetings. Sometimes I explore the science behind motivation, other times I share practical strategies you can implement tomorrow.

The angles are varied because joy at work is multifaceted. It emerges from meaningful relationships, engaging challenges, personal growth, recognition, autonomy, assumptions, beliefs, and a dozen other factors that interact in unique ways for each person and each organisation.

My Central Mission

Every post you’ll find here adds another angle to this theme. Whether I’m exploring the small rituals that transform a mundane Tuesday into something meaningful, examining how teams can create genuine connection, or diving into the psychology of flow states, it all comes back to the same core belief I hold: work doesn’t have to be something we endure.

Joy at work isn’t about ping pong tables or free snacks—though those don’t hurt. It’s about finding genuine satisfaction in what we do, creating environments where people can thrive, and discovering those moments when work feels less like work and more like purpose in action.

Richard Sheridan captured this beautifully in ‘Joy, Inc.’ when he wrote about building a company culture where joy isn’t just an occasional byproduct—it’s the deliberate, measurable objective. His work at Menlo Innovations proves that businesses can be both profitable and joyful, that these aren’t competing objectives but truly complementary ones.

Why Joy Matters

We spend roughly a third of our adult lives working. That’s too much time to spend feeling drained, disconnected, or simply counting down the hours until we can live our ‘real’ lives. Joy at work isn’t a luxury—it’s a necessity for a life well-lived.

When work becomes joyful, everything shifts. Problems become puzzles to solve rather than burdens to bear. Colleagues become collaborators rather than competitors. Monday mornings transform from something to dread into something to anticipate.

An Ongoing Conversation

This isn’t about me preaching a single philosophy or selling a miracle cure. It’s about building a community of people who believe work can be better—and who are willing to experiment, share, and learn together.

Your insights matter here. The comment sections often become the most valuable part of each post I write, where readers share what’s working in their workplaces, what isn’t, and what they’re trying next.

So whether you’re looking to transform your company culture, trying to support your team better, or someone simply seeking more fulfilment in your daily work life, you’ll find something here. Each post I publish is another piece of the larger puzzle: how to make the place where we spend so much of our lives a source of joy rather than just a paycheck.

Because life’s too short for joyless work.

Spread the Joy

If you’ve found something valuable here, please don’t keep it to yourself. Share this blog with colleagues, friends, and anyone else who might benefit from a more joyful approach to work. Forward posts that resonate with you, discuss ideas from here in your team meetings, or simply mention what I’m writing about to someone who’s struggling to find meaning in their Monday mornings.

The more people we reach with these ideas, the more workplaces we transform. Joy at work spreads—and it starts with conversations like the ones I hope we’re having here. Help build a movement where joyful work becomes the norm, not the exception.

Folks Matter™: A Human-Centered Approach to Business Success

In a business world dominated by metrics, margins, and market share, one fundamental question often gets overlooked: Do folks matter? This post provides a comprehensive answer—not just affirming that yes, folks absolutely do matter, but demonstrating why human relationships form the essential foundation for sustainable business success.

Introduction

Drawing on research from organisations like Gallup and insights from management thinkers like Peter Drucker, we explore how interpersonal connections determine which strategies succeed and which fail, regardless of how brilliant they appear on paper. The Folks Matter™ framework offers a practical approach to business strategy that places relationships at the centre rather than treating them as secondary considerations, showing how this people-centred philosophy translates into tangible competitive advantage.

The 14 Principles of the Folks Matter™ Framework

1. Relationship-Centred Approach

At the core of any successful organisation lies its interpersonal relationships—the connections that enable and energise collaborative work and innovation. The Folks Matter™ approach recognises this fundamental truth, putting meaningful human bonds at the heart of strategic thinking.

True folks-centred organisations transcend simplistic “people first” slogans. They require “having a genuine intention to help each person succeed and find fulfillment at work, along with a disciplined approach to effectively choosing and exhibiting the behaviours appropriate for the individual and the context.”

Research demonstrates this approach drives tangible results. According to Gallup, “teams buzzing with engagement see a 21% boost in profitability,” while companies that excel in developing their people are “1.5 times more likely to be celebrated as pinnacle performers in their industry.”

2. Collective Mindset Awareness

Beneath the surface of every organisation lies an invisible web of assumptions, beliefs, and mental models that profoundly shapes how folks work together. This collective mindset—what Edgar Schein called the “basic underlying assumptions” at the deepest level of organisational culture—determines which strategies succeed and which fail.

The renowned management thinker Peter Drucker understood this dynamic perfectly when he allegedly observed that “culture eats strategy for breakfast.” This insight emphasises the futility of brilliant strategies that clash with an organisation’s deeply held beliefs.

When an organisation understands its current cultural paradigm, it can deliberately evolve this mindset to support strategic priorities. Only with this level of cultural consciousness can an organisation ensure its strategy has a genuine chance of success.

3. Change Facilitation Capability

Implementing effective change strategies holds crucial importance, as “some 70% of all organisational change transformations fail, according to McKinsey” while “Gartner begs to differ, with research that shows 50% of organisational change efforts are considered a clear failure.”

Effective change facilitation in a Folks Matter™ organisation includes:

  • Clear communication about the vision and rationale for change
  • Involvement of all stakeholders in planning and implementation
  • Recognition of both emotional and logical aspects of the change process
  • Systematic approach using proven change models appropriate to the situation
  • Ongoing reinforcement to prevent reversion to previous patterns

4. Inclusive Stakeholder Approach

Instead of focusing narrowly on shareholders or even just customers, successful Folks Matter™ businesses create value for all the folks in their ecosystem:

  • Customers receive products and services that genuinely improve their lives
  • Employees find meaningful work, fair compensation, and opportunities for growth
  • Suppliers engage in mutually beneficial partnerships that promote innovation
  • Communities experience positive environmental and social impacts
  • Shareholders receive sustainable returns that reflect real value creation

Companies like Patagonia and Ben & Jerry’s have demonstrated that this inclusive approach creates more resilient businesses with stronger customer loyalty, higher employee engagement, and ultimately better long-term financial performance.

5. Fellowship-Based Collaboration

Organisations that embrace the Folks Matter™ philosophy thrive over the long term by adopting collective approaches to working:

  • In non-hierarchical organisations, “teams become self-supporting, decision-making is decentralised, and leadership is shared, not imposed from above”
  • Fellowship models prioritise “shared responsibility, trust, and open communication, fostering an environment conducive to creativity, inclusion, and effective decision-making”
  • People “communicate directly with each other and are accountable to fellow members of multi-disciplined teams” with guidance emerging organically

6. Joy-Centred Workplace Culture

Folks Matter™ organisations create environments where people find meaning and satisfaction:

  • As demonstrated at Menlo Innovations, joy can exist as “the core belief of our workplace” that “defines what we do and how we do it”
  • People find joy in their work “when they feel like they are doing something meaningful” and teams provide “an inspiring vision and clear expectations”
  • Workplaces focus on creating environments “filled with camaraderie, human energy, creativity, and productivity” rather than fear and ambiguity

7. Systems Thinking Integration

Folks Matter™ organisations view themselves as interconnected systems rather than isolated departments:

  • Systems thinking examines the circular interconnections that bind enterprise functions into an integrated whole
  • Decision-makers consider how changes in one area will impact other parts of the organisation
  • Problems appear holistically rather than in isolation
  • Teams recognise that optimising individual parts may not optimise the whole system of folks working together

8. Evidence-Based Operations

Effective Folks Matter™ businesses replace gut feelings with measurable insights:

  • Consistent metrics that track both outcomes for Folks That Matter™ and business performance
  • Regular review cycles to spot problems early and adjust course
  • Transparent sharing of key information across the organisation
  • Testing of major initiatives before full rollout

9. Constraint Recognition and Removal

High-performing Folks Matter™ businesses identify and address the factors limiting their growth:

  • The Theory of Constraints views systems as a chain limited by its weakest link
  • Resources focus on identifying and eliminating the current constraint
  • Once resolved, the team moves to the next constraint in a process of continuous improvement
  • The core concept holds that “total process throughput can only improve when the constraint improves”

10. Adaptive Team Structures

Rather than traditional department silos, Folks Matter™ organisations create team structures that can adapt quickly:

  • Small, cross-functional teams with end-to-end responsibility for specific products or customers
  • Minimal management layers to speed up decision-making
  • Clear authority for teams to solve problems without constant approvals
  • Teams organised around customer journeys rather than internal functions

The Peach model provides a practical framework here – pushing decision-making to the edges of the organisation where folks interact directly with customers and markets, rather than concentrating it at headquarters.

11. Focus Management

Successful Folks Matter™ organisations carefully consider which folks and needs to prioritise:

  • Cost of Focus represents the potential consequences of failing to include all relevant Folks That Matter™
  • Unlike Cost of Delay which has incremental financial impacts, Cost of Focus often has binary outcomes
  • Organisations identify which folks hold true critical importance to success, not just those who speak loudest
  • Teams balance between including too few perspectives (risking rejection) and too many (diffusing focus)

12. Time Value Awareness

Strategic Folks Matter™ organisations understand the financial impact of time:

  • Cost of delay exists as “a prioritisation framework that helps a business quantify the economic value of completing a project sooner as opposed to later”
  • Teams calculate the potential revenue or value lost by delaying key initiatives
  • Projects receive prioritisation based on their economic impact rather than politics or tradition
  • People develop a sense of urgency around high-impact initiatives

13. Collective Decision Processes

Successful Folks Matter™ organisations adjust their approach based on:

  • Fast feedback loops from all Folks That Matter™, especially customers and front-line employees
  • Regular review of industry trends and competitive moves
  • Willingness to abandon unsuccessful strategies quickly
  • Learning systems that capture and share successful approaches across all folks

14. Collaborative Innovation Infrastructure

Folks Matter™ companies that consistently create new value build systems for innovation:

  • Dedicated processes to capture and evaluate new ideas from all folks
  • Regular testing of small experiments before large investments
  • Partnerships with outside organisations to access new capabilities
  • Focus on innovations that benefit multiple groups of Folks That Matter™

Conclusion

The Folks Matter™ approach places human relationships at the centre while balancing the needs of all stakeholders, maintaining flexible structures, evidence-based operations, systems thinking, constraint management, focus awareness, and fellowship-centred collaborative cultures.

As the saying commonly attributed to Peter Drucker reminds us, “Culture eats strategy for breakfast.” This means that “no matter how well-designed your strategic plan is, it will fall flat unless your team shares the appropriate culture” to implement it successfully. The most successful Folks Matter™ organisations don’t pit culture against strategy but ensure they work in harmony, with each supporting and reinforcing the other.

Further Reading

Further Reading

Beer, M., & Nohria, N. (2000). Cracking the code of change. Harvard Business Review, 78(3), 133-141.

Corporate Governance Institute. (2023). What does culture eats strategy for breakfast mean? https://www.thecorporategovernanceinstitute.com/insights/lexicon/what-does-culture-eats-strategy-for-breakfast-mean/

Gallup. (2018). Employee engagement on the rise in the U.S. Gallup News. https://news.gallup.com/poll/241649/employee-engagement-rise.aspx

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

Jabian Consulting. (2023). Culture eats strategy for breakfast and transformation for lunch. The Jabian Journal. https://journal.jabian.com/culture-eats-strategy-for-breakfast-and-transformation-for-lunch/

Lean Production. (n.d.). Theory of constraints (TOC). https://www.leanproduction.com/theory-of-constraints/

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

The foundational text on Organisational Psychotherapy, “Hearts over Diamonds” introduces the concept of bringing psychotherapy techniques into organisational settings. Marshall argues that interpersonal relationships are at the heart of successful business, and presents a framework for transformational change that prioritises human connections over traditional management approaches. This book aims to support organisations seeking to become more humane, people-oriented, and productive.

Marshall, R. W. (2021). Memeology: Surfacing and reflecting on the organisation’s collective assumptions and beliefs. Falling Blossoms. https://leanpub.com/memeology

A self-help guide for organisations seeking to understand their culture at a deeper level. “Memeology” provides practical techniques for surfacing and examining collective assumptions and beliefs (or “memes”) that often unconsciously drive organisational behaviour. The book offers methodical approaches for unearthing these cultural patterns, helping organisations recognise how their unexamined beliefs may be limiting their effectiveness and preventing meaningful change.

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

Based on Marshall’s experience building and running a highly successful software development company, “Quintessence” describes a path toward becoming a highly effective software development organisation. Rather than prescribing specific practices or methodologies, the book encourages organisations to find their own path to excellence by leveraging the principles of Organisational Psychotherapy in tech business contexts.

McKinsey & Company. (2019). Why do most transformations fail? A conversation with Harry Robinson. https://www.mckinsey.com/capabilities/transformation/our-insights/why-do-most-transformations-fail-a-conversation-with-harry-robinson

Quote Investigator. (2017). Quote origin: Culture eats strategy for breakfast. https://quoteinvestigator.com/2017/05/23/culture-eats/

Change Management – Just Not As You Know It

The Unspoken Revolution: Change From Within

“Traditional change management pushes initiatives down. Successful change management bubbles up.”

Traditional change approaches create waterfalls of initiatives that cascade from executive decisions through management layers to frontline implementation. Whilst leadership can mandate new processes and structures, lasting and successful transformations follow a completely different path – change emerges organically from the front line up, following natural human networks rather than organisational hierarchies.

Traditional change management suffers from a profound misunderstanding: it casts frontline workers as mere recipients of change rather than its potential architects. The sterile boardroom vision ignores that those closted to the work – and to the customer – hold the real practical wisdom needed for meaningful transformation. While executives may decree change from above, it’s the quiet conversations in corridors and canteens that decide its fate. True organisational renewal emerges precisely where strategic aspiration collides with everyday reality—often messy, always human, and infinitely more complex than any change roadmap suggests.

Beyond the Boardroom: Where Change Actually Lives

Change initiatives born solely in boardrooms and consultants’ meetings often arrive stillborn on the shop floor. The polished presentations and ambitious roadmaps rarely survive first contact with operational reality. What executives perceive as “resistance” is typically the organisation’s immune system responding naturally to foreign bodies introduced without context.

True transformation isn’t about overcoming this resistance—it’s about tapping into the currents of change already flowing beneath the organisation’s surface. These underground streams of innovation exist in every company, typically found wherever frontline staff have developed workarounds to broken processes or created informal solutions to customer pain points. It’s precisely in these spaces where unspoken beliefs and tacit knowledge trump official doctrine, the officially sanctioned collective assumptions and beliefs of the organisation —where what people actually do diverges from what policy dictates they should do. The real cultural operating system of the organisation lives in these gaps between the official and the actual.

The Quiet Authority of Informal Networks

Formal hierarchies dictate reporting relationships, but informal networks determine how work actually gets done. These invisible influence structures—who people trust, who they go to with problems, whose opinion carries weight—form the true circulatory system of organisational change.

Conventional change management focuses exclusively on engaging formal leadership, overlooking the critical role of what we might call “credibility leaders”—those fellows at any level whose endorsement can legitimise new approaches amongst their peers. These fellows aren’t necessarily managers but are the organisational equivalent of trusted neighbours whose recommendation carries more weight than any corporate communication.

Growing Change Rather Than Imposing It

Perhaps the most fundamental shift in this approach is viewing change not as something to be engineered and implemented but as something to be cultivated and grown. This horticultural rather than architectural metaphor recognises that organisations, like gardens, are living systems with their own internal logic and natural tendencies.

The role of change leadership in this model becomes not about designing perfect solutions but about creating fertile conditions where better ways of working can naturally emerge and spread. It involves identifying where positive deviance already exists, understanding the underground collective assumptions and beliefs that make it work, and creating protected spaces where these approaches can be refined and eventually shared.

Measuring Success Differently

In top-down change, success is typically measured by milestones, deliverables, and compliance metrics. In organic change, success is measured by the voluntary adoption and adaptation of new approaches. The question shifts from “Have we implemented the change?” to “Is the change implementing itself?”

This requires a different level of patience and a tolerance for messiness. Organic change rarely follows neat timelines or produces predictable outcomes. But what it sacrifices in control, it gains in sustainability. Changes that emerge organically become part of the organisation’s DNA rather than foreign implants that will be rejected as soon as attention shifts elsewhere.

Bringing It All Together: A New Approach to Change Management

What if we’ve been asking the wrong questions about organisational change all along? What if the choice between top-down direction and bottom-up emergence is a false dichotomy? Could the most powerful transformations emerge from the dynamic tension between strategic vision and operational reality?

How often have we seen how the most brilliant change strategies falter when disconnected from frontline experience? And equally, how promising grassroots innovations wither without strategic sponsorship? What might happen if we created organisational systems where ideas, concerns and solutions could flow freely between levels—where executives and frontline staff engaged in genuine dialogue rather than parallel and conflicting monologues?

Is it possible that what we need is an approach to change management that works? To dismantle structured change management entirely and to fundamentally reimagine it? What if leaders stopped seeing themselves as architects imposing blueprints and started seeing themselves as gardeners creating conditions for natural growth? Or as pollsters seeking the great ideas from everyone across the organisation?

Could it be that the most subversive act in modern organisational change is disarmingly simple: what if we treated those who do the work as the foremost experts on how that work might evolve? What transformations might become possible then? And how much more likely would it be that such change meets the needs of all the Folks That Matter™?

 

Altruism and Egotism

Consider a fascinating paradox at the heart of human behaviour that has perplexed philosophers for centuries: the curious relationship between altruism and egotism. At first glance, these concepts appear diametrically opposed – one representing selfless concern for others, the other an excessive preoccupation with oneself. Yet upon closer examination, the boundary between these seemingly contradictory impulses becomes surprisingly blurred.

The False Dichotomy

Most of us have been raised to believe that altruism represents the noblest of human virtues. We celebrate those who sacrifice for others, who give without expectation of return, who place the welfare of the collective above their individual desires. Conversely, we tend to view egotism with suspicion – the self-serving individual who prioritises personal gain is often cast as the villain in our cultural narratives.

But what if this dichotomy is fundamentally flawed? What if, rather than representing opposite ends of a moral spectrum, altruism and egotism are inextricably linked – perhaps even two sides of the same psychological coin?

The Selfish Nature of Selflessness

When we perform an act of kindness, we often experience what psychologists call a “helper’s high” – a surge of positive emotions and satisfaction. This neurochemical reward system suggests that altruistic behaviour may serve an evolutionary function by reinforcing prosocial actions that benefit the group. In essence, we help others because it feels good to us to do so.

Consider the philanthropist who donates millions to charity. While their generosity undoubtedly benefits society, we cannot ignore the status, recognition, and sense of moral superiority that may accompany such gestures. Is this truly selfless, or might there be an element of ego gratification involved?

The Social Capital of Giving

In communities across Britain, volunteering and charitable work serve not only to support those in need but also to establish one’s reputation as a good citizen. The social capital gained through perceived altruism can translate into tangible benefits – expanded networks, professional opportunities, and enhanced social standing.

This is not to suggest that all charitable acts are merely self-serving calculations, but rather to acknowledge the complex motivations that drive our behaviour. Even when we believe ourselves to be acting purely out of concern for others, subconscious ego-driven factors are also at play.

The Egotism of Self-Sacrifice

Perhaps most intriguing is the way extreme altruism can itself become a form of egotism. The individual who martyrs themselves for a cause may be driven by a narrative in which they are the hero – a narrative that places them at the centre of importance. The parent who sacrifices everything for their children might be constructing an identity built around this sacrifice, one that provides them with meaning and purpose.

Indeed, the very act of defining oneself through one’s altruism represents a form of self-construction that is inseparable from ego.

Finding Balance

Understanding the intertwined nature of altruism and egotism need not lead to cynicism about human goodness. Rather, it invites us to approach our motivations with greater honesty and nuance. Perhaps true virtue lies not in the impossible quest for pure selflessness, but in the conscious alignment of our self-interest with the welfare of others.

The most sustainable forms of giving are those that acknowledge both the benefit to others and the satisfaction we derive from contributing. This balance allows us to nurture our communities while also meeting our own psychological needs for purpose, connection and meaning.

As we navigate the moral complexity of human nature, perhaps we might consider that the most enlightened approach is neither the denial of self-interest nor its unbridled pursuit, but rather the cultivation of an expanded sense of self – one that recognises our fundamental interconnectedness and finds personal fulfilment in anonymously contributing to collective wellbeing.

In the words of Oscar Wilde, “Selfishness is not living as one wishes to live, it is asking others to live as one wishes them to live.” True generosity, then, might be found not in the absence of ego, but in its thoughtful evolution.

The Oxymoron of Effective Leadership

The Leadership Paradox

Our modern obsession with leadership frameworks and development ironically undermines the very outcomes it seeks to achieve. The notion of ‘effective leadership’ has become something of a sacred cow in modern organisations. We’re bombarded with leadership frameworks, leadership courses, and leadership gurus promising to unlock the secrets of steering teams towards success. Yet there’s a fundamental contradiction at play: the very concept of leadership often undermines the most powerful drivers of human achievement.

The Power of Intrinsic Motivation

Consider for a moment what truly motivates people to do their best work. Time and again, research has shown that intrinsic motivation—that inner fire that drives us to excel—far outstrips any external prodding or direction. When individuals pursue mastery of their craft for its own sake, when they’re granted genuine autonomy over their work, and when they share a compelling common purpose with their colleagues, magic happens.

The Leadership Suppression Effect

The trouble with traditional leadership is that it frequently tramples these delicate flowers of intrinsic motivation. Even the most well-meaning leaders can inadvertently suppress the natural emergence of collaborative intelligence within their teams. By attempting to ‘lead’ from the top down, they create a subtle but pervasive dependency that dampens individual initiative and collective wisdom.

The Fellowship Alternative

Take the concept of fellowship, for instance. When people genuinely choose to work together, pooling their diverse talents and perspectives without hierarchical constraints, they often achieve remarkable outcomes. Silicon Valley’s early garage startups, Wikipedia’s vast knowledge commons, and countless open-source software projects stand testament to the power of voluntary collaboration untethered from traditional leadership structures.

The Futility of Leadership Development

The irony is that the more organisations invest in developing ‘better leaders’, the more they may be missing the point entirely. Perhaps the most effective form of leadership is the art of stepping back—creating spaces where intrinsic motivation can flourish, where fellowship can emerge organically, and where people can unite around shared purposes without the heavy hand of authority.

Coordination Without Control

This isn’t to suggest that organisations should descend into chaos or that coordination is unnecessary. Rather, it’s about recognising that the traditional leadership paradigm is fundamentally at odds with unleashing human potential. The most valuable role for those in positions of authority might be to focus on removing obstacles, fostering conditions for autonomous collaboration, and then having the wisdom to get out of the way.

Reimagining Organisational Structure

The Self-Organising Future

The truly revolutionary organisations of tomorrow might well be those that dare to question the leadership orthodoxy altogether. Instead of asking how to develop better leaders, perhaps we should be asking how to nurture environments where leadership becomes entirely unnecessary—where intrinsic motivation, fellowship, and shared purpose can work their magic unimpeded.

Conclusion: The Garden Metaphor

Natural Growth vs Directed Control

The oxymoron of effective leadership lies in this paradox: the most effective form of leadership might be its own gradual dissolution. In a world crying out for innovation, adaptation, and meaningful collaboration, isn’t it time to retire our obsession with leadership and embrace the messier but more authentic power of truly self-organising human systems? At least, is it time to surfaced our assumptions about leadership and reflect on more effective alternatives?

After all, as any gardener knows, the most vibrant gardens aren’t those where each plant is meticulously directed, but those where the right conditions allow natural growth to flourish. The same is true for human potential in our organisations.

The Ripple Effect: How Small Actions Create Lasting Impact

Understanding the Power of Positive Ripples

The concept of ripple effects in business settings mirrors that of a small stone dropped into still water. Each action, no matter how seemingly insignificant, has the potential to create waves of influence that extend far beyond its initial impact. In the workplace. These ripples can transform company culture, boost productivity, and forge stronger relationships amongst colleagues, ultimately flowing into personal lives and broader society.

Digital Evolution: A Natural Progression

Unlike the often disruptive nature of digital transformation, digital evolution represents a more organic approach to business improvement. This gradual, iterative process creates beneficial ripple effects throughout an organisation. When one team successfully adopts new shared assumptions and beliefs, their positive experiences naturally influence other folks to embrace similar changes. This evolutionary approach reduces resistance and creates sustainable progress.

Adaptive Integration

The ripple effects of digital evolution manifest through natural adoption patterns. As colleagues witness the benefits of new ways of thinking asnd acting, they become more receptive to change. This organic spread of digital literacy and acceptance creates a more resilient and adaptable workplace culture, with employees often bringing these more effective assumptions and beliefs into their personal lives and community activities.

Workplace Dynamics and Chain Reactions

When examining workplace dynamics, it becomes evident that beneficial ripple effects often start with small shifts. Someone who consistently offers genuine praise might inspire folks across the organisation to adopt similar practices. This cascading effect can gradually reshape the organisation’s approach to recognition and motivation, with employees often adopting these positive communication patterns in their personal relationships both inside and outside the workplace.

The Business Case for Positive Actions

Financial Benefits

Positive ripple effects frequently translate into tangible business outcomes. For instance, when a company prioritises employee wellbeing, the initial investment often yields substantial returns through reduced sick leave, increased productivity, and enhanced talent retention. These improvements cascade through the whole organisation, ultimately strengthening the organisation’s bottom line and contributing to employees’ financial security and life satisfaction.

Innovation and Creativity

When team members feel valued and supported, they’re more likely to share innovative ideas. This openness can spark a chain reaction of creative thinking across the organisation, leading to breakthrough solutions and competitive advantages in the marketplace. This enhanced creativity often spills over into personal pursuits and community initiatives, too.

Nurturing Professional Relationships

Building Trust Networks

Trust-building creates some of the most powerful ripple effects in busainess settings. When one person demonstrates reliability and transparency, it encourages reciprocal behaviour from colleagues. This mutual trust gradually extends throughout the organisation, fostering a more collaborative work (CKW) environment and often improving personal relationship dynamics.

Mentorship Multiplier Effect

Perhaps one of the most profound examples of beneficial ripple effects lies in mentorship. When experienced folks invest time in guiding others, they create a multiplier effect. Their mentees often go on to become mentors themselves, perpetuating a cycle of knowledge-sharing and development that extends even into community mentoring and family relationships.

The Social Ripple Effect

From Workplace to Home Life

Individual and team growth and positive workplace experiences significantly influence home life. Improved communication skills, enhanced emotional intelligence, and better stress management techniques learned at work naturally transfer to personal relationships. Parents might apply collaborative problem-solving (CKW) approaches with their children, while partners might adopt more effective listening strategies in their relationships.

Community Impact

As people develop stronger interpersonal skills and positive habits at work, they often become more engaged community members. The confidence and capabilities gained in workplace settings can lead to increased civic participation, volunteer work, and community fellowship roles.

Digital Enablement of Positive Ripples

The evolutionary approach to digital adoption amplifies positive ripple effects through enhanced connectivity and collaboration tools. Virtual mentoring platforms, digital collaboration tools, and collaborative workspaces extend the reach and impact of beneficial actions across geographical boundaries and organisational hierarchies.

Practical Implementation Strategies

To harness the power of positive ripple effects, organisations can implement several key strategies:

  • Start with authentic role-model behaviours that demonstrate desired values and practices. These actions naturally cascade through the organisation.
  • Embrace digital evolution by allowing teams to naturally discover and adopt beneficial changes at their own pace.
  • Create opportunities for cross-departmental collaboration, allowing positive practices to spread organically throughout the organisation.
  • Establish programmes that highlight and celebrate instances of positive impact, encouraging others to emulate beneficial behaviours.

Measuring Long-term Impact

While immediate effects might be readily apparent, the true value of positive ripple effects often emerges over time. Organisations might choose to implement long-term monitoring to track how initial actions influence various aspects of business performance, workplace culture, and broader social impact.

Looking Beyond the Workplace

The influence of positive ripple effects extends far beyond office walls, as exemplified by the remarkable legacy of DECUS (Digital Equipment Computer Users’ Society). This volunteer-driven organisation, which began as a simple user group for Digital Equipment Corporation’s customers, evolved into one of the most influential technical communities of its time. DECUS demonstrates how workplace initiatives can catalyse broader social impact.

The DECUS model showed how inter-personal relationships formed through work-related activities could blossom into lasting networks of innovation, knowledge sharing and friendship / fellowship. Members who initially joined to solve their own workplace challenges ended up creating educational programmes, developing open-source solutions, and fostering a culture of collaborative problem-solving that extended well beyond their company roles. Their technical symposia became legendary gathering places where ideas freely flowed between academia, industry, and hobbyist communities.

Much like DECUS’s ripple effects transformed the 1980s mini-computing landscape, today’s improved workplace relationships lead to enhanced customer service, stronger community engagement, and better work-life balance. When DECUS members brought their collaborative ethos back to their organisations, they created positive cycles that reinforced and amplified the initial beneficial actions. The society’s influence extended into members’ personal lives, with many participants forming lifelong friendships and mentoring relationships that transcended their business connections.

This historical example remains relevant today, as we sometimes see similar patterns in modern technical communities and professional networks. These benefits continue to contribute to societal wellbeing and social progress, just as DECUS’s volunteer-driven ethos helped democratise access to computing knowledge and expertise. The organisation’s legacy reminds us that when workplace initiatives are structured to encourage openness, collaboration, and community engagement, their positive impact can ripple throughout society for generations to come.

Conclusion

Understanding and intentionally creating positive ripple effects represents a powerful approach to organisational development and societal advancement. By recognising that every action has the potential for widespread impact, folks can make more informed choices about their behaviour and initiatives. When combined with a measured approach to digital evolution, these positive actions can transform workplace cultures, strengthen business outcomes, and create lasting beneficial change throughout inter-business networks, personal lives, and society at large.

Story: The Dry Kettle

Sarah Willis had been a culture consultant for fifteen years, but she still marveled at how the smallest details could reveal the deepest truths about an organisation. Today, she was shadowing the product team at TechFlow Solutions, a mid-sized software company that had hired her to help with their declining team performance and rising turnover rates.

At 10:30 AM, she observed Angela, a junior developer, approach the break room’s electric kettle. Angela lifted it, found it empty, and sighed. She filled it herself, pressed the button, and waited the full four minutes for it to boil, drumming her fingers on the counter. Sarah noticed Angela checking her phone repeatedly, clearly anxious about being away from her desk.

Throughout the day, Sarah witnessed this scene repeat five more times with different team members. Each person found an empty kettle, and each person showed the same mix of resignation and frustration. Most telling was that several senior team members walked right past the empty kettle without filling it, even when they had just emptied it themselves.

In her notes, Sarah wrote: “Dry kettle syndrome – chronic pattern of individual convenience over collective benefit. Team members consistently prioritise personal time savings over colleagues’ needs. No evidence of malice, but clear indication of systemic self-focus.”

During her feedback session with TechFlow’s leadership team, Sarah leaned forward in her chair. “I noticed something interesting in the break room today,” she began softly. “Have you ever paid attention to the kettle?”

The leadership team exchanged puzzled glances. Sarah continued, “What do you imagine it means when team members consistently find it empty? What patterns might that reveal about how people work together?”

The CTO shifted uncomfortably. “It’s just a kettle,” he said, but his tone suggested uncertainty.

“Is it though?” Sarah asked gently. “When you think about your highest-performing teams from the past, how did people tend to look after shared spaces and resources? What was different about how they treated each other’s needs?”

She paused, allowing the silence to deepen their reflection. “What would it mean if someone always made sure the kettle was full? How might that same mindset show up in other aspects of team collaboration?”

The room grew quiet as the implications sank in. Finally, the Head of Engineering spoke up, her voice thoughtful. “It’s about anticipating others’ needs, isn’t it? The same way we should be thinking ahead in our code reviews and documentation.”

Sarah nodded encouragingly. “And how might we begin to nurture that kind of awareness?”

Three months later, Sarah received an email from TechFlow’s HR director. The message included a photo of their break room kettle, now adorned with colorful sticky notes where team members left encouraging messages for each other. The director wrote: “The kettle is always full now, and surprisingly, so are our sprint commitments. Thank you for helping us see what was really empty.”

A Path to Better Team Communication

The Power of Communication Preferences

Communication lies at the heart of effective teamwork, yet we often overlook how differently each of us prefers to communicate, and be communicated with.

Many’s the time I’ve invited teams to spend a day exploring their individual communications styles using Wilson Learning’s Social Styles model and approach. The aim has always been simple yet profound: to help team members equip themselves with genuine empathy for each other’s communications preferences. At the heart of Social Styles lies a fundamental observation—when we tailor our communication style to match the preferences of our recipient, we’re more likely to be understood – and appreaciated, too.

This insight has proven transformative across many teambuilding workshops, where team members discover not just how they prefer to communicate, but how their fellows’ preferences might differ from their own. Time and again, I’ve watched as understanding dawns and teammates begin to see their past communication challenges in a new light.

The Social Styles Framework Explained

At its core, the Social Styles model recognises that people tend to display consistent patterns in how they prefer to communicate and interact with others. These patterns form distinct styles, each with its own strengths and characteristics. The value of this approach lies in its simplicity: by understanding these patterns, we can adapt our communication with others to better resonate with them.

A Model, Not a Box

It can be helpful to understand that Social Styles is a model—a lens through which we can view and understand communication preferences.

“All models are wrong – some are useful”

~ George Box

 

It’s not meant to pigeonhole individuals into rigid categories. People are complex and adaptable, often displaying different styles in different contexts or combining various aspects of multiple styles. The model serves as a practical tool for understanding and improving communication, not as a definitive categorisation of personality types.

The Four Primary Social Styles

Analytical Style

Analyticals are thoughtful, methodical, and detail-oriented. They prefer facts and data over emotions and tend to approach situations with careful consideration. These individuals value accuracy and logic above speed and often require thorough information before making decisions.

Driver Style

Drivers are direct, decisive, and results-focused. They communicate succinctly and prioritise outcomes over relationships. Time-conscious and task-oriented, Drivers appreciate efficiency and may come across as impatient with lengthy discussions or emotional considerations.

Expressive Style

Expressives are enthusiastic, creative, and people-oriented. They communicate with animation and energy, often using stories and metaphors. These individuals generate ideas readily and prefer big-picture thinking to detailed analysis. They value recognition and opportunities for social interaction.

Amiable Style

Amiables are supportive, patient, and relationship-focused. They excel at creating harmony and building consensus within teams. These individuals prefer cooperative approaches to competitive ones and may take time to build trust before sharing opinions openly.

I’ll add a new section after “The Four Primary Social Styles” and before “The Sixteen Sub-Styles”:

Different Styles, Different Communication Needs

Understanding how each Social Style approaches communication reveals fascinating insights into what different people need from their interactions. These varying needs often explain why what works brilliantly for one colleague might fall completely flat with another.

What Analyticals Need

Analyticals thrive on detail and precision. When communicating with them, they need time to process information, and they appreciate written documentation they can review thoroughly. They’re likely to become frustrated by vague statements or emotional appeals without supporting evidence. In meetings, they tend to need clear agendas and time to prepare their thoughts in advance.

What Drivers Need

Drivers need efficiency and results-focused communication. They appreciate direct approaches that get straight to the point and outline clear outcomes. They become impatient with lengthy preambles or excessive relationship-building conversation. When presenting to Drivers, they need you to lead with conclusions and have supporting details ready only if requested.

What Expressives Need

Expressives need engagement and interaction. They thrive on enthusiasm and appreciate when others share their energy for ideas and possibilities. They need time to explore concepts verbally and often process their thoughts through discussion. In presentations, they need the big picture first and appreciate visual aids and stories that bring concepts to life.

What Amiables Need

Amiables need personal connection and harmony. They appreciate when others take time to build rapport and show genuine interest in their perspectives. They need a safe space to share their thoughts and may require explicit invitation to contribute in group settings. When receiving feedback, they need it delivered with sensitivity and appreciation for their efforts.

The Impact in Practice

Understanding these varying needs transforms everyday workplace interactions. A status update that satisfies a Driver’s need for brevity might leave an Analytical feeling uninformed. Similarly, an Expressive’s enthusiastic brainstorming session might overwhelm an Amiable who needs more time to interact and chat.

The key isn’t to completely reshape our communication style for each interaction, but rather to make adjustments that acknowledge and respect these different needs. For instance, when sharing important news:

  • For Analyticals: Provide detailed written documentation alongside verbal explanations
  • For Drivers: Start with the bottom line, then be ready with supporting details if requested
  • For Expressives: Create opportunities for discussion and exploration of implications
  • For Amiables: Take time to check in personally and ensure they feel comfortable with changes

This understanding leads us to a crucial question for self-reflection: How often do you consciously attend to the communications needs of your team mates, and others? It’s a simple question, yet one that can transform our daily interactions when we pause to consider it regularly.

The Sixteen Sub-Styles: Understanding Blended Characteristics

Just as colours blend to create new shades, Social Styles often combine in unique ways within individuals. Whilst we might have a dominant style, many of us display characteristics of other styles in varying degrees. These combinations, or sub-styles, offer a richer understanding of how we communicate and interact. Think of them as subtle variations that help explain why two ‘Drivers’, for instance, might approach the same interaction rather differently.

Understanding these blends is particularly valuable because it reinforces that we’re not dealing with rigid categories, but rather with fluid combinations of traits and preferences. As you explore these combinations, you might recognise aspects of yourself or your colleagues in several of them—and that’s entirely natural. The sub-styles help us appreciate the nuanced ways in which communication preferences can manifest.

Driver Blends

  • Driver-Driver: Highly assertive and direct, with strong control needs
  • Driver-Analytical: Strategic decision-maker combining speed with analysis
  • Driver-Expressive: Dynamic and persuasive, with strong leadership tendencies
  • Driver-Amiable: Results-focused but maintains awareness of team harmony

Analytical Blends

  • Analytical-Analytical: Extremely detail-oriented and systematic
  • Analytical-Driver: Methodical yet decisive, values efficient processes
  • Analytical-Expressive: Combines careful analysis with creative solutions
  • Analytical-Amiable: Thorough and considerate, builds trust through expertise

Expressive Blends

  • Expressive-Expressive: Highly energetic and socially engaging
  • Expressive-Driver: Charismatic leader who drives for results
  • Expressive-Analytical: Creative problem-solver with attention to detail
  • Expressive-Amiable: Enthusiastic team-builder, focuses on positive relationships

Amiable Blends

  • Amiable-Amiable: Deeply supportive and relationship-focused
  • Amiable-Driver: Balanced approach to task and relationship needs
  • Amiable-Analytical: Patient problem-solver who values harmony
  • Amiable-Expressive: Warm and engaging, builds strong team connections

Style Interactions in Practice

Understanding these nuanced combinations helps teams appreciate the complexity of workplace interactions. For instance, an Analytical-Driver might need to consciously soften their approach when working with an Amiable-Expressive colleague, who may require more personal connection before diving into tasks.

Why Teams Benefit from Style Awareness

Breaking Down Communication Barriers

When team members understand that their colleagues aren’t being deliberately ornery but rather receiving communications through their natural style, tensions often dissolve. A direct communicator might learn to soften their approach with more relationship-oriented colleagues, whilst analytical team members might learn to provide more emotional context when needed.

Building Empathy Through Understanding

The day-long exploration of Social Styles serves as more than just a training exercise—it becomes a shared experience that builds lasting empathy and fellowship. Team members often experience ‘aha’ moments when they realise why past communications may have gone awry.

The Art of Style Flexing

Adapting Without Compromising

The most powerful insight from Social Styles is that we can maintain our authentic selves whilst adjusting our communication approach. This isn’t about changing who we are—it’s about attending to others’ needs and being more effective in how we convey our messages to different audiences.

Practical Applications in Daily Work

Teams who embrace style flexing often report improved outcomes in discussions, where different perspectives are better understood and valued; conflict resolution, as team members recognise triggers and preferences; and decision-making processes, where various approaches to processing information are accommodated.

Impact of Sub-Style Recognition

Understanding these nuanced combinations provides teams with a more sophisticated toolkit for communication. It helps explain why two people who share a primary style might still approach situations differently, leading to more precise adaptations in communication approaches.

Measuring Success

The true measure of success in implementing Social Styles awareness comes not from the workshop day itself, but from the subtle changes that follow. Teams typically report fewer misunderstandings, more productive meetings, and a general sense of improved collaboration and fellowship.

Looking Ahead

As our workplaces become increasingly diverse and complex, the ability to flex one’s communication style becomes not just useful, but essential. The investment in understanding Social Styles continues to pay dividends long after the initial training day, creating more resilient and effective teams.

Conclusion

Many’s the time I’ve witnessed the transformation that occurs when teams grasp the power of Social Styles. The initial scepticism – a common early response – often gives way to genuine appreciation for the differences among team members, and more importantly, for the tools to bridge those differences effectively.This understanding isn’t just a WIBNI or “nice to have”—it’s a crucial element of successful team dynamics. Remember, the goal isn’t to label or limit people, but rather to provide a practical approach for improving communication and understanding across teams, and throughout organisations.

Rossi’s Vision for Organisational Psychotherapy

Following on from my previous post about Peter Rossi’s view on social interventions and his Iron Law of Evaluation, our podcast team has been discussing the post, Rossi’s views, and  the connection with Organisational Psychotherapy.

You can listen to it here.

I would be delighted to hear from you about your thoughts on the topic.

– Bob

As You Like It?

We spend most of our days at work, but how often do we really stop and think about what that means? Our workplace is more than just a physical space—it’s a dynamic environment where human experiences, emotions, and connections come together.

What Truly Matters

For most people, work isn’t about completing tasks or hitting targets. It’s about us—real people with complex inner lives, bringing our whole selves, or not, to a shared space every single day.

Our Fundamental Needs

Feeling Genuinely Understood

At the core, we all need:

  • Our ideas to be valued, even when they’re not perfectly formed
  • The chance to have our voices heard without feeling exposed or vulnerable
  • Our unique perspectives to be genuinely welcomed, shared and explored
  • The freedom to ask questions without judgment

Recognising Our Worth

We need to feel that:

  • Our daily efforts contribute to something meaningful
  • Someone notices and appreciates our unique contributions
  • We’re part of something bigger than our individual roles
  • Our talents and personalities matter, not just our output

Note: Some yeara afo, Gallup published a list of things employess need to feel valued.

The Emotional Reality of Our Workplace

When our workplace culture ignores our human needs, we experience profound challenges:

  • A persistent, underlying anxiety becomes our constant companion
  • We feel increasingly invisible and undervalued
  • Emotional exhaustion starts to seep into every aspect of our lives
  • Our initial passion and engagement gradually fade

These aren’t just professional challenges—they’re deeply personal experiences that can erode our sense of self and purpose.

Reimagining Our Workplace Together

Creating Genuine Connections

The most jouous workplaces understand that we’re not interchangeable parts, but unique individuals. We need:

  • Authentic channels for sharing our thoughts and feelings
  • Fellows who genuinely listen and empathise
  • Moments that celebrate our humanity, not our productivity

Our Collective Power to Create Change

Setting aside formal leadership roles, each of us can contribute to a more compassionate workplace:

  • By courageously sharing our authentic experiences
  • Listening to our colleagues with genuine curiosity and care
  • Asking questions that invite deeper understanding
  • Challenging unhelpful patterns with kindness and respect

Beyond Transactional Work

Our work should be more than a mere exchange of time for money. It should be a source of growth, meaning, and human connection.

When we feel genuinely seen, heard, and valued, something magical happens. Our workplace transforms from a series of transactions into a community of mutual support and shared purpose.

An Invitation to Reflection

What if we take a moment to pause and look around our workplace. What do we feel? What small, meaningful action could we take today to make our collective experience more human, more compassionate?

Sometimes, the most profound changes begin with the simplest acts of empathy and understanding. And do we care about each other?

Our workplace is our shared story. And we have the power to write it, together.

The Software Crisis: A Failure of Imagination and Commitment

Understanding the Software Crisis: A Historical Perspective

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

The Roots of the Crisis: Complexity Beyond Control

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

The Dimensionality of Technological Complexity

Consider software development as navigating a multidimensional maze where:

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

Engineering Aspirations Versus Harsh Realities

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

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

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

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

Generational Capitulation: The Abdication of Technological Responsibility

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

The Demotivated Developer: A Portrait of Resignation

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

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

The Myth of Pragmatism: Disguised Indifference

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

Technological Stockholm Syndrome

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

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

The Lost Generation of Ambitious Problem Solvers

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

Acceptance: A Euphemism for Failure

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

Conclusion: A Call to Arms

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

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

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

The Relevance of Experience: Insights from Five Decades in Software Development

The Perennial Question: Why Should You Care?

If you’re a software developer or manager thereof navigating the ever-changing landscape of our industry, you’ve likely encountered countless blogs, each vying for your attention. Perhaps you’ve stumbled upon mine and wondered, “Why should I care about the musings of someone who’s been in the field for over five decades?” It’s a fair question, and one I’m happy to address.

The Unique Lens of Long-Term Experience

In the software development business (even that label is a misnomer) where technologies seem to emerge and evolve at breakneck speed, there’s an invaluable perspective that only time can provide. My five decades in this field have offered me a vantage point that’s both rare and illuminating. It’s not just about having witnessed the changes; it’s about understanding the underlying patterns, the cycles of innovation, and the constants that persist despite superficial transformations.

This long-term experience isn’t merely a chronicle of technological advancements. It’s a deep well of insights into the human aspects of software development – how teams collaborate, how culture is paramount, and how organisations adapt to new challenges. It’s about seeing the forest for the trees, recognising the echoes of past innovations in today’s breakthroughs, and understanding that while the tools and practices may change, the fundamental principles of attending to folks’ needs remain remarkably consistent.

In the following subsections, we’ll explore how this unique lens of long-term experience provides a context that can enrich your understanding of current trends and future directions in our field. Whether you’re a seasoned practitioner or just starting your journey, may I suggest that there’s value in a perspective that can inform your decisions, broaden your outlook, and perhaps even challenge some of your assumptions – both personal and collective – about the nature of progress in software development.

From Paper Tape to Petabytes: A Journey Through Computing Eras

My journey in software development began when paper tape was cutting-edge and has continued through to the era of petabyte storage. This span of experience isn’t just a testament to longevity; it’s a unique vantage point from which to observe the evolution of our field.

The Foundations of Innovation

One of the most valuable insights gained from this long-term perspective is the recognition of perennial, foundational concepts. What seems revolutionary today often has roots in concepts from decades past.

Beyond the Hype: Uncovering Enduring Principles

The Fallacy of “This Time It’s Different”

In an industry that thrives on the “next big thing,” it’s easy to get caught up in the hype of new technologies. However, my experience has shown me that while the tools change, the fundamental challenges of attending to folks’ needs through e.g. software remain remarkably consistent.

Timeless Challenges in a Changing Landscape

  • Human Psychology and Motivation: At its core, software development has always been a human endeavour. Dependent on relationships, collaborations, and fellowship.
  • Quality: Phil Crosby, and others, wrote about quality over fifty years ago. Yet from the users’ point of view, software today is as lame as it ever has been.
  • Value a.k.a. Meeting Folks’ Needs: So many projects and teams witter on about delivering value, yet noone seems to understand what value is. Let alone how to reliably deliver it.
  • Human-Computer Interaction: The principles of creating intuitive interfaces have evolved but not fundamentally changed since the days of command-line interfaces.
  • Data Integrity and Security: The scale and methods have changed, but the core concerns remain as critical as ever.

The Value Proposition: Why My Perspective Matters

Contextualising Current Trends

By drawing parallels between historical developments and current trends, I offer readers a broader context for understanding the evolution of our field. This perspective can be invaluable in making informed decisions about which principles and practices to adopt and which skills to develop.

Learning from History to Avoid Repeated Mistakes

The philosopher George Santayana famously wrote,

“Those who cannot remember the past are condemned to repeat it.”

This observation is particularly pertinent in the field of software development, where the rapid pace of change can sometimes obscure valuable lessons from the past.

Many of the challenges facing developers, managers and their organisations today have historical precedents. By sharing insights from past successes and failures, I aim to help the current generation avoid reinventing the wheel, missing out on eternal wisdom, or repeating past mistakes.

An Invitation to Dialogue

In the realm of software development, where innovation is constant and change is the only certainty, the exchange of ideas becomes not just valuable, but essential. This blog isn’t meant to be a one-way street of wisdom flowing from past to present. Rather, it’s an open forum, a meeting place where experience and fresh perspectives can maybe collide, coalesce, and create new insights.

The beauty of our field lies in its collaborative nature. No single perspective, no matter how well-informed or long-standing, can capture the full picture of our continually evolving industry. It’s in the synthesis of diverse viewpoints—from the battle-hardened veteran to the wide-eyed newcomer—that we can find the most profound and applicable wisdom.

So, as we delve into the following points about bridging generational divides and valuing your perspective, remember: this isn’t just about absorbing information. It’s an invitation to engage, to question, to challenge, and to contribute. Your voice, your experiences, and your insights are not just welcome—they’re essential to this ongoing conversation about the past, present, and future of software development.Assuming anyone cares, of course.

Bridging Generational Divides

The rapid pace of change can sometimes create a divide between generations of developers. My blog can serve as a bridge, fostering intergenerational dialogue and mutual understanding.

Your Perspective Matters

I encourage readers to engage with my posts critically. Your experiences in the current technological landscape are just as valid and relevant. By combining your fresh perspective with my historical insights, we can generate more comprehensive and nuanced understandings of our field.

Conclusion: The Synergy of Experience and Innovation

In an industry that often prioritises the new and novel, there’s immense value in also looking into and remembering fundamentals. My blog isn’t about nostalgia or resisting change; it’s about leveraging decades of accumulated wisdom to inform and enhance currently applied principles and practices.

I invite you to approach my posts with curiosity and an open mind. Whether you’re a seasoned attendant or just starting your journey, there’s always new tricks to learn from old dogs – and always new insights to be gained from unknown perspectives on old problems.

Let’s continue this dialogue and together shape the future of the software development business, informed by the lessons of the fundamentals and excited by the possibilities of the future.

The Mirage of Progress in Modern Software Development

Introduction

In an era where technological advancements seem to occur at breakneck speed, one might assume that software development practices and approaches are evolving just as rapidly. Yet, a sobering reality emerges upon closer inspection: meaningful progress in software development has been remarkably scarce since the dawn of the new millennium. This post aims to challenge the status quo and invite a dialogue about the future of the craft.

The Agile Paradox: Revolution or Regression?

The Curse of Snowbird

The 2001 Snowbird meeting, which birthed the Agile Manifesto, is often lauded as a watershed moment in software development history. However, two decades later, we might choose to critically examine whether this event truly catalysed innovation or inadvertently led us into a dead-end, a comfort zone of pseudo-progress.

The Agile Adoption Scam

While Agile practices promised a new era of flexibility and efficiency, their widespread adoption has often yielded unexpected consequences:

  • Cargo cult Agile: Rituals without understanding
  • The illusion of productivity: Mistaking movement for progress
  • One-size-fits-none: The fallacy of universal applicability
  • Promise unrealised: Most organisations are irredeemablly barren ground for key agile practices and principles

The Illusion of Progress

The Rebranding Con

Many purported ‘innovations’ in software development approaches over the past two decades have been mere repackaging of existing ideas. We’ve witnessed a parade of buzzwords—Scrum, Kanban, DevOps, and beyond—creating noise rather  than genuine advancements in how we build software. This constant rebranding often serves to refresh marketing materials rather than fundamentally improve the way the work works.

The Siren Song of Tools

Our industry’s obsession with tools and technologies has diverted attention from fundamental issues in development approaches. While tools can sometimes amplify productivity (counter-examp[le: JIRA), they often serve as a convenient smokescreen, concealing deeper systemic problems.

The Inertia of the Establishment

The Comfort of Complacency

Key players in the software development arena appear blithely content with the status quo. This inertia can be attributed to:

  • The lucrative nature of existing frameworks and certifications
  • Risk aversion: The path of least resistance
  • Organisational ossification: The challenge of implementing radical change at scale (well, any kind of meaningful change, really)

Charting a Course for Genuine Progress

Rekindling the Spirit of Innovation

To break free from this quagmire of stagnation, our industry might choose to:

  • Foster a culture of constructive dissent (Hah! As if that’ll ever happen)
  • Prioritise needs-driven development over process conformance (Cf. the Antimatter Principle)
  • Invest in reflection that challenges our fundamental assumptions about software creation and the role of software in attending to folks’ needs. (Cf. Organisational Psychotherapy)

Cross-Pollination: Learning from the Wider World

Software development stands to gain immensely from interdisciplinary insights:

  • Embracing design thinking’s user-centric approach
  • Applying lean product development principles Cf. “Product Development for the Lean Enterprise: Why Toyota’s System is Four Times More Productive and How You Can Implement It.” – Michael Kennedy
  • Leveraging systems thinking to tackle complex software ecosystems (Cf. Meadows, Beer, Senge, Weinberg, Deming, Ackoff, Goldratt, etc.)
Further Reading in Systems Thinking for Software Ecosystems

Meadows, D. H. (2008). Thinking in Systems: A Primer. Chelsea Green Publishing.

Senge, P. M. (1990). The Fifth Discipline: The Art and Practice of the Learning Organization. Doubleday/Currency.

Ackoff, R. L. (1974). Redesigning the Future: A Systems Approach to Societal Problems. John Wiley & Sons.

Beer, S. (1981). Brain of the Firm: The Managerial Cybernetics of Organization. John Wiley & Sons.

Deming, W. E. (1982). Out of the Crisis. MIT Press.

Weinberg, G. M. (2011). An Introduction to General Systems Thinking (Silver Anniversary Edition). Dorset House.

Conclusion: A Call to Action

The software development community stands at a critical juncture. While the early 2000s saw the seeds of innovation planted, we’ve since watched our field calcify around those initial ideas. Is it yet time for practitioners, thought leaders, and organisations to shatter the illusion of progress and push for genuine advancements in how we approach software development and its role in businesses more generally? Only by acknowledging and addressing this stagnation can we hope to usher in a new era of progress in our field.

The future of software development lies not in clinging to the past, but in daring to imagine—and create—truly transformative approaches to our craft. As my own contribution, allow me to offer: Organisational Psychotherapy.

Meaning and Purpose

In a world where burnout and disengagement are rampant, discovering meaning and purpose in our work has never been more crucial. But how can we transform our daily grind into a source of fulfilment and motivation? Let’s explore this vital question through the lenses of two pioneering thinkers and some practical, real-world applications.

The Wisdom of Viktor Frankl: Finding Light in the Darkest Places

Viktor Frankl (1905-1997), a renowned Austrian neurologist and psychiatrist, developed a revolutionary therapeutic approach known as logotherapy. But Frankl’s journey to this profound insight was forged in the crucible of unspeakable suffering.

As a Jewish psychiatrist in Vienna during World War II, Frankl was deported to Nazi concentration camps, including Auschwitz and Dachau. He endured three years of unimaginable hardship, losing his parents, brother, and pregnant wife to the Holocaust. It was through this harrowing experience that Frankl’s theories about the importance of meaning in human life were tested and solidified.

Logotherapy, often called the “Third Viennese School of Psychotherapy” (after Freud’s psychoanalysis and Adler’s individual psychology), is based on the premise that the primary motivational force in humans is the search for meaning. The term “logotherapy” is derived from the Greek word “logos,” which Frankl uses to denote “meaning.”

What sets logotherapy apart is its emphasis on the future rather than the past. Instead of dwelling on past traumas or subconscious drives, logotherapy focuses on the meanings to be fulfilled by the patient inow and n their future. This forward-looking approach makes it particularly relevant in our modern context, where many struggle to find purpose in an increasingly complex and sometimes alienating world.

Frankl’s experiences in the concentration camps led him to a startling observation: those who were able to hold onto a sense of meaning and purpose, even in the most dire circumstances, had a better chance of survival. He noticed that prisoners who had a reason to live – be it a loved one waiting for them, an unfinished work, or a deep-seated belief – were more resilient in the face of unimaginable hardship.

This school of therapy emphasises the importance of finding meaning in life, even – or especially – in the face of extreme suffering. Frankl argued that while we cannot avoid suffering, we can choose how to cope with it, find meaning in it, and move forward with renewed purpose. This idea is encapsulated in one of his most famous quotes:

“Everything can be taken from a man but one thing: the last of human freedoms – to choose one’s attitude in any given set of circumstances, to choose one’s own way.”

Frankl’s approach suggests that meaning can be found in three primary ways:

  1. By creating a work or doing a deed (creative values)
  2. By experiencing something or encountering someone (experiential values)
  3. By the attitude we take toward unavoidable suffering (attitudinal values)

These principles, born from the darkest chapter of human history, offer a powerful framework for finding purpose and meaning not just in therapy, but in all aspects of life – including our work.

In the context of our working lives, logotherapy invites us to look beyond mere job satisfaction or career success. It challenges us to find deeper meaning in our daily tasks, to see our work as a contribution to something greater than ourselves, and to maintain a sense of purpose even when faced with workplace challenges or disappointments.

As we delve deeper into the application of these ideas in the workplace, we’ll see how Frankl’s profound insights can transform our relationship with work, turning it from a source of stress or mere livelihood into a wellspring of meaning and personal fulfilment.

Daniel Pink’s Drive: The Surprising Truth About What Motivates Us

In his book “Drive”, American author Daniel Pink explores the elements that truly motivate individuals in the modern workplace. He argues that traditional carrot-and-stick approaches are often ineffective, particularly for complex, creative taskssuch as software development.

The Three Elements of True Motivation

Pink identifies three key components of intrinsic motivation:

  1. Autonomy: The desire to direct our own lives and work.
  2. Mastery: The urge to continually improve at something that matters.
  3. Purpose: The yearning to do what we do in service of something larger than ourselves.

Pink’s research suggests that when these three elements are present, individuals are more likely to be engaged and satisfied in their work, and thus happier and more productive. This insight challenges traditional management practices and calls for a reimagining of how we structure work and motivate employees.

The Synergy of Meaning and Purpose

While Frankl’s concept of meaning and Pink’s notion of purpose may seem distinct, they are, in fact, closely intertwined. Both emphasise the importance of connecting one’s work to a greater cause or ideal. Frankl’s logotherapy provides a philosophical foundation for understanding why meaning is crucial, while Pink’s research offers practical insights into how to foster that sense of meaning and purpose in the workplace.

Beyond the Company Mission: Expanding Our Horizons

While we might place some import on understanding our role in achieving company goals, true meaning often comes from seeing the bigger picture. Here’s some ways to broaden your perspective:

1. Connect Your Work to Societal Impact

  • Trace Your Impact: Map out how your work ripples through society. A software developer isn’t just writing code; they’re potentially improving healthcare systems or making education more accessible.
  • Share Success Stories: Collect and share anecdotes about how your work has positively affected real people’s lives.

2. Fuel Personal Growth

  • Skills Inventory: Regularly update a list of new skills you’ve gained. How have recent challenges expanded your capabilities?
  • Relationship Web: Map out the professional relationships you’ve built. How have these connections enriched your life and others’?

3. Align with Your Values

  • Values Check-In: Periodically assess how your work aligns with your core values. Where are the synergies? Where are the conflicts, and how can you address them?
  • Ethical Impact: Consider the ethical implications of your work. Are you contributing to a more just and sustainable world? Does that even matter to you?

4. Amplify Your Impact on Family and Community

  • Family Mission Statement: Create a family mission statement. How does your work contribute to your family’s goals and well-being?
  • Skill Donation: Use your work-related skills to support a local cause. A marketer could help a non-profit with their campaigns, for example.

5. Embrace Global Citizenship

  • Sustainability Audit: Assess your work’s environmental impact. Does that impact matter to you? Can you champion more sustainable practices in your role?
  • Cross-Cultural Bridges: Highlight opportunities to foster cross-cultural understanding through your work, even in small ways.

Practical Steps to Cultivate Meaning and Purpose

  1. Purpose Journaling: Spend 5 minutes at some point in each workday reflecting on moments of meaning and purpose.
  2. Impact Visualization: Create a visual representation of your work’s ripple effect on the world. Update it regularly.
  3. Value-Aligned Goal Setting: Set professional goals that align with your personal values and larger life purpose.
  4. Mentor or Be Mentored: Engage in mentorship to gain new perspectives and multiply your impact.
  5. Purpose-Driven Innovation: Propose projects or improvements that align more closely with your sense of purpose and the greater good.

The Ripple Effect: From Individual Purpose to Organisational Transformation

As more individuals connect with their sense of purpose at work, organisations transform. They become more than profit-generating entities; they evolve into forces for joy and positive change in the world. This shift not only benefits employees and companies but contributes to addressing global challenges and creating a more meaningful, purposeful society.

Remember, finding meaning and purpose is not a destination but a journey. It requires ongoing reflection, adjustment, and action. By integrating these ideas into our daily work lives, we can transform our relationship with work from a source of stress to a wellspring of fulfilment and positive impact.

What step will you take today to infuse more meaning and purpose into your work, and life?

My Social Media Journey: From Email to Twitter to Mastodon

Dove in flight

A Farewell to Twitter

As many of my regular readers might already know, I bid farewell to Twitter some years ago. At the time, I was operating under the handle @flowchainsensei and had amassed quite a following (15,000+), being one of the most-followed software people on the platform. The decision to quit was not taken by me, but various circumstances led me to step away from the Twitterverse.

An Unexpected Return

Life, as it often does, had other plans. Subsequent circumstances pulled me back into the fold of Twitter, this time under the group handle @alientechgroup. It was a chance to reconnect with the community, promote the initiative, and share insights once more.

The Final Departure

Twitter’s Transformation

In August, we made the decision to quit Twitter (now known as X) for good. The platform, once a vibrant space for discussion and idea-sharing, has unfortunately devolved into what can only be described as an open sewer. The toxicity and chaos that now pervade the site made it clear that it was time to move on to greener pastures.

Finding New Homes on the Web

The Blog: A Return to Roots

For those who wish to keep up with my thoughts and musings, I’m happy to announce that you can still find me right here on my blog. It’s a return to a more thoughtful, long-form medium of expression, free from the constraints and pitfalls of microblogging platforms.

Embracing Mastodon

In addition to my blog, I’ve found a new social media home on Mastodon. You can connect with me primarily at @flowchainsenseisocial@mastodon.social. Mastodon offers a refreshing alternative to traditional social media, with its decentralised structure and focus on user control.

Looking Forward

As we navigate the ever-changing landscape of social media, it’s important to find spaces that align with our values and foster meaningful connections. While my journey has thankfully taken me away from Twitter, I’m excited about the opportunities that lie ahead on Mastodon and through more traditional blogging.

I invite you all to join me on this new chapter. Let’s continue our discussions, share ideas, and build a community that values respect, intellectual discourse, and genuine human connection.

The Treasure Map to Quality Software: Attendin’ to Yer Crew’s Needs

Ahoy, ye scurvy dogs! Gather ’round and lend yer ears to this tale of software and product development on the high seas. Many a buccaneer be gettin’ lost in a maelstrom of metrics, practices, and fancy talk. But arrr, are we missin’ the real booty? Hoist the colors, for we be divin’ deep into the heart of software quality, and it ain’t what ye might expect!

Rethinking Quality: It Be Nothin’ About the Code, Ye Bilge Rats!

For many a moon, we’ve been measurin’ software quality through a spyglass of technical nonsense:

  • How many bugs per thousand lines o’ code?
  • What be the cyclomatic complexity score?
  • How’s our test coverage lookin’?
  • And other such landlubber gibberish!

But in the grand scheme o’ things, these metrics be as useful as a glass bottom boat in a typhoon. They’re missin’ the most crucial element: the human factor, ye swabs!

The True North of Software Quality

At its core, quality software be about one thing: how well it serves the needs of all the Scallywags That Matter™. This human-centric approach shifts our focus from mere technical excellence to genuine treasure creation.

Who Be These Scallywags?

  1. End-users: The landlubbers who interact with yer software daily.
  2. Business stakeholders: The wealthy merchants investin’ their doubloons into the project.
  3. Developers and maintainers: The wizards in the crow’s nest.
  4. Support staff: Yer frontline buccaneers in the battle for user satisfaction.
  5. Regulatory bodies: The naval officers enforcin’ compliance and safety.
  6. Society at Large: The port towns impacted by how ships do business, and the rum and grog they produce.

The Pirate’s Satisfaction Matrix

Imagine a map where each crew group forms a row, and their needs form the columns. True quality be achieved when we maximize satisfaction across this entire map. Let’s break it down like a shipwreck:

1. End-users: The Ultimate Judges

  • Needs: Ship-shape UX, reliability, speed, and security
  • Quality Indicator: User satisfaction scores, retention rates, feature adoption

2. Business Stakeholders: The Vision Keepers

  • Needs: Return on investment, market dominance, scalability
  • Quality Indicator: Booty growth, market share, operational efficiency

3. Developers and Maintainers: The Unsung Heroes

  • Needs: Clean code, comprehensive sea charts (documentation), extensibility
  • Quality Indicator: Development speed, bug fixin’ time, crew satisfaction

4. Support Staff: The Front-line Warriors

  • Needs: Clear error messages, robust loggin’, efficient troubleshootin’ tools
  • Quality Indicator: First-call resolution rates, average handlin’ time, CSAT scores

5. Regulatory Bodies: The Compliance Guardians

  • Needs: Adherence to the Pirate Code, audit trails, data protection
  • Quality Indicator: Compliance certifications, audit pass rates

The art of creatin’ quality software lies in findin’ the X that marks the spot to best serve all these competin’ interests.

Measurin’ True Quality: The Needsscape Satisfaction Index (NSI)

We propose a new treasure map: the Needsscape Satisfaction Index (NSI). Here’s how ye navigate it:

  1. Identify key needs for each crew group
  2. Assign weights to each need based on their declared priorities
  3. Regularly measure achievement levels for each need
  4. Calculate a weighted average to get yer NSI

A high NSI indicates products and services that ain’t just technically sound, but truly attend to the needs of all the Scallywags That Matter™.

Conclusion: Quality Be Human, Ye Bilge Rats!

In our quest for software excellence, let’s not lose sight o’ the open sea for the waves. Technical metrics be as useful as a chocolate teapot, true quality be measured in human terms. It’s about creatin’ software that makes life better for every swab it touches – from the end-user to the DevOps engineer. And better means attendin’ to folks’ needs.

The next time ye be assessin’ software quality, look beyond the code. Ask yerself: “How well does this serve the needs of the scallywags that matter?” That’s where the real treasure lies.

Remember, at the end of the day, we ain’t just buildin’ software. We’re creatin’ solutions for human needs. Let’s measure our success accordingly, or walk the plank!

Further Readin’ for Ye Scholarly Lubbers

Fer ye scurvy dogs keen on plunderin’ the depths o’ quality’s philosophy and practice, we be recommendin’ these legendary tomes, as essential as rum on a long voyage:

  1. Pirsig, R. M. (1774). Zen and the art of ship maintenance: An inquiry into values. Tortuga Press.
  2. Crosby, P. B. (1779). Quality is free: The art of making quality certain as the North Star. Blackbeard’s Library.

These complementary perspectives – one philosophical, one practical – provide a rich map for thinkin’ about and implementin’ quality in software and product development, and beyond. Now, drink up me hearties, yo ho!

The Paramount Indicator of Quality Software: Attending to Folks’ Needs

In the field of software and product development, we often find ourselves caught up in a whirlwind of metrics, methodologies, and best practices. But amidst this technical maelstrom, are we losing sight of what truly matters? With this post we’re diving deep into the heart of software and product quality, and it’s likely not what you expect.

Rethinking Quality: It’s Nothing About the Code

For decades, we’ve measured software quality through a technical lens:

  • How many bugs per thousand lines of code?
  • What’s the cyclomatic complexity score?
  • How’s our test coverage looking?
  • Etc.

In the bigger pitcure, these metrics have little relevance. They’re missing a crucial element: the human factor.

The True North of Software Quality

At its core, quality software is about one thing: how well it serves the needs of all the Folks That Matter™. This human-centric approach shifts our focus from mere technical excellence to genuine value creation.

Who Are These Folks?

  1. End-users: The folks who interact with your software daily.
  2. Business stakeholders: Those investing time and resources into the project.
  3. Developers and maintainers: The wizards behind the curtain.
  4. Support staff: Your frontline troops in the battle for user satisfaction.
  5. Regulatory bodies: The guardians of compliance and safety.
  6. Society at Large: The communities of people impacted by how organisations do business, and the products and services they produce.

Satisfaction Matrix

Imagine a matrix where each stakeholder group forms a row, and their needs form the columns. True quality is achieved when we maximise satisfaction across this entire matrix. Let’s break it down:

1. End-users: The Ultimate Judges

  • Needs: Intuitive UX, reliability, performance, security
  • Quality Indicator: User satisfaction scores, retention rates, feature adoption

2. Business Stakeholders: The Vision Keepers

  • Needs: ROI, market competitiveness, scalability
  • Quality Indicator: Revenue growth, market share, operational efficiency

3. Developers and Maintainers: The Unsung Heroes

  • Needs: Clean code, comprehensive documentation, extensibility
  • Quality Indicator: Development velocity, bug resolution time, employee satisfaction

4. Support Staff: The Front-line Warriors

  • Needs: Clear error messages, robust logging, efficient troubleshooting tools
  • Quality Indicator: First-call resolution rates, average handling time, CSAT scores

5. Regulatory Bodies: The Compliance Guardians

  • Needs: Adherence to standards, audit trails, data protection
  • Quality Indicator: Compliance certifications, audit pass rates

The art of creating quality software lies in finding the sweet spot that best serves all these competing interests.

Measuring True Quality: The Needsscape Satisfaction Index (NSI)

We propose a new metric: the Needsscape Satisfaction Index (SSI). Here’s how it works:

  1. Identify key needs for each stakeholder group
  2. Assign weights to each need based on their declared priorities
  3. Regularly measure achievement levels for each need
  4. Calculate a weighted average to get your NSI

A high NSI indicates products and services that are not just technically sound, but truly attend to the needs of all the Folks That Matter™.

Conclusion: Quality is Human

In our quest for software excellence, let’s not lose sight of the forest for the trees. Technical metrics have little relevance, true quality is measured in human terms. It’s about creating software that makes life better for everyone it touches – from the end-user to the DevOps engineer. And better means attending to folks needs.

The next time you’re assessing software quality, look beyond the code. Ask yourself: “How well does this serve the needs of the folks that matter?” That’s where true quality lies.

Remember, at the end of the day, we’re not just building software. We’re creating solutions for human needs. Let’s measure our success accordingly.

Further Reading

For those interested in diving deeper into the philosophy and practice of quality, we highly recommend these seminal works:

  1. Pirsig, R. M. (1974). Zen and the art of motorcycle maintenance: An inquiry into values. William Morrow & Company.
    This work explores the metaphysics of quality, challenging readers to reconsider their understanding of what quality truly means. While not specifically about software, Pirsig’s insights on the nature of quality are profoundly relevant to our field, offering a philosophical foundation for the human-centric approach to software and product quality discussed in this article.
  2. Crosby, P. B. (1979). Quality is free: The art of making quality certain. McGraw-Hill.
    Crosby’s book provides a practical, business-oriented approach to quality. His concept that “quality is free” because the costs of prevention are always lower than the costs of failure aligns well with our stakeholder-centric view of software and product quality. This book offers valuable insights into implementing quality processes that can be adapted to software and product development practices.

These complementary perspectives – one philosophical, one practical – provide a rich foundation for thinking about and implementing quality in software and product development, and beyond.