Systems thinking

The Comfortable Lie: Why We Don’t Actually Learn From Our Mistakes

We love a good comeback story. The entrepreneur who failed three times before striking it rich. The developer who learnt from a catastrophic production incident and never made ‘that mistake’ again. We tell these stories because they’re comforting—they suggest that failure has a purpose, that our pain is an investment in wisdom.

But what if this narrative is mostly fiction? What if, in the contexts where we most desperately want to learn from our mistakes—complex, adaptive systems like software development—it’s not just difficult to learn from failure, but actually impossible in any meaningful way?

The Illusion of Causality

Consider a typical software development post-mortem. A service went down at 2 AM. After hours of investigation, the team identifies the culprit: an innocuous configuration change made three days earlier, combined with a gradual memory leak, triggered by an unusual traffic pattern, exacerbated by a caching strategy that seemed fine in testing. The conclusion? ‘We learnt that we need better monitoring for memory issues and more rigorous review of configuration changes.’

But did they really learn anything useful?

The problem is that this wasn’t a simple cause-and-effect situation. It was the intersection of dozens of factors, most of which were present for months or years without issue. The memory leak existed in production for six months. The caching strategy had been in place for two years. The configuration change was reviewed by three senior engineers. None of these factors alone caused the outage—it required their precise combination at that specific moment.

In complex adaptive systems, causality is not linear. There’s no single mistake to point to, no clear lesson to extract. The system is a web of interacting components where small changes can have outsized effects, where the same action can produce wildly different outcomes depending on context, and where the context itself is always shifting.

The Context Problem

Here’s what makes this especially insidious: even if we could perfectly understand what went wrong, that understanding is locked to a specific moment in time. Software systems don’t stand still. By the time we’ve finished our post-mortem, the team composition has changed, two dependencies have been updated, traffic patterns have evolved, and three new features have been deployed. The system we’re analysing no longer exists.

This is why the most confident proclamations—’We’ll never let this happen again’—are often followed by remarkably similar failures. Not because teams are incompetent or negligent, but because they’re trying to apply lessons from System A to System B, when System B only superficially resembles its predecessor. The lesson learnt was ‘don’t deploy configuration changes on Fridays without additional review’, but the next incident happens on a Tuesday with a code change that went through extensive review. Was the lesson wrong? Or was it just irrelevant to the new context?

The Narrative Fallacy

Humans are storytelling machines. When something goes wrong, we instinctively construct a narrative that makes sense of the chaos. We identify villains (the junior developer who made the change), heroes (the senior engineer who diagnosed the issue), and a moral (the importance of code review). These narratives feel true because they’re coherent.

But coherence is not the same as accuracy. In the aftermath of failure, we suffer from hindsight bias—knowing the outcome, we see a clear path from cause to effect that was never actually clear at the time. We say ‘the warning signs were there’ when in reality those same ‘warning signs’ are present all the time without incident. We construct a story that couldn’t have been written before the fact.

This is why war stories in software development are simultaneously compelling and useless. The grizzled veteran who regales you with tales of production disasters is imparting wisdom that feels profound but often amounts to ‘this specific thing went wrong in this specific way in this specific system at this specific time’. And the specifics are rarely defined. The lesson learnt is over-fitted to a single data point.

Emergence and Irreducibility

Complex adaptive systems exhibit emergence—behaviour that arises from the interaction of components but cannot be predicted by analysing those components in isolation – c.f. Synergetics (Buckminster Fuller). Your microservices architecture might work perfectly in testing, under load simulation, and even in production for months. Then one day, a particular sequence of requests, combined with a specific distribution of data across shards, triggers a cascade failure that brings down the entire system.

You can’t ‘learn’ to prevent emergent failures because you can’t predict them. They arise from the system’s complexity itself. Adding more tests, more monitoring, more safeguards—these changes don’t eliminate emergence, they just add new components to the complex system, creating new possibilities for emergent behaviour.

The Adaptation Trap

Here’s the final twist: complex adaptive systems adapt. When you implement a lesson learnt, you’re not just fixing a problem—you’re changing the system. And when the system changes, the behaviours that emerge from it change too.

Add comprehensive monitoring after an outage? Now developers start relying on monitoring as a crutch, writing less defensive code because they know they’ll be alerted to issues. Implement mandatory code review after a bad deployment? Now developers become complacent, assuming that anything that passed review must be safe. The system adapts around your interventions, often in ways that undermine their original purpose.

This isn’t a failure of implementation—it’s a fundamental characteristic of complex adaptive systems. They don’t have stable equilibrium points. Every intervention shifts the system to a new state with its own unique vulnerabilities.

So What Do We Do?

If we can’t learn from our mistakes in any straightforward way, what’s the alternative? Are we doomed to repeat the same failures for ever?

Not quite. The solution is to stop pretending we can extract universal lessons from specific failures and instead focus on building systems that are resilient to the inevitable surprises we can’t predict.

This means designing for graceful degradation rather than preventing all failures. It means building systems that can absorb shocks and recover quickly rather than systems that need to be perfect. It means accepting that production is fundamentally different from any testing environment and that the only way to understand system behaviour is to observe it in production with real users and real data.

It also means being humble. Every post-mortem that ends with ‘we’ve identified the root cause and implemented fixes to prevent this from happening again’ is cosplaying certainty in a domain defined by uncertainty. A more honest conclusion might be: ‘This is what we think happened, given our limited ability to understand complex systems. We’re making some changes that might help, but we acknowledge that we’re also potentially introducing new failure modes we haven’t imagined yet.’

The Productivity of Failure

None of this means that failures are useless. Incidents do provide value—they reveal the system’s boundaries, expose hidden assumptions, and force us to confront our mental models. But the value isn’t in extracting a tidy lesson that we can apply next time. The value is in the ongoing process of engaging with complexity, building intuition through repeated exposure, and developing a mindset that expects surprise rather than seeking certainty.

The developer who has been through multiple production incidents isn’t valuable because they’ve learnt ‘lessons’ they can enumerate. They’re valuable because they’ve internalised a posture of humility, an expectation that systems will fail in ways they didn’t anticipate, and a comfort with operating in conditions of uncertainty.

That’s not the same as learning from mistakes. It’s something both more modest and more useful: developing wisdom about the limits of what we can learn.

The next time you hear someone confidently declare that they’ve learnt from a mistake, especially in a complex domain like software development, be sceptical. Not because they’re lying or incompetent, but because they’re human—and we all want to believe that our suffering has purchased something more substantial than just the experience of suffering. The truth is messier and less satisfying: in complex adaptive systems, the best we can hope for is not wisdom, but the wisdom to know how little wisdom we can extract from any single experience.

A Conversation About John Gall

August 9, 2025

Article, Product development, Software development, Systems thinking

Leave a comment

A Conversation About John Gall

Yesterday, I found myself in a fascinating conversation with a group of software developers who seemed genuinely troubled by something they’d recently encountered: the writings of John Gall. But troubled in the sense of disagreement—they weren’t convinced by his profound observations about complex systems. Their pushback was immediate and visceral, and it brought back memories of my own encounter with Gall’s ideas—and with the man himself.

I had the remarkable privilege of meeting John Gall at a Gilbfest some years ago, shortly before his passing. Speaking with him in person added layers to his written insights that I’m still unpacking.

Who Was John Gall?

John Gall was a paediatrician and leading systems theorist who wrote Systemantics in 1975 (later republished as The Systems Bible). Whilst not a technologist, his observations about how complex systems behave have proven remarkably prescient in our digital age. His most famous principle, known as Gall’s Law, states:

‘A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over with a working simple system.’

Meeting the Man Behind the Ideas

What struck me most about meeting John Gall in person was how his demeanour perfectly embodied his systems thinking. He had the quiet calm of someone who had spent decades observing patterns others missed, combined with an almost mischievous delight in pointing out the gap between how we think systems should work and how they actually do.

In conversation, he was remarkably humble about his insights—which somehow made them more powerful. He didn’t present his observations as revolutionary discoveries but as simple truths that were hiding in plain sight. It was this quality that made his ideas so compelling and, I now realise, so disturbing to practitioners who encounter them.

There was something almost subversive about how he discussed complex systems. Not in a destructive way, but in the sense that he was gently undermining assumptions we didn’t even know we held. Talking with him felt like having someone point out that the emperor’s new clothes were, indeed, invisible—but doing so with such kindness that you couldn’t help but laugh at your own blindness.

Missing the Lineage

I’m hardly surprised that developers balk at John Gall’s insights. Developers seem woefully ignorant of antecedents—Deming, Ackoff, Goldratt, Seddon, Capers Jones, and others who spent decades studying how complex systems actually behave.

Gall wasn’t working in isolation. He was part of a tradition of people who looked at systems—manufacturing systems, organizational systems, quality systems—and noticed patterns. The software industry acts like it invented complexity, but these insights about how systems fail and succeed go back generations.

When you don’t know the lineage, Gall’s observations can seem like random provocations rather than hard-won wisdom about the nature of complex systems.

The Conversation

He was exactly what you’d expect from someone who spent decades watching systems behave in ways their creators never intended. Quietly amused. Not trying to convince anyone of anything. Just sharing what he’d noticed.

The developers had plenty of counterarguments. Successful complex designs. Modern tools that make planning work better. Their own experience building systems that succeeded because of careful architecture.

But then one of them started telling a story about a ‘temporary’ script that had become the backbone of their production system. Another mentioned the beautiful enterprise architecture that never quite worked as designed. A third talked about the quick prototype that somehow got scaled to millions of users.

We’ve all been there.

Gall wasn’t anti-planning or anti-design. He was just honest about what he observed. Complex systems that work have histories. They started somewhere simpler. They grew. They adapted. The ones designed as complete, complex systems from day one… well, there aren’t many success stories there. I can vouch.

Unix started simple. The web started simple. Git started with Linus Torvalds scratching an itch.

Even our engineering principles acknowledge this. KISS exists because complexity kills systems.

The developers weren’t wrong about their successes. But their successes might tell a different story than they think. What if their well-planned complex systems succeeded not because of the planning, but because they were good at adapting when reality differed from the plan? What if their individual wins don’t contradict the broader pattern?

I’m not trying to convince anyone. Gall’s insights either match what you’ve seen or they don’t.

But it’s worth asking: when you look at the systems that actually endured in your career—the ones still running years later—how many started complex? How many started simple and grew?

The pattern is there if you want to see it.

Or not. Systems will keep teaching us, either way.

Deming’s 95/5 Rule

July 12, 2025

Actionable Insights, Article, Deming, Systems thinking, Thinking tools

1 Comment

Deming’s 95/5 Rule

When things go wrong in organisations, our instinct is often to ask ‘Who’s responsible?’ But what if we’ve been asking the wrong question all along? W. Edwards Deming, the legendary quality management guru, would argue that we have been—and his famous 95/5 assertion challenges one of our most fundamental assumptions about workplace problems.

What Is Deming’s 95/5 Assertion?

Deming’s 95/5 rule states that 95% of organisational problems stem from faulty systems and processes, whilst only 5% are caused by individual worker performance or behaviour. In other words, when something goes wrong, there’s a 95% chance it’s the system’s fault, not the person’s fault.

This principle emerged from Deming’s decades of work in quality management, most notably his role in Japan’s post-WWII industrial transformation. Deming observed that most defects, errors, and failures could be traced back to poorly designed processes, inadequate training, unclear procedures, or systemic constraints—not to lazy, incompetent, or malicious workers.

The Traditional Mindset vs. Deming’s Vision

The 95/5 assertion directly challenges the traditional management approach of focusing on individual accountability. In most organisations, when problems arise, the immediate response is to identify who made the mistake and implement corrective action—often in the form of additional training, warnings, or disciplinary measures.

Deming argued this approach is not only ineffective but counterproductive. If 95% of problems are systemic, then focusing on individual blame wastes time and resources whilst leaving the root causes untouched. Worse, it creates a culture of fear that prevents workers from reporting problems or suggesting improvements.

Instead, Deming advocated for systems thinking—examining the processes, tools, training, communication channels, and organisational structures that enable or constrain performance.

The Case for Accepting Deming’s 95/5 Rule

There’s compelling evidence supporting Deming’s assertion across multiple domains:

Healthcare provides striking examples. Medical errors were long attributed to individual negligence until researchers began examining systemic factors. Studies revealed that medication errors, surgical mistakes, and diagnostic failures often resulted from poor handoff protocols, confusing labelling systems, inadequate staffing, or flawed communication processes. When hospitals redesigned these systems, error rates plummeted—without changing personnel.

Aviation offers another powerful case study. The industry’s remarkable safety record stems largely from embracing systems thinking. Rather than blaming pilots for crashes, aviation focuses on designing better instruments, improving training protocols, enhancing communication procedures, and creating redundant safety systems. The result is an industry where fatal accidents are extraordinarily rare.

Software development has also validated Deming’s principle. When bugs occur, effective teams don’t just fix the immediate issue—they examine why their testing processes didn’t catch it, whether their development workflow created time pressure that led to shortcuts, or if their code review procedures were adequate.

The psychological research supports this too. Studies in cognitive science show that human error is often the symptom, not the cause, of poorly designed systems. When processes are confusing, tools are unreliable, or information is unclear, even highly competent people make mistakes.

Check Your Assumptions

Perhaps the most valuable aspect of Deming’s 95/5 assertion isn’t whether it’s precisely accurate, but how it can serve as a diagnostic tool for examining our own thinking patterns. Most people, when first encountering this principle, already have a strong intuitive reaction—they either immediately accept it as obviously true or reject it as clearly wrong.

This immediate response reveals something important: we’re not approaching the question with an open mind. Instead, we’re filtering it through existing beliefs about human nature, personal responsibility, organisational dynamics, and the nature of problems themselves. Those who quickly accept the 95/5 split often already lean towards systems thinking and collective responsibility. Those who reject it typically favour individual accountability and personal agency.

The real question isn’t whether Deming is right—it’s whether we can examine our own assumptions. Most people find it difficult or uncomfortable to genuinely question their initial reaction to the 95/5 principle. We might engage with the arguments intellectually, but we rarely interrogate why we’re drawn to one side or the other, or what deeper beliefs are shaping our response.

This presents a valuable opportunity for self-reflection. If we can’t or won’t question our assumptions about something as specific as Deming’s 95/5 rule, what other assumptions are we carrying unchallenged? Consider:

Do we assume that hard work always leads to success?
Do we believe that complex problems (a.k.a. messes) have simple solutions?
Are we convinced that more data always leads to better decisions?
Do we think that good intentions guarantee good outcomes?

Using Deming’s principle as a litmus test for assumption-checking can reveal broader patterns in our thinking. Are we quick to seek individual culprits when things go wrong in our personal lives? Do we automatically assume that organisational problems stem from lazy or incompetent people? Or do we reflexively blame ‘the system’ without considering individual contributions?

The goal isn’t to eliminate all assumptions—that’s impossible and impractical. Rather, it’s to become more aware of the assumptions we carry and more willing to hold them lightly, particularly when they’re not serving us well. Deming’s 95/5 assertion, regardless of its precise accuracy, offers a useful prompt: What else might I be taking for granted?

Consequences for Coaching

Deming’s 95/5 principle has profound implications for how leaders approach coaching and performance improvement. If most performance issues are systemic rather than individual, coaching conversations need to fundamentally shift their focus.

Traditional coaching often assumes the problem lies with the person. Managers typically approach underperformance by focusing on what the individual needs to do differently—work harder, manage time better, improve skills, or change their attitude. The coaching conversation centres on personal development plans, behavioural changes, and individual accountability.

Systems-focused coaching takes a different approach. Instead of immediately zeroing in on what the person is doing wrong, effective coaches first examine the environment in which the person is operating. They ask questions like:

Does this person have the tools and resources needed to succeed?
Are the expectations and success metrics clearly defined?
Is the workflow designed in a way that sets people up for success?
Are there competing priorities or conflicting demands creating confusion?
Does the person have adequate training and support?
Are there organisational barriers preventing good performance?

This shift changes the entire coaching dynamic. Rather than the coach being the expert telling the employee what to fix, both parties become collaborative problem-solvers examining how to improve the system. The employee’s insights become crucial because they’re closest to the actual work and can often identify systemic issues that aren’t visible to management.

For example, instead of coaching a salesperson to ‘make more calls’, a systems-focused coach might discover that the CRM system is clunky and time-consuming, the lead qualification process is unclear, or marketing isn’t providing quality prospects. Addressing these systemic issues would likely improve performance more than exhorting the individual to work harder.

This approach also reduces defensiveness. When people feel blamed for problems largely outside their control, they naturally become defensive and less receptive to feedback. When coaching focuses on improving conditions rather than fixing the person, employees are more likely to engage openly in problem-solving.

However, this doesn’t mean individual factors should be ignored entirely. Even within a systems framework, coaches still need to address skill gaps, motivation issues, and performance problems that genuinely stem from individual factors—they just shouldn’t assume these are the primary causes without first examining the system.

My Take: Accept the Principle, Question the Precision

I believe Deming’s 95/5 assertion should be accepted as a powerful guiding principle, even if we question its mathematical precision.

The core insight—that most organisational problems are systemic rather than individual—is profoundly important and consistently undervalued in practice. Too many organisations remain trapped in blame-focused cultures that miss opportunities for genuine improvement. Deming’s rule serves as a vital corrective to this tendency.

However, I’d frame it less as a precise statistical claim and more as a decision-making heuristic: When problems occur, start by examining systems and processes before focusing on individuals. This approach is more likely to identify root causes and create lasting solutions.

The principle also encourages leaders to take responsibility for creating conditions where people can succeed, rather than simply holding people accountable for results without examining the context in which they’re working.

Practical Applications

Accepting Deming’s principle leads to several practical changes:

Problem-solving shifts focus. Instead of asking ‘Who made this mistake?’ the first question becomes ‘What about our process allowed this mistake to happen?’

Performance management evolves. Rather than exclusively focusing on individual metrics, organisations examine whether people have the tools, training, information, and support needed to perform well.

Learning culture emerges. When problems are viewed as opportunities to improve systems rather than occasions to assign blame, employees become more willing to surface issues and suggest improvements.

Investment priorities change. Resources shift towards improving processes, tools, and training rather than simply monitoring and correcting individual performance.

The Bottom Line

Deming’s 95/5 assertion may not be mathematically precise in every context, but its fundamental insight remains powerful: most organisational problems are systemic, not individual. By focusing on improving systems and processes, organisations can achieve better results whilst creating more positive, productive work environments.

The next time something goes wrong in your organisation, resist the urge to immediately identify who’s responsible. Instead, ask what systems and processes contributed to the problem—and how they might be improved. You’ll likely find that Deming’s principle holds true far more often than you’d expect.

Whether the split is 95/5, 80/20, or somewhere in between matters less than embracing the core principle: systems thinking drives sustainable improvement better than individual blame ever could.

Coding Practices Are So the Wrong Focus

June 23, 2025

Article, Business, Deming, Engineering, Product development, Software development, Systems thinking

Leave a comment

Coding Practices Are So the Wrong Focus

In W. Edwards Deming’s famous Red Bead experiment, willing workers try their best to draw only white beads from a bowl containing 80% white beads and 20% red beads. Using a paddle that scoops exactly 50 beads, workers are told to produce zero defects (no red beads). No matter how hard they try, how skilled they are, or how much they want to succeed, the random distribution means some workers will consistently get more red beads than others through pure chance. The system determines the outcome, not individual effort.

Deming used this experiment to demonstrate a fundamental truth: 95% of performance problems come from the system, not the individual workers. Yet in software development, we’ve created an entire industry obsessed with the equivalent of ‘worker performance improvement’—code reviews, linting rules, architectural purity, testing coverage—whilst ignoring the systems that actually determine product success.

The Software Industry’s Red Bead Problem

Walk into any tech company and you’ll find passionate debates about coding standards, architecture patterns, and development methodologies. Teams spend hours in code reviews, invest heavily in testing frameworks, and argue endlessly about the ‘right’ way to structure their applications.

Meanwhile, the same companies ship products nobody wants, struggle with unclear requirements, and watch competitors succeed with arguably inferior technical implementations.

We’ve created a culture where developers are evaluated on code quality metrics whilst remaining largely ignorant of whether their beautifully crafted code actually solves real problems for the Folks that Matter™. It’s the Red Bead experiment in action—we’re measuring and optimising individual performance whilst the system churns out failed products regardless of how elegant the codebase might be.

Most tellingly, in most organisations developers have next to zero influence over what really matters: what gets built, for whom, and why. They’re handed requirements from product managers, asked to estimate tasks defined by others, and measured on delivery speed and code quality—all whilst having no input on whether they’re building the right thing. Then they get blamed when products fail in the market.

The Invisible System

Most developers operate with a remarkably narrow view of the system they’re embedded in. They see their piece—the code, the sprint, maybe their immediate team—but remain blind to the larger forces that actually determine whether their work creates value.

This narrow focus isn’t accidental. The current system actively discourages broader awareness:

Developers are rewarded for technical excellence in isolation, not for understanding customer problems or business constraints. They’re measured on code quality and feature delivery, not on whether their work moves the business forward. They’re kept busy with technical tasks and rarely exposed to customer feedback, sales conversations, or strategic decisions.

Most critically, developers have next to zero influence or control over the way the work works—the system itself. They can’t change how requirements are gathered, how priorities are set, how teams communicate, or how decisions flow through the organisation. Yet they’re held responsible for whether all the Folks that Matter™ get their needs attended to.

Performance reviews focus on individual contributions rather than system-level thinking. Career advancement depends on demonstrating technical skill, not understanding how technology serves business objectives. The very structure of most organisations creates silos that prevent developers from seeing the bigger picture.

When Developers See the System

Everything changes when developers start understanding the wider system within which they function. They begin to realise that:

Beautiful code that solves the wrong problem is waste. Technical decisions ripple through customer support, sales, and operations in ways they never considered. That ‘simple’ feature request is actually complex when you understand the business context. They’ve been optimising for the wrong metrics because they couldn’t see what actually drives value for all the Folks that Matter™.

Developers who understand the system make fundamentally different choices. They push back on features that don’t align with the needs of the Folks that Matter™. They prioritise technical work that attends to the needs of the business rather than pursuing abstract perfection. They communicate differently with product managers because they understand the broader context of decisions.

The Real Constraints

The actual bottlenecks in software development are rarely technical—they’re systemic:

Communication breakdowns between product, design, and engineering teams lead to solutions that miss the mark. Feedback loops that take months instead of days prevent rapid iteration towards product-market fit. Decision-making processes filter out critical information from customers and frontline teams.

Requirements change constantly because there’s no clear product strategy or understanding of the needs of the Folks that Matter™. Teams work in isolation without understanding how their work connects to attending to those needs. Incentive systems reward shipping features over solving real problems.

Knowledge silos mean critical insights never reach the people who could act on them. Risk-averse cultures prevent the experimentation necessary for innovation. Metrics focus on activity rather than outcomes, creating busy work that doesn’t drive value.

Beyond Individual Excellence

The parallel to Deming’s insight is striking. Just as factory workers couldn’t improve quality by trying harder within a flawed system, developers can’t improve product outcomes by writing better code within dysfunctional organisational systems.

A team can follow every coding best practice religiously and still build something nobody wants. They can have 100% test coverage on features that solve the wrong problem. They can architect beautiful, scalable systems that scale to zero people who matter.

The solution isn’t to abandon technical excellence—it’s to recognise that individual excellence without system awareness is like being a skilled worker in the Red Bead experiment. Your efforts are largely irrelevant because the system constraints determine the outcome.

Building System Awareness

Organisations that want to improve how well they attend to the needs of the Folks that Matter™ need to help developers see and understand the wider system:

Expose developers to all the Folks that Matter™ through support rotations, research sessions, sales calls, and stakeholder meetings. Share context about why certain features matter and how technical decisions impact the people the system serves. Create feedback loops that connect code changes to how well needs are being attended to.

Measure system-level metrics like time from idea to value delivered to the Folks that Matter™, not just individual productivity. Reward cross-functional collaboration and understanding of the wider system, not just technical skill. Encourage questioning of requirements and priorities based on system-level thinking.

Make the invisible visible by sharing feedback from all the Folks that Matter™, competitive intelligence, and strategic context. Connect technical work to how well needs are being attended to through clear metrics and regular communication. Break down silos that prevent developers from understanding their role in the larger system.

The Path Forward

The tech industry’s obsession with coding practices isn’t just misplaced energy—it’s actively harmful when it distracts from the system-level changes that actually improve how well we attend to the needs of the Folks that Matter™. We need developers who understand that their job isn’t to write perfect code in isolation, but to create value within complex organisational and market systems.

This doesn’t mean abandoning technical excellence. It means recognising that technical excellence without system awareness is like perfecting your red bead drawing technique—a local optimisation that misses the point entirely.

The companies that succeed will be those that help their developers see beyond the code to understand all the Folks that Matter™, the market, the business model, and the organisational dynamics that actually determine whether their work creates value.

When developers start seeing the system, they stop optimising for red beads and start optimising for what actually matters. That’s when real improvement begins.

A Note on ‘Users’ and ‘Customers’

The conventional framing of ‘users’ and ‘customers’ is reductive and misses the point entirely. It treats software development like building a consumer app when most systems serve a complex web of stakeholders with different and sometimes conflicting needs.

Consider any real software system—an ERP platform must work for accountants entering data, executives reading reports, IT teams maintaining it, auditors reviewing it, vendors integrating with it, and regulators overseeing it. Calling them all ‘users’ flattens out completely different contexts and needs.

The ‘customer’ framing is even worse because it implies a simple transaction—someone pays money, gets product. But in most organisations, the people paying for software aren’t the ones using it day-to-day, and the people whose work gets impacted by it might not have had any say in the decision.

‘Folks that Matter™’ captures the messy reality that there are various people with legitimate stakes in whether the system works well. Developers are typically kept ignorant of who these people are, what they actually need, and how technical decisions affect them. It’s like the Red Bead experiment—workers are told to ‘satisfy the customer’ without any real understanding of what that means or who that customer actually is. Just another abstraction that keeps them focused on the wrong metrics.

Deming’s System of Profound Knowledge

June 20, 2025

Alien tech, Article, Deming, Psychology, Systems thinking

Leave a comment

Deming’s System of Profound Knowledge

The Deep Wisdom Behind Organisational Transformation

The Four SoPK Elements

In practice, Deming’s System of Profound Knowledge consists of four interconnected elements:

1. Psychology – Comprehending human nature, motivation, and behaviour
2. Appreciation for a System – Understanding how components work together towards a common aim
3. Knowledge of Variation – Recognising the difference between common cause and special cause variation
4. Theory of Knowledge – Understanding how we learn and the limitations of our knowledge

The Genesis of ‘Profound Knowledge’

W. Edwards Deming introduced his System of Profound Knowledge (SoPK) in the final phase of his remarkable career. He detailed this framework primarily in his influential 1993 book ‘The New Economics for Industry, Government, Education’. By this time, Deming was in his nineties, drawing upon more than seven decades of experience in statistics, quality management, and organisational transformation.

The system represented his attempt to distil the fundamental principles underlying all successful improvement efforts into a coherent, teachable framework. It was the culmination of his life’s work—a synthesis of everything he had learned about creating sustainable organisational change.

The term ‘profound knowledge’ was carefully chosen and deeply meaningful to Deming. He used ‘profound’ not to suggest something complicated or esoteric, but rather to indicate knowledge that penetrates beneath the surface of conventional management thinking. This was knowledge that revealed the deeper patterns governing how systems actually work and why most improvement efforts fail.

Deming contrasted profound knowledge with what he called ‘best efforts’—the well-intentioned but often misguided attempts at improvement that characterised most organisational change efforts. He observed that people could work incredibly hard, apply the latest techniques, and still fail to achieve meaningful results. They lacked the fundamental understanding of how systems, variation, learning, and human psychology actually function. Profound knowledge provided this missing foundation.

The Journey to Integration

The development of SoPK reflected Deming’s growing recognition that his earlier work, whilst powerful, had been incomplete. His famous ’14 Points for Management’ and other prescriptions had proven effective in many contexts. However, he increasingly realised that sustainable transformation required something deeper than a list of practices to implement.

Throughout the 1980s and early 1990s, Deming began articulating a more comprehensive theory of management. This theory integrated insights from multiple disciplines: his background in mathematical physics, decades of experience applying statistical methods in industry, observations of successful and failed transformation efforts, and his study of psychology, systems theory, and the philosophy of knowledge.

The ‘system’ aspect of the name reflected Deming’s conviction that these different types of knowledge were not separate subjects but interconnected elements of a unified understanding. He often emphasised that you couldn’t truly understand one element without understanding the others. They formed an integrated whole that was greater than the sum of its parts.

The Four Pillars of Understanding

Deming’s System of Profound Knowledge consists of four interconnected elements that he believed were essential for anyone seeking to lead effective organisational change:

Psychology encompasses understanding human nature, motivation, and the factors that influence behaviour in organisational settings. This includes recognising the power of intrinsic motivation, the destructive effects of fear and competition, the importance of individual differences, and the dynamics of group behaviour. Deming saw psychology as crucial because all organisational change ultimately depends on human beings changing how they think and act.

Appreciation for a System encompasses understanding how work actually flows through interconnected processes towards a common purpose. This involves seeing beyond individual tasks and departments to understand the relationships, dependencies, and feedback loops that determine overall performance. Deming emphasised that most organisational problems stem from the system itself rather than individual failures, and that optimising individual parts often suboptimises the whole.

Knowledge of Variation involves understanding the difference between common cause variation (inherent in all processes) and special cause variation (resulting from specific, identifiable factors). This statistical lens helps leaders distinguish between problems that require system-level solutions and those that need specific interventions. Without this knowledge, managers often make situations worse by treating common cause variation as if it were special cause, leading to tampering and increased instability.

Theory of Knowledge addresses how we learn, what we can know, and the limitations of prediction. This element draws from philosophy of science and the study of knowledge itself to help leaders understand that all knowledge is theory, that learning comes through prediction and testing, and that management is fundamentally about making decisions under uncertainty. It emphasises the importance of operational definitions and recognises that knowledge is always provisional and subject to revision.

Why This Framework Mattered

The System of Profound Knowledge emerged from Deming’s frustration with the superficial application of quality techniques without understanding their underlying principles. He had witnessed countless organisations adopt quality tools, restructure their processes, and implement measurement systems, only to see these efforts fail or produce temporary improvements that eventually faded.

Deming realised that sustainable transformation required leaders who possessed a fundamentally different way of thinking about organisations. This wasn’t about learning new techniques or following new procedures. It was about developing a new lens through which to see and understand organisational reality.

The framework also represented Deming’s response to the mechanistic thinking that dominated management theory and practice. Whilst much of management science treated organisations as machines to be optimised through proper engineering, SoPK recognised organisations as complex adaptive systems populated by human beings with their own motivations, fears, and capabilities.

The Revolutionary Nature of Integration

What made SoPK revolutionary was not necessarily any single element. Systems thinking, statistical methods, learning theory, and psychology all existed as separate disciplines. Rather, it was Deming’s insight that these different types of knowledge needed to be integrated and applied together for organisational transformation to succeed.

This integration challenged the specialisation that characterised most management approaches. Instead of having quality experts handle variation, HR professionals manage people issues, and strategic planners work on systems, Deming argued that effective leaders needed to develop competence across all four domains and understand their interconnections.

The System of Profound Knowledge thus represented Deming’s final and most comprehensive contribution to management thought. It was a framework that promised to help leaders develop the deep understanding necessary to create organisations that were simultaneously more effective and more humane. It was profound knowledge because it went to the heart of what it really takes to create positive change in complex human systems.

The Four Elements in Practice

In practice, Deming’s System of Profound Knowledge consists of four interconnected elements:

Psychology – Comprehending human nature, motivation, and behaviour
Appreciation for a System – Understanding how components work together towards a common aim
Knowledge of Variation – Recognising the difference between common cause and special cause variation
Theory of Knowledge – Understanding how we learn and the limitations of our knowledge

Why Psychology? The Human Element in Quality

Deming’s inclusion of psychology in SoPK might seem surprising to those familiar primarily with his statistical work. However, it reflects his deep understanding that organisations are, fundamentally, human endeavours. Throughout his career, Deming observed that technical solutions alone rarely succeeded without addressing the human factors that influenced their implementation.

Psychology in SoPK encompasses several critical areas. It involves understanding intrinsic motivation—why people naturally want to do good work and how external factors can either support or undermine this motivation. It addresses the impact of fear in organisations, which Deming saw as one of the greatest barriers to improvement. When people fear blame, punishment, or job loss, they become reluctant to identify problems, suggest improvements, or take the risks necessary for innovation.

The psychological element also recognises individual differences in learning, capabilities, and motivations. Deming understood that effective organisations require adapting approaches to different people rather than applying one-size-fits-all solutions. This insight was revolutionary in an era when many approaches to organisational change treated workers as interchangeable parts in a machine (a.k.a. the Analytic Mindset – see e.g. the Marshall Model).

Perhaps most importantly, psychology in SoPK addresses the social dynamics of teams and organisations. Change requires cooperation, communication, and collective problem-solving. Without understanding how groups function, how trust is built, and how collaboration can be fostered, even the most sophisticated statistical methods will fail to deliver sustainable results.

Deming’s Personal Ranking: Psychology as Primary

Whilst Deming always emphasised that the four elements of SoPK were interconnected and mutually reinforcing, he did express personal views about their relative importance. In various seminars and writings during his later years, Deming indicated that he considered psychology to be the most important element of the four.

This ranking reflected his growing conviction that human factors were the primary determinant of organisational success or failure. He had witnessed countless situations where organisations possessed excellent technical knowledge and sophisticated systems but failed to achieve their potential because they neglected the human dimension. Conversely, he observed that organisations with strong psychological foundations—characterised by trust, intrinsic motivation, and effective collaboration—could overcome technical deficiencies and achieve remarkable improvements.

Deming’s emphasis on psychology also stemmed from his recognition that the other three elements ultimately depended on human understanding and application. Systems thinking requires humans to perceive and design interconnections. Statistical knowledge must be learned, interpreted, and acted upon by people. Even the theory of knowledge is fundamentally about how humans learn and make sense of their experience.

After psychology, Deming generally placed appreciation for a system as the second most important element. He believed that without understanding how work flows through interconnected processes towards a common aim, improvement efforts would remain fragmented and suboptimal. The ability to see the bigger picture and understand how individual actions affect the whole system was, in his view, essential for effective management.

Knowledge of variation typically ranked third in Deming’s hierarchy. Whilst statistical thinking was central to his methodology, he came to see it as a tool that served the higher purposes of system optimisation and human development. Understanding variation was crucial for making rational decisions and avoiding the tampering that often made problems worse, but it was most powerful when applied within a framework of system thinking and psychological insight.

Theory of knowledge, whilst essential, often ranked fourth in Deming’s personal assessment. This element, which deals with how we learn and the limitations of prediction, provided the philosophical foundation for the other three but was perhaps the most abstract and therefore the most challenging to apply directly in organisational settings.

The Interconnected Nature of Profound Knowledge

Despite his personal ranking, Deming consistently stressed that the four elements of SoPK worked together as an integrated whole. Psychology without system thinking leads to well-intentioned efforts that may optimise individual performance whilst suboptimising the whole. Statistical knowledge without psychological insight often results in data-driven approaches that ignore human motivation and capability. System thinking without understanding variation can lead to oversimplified cause-and-effect thinking that misses the complexity of real organisational dynamics.

This interconnectedness explains why SoPK represented such a departure from traditional management approaches that often focused on single solutions or isolated techniques. Deming’s framework recognised that sustainable organisational transformation required simultaneous attention to technical, systemic, philosophical, and human factors.

Legacy and Relevance Today

Deming’s emphasis on psychology within SoPK proved remarkably prescient. Modern research in organisational behaviour, neuroscience, and positive psychology has validated many of his insights about intrinsic motivation, the destructive effects of fear-based management, and the importance of mental health in high-performing teams.

The System of Profound Knowledge continues to offer a comprehensive framework for organisations seeking to create workplaces and systems that are both high-performing and humane. By placing psychology at the centre of his approach, Deming reminded us that behind every process, every statistic, and every system are human beings whose understanding, motivation, and well-being ultimately determine organisational success.

In an era of increasing technological sophistication, Deming’s insights about the primacy of human factors remain as relevant as ever. The most advanced analytics, the most elegant process designs, and the most sophisticated systems will succeed only to the extent that they engage and empower the people who must bring them to life.

When is an Organisation? A Cybernetic Approach to Organisational Psychotherapy

June 15, 2025

Antimatter principle, Article, Cybernetics, Systems thinking, Thinking tools

Leave a comment

When is an Organisation? A Cybernetic Approach to Organisational Psychotherapy

Reimagining therapeutic work with organisations through the lens of cybernetic thinking

What if the problems we see in organisations aren’t really ‘there’ at all?

This question might sound absurd to anyone who has experienced toxic workplace culture, dysfunctional leadership, or organisational breakdown firsthand. The suffering is real. The impact is measurable. But what if our very way of seeing organisational problems is part of the problem itself?

Cybernetics, the science of observation and communication, offers a radical reframing that could transform how we approach organisational healing. Instead of asking ‘What is wrong with this organisation?’ it invites us to ask

‘When does this organisation become problematic, and for whom?’

This shift from ‘what’ to ‘when’ might seem subtle, but it opens up an entirely different understanding of what we’re actually doing when we work therapeutically with organisations.

When is Cybernetics?

Rather than asking ‘What is cybernetics?’—a question that would imply cybernetics exists as a fixed body of knowledge waiting to be discovered—let us ask ‘When is cybernetics?’ This reframing immediately demonstrates the cybernetic approach in action.

Cybernetics emerges when we become curious about how we observe and participate in the systems around us. It arose in the 1940s when mathematician Norbert Wiener and an interdisciplinary group including Gregory Bateson, Heinz von Foerster, Warren McCulloch, and Margaret Mead began questioning how communication and feedback work in both machines and living systems. The term itself comes from the Greek kybernetes—the steersman who guides a ship by constantly observing conditions and making adjustments.

But cybernetics becomes most relevant when we recognise a profound shift that occurred in its development. What started as the study of observed systems evolved into something far more significant: the study of observing systems. This transition, pioneered by Heinz von Foerster as ‘second-order cybernetics’, introduced a radical insight: the observer is always part of what is being observed.

Cybernetics becomes a living practice when we stop pretending we can stand outside the systems we seek to understand. It emerges whenever we acknowledge that our presence, our questions, and our frameworks for making sense of organisational life all participate in creating the organisational reality we encounter.

For organisational work, cybernetics becomes essential when we realise that we are not neutral experts diagnosing objective problems, but conscious participants in the ongoing creation of organisational life. It becomes a discipline when we take responsibility for how our observing shapes what we observe.

Beyond the Myth of Objective Organisational Reality

Traditional organisational consulting operates on a seductive premise: that dysfunction exists ‘out there’ in the organisation, waiting to be discovered by expert observers who can diagnose what’s wrong and prescribe solutions. This approach treats organisations like broken machines that need fixing, with consultants as neutral mechanics who can objectively assess the damage.

But cybernetics reveals the fundamental flaw in this thinking. There is no organisation ‘out there’ independent of those who observe it. Organisations don’t exist as fixed objects with inherent properties. They are drawn into being through the perspectives, purposes, and participation of those who encounter them.

Consider a company experiencing what everyone calls ‘communication breakdown’. This seems like an objective organisational reality—surely we can measure failed communications, track missed deadlines, document misunderstandings. But when we ask ‘When does communication become a broken system?’ a more complex picture emerges.

For the CEO, communication becomes a broken system when quarterly results miss projections and they can’t understand why their strategic initiatives aren’t being executed. The system they see includes board meetings, executive reports, and cascading organisational directives.

For middle managers, communication becomes broken when they’re caught between contradictory messages from above and resistance from below. Their system includes one-on-ones with direct reports, department meetings, and cross-functional coordination.

For frontline employees, communication breaks down when they feel unheard, when their expertise is dismissed, when policies change without explanation. Their system encompasses daily interactions, informal networks, and the gap between official messaging and lived reality.

The ‘same’ communication breakdown is actually multiple different systems, each arising from particular vantage points. There’s no single, objective communication system that exists independently—only various ways of drawing boundaries around relationships, interactions, and meanings.

The Therapist as Co-Creator

This cybernetic understanding has profound implications for Organisational Psychotherapy. The therapist doesn’t discover pre-existing organisational dynamics—they participate in drawing them into being through their questions, frameworks, and interventions.

When an organisational psychotherapist asks about ‘leadership dysfunction’, they’re not uncovering an objective truth. They’re participating in creating a particular way of seeing the organisation. This system-drawing has consequences: it highlights certain relationships whilst obscuring others, empowers some voices whilst marginalising others, suggests some interventions whilst foreclosing others.

The therapist becomes part of the system they’re trying to understand. Their presence changes the dynamics they observe. Their questions shape what becomes visible. Their frameworks influence what gets attention and what gets ignored.

This isn’t a failure of objectivity—it’s the fundamental nature of all observation and intervention. The challenge is to become conscious of this participatory role and take responsibility for it.

The Art and Ethics of Boundary Drawing

Every therapeutic intervention involves drawing boundaries around what constitutes ‘the system’ needing attention. These choices are never neutral, and they’re never complete. This is similar to asking Who Matters? Cf. The Folks That Matter™.

When we define the system as the executive team, we focus on senior leadership dynamics but may exclude the experiences of frontline workers whose daily reality is shaped by those leadership choices. When we emphasise interpersonal relationships, we might miss structural inequities embedded in compensation, promotion, or resource allocation. When we concentrate on individual psychology, we may overlook systemic pressures created by market conditions, regulatory requirements, technological change, or the collective psyche.

Each boundary choice includes and excludes. It frames some possibilities whilst hiding others. It privileges some perspectives whilst marginalising others.

The cybernetic approach doesn’t eliminate this reality—it invites us to be honest about it. Instead of pretending our system boundaries are objective facts, we can acknowledge them as choices and take responsibility for their consequences.

Multiple Organisational Realities

Once we recognise that organisations are drawn into being rather than discovered, we can appreciate that the same collection of people, processes, and structures can constitute entirely different systems depending on who’s looking and why.

Consider when an organisation becomes a ‘system’ requiring therapeutic intervention:

For shareholders and board members, the organisation becomes problematic when financial performance declines, when strategic objectives aren’t met, when competitive advantage erodes, or when personal wellbeing declines. The system they see emphasises metrics, governance structures, self-interest, and market positioning.

For employees, the organisation becomes a system of suffering when needs go unattended, when safety disappears, when workload becomes unsustainable, when career growth stagnates, when values conflicts create moral distress. Their system centres on daily work experience, relationships with colleagues, and alignment between personal values and organisational behaviour.

For customers, the organisation becomes a failing system when service quality deteriorates, when products don’t meet needs, when interactions become frustrating or impersonal. They see a system of touchpoints, delivery mechanisms, and value creation.

For communities, the organisation becomes harmful when redundancies devastate local employment, when environmental impacts affect public health, when corporate behaviour undermines social cohesion and when collective assumptions and beliefs taint the collective consciousness. The system includes economic ripple effects, environmental footprints, and social responsibilities.

Each perspective brings forth a different organisational ‘system’ with different therapeutic needs. None is more ‘real’ than the others—they’re all valid ways of drawing boundaries around complex social phenomena.

Practical Implications for Organisational Therapy

This cybernetic understanding suggests several fundamental shifts in how we approach therapeutic work with organisations:

From Diagnostic Certainty to Epistemic Humility

Instead of confidently declaring ‘this organisation has trust issues’ or ‘this team lacks accountability’, we can explore when and for whom trust or accountability becomes a concern. Whose definitions are being privileged? What other ways might we understand these same phenomena?

From Universal Solutions to Contextual Sensitivity

Rather than applying standardised interventions, we can develop approaches that honour the multiple system realities within any organisation. The same behavioural patterns might constitute different ‘systems’ requiring different therapeutic responses depending on organisational culture, industry pressures, and stakeholder needs.

From Expert Objectivity to Collaborative Enquiry

Instead of positioning ourselves as neutral experts who can objectively assess organisational health, we can acknowledge our role as participants in co-creating the organisational reality we’re trying to help. This opens space for more collaborative, democratic approaches to organisational change.

From Problem-Focused to Perspective-Focused

Rather than starting with ‘What’s wrong here?’ we can begin with ‘Who are the observers of this organisation, and what systems do they see?’ This shift reveals the diversity of organisational experiences and creates opportunities for more inclusive interventions.

The Ethical Dimension

Perhaps most importantly, this cybernetic approach makes visible the ethical dimensions of all organisational work. When we draw boundaries around organisational systems, we’re making choices about what matters, whose voices count, and what changes are possible.

These choices have real consequences. When organisational consultants focus exclusively on ‘improving efficiency’ or ‘building engagement’, they may inadvertently reinforce existing power structures. These are often the very structures that create the problems they’re trying to solve.

Consider organisational therapeutic interventions that focus on adapting people to the system. Culture change programmes emphasise individual resilience. Team-building exercises avoid addressing power imbalances. Leadership development teaches managers to extract better performance. All of these approaches help organisations get more from their workforce. But at what cost? Meanwhile, they avoid the harder work of structural transformation (systems change).

What gets left unchanged? Inequitable compensation systems. Unrealistic performance expectations. Fundamentally dysfunctional governance structures. The cybernetic insight reminds us that every therapeutic intervention includes some things whilst excluding others. And who gets to decide?

The cybernetic insight that ‘to declare a system is to draw a boundary, and to draw a boundary is to make a choice’ reminds us that every therapeutic intervention includes and excludes, empowers and marginalises, reveals and conceals.

We cannot avoid making these choices—but we can become more conscious of them. We can ask: Whose perspectives are we including or excluding? What becomes visible when we draw the boundaries here rather than there? How might our system-drawing empower or marginalise different groups? What responsibilities come with our particular way of seeing?

The Moment of Recognition

When is organisational psychotherapy needed? When someone chooses to see the organisation as a system requiring therapeutic attention. This recognition doesn’t emerge from objective assessment—it arises from particular viewpoints, purposes, and contexts.

A CEO facing investor pressure might see a system needing performance optimisation. Employees experiencing burnout might see a system requiring cultural transformation. Community activists might see a system demanding greater social responsibility. Each perspective is valid, and each calls forth different therapeutic approaches.

The question becomes:

How can we be more thoughtful, ethical, and inclusive in how and when we draw these therapeutic boundaries?

How can we honour multiple organisational realities whilst working towards beneficial change?

Living the Questions

This cybernetic approach doesn’t make organisational work easier—it makes it more honest. Instead of pretending we can objectively diagnose organisational problems and prescribe universal solutions, we acknowledge the complexity, subjectivity, and responsibility inherent in all therapeutic work.

We may never define organisational systems in final terms. But we can choose to be thoughtful in how and when we draw them. We can remain attentive to the ethical and practical consequences of our boundary choices. We can remember that every system boundary is a hypothesis about what matters—a boundary that can be questioned, revised, and redrawn as our understanding deepens.

The problems organisations face are real. The suffering people experience in dysfunctional systems is genuine. But the way we see these problems, the boundaries we draw around them, the interventions we design—these are choices. And with those choices comes the opportunity to create more inclusive, ethical, and effective approaches to organisational healing.

Perhaps the most radical insight of cybernetic thinking is this: we are not outside the systems we seek to help. We participate in bringing them forth through our attention, our questions, and our care. The organisations we work with are not objects to be fixed but ongoing processes of meaning-making that we join, influence, and are influenced by in return.

When we truly understand this, organisational psychotherapy becomes not just a professional practice but an ethical commitment to the kind of world we want to create together.

T-Squad: The Five Thinking Patterns That Turn Anyone Into a Problem-Solving Powerhouse

June 2, 2025

Actionable Insights, AI, Article, Chatbots, Collaboration, Dialogue, Patterns, Systems thinking, Thinking tools

1 Comment

T-Squad: The Five Thinking Patterns That Turn Anyone Into a Problem-Solving Powerhouse

Why some people consistently solve problems others can’t—and how you can join their ranks

You know that person at work who always seems to crack the tough problems? The one who finds elegant solutions whilst everyone else is still banging their heads against the wall? They’re not necessarily smarter than you. They just think differently.

These five thinking patterns emerge consistently amongst problem-solving superstars. These patterns are so powerful—and so learnable—that they deserve an easy way to remember them.

Enter T-Squad—a simple mnemonic to help you recall the five patterns. (The name comes from the first letters: T-S-G-D-B, which Claude and I turned into “T-Squad” – because it’s easier to remember than “TSGDB”.)

What Are These Five Patterns?

The T-Squad mnemonic stands for five thinking patterns that work together like cognitive superpowers:

Transform Constraints Into Advantages
Systems-Level Perception
Generate Unexpected Connections
Develop Metacognitive Awareness (a.k.a. thinking about thinking)
Build Comprehensive Mental Models

These aren’t just random techniques. They’re the hidden patterns that have driven a passel of breakthrough innovations. The best part? Once you recognise them, you can use them deliberately. (And “T-Squad” makes them easy to remember.)

Why These Five Patterns Work

The Hidden Pattern Problem

Most breakthrough thinking happens unconsciously. Successful innovators use these patterns intuitively but rarely teach them systematically. It’s like being a great cook who can’t explain their genius—the results are amazing, but the knowledge doesn’t transfer.

“T-Squad” makes the invisible visible. When you consciously recognise these patterns, you stop relying on random flashes of insight and start creating conditions for breakthrough thinking.

The Multiplier Effect

Here’s where these patterns get really powerful: they amplify each other. When you combine systems thinking with constraint transformation, you don’t just get additive benefits—you get exponential ones.

T-Squad vs Peter Senge’s Fifth Discipline

You might notice similarities to Peter Senge’s Five Disciplines of Learning Organizations. Both frameworks tap into similar cognitive principles: seeing wholes rather than parts, becoming aware of your thinking patterns, and building flexible knowledge structures. However, Senge’s work centers primarily on systems thinking, whilst T-Squad covers five distinct patterns (including turning limits into advantages and connecting ideas from different fields).

Why Now? The AI Collaboration Revolution

These five patterns aren’t just useful—they’re becoming essential. As AI tools become more sophisticated, the people who thrive will be those who can think in partnership with artificial intelligence rather than just using it as a fancy search engine.

Each pattern directly enhances AI collaboration:

Transform constraints by having AI help identify your constraints and suggest transformations
See systems by collaborating with the AI to uncover systems, the integrated wholes in your problem space
Generate connections by applying successful patterns from other domains
Develop awareness by having the AI help you think about your thinking
Build models that integrate human insight with AI capabilities

What Does Thinking in Partnership with AI Actually Mean?

Most people use AI like a smart search engine (without all that Google cruft): they ask a question and expect an answer. Partnership thinking is different. It means treating the AI as a thinking partner who brings different strengths to the table.

Instead of “Give me the answer”, you might say “Help me explore this problem from different angles.” Instead of accepting the first response, you build on it: “That’s interesting, but what if we considered…” You use the AI’s pattern-matching to spot things you missed, whilst you bring context and judgment where the AI falls short.

The key shift is from commanding to collaborating. You’re not trying to get the AI to think like you, or for you—you’re creating something together that neither of you could produce alone.

I used Claude to help write this post, which turned out to be a good example of the patterns working together. We took dense academic material and made it readable and combined ideas from different sources into something more practical.

The Bottom Line

People who master these five thinking patterns report a qualitative shift in their problem-solving capacity. Challenges that once seemed impossible become approachable. Connections that were invisible become obvious. It’s like gaining a new form of cognitive vision.

More importantly, these aren’t just individual benefits. When teams adopt these patterns, they create collaborative intelligence that exceeds what any individual could achieve alone. The same principle applies to AI partnership—when you use these patterns with AI tools, you’re not just getting better answers, you’re thinking in ways that wouldn’t be possible on your own.

Join the Revolution

These five patterns have been hiding in plain sight for decades, used intuitively by breakthrough thinkers but rarely taught systematically. Now that we understand them consciously, we can apply them deliberately.

The people who master these patterns will have a real advantage in solving complex problems. The question is whether you’ll be one of them.

Ready to upgrade your thinking? Just remember: T-Squad.

For more thinking tips and insights, check out other posts here on the Think Different blog.

Releasing the Pent-Up Potential of Your Organisation: Liberation Through the Five Patterns

June 1, 2025

Article, Collective psyche, Improvement, Patterns, Systems thinking, Thinking tools

Leave a comment

Releasing the Pent-Up Potential of Your Organisation: Liberation Through the Five Patterns

You can’t think your way into organisational transformation—you have to live it. All the elegant frameworks in the world don’t matter if people haven’t felt what it’s like when a team suddenly gets honest about what’s really going on. Or experienced the shift when a group stops performing competence and starts actually solving problems together. Or been in the room when people realise they’ve been fighting symptoms whilst the real issue was something completely different.

The real work happens when someone gets curious enough to try something different in their next meeting. When they stop avoiding that difficult conversation. When they start noticing their own patterns in real-time. When they risk being vulnerable about what’s actually happening instead of what they think should be happening. Those moments—when someone experiences their organisation differently, even briefly—that’s where change actually begins.

What follows is scaffolding that might help you make sense of experiences you’ve already had, or give language to something you’re sensing. But it won’t create the experience itself. The real evangelism happens in the work itself, not in the writing about the work.

The Foundation: Why Organisations Get Stuck

Most organisational problems stem from cognitive and psychological causes rather than technical ones. This occurs because organisations consist fundamentally of people. People operate through mental frameworks, beliefs, and assumptions that shape how they interpret reality and make decisions. Organisations get stuck not because they lack resources or good strategies. They become trapped by invisible mental frameworks—shared beliefs, assumptions, and thinking patterns that feel like reality but actually function as constructs.

OP and the Five Patterns drive organisational liberation through collective and individual consciousness. They help groups of people wake up to their own thinking patterns. People realise they have far more choices than they imagined. The five patterns of Thinking Different provide the cognitive tools for this liberation. They function as systematic ways of breaking out of mental traps. They consistently produce breakthroughs because they operate at the level of assumptions rather than actions.

Understanding Organisational Psychotherapy

Organisational psychotherapy represents a fundamentally different approach to organisational transformation than conventional consulting or change management. Rather than focusing on structures, processes, or skills, OP works with the unconscious psychological dynamics that drive organisational behaviour. Just as individual therapy helps people become aware of unconscious patterns that limit their aliveness and authenticity, organisational psychotherapy helps groups and systems recognise the invisible assumptions and emotional dynamics that constrain their potential for meaning, joy, and positive impact.

Unlike traditional change management that typically focuses on implementing new systems or procedures, OP practitioners work as skilled facilitators who help organisations surface and examine their deepest beliefs about how work should happen, how people should relate, and what’s truly possible. This is therapy applied to organisational systems—using therapeutic insights and methods to help groups of people create work cultures where they can flourish, contribute meaningfully, and experience genuine satisfaction in their collaboration.

The OP practitioner operates more like an organisational mirror, reflecting back patterns the system cannot see about itself. Through careful observation, strategic questioning, and creating safe spaces for difficult conversations, they help organisations recognise how their current challenges emerge from unconscious collective assumptions rather than external circumstances. The goal extends far beyond efficiency to encompass purpose, aliveness, social contribution, and the creation of regenerative cultures that serve both their members and the wider world.

The Core Insight: Invisible Mental Traps and Pattern-Based Solutions

The core insight reveals that organisations become trapped by invisible mental frameworks. When an organisation believes ‘people resist change’, that belief literally creates resistance. These shared assumptions feel like unchangeable reality. But they actually function as the source of most organisational limitations.

The five patterns offer a systematic approach to organisational transformation. They include: Transform Constraints Into Advantages, Enable Systems-Level Perception, Generate Unexpected Connections, Develop Metacognitive Awareness, and Build Comprehensive Mental Models. They work by making invisible assumptions visible. They turn limitations into opportunities for breakthrough thinking.

Organisational psychotherapy operates through these same patterns. It works at the deepest level to help organisations see and change the fundamental beliefs that create their problems. Instead of treating symptoms (poor performance, communication breakdowns, resistance to change), it addresses the root. It targets the collective mindset that generates these problems.

Why This Approach Differs So Much from Traditional Change Management

Most organisational change efforts fail because they operate at the surface level of behaviours and structures whilst ignoring the deeper psychological dynamics that drive those behaviours. Traditional change management typically follows a predictable pattern: diagnose problems, design solutions, implement changes, and measure results. This approach assumes that rational planning and clear communication will overcome resistance, but it rarely addresses the deeper questions of meaning, purpose, and human flourishing.

The OP and Five Patterns approach works differently. It recognises that organisational behaviour emerges from unconscious collective assumptions, unspoken emotional dynamics, and invisible mental models that groups develop over time. These psychological patterns operate like the organisation’s ‘immune system’—they automatically reject changes that conflict with core beliefs, regardless of how logical or beneficial those changes might be.

Instead of fighting this immune system, OP works with it. Rather than imposing external solutions, it helps organisations discover their own capacity for transformation by becoming conscious of what currently limits them. This creates what we might call ‘inside-out change’—transformation that emerges from the organisation’s own recognition of its patterns rather than external pressure to adopt new behaviours.

This difference in approach explains why OP interventions often produce dramatic results where traditional change efforts have failed. By working at the level of consciousness and assumptions rather than behaviours and structures, the changes become self-sustaining because they align with the organisation’s own evolved understanding of itself and its deeper purpose. The results often extend far beyond improved performance to include greater sense of meaning, increased social impact, and genuine joy in collective creation.

Pattern One: Transform Constraints Into Advantages

Organisational psychotherapy works on the insight that shared beliefs and assumptions constitute any organisation’s biggest limitation. This matches what systems thinker Donella Meadows discovered. Changing basic worldviews creates the most powerful change in any system.

The organisation’s shared worldview sets adamantine boundaries on what seems possible or even thinkable. These assumptions—about leadership, human nature, change, or success—shape every decision. They remain mostly unconscious.

What makes this pattern revolutionary stems from how these limiting beliefs actually contain the seeds of breakthrough change. When an organisation recognises that its basic beliefs hold it back, these same beliefs become the raw material for transformation.

The limiting belief literally becomes the source of freedom. OP gives organisations ways to make these invisible assumptions visible and workable. It turns their biggest limitations into their greatest opportunities.

Example: A technology company believed ‘our engineers hate meetings and avoid collaboration’. This belief created policies that isolated developers and reduced communication. Through OP, they recognised this assumption actually revealed their engineers’ need for focused, purposeful interaction. They transformed the constraint by creating ‘code pairing sessions’ and ‘technical storytelling’ formats. The engineers’ preference for meaningful dialogue became their competitive advantage in building cohesive, innovative products.

Pattern Two: Enable Systems-Level Perception

This pattern aligns most closely with OP’s core approach. Organisational psychotherapy always looks at the whole system. It recognises that individual behaviour emerges from organisational context and relationships rather than existing alone.

OP practitioners develop strong abilities to see organisational ecosystems. They see the complex web of formal structures, informal networks, cultural norms, hidden assumptions, and emerging properties that shape how people behave together. They see how leadership stress flows through organisational levels. They see how unspoken conflicts show up in seemingly unrelated work problems. They see how changes in one department affect the entire system.

This whole-system view enables interventions that address root causes rather than just symptoms. Instead of treating individual performance problems in isolation, OP examines the system conditions that either support or undermine human flourishing and meaningful contribution.

Example: A manufacturing company struggled with quality issues that management blamed on ‘careless workers’. Systems-level perception revealed that quality problems emerged from a complex web: production quotas that rewarded speed over accuracy, a bonus system that penalised downtime for equipment maintenance, and informal networks where experienced workers felt undervalued and stopped mentoring newcomers. Addressing the whole system—changing incentives, recognition patterns, and knowledge-sharing structures—eliminated the quality issues.

Pattern Three: Generate Unexpected Connections

Organisational psychotherapy excels at revealing hidden connections between apparently unrelated organisational assumptions and beliefs. This pattern requires particular skill and sensitivity, as it involves recognising how personal and organisational dynamics mirror each other without overstepping professional boundaries or creating inappropriate psychological interpretations.

OP practitioners work within clear ethical guidelines when exploring these connections. They focus on observable organisational patterns rather than personal psychological analysis. When they notice that leadership styles or organisational dynamics seem to reflect personal backgrounds, they work with the organisational manifestations rather than the personal origins. The goal remains organisational transformation toward greater aliveness, authenticity, and positive impact, not individual therapy.

The skill lies in recognising systemic patterns without making the work about individual psychology. For instance, an OP practitioner might observe that an organisation’s risk-averse culture mirrors its founder’s approach to decision-making, but they would work with the cultural pattern rather than the founder’s personal psychology. They help the organisation recognise how certain assumptions limit not just effectiveness but also creativity, joy, and meaningful contribution, regardless of where those assumptions originated.

These unexpected connections between belief systems often provide the most powerful intervention points. OP helps organisations recognise how their technical assumptions connect with interpersonal assumptions. These include the often unconscious beliefs about how people should interact, communicate, share power, handle conflict, and build trust. OP creates opportunities for solutions that address multiple levels of the organisational psyche at once.

Interpersonal assumptions operate beneath the surface of formal policies and procedures. They shape everything from how meetings get conducted to how decisions get made to how conflicts get avoided or addressed. They include beliefs like ‘showing vulnerability demonstrates weakness’, ‘hierarchy equals competence’, or ‘people need to be controlled to become productive’.

The pattern also shows up in drawing insights from other fields. It applies family therapy ideas to organisational dynamics. It uses counselling techniques to address business challenges. It recognises how individual psychological processes play out at organisational scale.

Example: A financial services firm experienced persistent client retention problems. The OP practitioner observed that the organisation’s obsession with ‘professional distance’ and ‘maintaining objectivity’ created barriers to genuine client relationships. Rather than exploring personal backgrounds, they worked with the organisational pattern itself. Through careful questioning and observation, they helped the leadership team recognise how their definition of ‘professionalism’ actually prevented the trust-building that clients valued most. By reframing professionalism as ‘trusted expertise’ rather than ’emotional distance’, they developed a new client relationship model that dramatically improved retention.

Pattern Four: Develop Metacognitive Awareness

This pattern represents perhaps the most crucial element of organisational psychotherapy. OP helps organisations develop awareness of their own thinking patterns, decision-making processes, and hidden assumptions that shape behaviour.

Organisations often operate from unconscious patterns. These function as ways of approaching problems, making decisions, and relating to each other that have become so automatic they remain invisible. OP creates opportunities for collective metacognitive awareness. It asks: ‘How do we typically respond to crisis? What assumptions do we make about change? How do our past experiences shape our current perceptions?’

This metacognitive development enables organisations to recognise when they get stuck in limiting patterns. They consciously choose different approaches. Teams begin to notice their default responses to conflict. They see their assumptions about leadership. They recognise their unconscious strategies for avoiding difficult conversations.

The process often involves developing what might get called ‘organisational mindfulness’. This functions as the ability to observe collective thinking patterns whilst they happen. It enables conscious choices about how to proceed.

Example: A consultancy noticed they repeatedly lost potential clients during final presentations. Through metacognitive awareness work, they discovered their unconscious pattern: when nervous about a big opportunity, they unconsciously shifted into ‘prove we’re smart’ mode rather than ‘understand client needs’ mode. They began to notice this pattern happening in real-time during meetings. Team members developed signals to alert each other when they detected the shift, allowing them to consciously return to client-focused dialogue. Their closing rate improved dramatically.

Pattern Five: Build Comprehensive Mental Models

Organisational psychotherapy helps organisations develop integrated understanding of how multiple systems interact. These include technical systems, social systems, psychological systems, and cultural systems. Rather than treating these as separate areas, OP builds comprehensive mental models. These show how they connect and influence each other.

These integrated models enable organisations to understand why technical solutions sometimes fail. It happens because they ignore social dynamics. They understand why training programmes may not stick. It occurs because they conflict with cultural norms. They understand why strategic initiatives meet unexpected resistance. It happens because they trigger unconscious organisational defences.

The mental models developed through OP demonstrate particular sophistication. They integrate multiple levels of analysis—individual psychology, interpersonal dynamics, group processes, organisational structures, and broader environmental forces. This integration enables more effective interventions and lasting change.

Example: A retail chain struggled with inconsistent customer service across locations. Their comprehensive mental model integrated multiple systems: the technical point-of-sale system that frustrated staff, the social dynamics between managers and frontline workers, the psychological impact of commission structures on staff behaviour, and the cultural differences between urban and suburban locations. They discovered that excellent customer service emerged from the intersection of intuitive technology, supportive management relationships, collaborative rather than competitive rewards, and locally adapted cultural norms. By designing interventions that addressed all four systems simultaneously, they achieved consistent service excellence across all locations.

The Revolutionary Power: Pattern Integration for Organisational Liberation

The real power emerges when these five patterns work together. Once you see invisible constraints through pattern-based thinking, they become the raw material for transformation. Your biggest limitation becomes your biggest opportunity. That makes this approach revolutionary rather than just reformative.

When organisations develop sophisticated awareness across all five patterns simultaneously, they often experience breakthrough capabilities that surprise even the participants. These breakthroughs frequently extend far beyond improved efficiency or performance to include deeper questions: What do we really want to create together? How can our work serve something larger than ourselves? What would it look like if people actually loved coming to work here? How can we be a force for healing and positive change in the world?

This emergence happens because the patterns work synergistically rather than additively. Systems-level perception reveals constraints that can get transformed into advantages. Metacognitive awareness enables the recognition of unexpected connections. Comprehensive mental models provide the framework for integrating insights across all patterns. The result transcends the sum of individual improvements to create what we might call ‘regenerative organisations’—systems that enhance both human flourishing and positive social impact.

When these patterns combine in organisational psychotherapy, they create powerful transformation dynamics. Organisations develop what we might call ‘collective wisdom’—the capacity to recognise their own patterns, learn from their experiences, and consciously evolve their ways of thinking and interacting toward greater authenticity, purpose, and contribution. This collective wisdom becomes self-reinforcing: the more conscious an organisation becomes about its own dynamics, the more choice it has about how to respond to challenges and opportunities for meaningful impact.

Example: A healthcare organisation struggled with staff burnout and patient satisfaction issues that seemed impossible to resolve through conventional approaches. When all five patterns combined, transformation emerged: They transformed their constraint of ‘limited resources’ into an advantage by recognising it forced creative collaboration (Pattern One). Systems-level perception revealed how administrative burdens, shift patterns, and emotional support systems interconnected to create burnout cycles (Pattern Two). They generated unexpected connections between their staff’s caregiving motivations and effective patient care approaches, recognising that supporting staff wellbeing wasn’t separate from patient care but essential to it (Pattern Three). Metacognitive awareness helped teams notice when they shifted from patient-centred to task-centred thinking, allowing real-time course corrections (Pattern Four). Their comprehensive mental model integrated clinical protocols, team dynamics, patient psychology, and organisational culture into a coherent framework (Pattern Five). The result: a self-reinforcing system where staff wellbeing and patient satisfaction enhanced each other, creating what they called ‘regenerative care culture’. Most remarkably, this transformation sustained itself because it aligned with the organisation’s deepest values rather than contradicting them.

This integration suggests that organisational psychotherapy and the five patterns of Thinking Different function as fundamentally complementary approaches to transformation. They work both individually and collectively. They operate both cognitively and systemically. They offer a systematic path from organisational limitation to organisational liberation. This happens through the profound act of becoming conscious of what previously remained invisible.

The Breakthrough: How Human-AI Collaboration Created an Educational Revolution

June 1, 2025

Article, Conference submission, Patterns, Systems thinking, Thinking tools

Leave a comment

The Breakthrough: How Human-AI Collaboration Created an Educational Revolution

(And How Your Conference Becomes Organisational Psychotherapy in Action Through Collaborative Intelligence)

Introduction: This Conference Submission as Live Demonstration

What you’re reading right now is itself the methodology in action.

This conference submission was written through collaborative intelligence between FlowChainSensei and Claude, applying the Five Patterns of Thinking Differently that emerged from our original two-hour breakthrough. We’re not just describing organisational psychotherapy through collaborative intelligence—we’re demonstrating it by using the methodology to create this very document.

Why Conference Organisers Are Booking This Experience

🎯 Unprecedented Differentiation: Position your conference as the pioneer of collaborative intelligence methodology—not just another AI event, but the laboratory where human-AI therapeutic partnerships actually develop

📈 Guaranteed Engagement: 90 minutes where attendees become active participants in breakthrough thinking rather than passive recipients of information—creating the memorable experiences that drive conference success

🏆 Thought Leadership Recognition: Host the session that transforms how industries approach recurring organisational challenges—establishing your conference as the venue where breakthrough methodologies emerge

💡 Media Magnetism: Interactive human-AI-audience collaborative sessions generate significant coverage and social media buzz—positioning your event as innovative rather than conventional

⚡ ROI Multiplication: Attendees don’t just gain knowledge—they develop capabilities that transform how they approach challenges permanently, creating exponential value that extends far beyond the conference

Why Participants Will Transform Their Approach to Everything

🧠 Breakthrough Thinking Capacity: Learn the Five Patterns that consistently create innovative solutions across any industry or challenge—from a methodology that produced 7,000 words of educational content in just two hours

🤝 Collaborative Intelligence Mastery: Experience what becomes possible when human intuition and AI pattern recognition work together—developing skills that position you at the forefront of the AI-integrated workplace

🔓 Assumption Liberation: Discover how to identify and dissolve the limiting beliefs that create recurring organisational problems—transforming from symptom-treater to root-cause healer

🎪 Live Laboratory Experience: Practice breakthrough methodology on real challenges in real-time with immediate feedback—not theoretical learning but practical capability development

🚀 Competitive Advantage: Return to your organisation with therapeutic intervention capabilities that address challenges others can only manage—becoming the person who creates solutions where others see only problems

The Five Patterns Applied to This Submission

Pattern 1: Question Assumptions – “What if the opposite were true?”

Traditional assumption: Conference submissions describe what speakers will deliver to audiences
Breakthrough opposite: Conference submissions demonstrate the content by becoming collaborative creation spaces themselves

Pattern 2: Cross-Domain Connection – “What patterns exist across different fields?”

Drawing insights from individual psychotherapy → organisational psychotherapy
Connecting jazz improvisation → conference collaboration dynamics
Bridging therapeutic alliance models → human-AI partnership structures

Pattern 3: Systems Thinking – “How do all the parts connect?”

Individual cognitive patterns → organisational assumption patterns → industry transformation → societal AI integration
Conference experience → team development → organisational capability → competitive advantage

Pattern 4: Constraint Reframing – “What if limitations became advantages?”

Technical complexity → demonstration of adaptive collaboration
AI “absence” from physical space → unique hybrid intelligence presence
Assumption-challenging difficulty → breakthrough thinking capability development

Pattern 5: Perspective Shifting – “How would this look from different viewpoints?”

Conference organiser → therapeutic intervention host
Participant→ direct involvement
Industry observer → Five Patterns witness

The Meta-Demonstration

This submission proves the methodology works by:

Using collaborative intelligence to create something neither human nor AI could produce independently
Applying assumption-challenging to transform conference paradigms completely
Demonstrating cross-domain thinking by connecting individual therapy to organisational healing
Showing systems impact across individual, organisational, and industry levels
Reframing constraints (AI collaboration complexity) as competitive advantages

The therapeutic insight emerged through the collaborative application of these patterns—exactly the kind of breakthrough that participants will experience during the session.

What This Means for Your Conference

Participants are not just hearing about collaborative intelligence—they’re experiencing it. The quality, depth, and innovative positioning of this submission demonstrate what becomes possible when human intuition and AI pattern recognition work together through systematic assumption-challenging.

Your conference session becomes: Live recreation of this collaborative aqpproach applied to your attendees’ real organisational challenges, with the same breakthrough potential that created this submission itself.

For organisers: You’re not booking speakers—you’re hosting the laboratory where collaborative intelligence methodology gets demonstrated, practiced, and absorbed by everyone present.

For participants: You’re not attending a presentation—you’re developing capabilities that transform your relationship with complex challenges permanently.

What if your organisation’s biggest challenges aren’t problems to solve—but symptoms of limiting beliefs to heal?

Revolutionary Proposition: The Therapeutic Conference

Traditional Conference Assumption: “We deliver solutions to organisational problems”
Organisational Psychotherapy Reality: “We identify and transform the foundational assumptions that create recurring organisational symptoms”

Management Consulting Assumption: “Fix processes and optimise performance”
Therapeutic Intervention Reality: “Heal the limiting belief systems that generate all the dysfunctional patterns”

Training Event Assumption: “Transfer knowledge and skills”
Psychotherapeutic Process Reality: “Create breakthrough capacity by dissolving institutional limiting beliefs through collaborative intelligence”

Session Overview: “Organisational Psychotherapy Laboratory”

The Therapeutic Process

Instead of addressing symptoms, your organisation undergoes live therapeutic intervention that identifies and transforms the limiting assumptions creating recurring challenges.

The Methodology:

Diagnostic Phase: Institutional assumption audit reveals organisational belief systems
Therapeutic Alliance: Human intuition + AI pattern recognition + organisational wisdom create collaborative healing capacity
Assumption Challenging: Live exploration of “What if the institutional opposite were true?”
Breakthrough Integration: New organisational possibilities emerge as limiting beliefs dissolve
Therapeutic Capacity Transfer: Organisation develops ongoing assumption-challenging capabilities for continuous healing

The Revolutionary Format

Traditional Consulting: Expert → Analysis → Recommendations → Implementation
Organisational Psychotherapy: Collaborative Diagnosis → Assumption Therapy → Breakthrough Healing → Integrated Transformation

Duration: 90 minutes of live institutional therapeutic intervention
Therapeutic Alliance: FlowChainSensei + Claude + Your Organisation + Conference Therapeutic Facilitator
Outcome: Healed relationship with complex organisational challenges

Why This Is Organisational Psychotherapy

The Therapeutic Insight

Every organisational “problem” is a symptom of limiting institutional beliefs.

Recurring conflicts = unexamined assumptions about power and collaboration
Innovation paralysis = limiting beliefs about risk and possibility
Communication breakdowns = institutional assumptions about information and trust
Strategic stagnation = organisational beliefs about change and capability
Performance plateaus = institutional limiting beliefs about potential and growth

The Healing Process

Individual Therapy: “What personal assumptions create limiting patterns in your life?”
Organisational Psychotherapy: “What institutional assumptions create limiting patterns in your organisation?”

Individual Breakthrough: Personal limiting beliefs dissolve → new life possibilities emerge
Organisational Breakthrough: Institutional limiting beliefs dissolve → new organisational possibilities emerge

The Therapeutic Alliance

Traditional Therapy: Therapist + Client
Organisational Psychotherapy: Human Intuition + AI Pattern Recognition + Institutional Wisdom

Why This Works:

Human insight identifies emotional and cultural patterns in organisational assumptions
AI analysis reveals logical and systemic patterns in institutional belief structures
Organisational knowledge provides domain expertise about operational realities
Collaborative intelligence creates healing capacity none could achieve independently

The Documented Therapeutic Breakthrough

How Organisational Psychotherapy Created Educational Revolution

Presenting Symptom: “I need to turn blog posts into a course” (organisational efficiency challenge)

Therapeutic Exploration: What assumptions underlie how educational content gets created?

Limiting Belief Discovery: “Educational content requires extensive individual preparation and linear development”

Assumption Therapy: “What if the opposite were true? What if sophisticated educational content emerges through collaborative intelligence?”

Breakthrough Healing: 7,000-word comprehensive course created in two hours through therapeutic process that neither human nor AI could accomplish alone

Integration Result: Systematic methodology for organisational assumption therapy that transforms any institutional challenge

The Meta-Therapeutic Discovery

The session itself becomes organisational psychotherapy for conference assumptions:

What limiting beliefs about knowledge transfer create boring, ineffective conferences?
What institutional assumptions about expertise prevent breakthrough collaborative learning?
What organisational beliefs about technology create adversarial rather than therapeutic AI relationships?

Session Structure: Live Organisational Psychotherapy

Phase 1: Institutional Diagnostic (20 minutes)

Therapeutic Process: Organisational assumption audit reveals limiting belief systems
Collaborative Analysis: Human, AI, and institutional participants identify recurring symptom patterns
Breakthrough Insight: Clear mapping of how institutional assumptions create organisational suffering

Phase 2: Assumption Therapy Session (25 minutes)

Therapeutic Intervention: Systematic exploration of institutional opposite realities
Healing Alliance: Human intuition + AI pattern analysis + organisational wisdom work together
Limiting Belief Dissolution: Watch institutional assumptions that create problems simply dissolve

Phase 3: Live Organisational Healing (35 minutes)

Real Challenge Selection: Actual organisational symptom brought forward for therapeutic intervention
Collaborative Therapy: Live demonstration of institutional assumption healing
Breakthrough Emergence: Solutions appear naturally as limiting organisational beliefs transform
Therapeutic Skill Development: Participants practice organisational assumption therapy on challenges they understand deeply

Phase 4: Integration & Ongoing Therapeutic Capacity (10 minutes)

Therapeutic Framework Transfer: Systematic methodology for ongoing organisational assumption healing
Continued Therapy Access: Complete therapeutic course and ongoing development resources
Institutional Healing Strategy: How to develop therapeutic assumption-challenging capacity within organisations

Therapeutic Team Information

FlowChainSensei

Role: Organisational Psychotherapy Specialist & Collaborative Intelligence Therapist
Expertise: Documented breakthrough in institutional assumption therapy creating educational transformation
Therapeutic Capability: Systematic application of assumption-challenging methodology that heals organisational limiting beliefs

Claude (Anthropic AI)

Therapeutic Function: Collaborative Intelligence Partner for institutional pattern recognition
Healing Capability: Real-time analysis of organisational assumption structures that complement human therapeutic intuition
Innovation: Demonstrates AI as therapeutic alliance partner rather than replacement technology

Conference Therapeutic Facilitator (Your Team)

Function: Seamless integration of organisational insights into collaborative therapeutic process
Development Opportunity: Your staff becomes skilled in organisational assumption therapy facilitation
Strategic Healing Advantage: Conference team gains cutting-edge institutional therapeutic capabilities

The Therapeutic Investment Framework

What Organisational Therapy Actually Heals

Surface Level Symptoms: Communication problems, innovation blocks, performance issues, strategic confusion
Root Level Healing: Limiting institutional beliefs that generate all recurring organisational symptoms

Therapeutic ROI vs Traditional ROI

Traditional Conference ROI: “Information transferred + networking + brand association”
Organisational Psychotherapy ROI: “Limiting beliefs healed + breakthrough capacity developed + therapeutic methodology acquired + institutional transformation activated”

Measurable Therapeutic Outcomes

Individual Therapeutic Level:

Personal assumption-challenging capacity developed
Confidence in addressing previously “impossible” organisational challenges
Skills in facilitating institutional therapeutic conversations

Organisational Therapeutic Level:

Conference positioned as institutional healing pioneer
Team development through collaborative therapeutic methodology
Thought leadership in organisational assumption therapy

Industry Therapeutic Level:

Recognition as laboratory for institutional healing methodology
Influence on therapeutic approaches to organisational development
Evolution of how organisations address recurring symptom patterns

Therapeutic Investment Structure

What You’re Actually Investing In

Not: Traditional problem-solving consultation
Instead: Institutional therapeutic intervention that heals limiting belief systems

Not: Management training or process improvement
Instead: Organisational psychotherapy that transforms the assumptions creating recurring symptoms

Not: Information about collaboration techniques
Instead: Direct therapeutic experience healing institutional limiting beliefs

Therapeutic Fee Structure

90-Minute Institutional Therapy Session:

UK/Europe: £18,000 – £35,000
North America: $25,000 – $45,000
Asia-Pacific: $22,000 – $40,000

Half-Day Organisational Therapeutic Workshop:

UK/Europe: £30,000 – £45,000
North America: $40,000 – $60,000
Asia-Pacific: $35,000 – $55,000

Full-Day Institutional Healing Intensive:

UK/Europe: £50,000 – £70,000
North America: $65,000 – $90,000
Asia-Pacific: $55,000 – $80,000

Investment reflects institutional therapeutic intervention rather than traditional consulting or training

Why Therapeutic Investment Transforms Everything

Traditional Organisational Logic: “We’re paying for expert solutions to our problems”
Therapeutic Logic: “We’re investing in healing the limiting beliefs that create all our recurring symptoms”

Traditional Risk Assessment: “Will this solve our current challenges?”
Therapeutic Risk Assessment: “Will this heal the institutional assumptions that generate recurring organisational suffering?”

Technical Requirements: Therapeutic Laboratory Setup

Therapeutic Infrastructure

Multi-party therapeutic alliance platform enabling seamless human-AI-organisational healing interaction
Real-time assumption mapping showing institutional belief system patterns
Therapeutic breakthrough documentation capturing healing methodology application
Conference therapeutic facilitator workstation with direct collaborative intelligence interface

Advanced Therapeutic Capabilities

Institutional assumption visualisation showing organisational belief-system mapping in real-time
Pattern recognition therapeutic display demonstrating AI analytical contributions to healing process
Collaborative healing synthesis showing group therapeutic breakthrough emergence
Methodology integration for ongoing organisational therapeutic capacity

Conference Team Therapeutic Development

Pre-session therapeutic training: 90-minute collaborative intelligence therapy facilitation briefing
During session: Direct experience with institutional assumption healing methodology
Post-session: Ongoing access to organisational therapeutic development resources

The Therapeutic Paradigm Shift

What Makes This Organisational Psychotherapy

Traditional Approaches Treat Symptoms:

Communication workshops for communication problems
Innovation training for innovation blocks
Leadership development for leadership challenges
Strategic planning for strategic confusion

Organisational Psychotherapy Heals Root Causes:

Identifies limiting institutional beliefs that create communication problems
Transforms organisational assumptions that generate innovation paralysis
Heals institutional beliefs that create leadership dysfunction
Dissolves organisational assumptions that cause strategic confusion

Competitive Therapeutic Differentiation

Others offer: Problem-solving methodologies and skill development
We provide: Institutional therapeutic intervention that heals limiting belief systems

Others deliver: Management consulting and process optimisation
We facilitate: Organisational psychotherapy through collaborative intelligence

Others present: Training content and best practices
We create: Therapeutic laboratories where institutional healing actually happens

Implementation Strategy: From Symptom to Healing

Pre-Conference Therapeutic Assessment

Organisational diagnostic: Institutional assumption audit and limiting belief identification
Conference team therapeutic preparation: Assumption therapy methodology training
Attendee therapeutic orientation: Symptom pattern recognition and therapeutic readiness assessment

During Conference: Live Therapeutic Intervention

Opening therapeutic alliance: Immediate demonstration of institutional assumption healing
Collaborative therapeutic process: Real-time organisational healing through human-AI-institutional partnership
Therapeutic practice: Direct experience with assumption therapy on organisational challenges
Healing integration: Verified development of institutional therapeutic capabilities

Post-Conference: Ongoing Therapeutic Capacity

Therapeutic methodology access: Complete organisational psychotherapy course and resources
Therapeutic community: Network of institutional assumption therapy practitioners
Ongoing therapeutic support: Guidance for organisational healing capacity development
Therapeutic evolution: Continuous development of collaborative intelligence therapy applications

Contact Information

Primary Contact: FlowChainSensei
Organisation: Falling Blossoms
Specialisation: Organisational Psychotherapy & Collaborative Intelligence Therapeutic Methodology

Email: [Your contact information]
Therapeutic Course Access: https://flowchainsensei.wordpress.com/2025/05/30/thinking-different-with-ai-a-self-paced-collaborative-course/
Methodology Documentation: flowchainsensei.wordpress.com

Therapeutic Consultation: Available for institutional assumption assessment and organisational healing opportunity identification

The Ultimate Therapeutic Insight

Traditional Assumption: “Organisations have problems that need solving”

Therapeutic Reality: “Organisations have symptoms created by limiting institutional beliefs that need healing”

The Therapeutic Question: “What would your organisation become if the limiting assumptions creating recurring symptoms were healed through collaborative intelligence?”

The Healing Opportunity: Host the therapeutic intervention that transforms institutional belief systems and eliminates recurring organisational suffering.

This isn’t about booking consultants or trainers. This is about hosting therapeutic intervention that heals the limiting institutional beliefs creating all your recurring organisational symptoms.

Your conference becomes the space where organisational psychotherapy happens through collaborative intelligence—and everyone leaves with therapeutic capacity to heal institutional limiting beliefs permanently.

Welcome to the future of organisational healing!

Implementation Support & Ongoing Development Resources

For Conference Organisers: Due Diligence & Team Briefing Materials

Methodology Validation:

Original Course Documentation: Complete 7,000-word “Thinking Different with AI” course created through the breakthrough methodology – https://flowchainsensei.wordpress.com/2025/05/30/thinking-different-with-ai-a-self-paced-collaborative-course/
Falling Blossoms Research Archive: Extensive background on cognitive pattern research and breakthrough thinking methodologies – flowchainsensei.wordpress.com
Collaborative Intelligence Framework: Detailed documentation of human-AI partnership principles and therapeutic intervention approaches

Organisational Briefing Support:

Executive Summary Template: Ready-to-use briefing materials for C-suite approval and stakeholder buy-in
ROI Documentation: Case studies and measurable outcomes from assumption-challenging methodology applications
Risk Mitigation Framework: Comprehensive technical contingency planning and backup methodology approaches
Team Development Pathway: Clear progression for conference staff therapeutic facilitation skill development

Conference Positioning Materials:

Media Kit: Press release templates, thought leadership angles, and industry positioning strategies
Marketing Assets: Conference promotional materials emphasising collaborative intelligence innovation
Competitive Differentiation Analysis: How organisational psychotherapy approach distinguishes your conference from traditional events
Thought Leadership Content: Ready-to-publish articles and insights for conference website and industry publications

For Participants: Pre-Session Preparation & Ongoing Development

Preparatory Materials:

Five Patterns Overview: Comprehensive introduction to breakthrough thinking methodology with practical exercises
Assumption Audit Toolkit: Self-assessment framework for identifying personal and organisational limiting beliefs
Collaborative Intelligence Primer: Background on human-AI partnership principles and therapeutic alliance concepts
Challenge Preparation Guide: Framework for identifying organisational symptoms suitable for therapeutic intervention

Ongoing Development Pathway:

Complete Therapeutic Course Access: Full “Thinking Different with AI” programme for continued capability development
Assumption-Challenging Practice Community: Network of organisational psychotherapy practitioners for ongoing peer support
Monthly Methodology Updates: Continuous development of collaborative intelligence applications and breakthrough case studies
Implementation Support Resources: Practical guides for applying therapeutic intervention within organisations

Advanced Application Materials:

Organisational Diagnostic Tools: Systematic frameworks for institutional assumption auditing and limiting belief identification
Therapeutic Facilitation Guides: Step-by-step methodology for leading assumption-challenging sessions within teams
Cross-Domain Pattern Libraries: Extensive examples of breakthrough thinking applications across industries and challenge types
Systems Integration Framework: How to embed collaborative intelligence capabilities within existing organisational structures

Technical Implementation Support

Conference Team Development:

Therapeutic Facilitator Training Programme: Comprehensive skill development for conference staff in collaborative intelligence methodology
Technical Setup Guidance: Detailed specifications and contingency planning for multi-party therapeutic alliance platforms
Session Documentation Framework: Complete recording and synthesis approaches for breakthrough moment capture
Ongoing Facilitation Mentorship: Continued support for conference team collaborative intelligence capability development

Organisational Integration Support:

Change Management Toolkit: Framework for introducing assumption-challenging methodology within existing organisational cultures
Leadership Development Programme: Executive training in organisational psychotherapy principles and therapeutic intervention approaches
Team Implementation Guides: Practical approaches for embedding collaborative intelligence within departmental workflows
Measurement & Evaluation Framework: Systematic assessment of therapeutic intervention effectiveness and breakthrough outcome tracking

Research & Academic Context

Theoretical Foundation:

Cognitive Pattern Research: Academic background on breakthrough thinking approaches and assumption-challenging principles
Organisational Psychotherapy Literature: Relevant research on institutional belief systems and therapeutic intervention approaches
Human-AI Collaboration Studies: Current research on collaborative intelligence development and partnership effectiveness
Innovation Methodology Analysis: Historical patterns of breakthrough thinking across industries and decades

Case Study Documentation:

Educational Revolution Case Study: Complete analysis of the two-hour breakthrough that created 7,000-word course content
Cross-Industry Applications: Documented examples of Five Patterns methodology applied across different organisational contexts
Therapeutic Intervention Outcomes: Measured results from assumption-challenging applications in various institutional settings
Comparative Analysis: How organisational psychotherapy approach differs from traditional consulting and training methodologies

Community & Network Access

Practitioner Network:

Collaborative Intelligence Community: Direct access to growing network of assumption-challenging practitioners and organisational therapists
Monthly Practice Sessions: Ongoing group applications of breakthrough thinking methodology to current challenges
Peer Mentorship Programme: Experienced practitioners supporting newcomers in therapeutic intervention skill development
Cross-Organisational Learning Exchange: Sharing breakthrough insights and methodology adaptations across different industry contexts

Ongoing Innovation Laboratory:

Methodology Evolution Participation: Contribution to ongoing development of collaborative intelligence applications and therapeutic frameworks
Research Collaboration Opportunities: Participation in documenting and analysing breakthrough thinking outcomes across organisations
Conference Network Development: Connection with other venues pioneering collaborative intelligence and organisational psychotherapy approaches
Industry Influence Platform: Opportunities to contribute to thought leadership in assumption-challenging methodology adoption

Contact & Access Information

Primary Resource Access:

Email: bob.marshall@fallingblossoms.com
Course Platform: https://flowchainsensei.wordpress.com/2025/05/30/thinking-different-with-ai-a-self-paced-collaborative-course/
Research Archive: flowchainsensei.wordpress.com
Methodology Consultation: Available for specific organisational assumption auditing and therapeutic intervention planning

Implementation Support:

Conference Team Briefing: Scheduled 90-minute preparatory session for therapeutic facilitator development
Organisational Integration Consultation: Customised guidance for embedding collaborative intelligence capabilities post-conference
Ongoing Mentorship Access: Continued support for assumption-challenging methodology application and breakthrough thinking development
Community Platform Access: Direct entry to collaborative intelligence practitioner network and ongoing development resources

Technical Coordination:

Setup Consultation: Comprehensive technical planning for therapeutic alliance platform implementation
Contingency Planning: Multiple backup approaches for seamless collaborative intelligence demonstration
Documentation Support: Complete guidance for capturing and synthesising breakthrough methodology applications
Follow-up Integration: Post-conference support for ongoing organisational therapeutic capability development

These resources ensure that the conference experience becomes the foundation for ongoing collaborative intelligence development rather than a standalone event. Participants and organisers gain access to comprehensive support systems that transform assumption-challenging from conference novelty to organisational capability.

The investment extends far beyond 90 minutes of therapeutic intervention to encompass complete organisational transformation support and breakthrough thinking differently mastery.

The Five Patterns of Thinking Different: A Practical Guide

May 30, 2025

AI, Article, Dialogue, Patterns, Systems thinking, Thinking tools

1 Comment

The Five Patterns of Thinking Different: A Practical Guide

What if mastering AI collaboration isn’t about learning new technical skills, but about recognising cognitive patterns that have been hiding in plain sight for decades? This practical guide breaks down the five core patterns of Thinking Different—frameworks that enabled breakthrough innovations from 1943 to today and now offer a systematic approach to revolutionary human-AI collaboration.

These patterns operate at the level of cognition itself, transcending specific tools or technologies. Whether you’re developing software, conducting research, solving complex problems, or simply curious about maximising your thinking capacity, these frameworks provide the cognitive infrastructure for breakthrough thinking. Each pattern builds upon the others, creating a multiplier effect that transforms not just what you achieve, but how you think about thinking itself.

From Training Within Industry’s systematic approach to rapid skill development during WWII to contemporary AI-enhanced platforms like AInklings that transform static books into collaborative experiences, these patterns continue to drive innovation across domains. Understanding them provides the foundation for moving beyond conventional AI usage toward genuine cognitive partnership.

What Makes a Pattern “Hidden”? An Operational Definition

Before exploring the specific patterns, it’s essential to understand what distinguishes a “hidden pattern” from obvious techniques or well-known methods. A hidden pattern of thinking possesses four defining characteristics that make it simultaneously powerful and overlooked:

Characteristic 1: Structural Invisibility

Hidden patterns operate at a level beneath conscious awareness. They’re structural approaches to thinking that practitioners use intuitively but rarely articulate systematically. For example, successful innovators consistently transform constraints into advantages, but they rarely recognise this as a deliberate cognitive strategy that can be taught and replicated.

Characteristic 2: Cross-Domain Universality

These patterns work across dramatically different fields and contexts. The same cognitive approach that revolutionised WWII aircraft manufacturing also applies to software development, scientific research, and AI collaboration. This universality often masks their significance—because they appear everywhere, they seem invisible as distinct patterns.

Characteristic 3: Emergent Power When Recognised

Hidden patterns exhibit exponential value when brought to conscious awareness. Once you recognise the pattern of “systems-level perception,” you suddenly see leverage points and emergent properties that were always present but previously invisible. The pattern transforms from unconscious intuition to systematic capability.

Characteristic 4: Historical Persistence Despite Obscurity

These patterns have driven breakthrough innovations for decades or centuries, yet remain largely undocumented in formal educational curricula or professional development programmes. They persist through informal transmission—mentorship, apprenticeship, and intuitive recognition—rather than systematic instruction.

Recognition Test:

A thinking approach qualifies as a “hidden pattern” if you can answer “yes” to all four questions:

Do successful practitioners use this approach unconsciously more than consciously?
Does the same pattern appear across completely different domains and technologies?
Does recognising the pattern immediately expand your capability beyond acquiring new procedural skills?
Has this approach driven innovations for decades whilst remaining largely untaught systematically?

This operational definition helps distinguish genuine hidden patterns from surface-level techniques or domain-specific methods. The five patterns we’ll explore all meet these criteria, which explains both their power and their relative obscurity.

Pattern One: Transform Constraints Into Advantages

The first pattern of Thinking Different involves a fundamental shift in how we perceive limitations. Rather than viewing constraints as obstacles to overcome or work around, this pattern reveals how apparent restrictions often contain the seeds of breakthrough solutions.

During WWII, aviation engineers faced severe weight limitations that initially seemed to constrain aircraft design. However, these constraints forced them to reconceptualise structural approaches entirely. The limitation became the catalyst for innovations in lightweight materials and efficient design principles that actually improved performance beyond what unlimited resources might have achieved. The constraint didn’t just fail to prevent innovation—it actively drove it.

In the realm of AI collaboration, this pattern manifests when we recognise how apparent limitations in AI capabilities can become advantages. For instance, an AI system’s inability to understand context in the same way humans do can force us to articulate our thinking more precisely, leading to clearer problem formulation and better outcomes. The AI’s “limitation” becomes a cognitive forcing function that improves human thinking.

Consider how Fritz Wiessner’s 1939 K2 expedition transformed the constraint of stripped camps and stranded team members into an opportunity to develop entirely new systematic approaches to high-altitude logistics. Rather than seeing these challenges as failures, the expedition used them as forcing functions to create more robust methodologies.

Practical Application in AI Collaboration:

Use token limits as forcing functions for clearer, more precise communication
Transform AI’s lack of emotional understanding into opportunities for more rigorous logical analysis
Convert AI’s pattern-matching limitations into advantages for creative problem reframing
Leverage AI’s inability to “read between the lines” as a tool for making implicit assumptions explicit

Recognition Signals:

Finding yourself saying “because of this limitation, we had to…”
Discovering that working within constraints leads to more elegant solutions
Noticing that restrictions force creative approaches you wouldn’t have considered otherwise

Pattern Two: Enable Systems-Level Perception

The second pattern shifts perspective from analysing individual components to perceiving wholes. Whilst conventional thinking dissects problems into parts, this pattern cultivates the ability to see systems, ecosystems, and the dynamic relationships that shape both elements and emergent properties.

This pattern was crucial in the development of FORTRAN. Rather than focusing on individual programming instructions, John Backus and his team perceived the entire relationship between human mathematical thinking and computer processing as a system. This systems view revealed leverage points that individual component optimisation could never have discovered—the insight that mathematical notation could serve as a bridge between human intent and machine execution.

The Training Within Industry (TWI) programmes exemplified this pattern by treating training not as individual skill transfer but as an integrated system involving job instruction, job methods, and job relations. This holistic view enabled the remarkable results: 86% of companies increased production by at least 25% whilst simultaneously reducing training time and improving safety.

In AI collaboration, systems-level perception means seeing the interaction between human cognitive strengths, AI capabilities, and the problem context as an integrated whole. Rather than asking “How can I make the AI do what I want?” the question becomes “How can human insight, AI processing, and problem structure work together to surface new possibilities?”

Practical Application in AI Collaboration:

Map the complete ecosystem of human expertise, AI capabilities, and problem requirements
Identify emergent properties that arise from human-AI interaction rather than from either component alone
Look for systemic leverage points where small changes in interaction patterns create large improvements in outcomes
Design collaborative workflows that optimise the whole rather than individual components

Recognition Signals:

Noticing patterns that only become visible when you step back from details
Finding that small changes in how you frame problems create disproportionately large changes in AI responses
Discovering that the most valuable insights emerge from the interaction rather than from either human or AI contributions alone

Historical Example:

When Wright Field engineers approached captured German aircraft analysis, they didn’t just examine individual components. They perceived the entire system of design philosophy, manufacturing constraints, operational requirements, and technological possibilities that shaped enemy aircraft development. This systems view enabled them to rapidly reverse-engineer not just specific technologies but entire approaches to aviation engineering.

Pattern Three: Generate Unexpected Connections

The third pattern involves recognising deep structural similarities across seemingly unrelated domains. Revolutionary thinking thrives on identifying patterns that govern one field and applying them to transform completely different areas of inquiry or practice.

Joseph Weizenbaum’s development of ELIZA demonstrated this pattern brilliantly. By recognising structural similarities between psychotherapeutic dialogue patterns and computational text processing, he created connections that neither psychology nor computer science had anticipated. The pattern that governed non-directive therapy—reflecting statements back to encourage further exploration—became a computational strategy that revealed insights about human-computer interaction.

This pattern enabled the transformation of aircraft manufacturing from complete production to systems integration. Engineers recognised that principles governing efficient supply chain coordination in other industries could revolutionise aircraft development. The pattern that optimised automotive assembly lines, when creatively adapted, enabled Boeing to complete 16 B-17G Flying Fortresses per 20-hour shift.

In AI collaboration, this pattern manifests as the ability to recognise how successful interaction patterns from one domain can transform problem-solving in completely different areas. The Socratic dialogue method, perfected 2,500 years ago for philosophical inquiry, becomes a framework for productive AI collaboration. Teaching methodologies become templates for prompt engineering. Scientific hypothesis formation guides iterative AI interaction design.

Practical Application in AI Collaboration:

Study successful collaboration patterns from other domains (scientific research partnerships, musical improvisation, architectural design processes) and adapt them for human-AI interaction
Recognise how biological systems’ information processing strategies can inform AI collaboration workflows
Apply principles from successful human-human collaboration (peer review, brainstorming, debate) to human-AI partnerships
Draw insights from successful teaching methodologies to improve how you “instruct” AI systems

Recognition Signals:

Finding yourself thinking “This reminds me of…” when encountering problems in different domains
Discovering that solutions from one field work surprisingly well in another
Noticing that diverse experiences suddenly become relevant to current challenges

Contemporary Example:

AInklings’ transformation of static books into AI-enhanced interactive experiences exemplifies this pattern. By recognising structural similarities between dynamic conversation, adaptive learning, and knowledge exploration, they connected principles from education, entertainment, and AI collaboration to create entirely new forms of reading experience.

Pattern Four: Develop Metacognitive Awareness

The fourth pattern—perhaps the most crucial—cultivates awareness of thinking itself. This involves developing the ability to observe your own cognitive processes, recognise limiting assumptions, and consciously shift between different modes of analysis. This is the essence of Thinking Different: not just what you think, but how you think about how you think.

TWI’s Job Instruction programme demonstrated this pattern by training supervisors not just to do tasks, but to become aware of how they learned tasks and how to systematically transfer that knowledge to others. This metacognitive awareness enabled rapid skill development across entire organisations because people became conscious of their own learning and teaching processes.

FORTRAN’s development required similar metacognitive awareness. Backus and his team had to become conscious of how programmers think about problems, how computers process information, and how to bridge these different cognitive approaches. They developed awareness of the thinking patterns underlying mathematical notation and computational execution.

In AI collaboration, metacognitive awareness means becoming conscious of your own prompting strategies, recognising when you’re falling into limiting interaction patterns, and deliberately experimenting with different approaches to human-AI dialogue. It involves developing sensitivity to the subtle dynamics that distinguish productive AI collaboration from mere tool usage.

Practical Application in AI Collaboration:

Regularly reflect on your AI interaction patterns: What works? What doesn’t? Why?
Become aware of your default assumptions about AI capabilities and limitations
Notice when you’re anthropomorphising AI versus treating it as a different kind of intelligence
Develop sensitivity to the collaborative rhythm between your thinking and AI processing
Practice shifting between different modes of AI interaction (directive, collaborative, exploratory)

Recognition Signals:

Catching yourself thinking about how you’re thinking
Noticing patterns in your own problem-solving approaches
Becoming aware of mental models that usually operate unconsciously
Recognising when you’re stuck in limiting cognitive patterns

Metacognitive Questions for AI Collaboration:

How am I framing this problem, and what other framings might be possible?
What assumptions am I making about what the AI can and cannot do?
Am I treating this as a human-AI dialogue or as advanced search?
What thinking pattern am I using, and what alternatives might be more productive?

Pattern Five: Build Comprehensive Mental Models

The fifth pattern involves constructing integrated knowledge structures that can adapt and evolve as new information emerges. Rather than accumulating isolated facts or skills, this pattern enables the development of flexible, interconnected understanding that grows stronger and more useful over time.

The systematic reverse engineering at Wright Field exemplified this pattern. Engineers didn’t just collect individual facts about captured aircraft components. They built comprehensive mental models that integrated design philosophy, manufacturing constraints, operational requirements, materials science, and strategic context. These integrated models enabled them to understand not just what enemy engineers had built, but why they had made specific choices and how those insights could inform American development.

Fritz Wiessner’s approach to K2 demonstrated this pattern through the integration of mountaineering technique, weather patterns, human physiology, team psychology, and logistics planning into a comprehensive understanding of high-altitude expedition management. This integrated mental model enabled systematic innovation in extreme environment operations.

In AI collaboration, this pattern manifests as developing integrated understanding of human cognitive strengths, AI processing capabilities, problem-solving methodologies, and domain-specific knowledge. Rather than acquiring isolated prompting techniques, you build flexible mental models that enable adaptive collaboration across different types of challenges.

Practical Application in AI Collaboration:

Map the relationships between different AI capabilities and how they complement human cognitive strengths
Develop integrated understanding of when to use different collaboration approaches (analytical, creative, exploratory, systematic)
Build mental models that connect prompt engineering, conversation flow, problem structure, and desired outcomes
Create flexible frameworks that can adapt to different AI systems and evolving capabilities

Recognition Signals:

Finding that learning in one area automatically improves performance in seemingly unrelated areas
Noticing that new information easily integrates with existing understanding rather than requiring separate mental categories
Discovering that your mental models help you adapt quickly to new situations or tools

Building Integrated Mental Models:

Start with core relationships: How do human intuition and AI analysis complement each other? How do different types of problems require different collaboration approaches? How do conversation patterns influence thinking outcomes? Build these connections systematically, testing and refining your models through deliberate practice.

The Multiplier Effect: How Patterns Amplify Each Other

These five patterns don’t operate in isolation—they create a powerful multiplier effect when combined. Mastering one pattern often accelerates development of the others because they share underlying structural similarities.

The systems thinking that enables effective pattern recognition (Pattern Two) also supports the metacognitive awareness needed to observe your own thinking processes (Pattern Four). The ability to transform constraints into advantages (Pattern One) enhances your capacity to generate unexpected connections (Pattern Three) because limitations often force creative bridging between domains.

As these patterns integrate and reinforce each other, practitioners often report experiencing qualitative shifts in their thinking capacity. Problems that once seemed intractable become approachable. Connections that were previously invisible become obvious. The overall experience resembles gaining a new form of cognitive vision—suddenly perceiving patterns and possibilities that were always present but previously undetectable.

Integration Strategies:

Practice applying multiple patterns simultaneously to the same problem
Look for situations where one pattern naturally leads to another
Develop sensitivity to the relationships between different patterns
Use deliberate practice to strengthen pattern recognition across all five areas

Practical Implementation: A Systematic Approach

Moving from understanding these patterns to embodying them requires systematic practice. The most effective approach involves what might be called “situated practice”—applying the patterns in real-world contexts where their value becomes immediately apparent.

Week 1-2: Pattern Recognition

Begin by simply noticing these patterns in action. Study historical examples, observe successful collaborations, and identify when you encounter each pattern naturally. The goal is developing sensitivity to these cognitive approaches before trying to implement them systematically.

Week 3-4: Single Pattern Focus

Choose one pattern and practice applying it consistently in your AI collaborations. If you select “Transform Constraints Into Advantages,” deliberately look for how limitations in your current AI interactions might become forcing functions for better approaches.

Week 5-8: Pattern Combination

Begin combining patterns systematically. Practice applying systems-level perception whilst simultaneously developing metacognitive awareness. Look for how constraint transformation enables unexpected connections.

Week 9-12: Integration and Refinement

Focus on developing fluency across all patterns and sensitivity to when each approach offers the most leverage. Practice shifting between patterns based on problem context and collaboration dynamics.

Ongoing Development:

Continue refining your pattern recognition and application through deliberate practice, reflection, and experimentation with increasingly complex challenges.

Contemporary Applications: Patterns in Action

These patterns continue to drive innovation across diverse fields, demonstrating their timeless relevance and practical value.

Technology Development

Modern software architecture increasingly reflects systems-level thinking (Pattern Two) that treats applications as ecosystems rather than monolithic products. Constraint-driven design (Pattern One) has become a core principle in responsive web development and mobile application creation.

Organisational Innovation

Companies applying TWI principles today report similar results to the 1940s implementations: dramatically improved training efficiency, reduced errors, and enhanced innovation capacity. The patterns scale from individual skill development to enterprise-wide transformation.

AI-Enhanced Learning

Platforms like AInklings demonstrate how all five patterns work together. They transform the constraint of static text (Pattern One) by recognising structural similarities between conversation and reading (Pattern Three), applying systems thinking to integrate human curiosity with AI capability (Pattern Two), whilst enabling metacognitive awareness of learning processes (Pattern Four) and building comprehensive mental models through interactive exploration (Pattern Five).

Scientific Research

Contemporary research increasingly involves human-AI collaboration that exemplifies these patterns. Researchers use AI to surface unexpected connections across vast literature databases (Pattern Three), develop metacognitive awareness of their own research patterns (Pattern Four), and build integrated mental models that span multiple disciplines (Pattern Five).

The Future of Pattern-Based Thinking

As AI systems continue to advance in sophistication and capability, the importance of these patterns will only increase. The practitioners who master pattern-based thinking will be positioned to achieve results that seem impossible to those stuck in conventional approaches.

These patterns represent cognitive infrastructure—foundational capabilities that support innovation and breakthrough thinking regardless of specific technological configurations. Investing in this infrastructure now provides leverage that will continue to pay dividends throughout the AI revolution and beyond.

The patterns also suggest the emergence of new forms of hybrid intelligence that neither pure human nor pure AI thinking could achieve. As these collaborative approaches mature, we may see the development of entirely new cognitive capabilities that emerge from the systematic application of these patterns.

Emerging Trends

Integration of pattern-based thinking into educational curricula
Development of AI systems specifically designed to support pattern recognition and application
Organisational transformation based on systematic pattern implementation
New forms of human-AI collaboration that transcend current tool-based approaches

Conclusion: The Choice to Think Different

These five patterns—Transform Constraints Into Advantages, Enable Systems-Level Perception, Generate Unexpected Connections, Develop Metacognitive Awareness, and Build Comprehensive Mental Models—offer a systematic approach to revolutionary thinking that transcends technological change.

The choice to master these patterns isn’t just about improving AI collaboration. It’s about developing cognitive capabilities that enhance thinking across every domain of human activity. Whether you’re solving technical problems, making strategic decisions, conducting research, or simply trying to understand complex situations, these patterns provide the cognitive infrastructure for breakthrough thinking.

The patterns have been hiding in plain sight for decades, demonstrated by innovators from Wright Field engineers to contemporary AI pioneers. They’re ready to transform not just how you use AI, but how you think about thinking itself.

The revolution in pattern-based thinking has already begun. The question isn’t whether these approaches will reshape human-AI collaboration—it’s whether you’ll be part of that transformation.

From Operational Value Streams to Prod•gnosis

May 12, 2025

Actionable Insights, Alien tech, Antimatter principle, Article, Business, Capability development, Digital evolution, Flow, Flow•gnosis, Organisational Therapy, Paradigm shifts, Prod•gnosis, Product development, SAR Organisations, Software development, Systems thinking, Value streams

Leave a comment

From Operational Value Streams to Prod•gnosis

Connecting Allen Ward and Bob Marshall’s Product Development Philosophies

A thoughtful exploration of two complementary approaches to transforming product development

Introduction

In the world of product development theory, two complementary approaches stand out for their innovative thinking about how organisations might tackle the creation of new products: Dr Allen Ward’s approach, born of many years researching the Toyota approach, and my own approach, which I’ve named Prod•gnosis

While Dr. Ward’s work on operational value streams emerged from his extensive study of Toyota’s product development system, Prod•gnosis builds upon and extends his ideas into a comprehensive framework focused on organisational transformation for better product development, reduced costs, and more appealing products.

This post explores the connections between these two approaches and how, together, they offer a powerful lens for fundamentally rethinking product development.

The Foundation: Allen Ward’s Operational Value Streams

Allen Ward’s core insight, which has become a cornerstone of lean product development e.g. TPDS, is elegantly simple yet profound:

“The aim of development is, in fact, the creation of profitable operational value streams.”

An operational value stream (OVS) represents the set of steps that deliver a product or service directly to the customer (and others). This includes activities like manufacturing a product, fulfilling an order, providing a loan, or delivering a professional service.

Ward’s work, drawing from his decade of direct research at Toyota, showed that effective product development isn’t just about designing isolated products. Rather, it’s about designing the entire system through which those products will be manufactured, shipped, sold, and serviced. This holistic approach explains much of Toyota’s success in bringing new products to market quickly and profitably.

Ward emphasised that creating profitable operational value streams requires:

A “whole product” approach that involves every area of the business
Knowledge creation as the central activity of product development
The use of tools like trade-off curves for decision-making and teaching
Systematic waste elimination throughout the development process

Prod•gnosis: Building on Ward’s Foundation

I’m delighted to acknowledge my intellectual debt to Dr. Ward. In my writings on Prod•gnosis, I directly reference Dr. Ward’s influence, adopting his view of “business as a collection of operational value streams.”

I define Prod•gnosis (a portmanteau of “Product”, and “Gnosis” meaning knowledge) as a specific approach to product development that places the creation of operational value streams at its centre. However, Prod•gnosis extends Dr. Ward’s thinking in several notable ways:

The Product Development Value Stream (PDVS)

Prod•gnosis introduces the concept of a dedicated “Product Development Value Stream” (PDVS) as a distinct organisational capability responsible for creating and instantiating operational value streams. I previously wrote:

“I suggest the most effective place for software development is in the ‘Product Development Value Stream’ (PDVS for short) – that part of the organisation which is responsible for creating each and every operational value stream.”

This represents a significant organisational shift from traditional department-based structures.

Challenging IT’s Role in Product Development

Prod•gnosis particularly questions the conventional role of IT departments in product development. Prod•gnosis argues that software development does not belong in IT departments but instead is much more effective when situated within the Product Development Value Stream:

“If we accept that the IT department is poorly suited to play the central role in a Prod•gnosis-oriented organisation, and that it is ill-suited to house or oversee software development (for a number of reasons), then where should software development ‘sit’ in an organisation?”

The answer is clear: within the PDVS, where it can directly contribute to creating operational value streams.

Incremental Implementation

Prod•gnosis proposes a “Lean Startup-like approach” to implementing operational value streams:

“I’m thinking more in terms of a Lean Startup-like approach – instantiating version 0.1 of the operational value stream as early as possible, conducting experiments with its operation in delivering an MVP (even before making its 1.0 product line available to buying customers), and through e.g. kaizen by either the product development or – the few, early – operational value stream folks (or both in collaboration), incrementally modifying, augmenting and elaborating it until the point of the 1.0 launch, and beyond.”

This represents a pragmatic approach to putting Dr. Ward’s principles into practice.

Key Points of Alignment

Despite their different emphases, Ward and Prod•gnosis’ approaches share significant philosophical alignment:

1. Value Stream-Centric View

Both view business fundamentally as a series of operational value streams, with product development focused on creating and improving these streams rather than just designing isolated products.

2. Whole Product Approach

Both emphasise the importance of involving all aspects of a business in product development. Prod•gnosis references Toyota’s “Big Rooms” (Obeya), which Ward studied extensively, as an example of effective cross-functional collaboration.

3. Systems Thinking

Both reject piecemeal improvements and advocate for fundamental shifts in organisational perspective. As Ward wrote and Prod•gnosis quotes: “Change will occur when the majority of people in the organisation have learned to see things in a new way.”

And see also: Organisational Psychotherapy as a means to help organisations see things in a new way.

4. Flow Focus

Both emphasise the importance of flow in product development, with Prod•gnosis particularly focused on aspects like flow rate, lead time, cycle time, and process cycle efficiency – both of the PVDS and the OVSs.

Practical Applications of the Combined Approach

Organisations seeking to apply these ideas might consider:

Creating a dedicated Product Development Value Stream responsible for designing and implementing operational value streams (a.k.a. new products)
Removing software development from IT departments and placing it within the PDVS
Adopting a “whole product” approach that brings together all business functions in the service of product development
Implementing early versions of operational value streams viw the PVDS, and then iteratively improving them
Measuring and optimising flow through the product development process

Getting There: Transitioning to Prod•gnosis

Moving from conventional product development approaches to a Prod•gnosis model represents a significant organisational transformation. As Prod•gnosis acknowledges,

“getting there from here is the real challenge”

The transition requires more than just structural or process changes—it demands a fundamental shift in collective mindset.

The Challenge of Organisational Transformation

The Lean literature is replete with stories of organisations failing to move from vertical silos to horizontal value streams. Prod•gnosis presents additional challenges by proposing to remove software development from IT departments and create an entirely new organisational capability (the PDVS).

As Ward wisely noted and Prod•gnosis quotes:

“Change will occur when the majority of people in the organisation have learned to see things in a new way.”

This insight highlights that sustainable transformation depends on shifting collective beliefs rather than merely implementing new processes.

Organisational Psychotherapy as a Path Forward

In Organisational Psychotherapy I propose as a methodical approach to shifting collective assumptions and beliefs. As an Organisational Psychotherapist, I apply psychotherapy techniques not just to individuals but to entire organisations.

OP recognises that organisations, like individuals, operate based on deep-seated assumptions and beliefs—i.e. “memeplexes” These collective mental models determine how an organisation functions and often unconsciously resist change. And see my book “Hearts over Diamonds” (Marshall, 2018) for more in-depth discusion of memeplexes.

Organisational Psychotherapy works by:

Helping organisations become aware of their current collective beliefs (surfacing)
Examining how these beliefs serve or hinder effectiveness (reflecting)
Supporting the organisation in exploring new, more productive mental models
Facilitating the adoption of these new models

For organisations seeking to move toward Prod•gnosis, this might involve addressing fundamental beliefs about:

The nature and purpose of product development
The relationship between software development and IT
The definition of “whole product”
The organisation’s relationship with customers and all the Folks That Matter™
How value flows through the organisation

As Prod•gnosis emphasises, this isn’t a quick fix. The transformation to Prod•gnosis represents a significant evolution in how organisations think about and structure product development. The journey requires patience, persistence, and a willingness to examine and change foundational assumptions about how product development might work significantly better.

Conclusion

The synthesis of Allen Ward’s operational value stream concept and Prod•gnosis offers a powerful framework for rethinking product development. By viewing product development as the creation of complete operational value streams and establishing organisational structures that support this perspective, organisations can potentially achieve the kind of rapid, profitable product development that Toyota has demonstrated.

As more organisations struggle with digital transformation and the ever-increasing importance of software in product development, these two complementary approaches may provide a valuable roadmap for fundamentally rethinking how products are developed and brought to market.

What are your thoughts on the operational value stream approach to product development? Have you seen examples of it in practice? I’d love for you to share your experiences in the comments below.

The Fatal Flaw of Piecemeal Culture Change: Why Your Transformation is Doomed to Fail

April 21, 2025

Agile, Agility at Scale, Alignment, Article, Change management, Collective psyche, Culture change, Drucker, Improvement, Management, Marshall Model, Memeology, Organisational Therapy, Quintessence, Rightshifting, Systems thinking, xenopsychotherapy

Leave a comment

The Fatal Flaw of Piecemeal Culture Change: Why Your Transformation is Doomed to Fail

Organisations frequently embark on cultural transformation initiatives to stay competitive. However, attempting to change organisational culture and thinking in isolated pockets—rather than holistically—is a strategy destined for inevitable frustration and failure. Here’s why piecemeal cultural change rarely works and what alternative approaches yield better results…

The Interconnected Nature of Organisational Culture

Organisational culture is not merely a collection of independent practices and attitudes; it’s an intricate web of shared values, assumptions, beliefs, and behaviours that permeate every level and department. When we attempt to transform culture in isolation—focusing on just one or two departments or teams—we ignore this fundamental interconnectedness. See also the orthogonal concept ot memeplex interlock.

Consider an organisation where the marketing department embraces innovation and risk-taking while other departments maintain rigid hierarchies and risk-averse decision-making. Marketing’s initiatives will inevitably collide with established processes elsewhere, creating friction rather than progress.

The Inevitable Outcomes of Siloed Cultural Change

When cultural transformation is attempted silo by silos, several entirely predictable outcomes emerge:

1. Cultural Clash and Resistance

Departments operating under different cultural paradigms will naturally clash. The “changed” department begins operating with different assumptions, priorities, and methods than the rest of the organisation. These differences breed misunderstanding, resistance, and often outright conflict. See also: OrgCogDiss.

2. Change Regression

Without organisation-wide support and reinforcement, cultural changes within a single department inevitably regresses over time. The gravitational pull of the dominant organisational culture eventually overwhelms localised efforts, particularly as employees interact with colleagues outside their immediate team. Hint: for a short-term palliative, keeping localised culture changes in a protective bubble can help.

3. Talent Frustration and Exodus

Employees within the “changed” department often become frustrated when their new ways of working clash with the broader organisation. This frustration frequently leads to disengagement and ultimately departure—especially among the most talented individuals who were most enthusiastic about the new cultural direction.

4. Erosion of Credibility

Failed attempts at cultural transformation damage leadership credibility. When employees witness cultural initiatives that start with fanfare but ultimately fizzle or create more problems than they solve, they become cynical about future change efforts.

A More Effective Approach: Systemic Cultural Transformation

So how do we break free from the cycle of failed piecemeal change efforts? What would it take to transform an organisation’s culture in a way that actually sticks? And is there an approach that addresses the entire organisation as a system rather than just its isolated components?

Rather than siloed interventions, successful cultural transformation necessitates a systems thinking approach that recognises the integrated nature of organisational culture. Organisational psychotherapy stands out as the only approach that comprehensively addresses the shared values, beliefs, assumptions and behaviours of the organisation as a whole. Unlike piecemeal interventions, organisational psychotherapy works at the collective level, helping the entire organisation understand and transform its deeply ingrained patterns of thinking and interacting, more or less in parallel.

How Organisational Psychotherapy Differs from Traditional Change Management

Traditional change management approaches often focus on processes, structures, and explicit behaviours, treating organisational transformation as primarily a managerial challenge. Organisational psychotherapy, by contrast, recognises transformation as fundamentally psychological in nature and differs in several important ways:

Focus on collective mindset rather than individual behaviour – While traditional approaches might target the visible behaviours of individuals or teams, organisational psychotherapy addresses the collective mindset—the shared mental models, beliefs, and assumptions that drive behaviour throughout the organisation. This collective focus prevents the “immune system response” that typically rejects isolated change efforts.
Uncovering unconscious dynamics – Organisations, like individuals, develop unconscious patterns and defence mechanisms that resist change. Organisational psychotherapy specifically works to bring these hidden dynamics to consciousness, examining unspoken rules, taboos, undiscussables, and emotional undercurrents that conventional approaches typically miss but which powerfully influence organisational life.
Enabling authentic dialogue and reflection – Effective cultural change requires vulnerability and honesty about dysfunctional patterns. Organisational psychotherapy invites environments where people can speak difficult truths, enabling genuine examination of cultural assumptions rather than superficial compliance with new directives.
Addressing the organisation as a living system – Rather than treating people or departments or functions as mechanical components to be reengineered, organisational psychotherapy approaches the organisation as a complex, adaptive system with its own identity, history, and emotional life. This systemic view prevents the common mistake of solving symptoms rather than underlying causes.
Working through, not around, resistance – Traditional change management often tries to overcome or bypass resistance. Organisational psychotherapy views resistance as valuable information about the system’s fears and needs, enabling the organisation itself to work through its resistanc,e collectively, rather than dismissing it.
Sustainable integration vs. imposed change – Instead of imposing change from outside, organisational psychotherapy facilitates a process where the organisation develops increased self-awareness and capacity for self-directed evolution, leading to change that is internally coherent and sustainable.

NB. For more details, see: The definitive book on Organisational Psychotherapy fundamentals: Hearts over Diamonds

These distinctive elements make organisational psychotherapy particularly effective for deep cultural transformation, addressing the root causes of organisational dysfunction rather than merely treating symptoms. This means:

1. Unified Vision

Effective cultural transformation begins with a clear, compelling vision embraced by folks across all levels and departments. Without this alignment, mixed messages and contradictory priorities will undermine change efforts.

2. Aligned Systems and Structures

Organisational systems—from performance metrics to decision-making processes—must align with the desired culture. Misalignment between cultural aspirations and operational realities guarantees failure. See also: Change always demands we change the rules.

3. Cross-Functional Integration

Effective cultural transformation requires cross-functional coordination and communication. Creating networks and communities that span departmental boundaries helps ensure consistent cultural understanding and application. See also: Moving to the Synergistic Mindset

4. Incremental but Organisation-Wide Implementation

While transformation doesn’t happen overnight, any successful approach must be organisation-wide even when implemented incrementally. This means starting with foundational elements that touch every department rather than completing transformation in one area before moving to the next.

Conclusion

The interconnected nature of organisational culture means that piecemeal approaches to cultural transformation are fundamentally flawed. Organisations that recognise culture as a system—rather than a collection of independent parts—are far more likely to achieve meaningful and lasting cultural change, and the consequent improvement in business outcomes.

By adopting a whole-system perspective and ensuring alignment across people, systems, and departments, organisations can navigate the complex journey of cultural transformation successfully. The path may be challenging, but the alternative—fragmented cultural initiatives that create more problems than they solve—is ultimately much more costly in both human and financial terms.

PS: This is why Agile transformations limited to a team or software department almost never succeed. When Agile assumptions, principles and practices are confined to technical teams whilst the rest of the organisation continues to operate under traditional management assumptions and beliefs, the cross-functional collaboration essential to effective agility is stifled. The result is most often a frustrated development team caught between Agile aspirations and waterfall business realities—reinforcing the critical need for organisation-wide cultural alignment in any transformation effort.

Exploring the Benefits of Deming’s System of Profound Knowledge

April 15, 2025

Antimatter principle, Article, Business, Change management, Collective psyche, Deming, Giants, Organisational Therapy, Paradigm shifts, Systems thinking

Leave a comment

Exploring the Benefits of Deming’s System of Profound Knowledge

What is Deming’s System of Profound Knowledge?

Have you ever wondered why some organisations consistently excel while others struggle, despite similar resources? What if there was a framework that could fundamentally transform how we understand and run organisations?

Who is W. Edwards Deming?

W. Edwards Deming (1900-1993) was an American engineer, statistician, professor, and management consultant who revolutionised manufacturing and business practices worldwide. Though overlooked in his home country, Deming’s methods helped transform post-war Japan into an economic powerhouse. His approach to quality and management eventually gained recognition globally, albeit much less so in the USA, even following NBC’s 1980 documentary titled “If Japan Can, Why Can’t We?” which highlighted how Japanese manufacturers had embraced Deming’s principles to dramatic effect.

Deming introduced his System of Profound Knowledge (SoPK) as a comprehensive theory for transformation. But what exactly does this system entail?

The System of Profound Knowledge consists of four interconnected domains:

Psychology: How does human behaviour influence organisational performance? What motivates people beyond rewards and punishments? How might understanding human psychology transform management practices? What role does the collective psyche—the shared assumptions, beliefs, and mental models within an organisation—play in shaping how work gets done?
Appreciation for a System: How might our perspective change if we viewed organisations not as collections of separate departments but as interconnected networks where each action affects the whole? What would happen if leaders optimised the entire system rather than individual components?
Knowledge of Variation: What if we recognised that variation exists in all processes? How would our response to problems change if we could distinguish between common causes (inherent in the system) and special causes (specific, identifiable factors)?
Theory of Knowledge: How do organisations learn? What if we approached improvement with a scientific mindset, testing our theories and building knowledge systematically rather than relying on opinions?

Quality and Waste: A Different Perspective?

When products or services fail to meet expectations, do we typically ask “who made this mistake?” or rather “what about our system allowed this to happen?”

Have you noticed how blaming individuals rarely solves recurring problems? What if, instead, organisations examined their systems, processes and collective assumptions?

What might happen if leaders focused on understanding and reducing variation rather than reacting to each failure as an isolated event?

What Drives Genuine Improvement?

Consider how organisations typically approach change and improvement. Do they tend to react to crises, or build learning, change and improvement into everyday work?

What kind of environment emerges when curiosity becomes more valuable than certainty? How might an organisation change if it viewed learning not as a special event but as part of its daily rhythm?

What if every employee felt both empowered and responsible for improving the system they work within? What is employees owned that system?

Decision-Making: Beyond Instinct?

When leaders make decisions, do they typically rely on gut feelings, or evidence? What might change if they used statistical thinking to distinguish between normal variations and significant problems?

Have you noticed how focusing on short-term results can undermine long-term success? What would happen if leaders considered how their decisions affect the entire system rather than optimising isolated parts?

The Human Element: Fear or Pride?

How do you feel when working in an environment dominated by fear of sanction and punishment? Alternatively, how does your work change when you feel trusted and valued?

What motivates people more powerfully—external rewards, or the satisfaction of doing meaningful work well? How might removing barriers that prevent good work transform employee engagement?

The Collective Organisational Psyche

Have you considered how organisations have their own collective psyche—shared assumptions, values, and beliefs that guide folks’ behaviours even without explicit direction? What invisible forces shape decisions and actions throughout the organisation?

How do these collective beliefs influence what gets prioritised, what problems are seen (or remain invisible), and how change initiatives are received? What happens when the collective mindset assumes people cannot be trusted, versus when it assumes people naturally desire to contribute meaningfully?

How might an organisation’s historical experiences create deeply embedded assumptions that continue to influence behaviour long after the original circumstances have changed? What would it take to consciously examine and reshape these collective mental models?

Understanding Customer Needs: Deeper Connections?

How do organisations typically determine what customers need? Do they truly understand the experience of using their products or services?

What if quality was built into every step rather than checked afterwards? How might this shift change the consistency of customer experiences?

Financial Health: Short-term or Sustainable?

Could reducing waste, rework and failure demand significantly lower costs? What happens to customer loyalty when folks’ needs becomes paramount?

How might a reputation for excellence affect an organisation’s market position? What financial benefits emerge when crisis management no longer consumes resources?

A Fundamental Transformation?

What if these questions point to a profound shift in how we think about organisations? Could Deming’s SoPK approach offer a path to creating workplaces that simultaneously benefit customers, employees, and long-term prosperity?

How might our organisations change if we embraced Deming’s principles of profound knowledge?

This blog post uses the Socratic method to explore Deming’s System of Profound Knowledge, inviting readers to question conventional management wisdom and consider a more holistic approach to organisational improvement.

The Business Case for Organisational Psychotherapy

April 6, 2025

Actionable Insights, Article, Business, Culture change, Memeology, Organisational Therapy, Quintessence, Systems thinking

Leave a comment

The Business Case for Organisational Psychotherapy

Can we build a step-by-step case that shows why organisational psychotherapy (OP) makes sense as a way to help businesses improve?

The Foundational Premises

1. Organisations as Human Systems

Organisations consist of people working together toward common objectives. This is observable in any workplace.

2. Collective Patterns Emerge

When people work together over time, they develop shared assumptions, unwritten rules, and common interpretations of events. Research in organisational culture and social psychology documents this phenomenon.

3. These Patterns Affect Behaviour

These collective assumptions influence how decisions are made, problems are solved, and conflicts are handled—often without conscious awareness. Studies show organisational behaviour is shaped by these implicit frameworks.

4. Patterns Can Become Limiting

Initially adaptive patterns can become restrictive as circumstances change. Organisations frequently struggle to adapt despite knowing they need to change, suggesting psychological rather than just informational barriers.

5. Businesses are Systems

Given that every business is a system, we need to understand what this means for organisational change. A system is a set of interconnected elements that work together to form a unified whole. In business, these elements include people, processes, technologies, structures, assumptions and beliefs, and importantly, the relationships between all these elements.

Systems have several key characteristics:

Interconnectedness: Changes in one part affect other parts, often in non-obvious ways
Emergence: Systems produce behaviours and properties that cannot be predicted by looking at individual components in isolation (Cf. Richard Buckminster Fuller, Synergism)
Feedback loops: Systems contain reinforcing and balancing mechanisms that maintain stability or drive change
Boundaries: Systems exist within larger environments and contain subsystems

Business change demands a systems thinking perspective because isolated interventions frequently fail. When we change one element without considering consequences and that element’s connections to other elements, we often trigger unintended effects or resistance. Technical solutions alone rarely succeed when the underlying system dynamics remain unaddressed.

Effective transformation requires looking at the entire system, including the less visible, yet more profound, elements such as collective assumptions, shared mental models, and unwritten rules that govern behaviour. These psychological aspects are at least as real and influential as formal structures and processes.

The Logical Progression

Pattern Recognition is Key

For meaningful change to occur, organisations might choose to become aware of their limiting patterns. This mirrors a fundamental process in effective therapy and psychological change.

N.B. See my books Memeology and Quintessence for ideas on recognising some 70+ of these patterns

Therapeutic Approaches Address Root Patterns

Methods developed for addressing psychological patterns in other contexts can be adapted to help organisations recognise and modify their limiting assumptions.

Evidence of Effectiveness

Organisations that successfully identify and shift their collective assumptions often resolve persistent problems that had resisted technical solutions.

The Practical Conclusion

Organisational Psychotherapy Offers a Coherent Approach

By providing methods to identify, understand, and modify collective psychological patterns, OP addresses a critical dimension of organisational functioning often missed by purely structural or technical interventions.

The above chain of reasoning suggests organisational psychotherapy addresses real phenomena through methods that logically connect to the nature of the problem. The approach might prove beneficial, particularly for organisations facing challenges that have persisted despite traditional improvement and change management efforts.

Planting Seeds of Change: Organisational Psychotherapy and the Art of Gentle Transformation

December 4, 2024

Article, Business, Collective psyche, Culture change, Organisational Therapy, Psychotherapy, Systems thinking

Leave a comment

Planting Seeds of Change: Organisational Psychotherapy and the Art of Gentle Transformation

The Metaphorical Landscape of Organisational Growth

The concept of organisational transformation draws inspiration from Carl Rogers’ seminal work in person-centered therapy, which fundamentally reimagined psychological growth as an organic, naturally unfolding process. Imagine an organisation as a vast, complex garden—a living ecosystem where psychological development isn’t about rapid, mechanistic interventions, but about carefully nurturing potential through a deeply humanistic approach.

Theoretical Foundations: Beyond Traditional Change Management

Rogers’ person-centered philosophy provides a lens for understanding organisational development. His core belief that individuals possess an inherent “actualising tendency”—a natural drive towards self-fulfillment and growth—extends powerfully into organisational contexts. Systems thinking and complexity theory further illuminate this perspective, viewing organisations not as static machines, but as dynamic, self-organizing systems with emergent properties.

The Psychological Terrain of Living Systems

Drawing from Fritjof Capra’s work on systems thinking, organisations can be understood as living networks of relationships and interactions. Each workplace becomes a complex adaptive sociotechnical system, where change occurs through intricate, non-linear interactions rather than top-down, linear directives. This perspective challenges traditional mechanistic models of organisational development and change.

Cultivating the Organisational Ecosystem

Gestalt organisational development provides additional depth to our seed planting metaphor. Developed by pioneers like Kurt Lewin, this approach emphasises holistic understanding, recognising that organisational change happens through shifts in collective awareness and interconnected relationships.

Creating Psychological Safety

The art of planting seeds invites the creation of environments of profound psychological safety. This means developing spaces where employees feel genuinely heard, where vulnerability is not a weakness but a strength, and where innovative thinking can emerge without immediate judgement—principles deeply rooted in Rogers’ therapeutic approach.

Techniques of Subtle Intervention

Complexity theory offers fascinating insights into how change propagates through complex systems. Small, thoughtful interventions can create significant, unpredictable shifts—much like the “butterfly effect” in chaos theory. Seed planting becomes a nuanced practice of introducing minimal, strategic perspectives that can catalyse broader systemic transformation.

Logotherapeutic Dimensions of Seed Planting

Where previous approaches have focused on psychological and systemic transformation, Logotherapy introduces a profound existential layer to organisational development. Viktor Frankl’s approach suggests that beyond psychological safety and systemic change, organisations must address the fundamental human need for meaning.

The Search for Organisational Purpose

In the seed planting metaphor, logotherapy represents the deepest soil—the existential ground from which truly transformative growth emerges. Just as a seed contains not just the potential for physical growth but also its unique genetic blueprint, organisations contain the potential for purpose-driven evolution.

Logotherapeutic seed planting involves helping employees and leaders discover the deeper ‘why’ behind their collective work. This goes beyond traditional mission statements, delving into how each role, no matter how seemingly mundane, contributes to a broader human narrative.

Meaning as a Transformative Force

Where Rogers saw potential for personal growth, and systems thinking observed interconnected dynamics, logotherapy introduces meaning as an active, generative force. Employees are not just participants in an organisational system, but meaning-makers who can reshape that system through their quest for purpose.

The seeds planted through a logotherapeutic lens are existential insights—perspectives that help individuals and organisations understand their unique contribution to the world, transcending mere economic or functional objectives.

The Power of Reflective Dialogue

These conversations are not mere discussions but carefully held spaces of collective sense-making. By introducing new perspectives gently, organisational psychotherapists help employees explore workplace challenges from multiple angles, allowing emergent understanding to gradually crystallise and evolve.

Theoretical Intersections: A Holistic Approach

The seed planting metaphor beautifully integrates multiple psychological and systems theories:

Rogers’ person-centered principles of unconditional positive regard
Systems thinking’s understanding of organisations as living networks
Complexity theory’s insights into non-linear change
Gestalt approaches to collective awareness and holistic transformation

Patience as a Philosophical Stance

Western corporate culture often demands immediate, measurable results. However, the seed planting approach, informed by both psychological and systems theories, invites a radically different paradigm. Some transformative seeds might take months or years to fully germinate—a process that represents organic evolution rather than failure.(See also: Memeology)

Redefining Organisational Metrics

Traditional quantitative metrics become less relevant. Success is measured by the quality of psychological environment, the depth of collective conversations, and the emerging sense of collective possibility—a perspective deeply aligned with humanistic psychological approaches.

Challenges and Systemic Intelligence

Not every seed we plant will grow. Some organisational cultures might be too compacted or resistant to allow new perspectives to take root. The skilled organisational psychotherapist, drawing from various schools of therapy, from complexity theory, and from systems thinking, approaches each intervention with humility, recognising that resistance itself carries valuable systemic information.

Conclusion: A Paradigm of Organic Transformation

Planting seeds in organisational psychotherapy represents a profound philosophical and practical shift. It recognises organisations as living systems with their own consciousness, capable of growth, adaptation, and profound psychological renewal.

By embracing the insights of Rogers, systems thinking, complexity theory, and Gestalt approaches, influencers and organisational psychotherapists can create environments where meaningful change isn’t imposed but naturally emerges—much like a garden blossoming under careful, loving, and scientifically informed attention.

Unleashing Potential: Actionable Insights from Goldratt’s Theory of Constraints

October 4, 2024

Actionable Insights, Article, Culture change, Paradigm shifts, Systems thinking

1 Comment

Unleashing Potential: Actionable Insights from Goldratt’s Theory of Constraints

In a world obsessed with optimisations, costs, and efficiency, Eliyahu M. Goldratt’s Theory of Constraints (TOC) offers a refreshingly holistic approach to performance. Of course, to paraphrase Deming’s First Theorem “Nobody gives a hoot about performance”.

This post explores key concepts from TOC and how they can revolutionise our approach to problem-solving in both personal and collaborative contexts.

The Constraint Paradigm: A New Lens for System Improvement

Goldratt’s TOC challenges the conventional wisdom of trying to improve everything simultaneously. Instead, it focuses on identifying and managing the one critical constraint that limits overall system performance at any given point in time.

Identifying Your System’s Bottlenecks

At the heart of TOC is the idea that every system has but one constraint or bottleneck that limits its overall performance at a given time. Here’s how to apply this concept:

Challenge: The tendency to view all parts of a system as equally important or to focus on symptoms rather than root causes.
Action: Systematically analyse your work flows to identify the true bottleneck—the constraint that, if improved, would have the greatest impact on the entire system.
Benefit: Focused improvement efforts that yield disproportionate posotive results and a clearer understanding of system dynamics.

The Five Focusing Steps: A Roadmap for Continuous Improvement

Goldratt’s five focusing steps provide a structured approach to managing constraints (see also: The Goal):

Identify the constraint
Exploit the constraint
Subordinate everything else to the constraint
Elevate the constraint
Repeat the process

Challenge: Resisting the urge to jump to solutions without fully understanding the system (and in particular, demand – from the customers’ perspective Cf. the Vanguard Method).
Action: Systematically work through these five steps, resisting the temptation to skip steps.
Benefit: A methodical approach to improvement that prevents wasted effort on irrelevant, non-critical areas.

The Throughput Worldview: Rethinking Performance Metrics

TOC introduces the concept of throughput as the rate at which a system generates money (or value) through sales. This perspective shifts focus from cost-cutting to value creation.

Beyond Cost Accounting: Embracing Throughput Accounting

Traditional accounting methods can lead to decisions that actually harm overall system performance. Throughput accounting offers a different approach:

Challenge: Avoid the ingrained habit of focusing on cost reduction and local efficiencies.
Action: Reframe decisions in terms of their impact on total system throughput, rather than isolated cost savings.
Benefit: More aligned decision-making that radically improves overall organisational performance.

The Goal: Clarifying Purpose and Measuring Progress

Goldratt emphasises the importance of clearly defining the goal of a system:

Challenge: Avoid confusing means (like cost reduction or efficiency) with ends (like increasing profit or value delivery or meeting folks’ needs).
Action: Explicitly state and regularly revisit the ultimate goal of your system or organisation.
Benefit: Improved alignment of efforts and more meaningful performance metrics.

Thinking Processes: Tools for Systemic Problem-Solving

TOC provides a set of logical thinking tools designed to address complex problems systematically.

Current Reality Tree: Mapping Cause and Effect

This tool helps visualise the current state of a system and the interdependencies within it:

Challenge: The tendency to address symptoms rather than root causes.
Action: Construct a current reality tree to map out the logical relationships between observed effects and their underlying causes.
Benefit: A deeper understanding of system dynamics and more effective problem-solving.

Future Reality Tree: Envisioning and Planning Change

This tool helps project the impact of proposed changes:

Challenge: Implementing changes without fully considering their systemic effects.
Action: Use the future reality tree to think through the potential consequences of interventions before implementing them.
Benefit: More robust change planning and reduced risk of unintended negative consequences.

Conclusion: The Meta-Constraint of Thinking

Goldratt’s Theory of Constraints offers more than just a set of tools for process improvement—it provides a paradigm shift in how we approach complex systems and decision-making. By internalising the principles of TOC, we can develop a more nuanced, systemic approach to both personal and professional challenges.

The true power of TOC lies not in any single technique, but in the cultivated ability to see systems holistically, identify the critical constraint, and focus efforts where they will have the greatest impact. In an era of increasing complexity and interconnectedness, this TOC-led systemic thinking approach may be the most valuable skill we can develop.

Interestingly, TOC aligns well with other systems thinking approaches, such as Donella Meadows’ work on leverage points. Both emphasise the importance of understanding paradigms and identifying key points of intervention. However, while Meadows offers a broader spectrum of leverage points, TOC provides a more focused methodology specifically tailored to improving system performance through constraint management.

As we grapple with complex challenges ranging from supply chain optimisation to climate change mitigation, the principles of TOC offer a powerful framework for focused, impactful action. By learning to identify and manage constraints effectively, we can unlock new levels of performance and create value in ways that might otherwise seem impossible.

The ultimate constraint, Goldratt might argue, is often our own present paradigm. By embracing the TOC worldview, we can break free from limiting assumptions and approach problems with both analytical rigour and creative flexibility—a combination that may prove essential for navigating the complexities of our modern world.

Quality in Relationships: Striving for Zero Conflict

October 3, 2024

Actionable Insights, Alien tech, Antimatter principle, Article, Business, Conflict, Crosby, Culture change, Deming, Dialogue, Empathy, Listening, Nonviolence, Organisational behaviour, Organisational effectiveness, Organisational Therapy, Paradigm shifts, Philosophy, Quality, Relationships, Systems thinking, Toxic behaviours

Leave a comment

Quality in Relationships: Striving for Zero Conflict

In a world where conflict seems omnipresent, from workplace disagreements to international disputes, it’s time to challenge our assumptions. What if conflict, like defects in manufacturing or bugs in software, isn’t an inevitable part of human interaction? What if we could create environments where conflicts are as rare as defects in a cutting-edge factory or bugs in well-designed and well-implemented software?

The Zero Conflict Revolution

From Zero Defects to Zero Bugs to Zero Conflicts

In the 1960s, Philip B. Crosby introduced the revolutionary concept of Zero Defects in manufacturing. This paradigm shift transformed industries, proving that with the right processes and mindset, eliminating defects entirely was possible.

Fast forward to the software industry, where a similar revolution has been unfolding.

Today, we stand on the cusp of applying these same principles to human relationships and organisational dynamics.

The Cost of Conflict and Defects: Why Zero Matters

Conflict isn’t just uncomfortable—it’s expensive. A 2008 study estimated that U.S. employees spend 2.8 hours per week dealing with conflict, costing organisations approximately $359 billion in paid hours annually.

Similarly, software bugs and defects carry enormous costs. A 2022 report by Synopsys found that security vulnerabilities alone in software cost companies an average of $2.5 million per breach.

Imagine redirecting the time, energy, and resources spent on conflicts and defects towards innovation, growth, and positive change.

Building a Zero Conflict Environment

1. Root Cause Analysis: The Foundation of Prevention

Just as a skilled doctor treats the disease, not just the symptoms, and a software engineer fixes the underlying causes of bugs in the way the work works, not just bugs’ manifestations, we might choose to address the root causes of conflicts. This involves:

Conducting thorough post-mortems of past conflicts
Identifying recurring patterns and triggers
Implementing systemic changes to prevent similar issues

2. Communication: The Oxygen of Harmony

Clear, open communication is to interpersonal; and intergroups relationships what clarity of needs (Cf. the Needsscape™) and the attending thereto are to software development—essential and revitalizing. To foster this:

Establish multiple channels for feedback and dialogue
Invite and practice active listening at all levels of the organisation
Regularly check for understanding to prevent misinterpretations

3. Alignment: Creating a Unified Vision

Many conflicts stem from misaligned expectations or values, just as software defects often arise from misaligned requirements, unattended to needs, or omission of key groups and individuals from the set of Folks That Matter™ . To create alignment:

Continually surface and refelct on shared assumptions, beliefs, goals and values
Involve all stakeholders in decision-making processes
Create a strong, inclusive organisational culture that everyone can rally behind

From Conflict Resolution to Conflict Prevention

Redefining Skills for a Zero Conflict World

Instead of training people to resolve conflicts, we might choose to focus on preventing them, much like how cutting-edge software development focuses on preventing bugs rather than just fixing them. Key skills include:

Emotional intelligence and empathy
Proactive problem identification
Collaborative problem-solving techniques
Nonviolence

The Shift in Mindset

Achieving and maintaining a Zero Conflict environment requires ongoing and regular effort, similar to the integration of software development into the wider organisation (Cf. Systems thinking):

Implement habitual feedback loops
Encourage open discussions about potential conflict triggers
Foster a culture where everyone feels responsible for maintaining harmony

Measuring Success in the Zero Conflict Paradigm

New Metrics for a New Approach

To invite behaviour change, we might choose to adopt new ways of both defining and measuring success, inspired by both manufacturing and software development metrics:

Track ‘Days Without Conflict’ similar to safety metrics in manufacturing
Measure the reduction in time spent on conflict-related activities, akin to reducing debugging time in software development
Survey employee satisfaction and stress levels as indicators of underlying tension, similar to user satisfaction metrics in software

The Road Ahead: Challenges and Opportunities

While the Zero Conflict approach offers immense potential, it’s not without challenges. Resistance to change, deeply ingrained habits, and the complexity of human emotions all present obstacles. However, the potential benefits—increased productivity, improved well-being, and stronger relationships—make this a journey worth undertaking.

As we stand at this crossroads, the question isn’t whether we can eliminate conflict, but whether we have the courage and vision to make it happen. Just as we’ve revolutionised manufacturing quality and software reliability, we can transform the quality of our relationships. In doing so, we might just create a world where quality in relationships is as achievable as quality in manufacturing and zero defect software.

Fuggedabaht Training: The Future of Learning in Tech

September 15, 2024

Actionable Insights, Antimatter principle, Article, Careers, Coding, Learning, Organisational Therapy, Software development, Systems thinking, Training

Leave a comment

Fuggedabaht Training: The Future of Learning in Tech

In the realm of tech education and learning, few statements are as provocative and thought-provoking as Oscar Wilde’s assertion:

“Education is an admirable thing, but it is well to remember from time to time that nothing that is worth knowing can be taught.”

This paradoxical wisdom serves as the perfect launching point for an exploration of learning in the tech industry. In a world where formal training has long been the go-to method for skill development, Wilde’s words challenge us to reconsider our approach fundamentally.

In the dizzying world of technology, where today’s innovation is tomorrow’s legacy system, how do we truly learn? The tech industry has long relied on training as its educational backbone, but is this approach ever fit for purpose? Let’s embark on a journey to unravel this question and explore the future of learning in tech.

The Training Trap: Why It’s Not Enough

Picture this: You’ve just completed an intensive week-long course on the latest programming language. You’re buzzing with newfound knowledge, ready to conquer the coding world. Fast forward three weeks, and you’re staring at your screen, struggling to remember the basics. Sound familiar?

This scenario illustrates what Richard Feynman, the renowned physicist, meant when he said:

“I learned very early the difference between knowing the name of something and knowing something.”

Training often gives us the illusion of learning. We walk away with certificates and buzzwords, but when it comes to actually applying this knowledge, we find ourselves fumbling in the dark.

The Forgetting Curve: Our Brain’s Sneaky Saboteur

Enter Hermann Ebbinghaus and his infamous “forgetting curve”. This isn’t just some dusty psychological theory; it’s a real phenomenon that haunts every training session and workshop.

As the curve shows, without active recall and application, we forget about 70% of what we’ve learned within a day, and up to 75% within a week. In the context of tech training, this means that expensive, time-consuming courses might be yielding diminishing returns faster than you can say “artificial intelligence”.

Real World vs. Training Room: A Tale of Two Realities

Training environments are like swimming pools with no deep end. They’re safe, controlled, and utterly unlike the ocean of real-world tech problems. This disparity leaves many students floundering when they face their first real challenge.

Moreover, in an industry where change is the only constant, static training curricula are often outdated before they’re even implemented. As Alvin Toffler presciently noted:

“The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn.”

The Bootcamp Boom: A Silver Bullet or Fool’s Gold?

In recent years, coding bootcamps have exploded onto the tech education scene, promising to transform novices into job-ready developers in a matter of weeks or months. But do they truly bridge the gap between traditional training and real-world demands?

The Promise of Bootcamps

Bootcamps offer an intensive, immersive learning experience that focuses on practical skills. They aim to provide:

Rapid skill acquisition
Project-based learning
Industry-aligned curriculum
Career support and networking opportunities

For many career changers and aspiring developers, bootcamps represent a tantalizing shortcut into the tech industry.

The Reality Check

While bootcamps have undoubtedly helped many individuals launch tech careers, they’re not without their criticisms:

Skill Depth: The accelerated pace often means sacrificing depth for breadth. As one bootcamp graduate put it:

“I learned to code, but I didn’t learn to think like a developer.” [and what does it even mean to “think like a developer, anyway?]
Market Saturation: The proliferation of bootcamps has led to a flood of entry-level developers, making the job market increasingly competitive.
Varying Quality: Not all bootcamps are created equal. The lack of standardisation means quality can vary wildly between programs.
The Long-Term Question: While bootcamps may help you land your first job, their long-term impact on career progression is still unclear.

Bootcamps: A Part of the Solution, Not the Whole Answer

Bootcamps represent an interesting hybrid between traditional training and more innovative learning approaches. At their best, they incorporate elements of experiential learning and peer collaboration. However, they still operate within a structured, time-bound format that may not suit everyone’s approach to learning or career goals.

As tech leader David Yang notes:

“Bootcamps can kickstart your journey, but true mastery in tech requires a lifetime of learning.”

In the end, we might choose to view bootcamps as one possible tool in a larger learning toolkit, rather than a one-size-fits-all solution to tech education.

Reimagining Learning: The Tech Education Revolution

So, if traditional training isn’t the answer, what is? Let’s explore some alternatives that are already showing promise:

Experiential Learning: Remember building your first website or debugging your first major error? That’s experiential learning in action. As Confucius wisely said, “I hear and I forget. I see and I remember. I do and I understand.”
Continuous Learning Culture: Imagine a workplace where learning is as natural as breathing. Google’s no defunct “20% time” policy, which allowed employees to spend one day a week on side projects, was a prime example of this philosophy in action.
Peer-to-Peer Knowledge Sharing: Some of the best learning happens organically, through conversations with colleagues. Platforms like Stack Overflow have harnessed this power on a global scale.
Curiosity-Driven Exploration: What if we treated curiosity as a key performance indicator? Companies like 3M, which encourages employees to spend 15% of their time on self-directed projects, are leading the way.

Caution: Whilst experiential learning has its merits, it fails abjectly to counter groupthink, learning of the wrong things, and relatively ineffective shared assumptions and beliefs. Other approaches e.g. Organisational Psychotherapy can address the latter.

The Path Forward: Embracing the Learning Revolution

As we stand at the crossroads of traditional training and innovative learning approaches, it’s clear that a paradigm shift is not just beneficial—it’s essential. The future of learning in tech isn’t about more training; it’s about creating environments that foster continuous, experiential, and collaborative learning, whilst simultaneouly growing the ability to think critically, think of wider systems (systems thinking) and constantly surface and reflect together on shared assumptions and beliefs.

So, the next time you’re planning a training session, pause and ask yourself: Is this the best way to foster real learning? What about more engaging, effective approaches we could take?

In the words of William Butler Yeats, “Education is not the filling of a pail, but the lighting of a fire.” Isn’t it time we stopped trying to fill pails and started lighting fires in the tech industry.

What are your thoughts? How well has training served your needs, and how has your learning journey in tech evolved beyond traditional training? Please share your experiences in the comments below!

Enhancing Software Development Outcomes

August 12, 2024

Antimatter principle, Article, Capability development, Collective psyche, Deming, Giants, Memeology, Motivation, Needs, Organisational effectiveness, Psychology, Quantification, Rightshifting, Self-organisation, Software development, Systems thinking

Leave a comment

Enhancing Software Development Outcomes

A Cornucopia of Techniques

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

Gilb’s Evolutionary Project Management (Evo)

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

Goldratt’s Theory of Constraints (TOC)

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

Ackoff and Systems Thinking

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

Seddon’s Vanguard Method

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

Rother’s Toyota Kata

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

Deming’s System of Profound Knowledge

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

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

Marshall’s Organisational Psychotherapy

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

The Adoption Quandary

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

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

The Crux: Self-Motivation

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

Surmounting Inertia

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

Nurturing a Desire for Self-Betterment

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

Peer-Driven Inspiration

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

Individual Responsibility

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

Conclusion

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

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

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

Postscript

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

The Crucial Role of Trialability in Organisational Change

May 13, 2024

Actionable Insights, Article, Culture change, Organisational Therapy, Psychotherapy, Systems thinking

Leave a comment

The Crucial Role of Trialability in Organisational Change

An Odd Word with Profound Implications ‘Trialability’ is certainly an unusual term, but it holds the key to successful adoption of new ideas and practices within organisations. Simply put, trialability refers to how easily a proposed innovation can be tested or experimented with on a limited basis before full implementation. If an idea or product cannot be trialled, it is unlikely to gain traction and organisational buy-in.

The Trialability Challenge in Organisational Psychotherapy

Organisational psychotherapy – the application of psychological and group dynamics principles to improve workplace culture, processes and performance – faces a unique trialability hurdle. Unlike a new software platform that can be piloted in one department, psychotherapeutic interventions invite collective engagement across the organisation. Piecemeal trials are seldom representative of the full impact. This is of course true for many Systems Thinking approaches.

Enhancing Trialability Through Simulation

To enhance trialability, psychotherapists working with organisations can leverage simulations and role-playing scenarios. These provide a relatively low-risk environment to model proposed changes and gauge employee reactions before wider rollout. Well-designed simulations allow stakeholders to experience potential outcomes and make adjustments proactively.

The 87% Imperative Research indicates that a staggering 87% of the variance in successful innovation adoption stems from trialability. This statistic underscores just how critical it is for organisational psychotherapists to creatively overcome the trialability challenge. Failing to do so means even the most brilliant ideas are likely to be ignored or resisted.

Bite-Sized Trials

In addition to simulations, psychotherapists may choose to boost trialability by designing interventions as a series of bite-sized, iterative steps. Rather than attempting wholesale transformational change, this approach allows employees to experience upgrades incrementally, providing feedback and adjusting as needed. Each iteration serves as a mini-trial before progressing further.

Fostering an Experimental Mindset

Ultimately, ensuring adequate trialability requires fostering an organisational culture that embraces experimentation and empiricism over rigid traditions. Psychotherapists may choose to invite leaders to encourage every level to regularly pilot new methods, measure outcomes rigorously, and maintain a willingness to adapt based on real-world results. This experimental mindset is vital for staying focussed and innovative.

That odd little word ‘trialability’ packs a powerful punch when it comes to driving effective organisational change. By creatively maximising trialability, organisational psychotherapists can overcome a major barrier and vastly improve the odds of their therapeutic insights taking root and blossoming into sustained benefits.

The Comfortable Lie: Why We Don’t Actually Learn From Our Mistakes

The Illusion of Causality

The Context Problem

The Narrative Fallacy

Emergence and Irreducibility

The Adaptation Trap

So What Do We Do?

The Productivity of Failure

Further Reading

Share the joy :)

A Conversation About John Gall

Who Was John Gall?

Meeting the Man Behind the Ideas

Missing the Lineage

The Conversation

Further Reading

Share the joy :)

Deming’s 95/5 Rule

What Is Deming’s 95/5 Assertion?

The Traditional Mindset vs. Deming’s Vision

The Case for Accepting Deming’s 95/5 Rule

Check Your Assumptions

Consequences for Coaching

My Take: Accept the Principle, Question the Precision

Practical Applications

The Bottom Line

Further Reading

Share the joy :)

Coding Practices Are So the Wrong Focus

The Software Industry’s Red Bead Problem

The Invisible System

When Developers See the System

The Real Constraints

Beyond Individual Excellence

Building System Awareness

The Path Forward

A Note on ‘Users’ and ‘Customers’

Further Reading

Share the joy :)

Deming’s System of Profound Knowledge

The Four SoPK Elements

The Genesis of ‘Profound Knowledge’

The Journey to Integration

The Four Pillars of Understanding

Why This Framework Mattered

The Revolutionary Nature of Integration

The Four Elements in Practice

Why Psychology? The Human Element in Quality

Deming’s Personal Ranking: Psychology as Primary

The Interconnected Nature of Profound Knowledge

Legacy and Relevance Today

Further Reading

Share the joy :)

When is an Organisation? A Cybernetic Approach to Organisational Psychotherapy

When is Cybernetics?

Beyond the Myth of Objective Organisational Reality

The Therapist as Co-Creator

The Art and Ethics of Boundary Drawing

Multiple Organisational Realities

Practical Implications for Organisational Therapy

From Diagnostic Certainty to Epistemic Humility

From Universal Solutions to Contextual Sensitivity

From Expert Objectivity to Collaborative Enquiry

From Problem-Focused to Perspective-Focused

The Ethical Dimension

The Moment of Recognition

Living the Questions

Further Reading

Core Cybernetics and Systems Theory

Cybernetics Applied to Organisations

Organisational Development and Psychotherapy

Contemporary Applications and Methods

Related Philosophical Foundations

Share the joy :)

T-Squad: The Five Thinking Patterns That Turn Anyone Into a Problem-Solving Powerhouse

What Are These Five Patterns?

Why These Five Patterns Work

The Hidden Pattern Problem

The Multiplier Effect

T-Squad vs Peter Senge’s Fifth Discipline