Ahead of Its Time
How Familiar Proved Human Flourishing and Business Success Naturally Align
When we started Familiar in 1996, we weren’t building just another software company. Our stated purpose was deceptively simple:
‘To help people—clients, employees, suppliers, everyone—come together to explore what fulfilment meant for each’
This wasn’t corporate mission-speak. It was a genuine proof of concept for creating conditions where human flourishing could emerge through meaningful work.
For years, I’d been immersed in the work of Deming, Goldratt, Ackoff, and other systems thinkers who had fundamentally challenged traditional management orthodoxy. These weren’t reformers trying to make conventional management more humane—they were revolutionaries who understood that command-and-control structures were fundamentally incompatible with human flourishing in collaborative knowledge work environments.
Having worked as a software development consultant from circa 1982-1996, I’d observed the same dysfunctional patterns across dozens of organisations over fourteen years. I already knew by 1996 that we could do so much better. The theoretical insights provided the foundation, but the extensive real-world experience provided the urgency: an organisation where people could genuinely explore what fulfilment meant through meaningful work, free from the industry-wide dysfunction I’d witnessed repeatedly.
Familiar became my proof of concept for whether antimanagement philosophy could create conditions for human flourishing through meaningful work. The name ‘Familiar’ itself carried three layers of meaning:
- Something well-known (trustworthy)
- Family-related (close relationships)
- A witch’s familiar (the magical companion that guides and empowers).
And there was another layer of irony: whilst the name promised something familiar and comforting, the way we actually delivered stuff was profoundly unfamiliar to anyone steeped in conventional management thinking. The antimanagement philosophy, distributed organising intent, fear elimination, and mission command (auftragstaktik) principles would have felt completely alien, even threatening, to traditional managers. They’d encounter something that called itself “Familiar” but operated in ways that challenged everything they thought they knew about running organisations.
We weren’t just delivering software—we were creating a space where people could explore fulfilment through genuine contribution, which required abandoning familiar management assumptions and beliefs to embrace something genuinely transformative.
The Foundation: Systems Thinking
My approach at Familiar was built on three fundamental insights I’d gleaned from the masters:
Deming’s revelation: Most problems in organisations are system problems, not people problems. When people consistently fall short, look at the system they’re operating within, not their individual capabilities.
Goldratt’s insight: Every system has constraints, and optimising anything other than the constraint is just an illusion of improvement. Find the bottleneck, manage the bottleneck, everything else is secondary.
Ackoff’s wisdom: Organisations are systems, and systems are more than the sum of their parts. You can’t understand a system by taking it apart—you have to understand how the parts interact to produce the whole.
These weren’t abstract theories to me—they were practical frameworks for building something better than the command-and-control tech organisations I’d observed.
Deming in Practice: Eliminating Fear
Deming’s fourteenth point was ‘drive out fear’—essential for any organisation trying to help people explore fulfilment. People can’t discover what meaningful work looks like when they’re afraid of making mistakes, taking initiative, or suggesting better approaches.
In most tech organisations I’d observed during fourteen years of consulting work, fear was endemic. Fear of choosing the wrong technical approach. Fear of missing deadlines. Fear of client complaints. Fear of looking incompetent in front of colleagues. Fear re: job security and peremptory job loss. This fear led to exactly the behaviours Deming predicted: people stopped thinking, stopped experimenting, stopped suggesting better ways to do things.
At Familiar, I deliberately applied concepts to eliminate fear:
Technical decisions: Instead of requiring approval for architectural choices, we established technical principles and let people apply them based on their understanding of the organising intent. If someone made a choice that didn’t work out, we treated it as learning, not failure. I can remember our first major client project where we got hung up on a technical decision and set the schedule back by weeks. I have to hold my hand up for that one – and for modelling learning in action.
Client interactions: Instead of requiring all client communication to flow through me, we exposed everyone to the principles of client relationships and let them engage directly based on our shared organising intent. This reduced the fear of ‘saying the wrong thing’ because everyone understood the underlying purpose.
Deadlines: Instead of punitive deadline management, we focused on understanding constraints and bottlenecks. When projects ran into trouble, we asked ‘what’s preventing progress?’ and definitely not ‘who’s responsible?’
The outcome was remarkable. People proposing improvements to client requirements—not because they had to, but because they found fulfilment in attending to folks’ genuine needs. They began experimenting with better technical approaches because the work itself became engaging rather than just completing assigned tasks. They took ownership of problems because they discovered meaning in being truly helpful.
Goldratt’s Constraint Theory: Finding the Real Bottleneck
Goldratt taught us that every system has exactly one constraint at any given time, and that constraint determines the performance of the entire system. Most organisations waste enormous energy optimising non-constraints whilst ignoring the thing that actually limits their throughput.
In software development, I discovered the constraint was almost never coding speed—it was usually something much more subtle:
Needs understanding: Projects stall not because developers are slow, but because they haven’t yet understood what people really need (as opposed to what they think they want).
Context switching: People are inefficient not because they lack skills, but because they are juggling too many deiiverables simultaneously.
Decision delays: Work backs up not because of technical complexity, but because someone waits for approval to proceed.
Knowledge isolation: Problems persisted not because they were difficult, but because the person who understood the solution wasn’t talking to the person who had the problem.
Once I started looking for these systemic constraints instead of individual performance issues, solutions became obvious. We adopted an approach of front-load understanding of genuine needs (“Stakeholders’ Needs” as per Javelin). We limited work-in-progress. We eliminated approval bottlenecks by distributing decision-making authority. We created approaches for knowledge sharing.
The results were dramatic: our throughput improved not because people worked harder, but because we removed the things that were preventing them from working effectively.
Ackoff’s Interactive Design: Purpose-Driven Organisation
Ackoff’s approach to organisational design started with a fundamental question: ‘What is this system trying to accomplish?’ Not what it’s currently doing, but what it should ideally achieve if it were perfectly designed for its purpose.
For Familiar, the ideal wasn’t just ‘deliver software products on time and budget’—that was an operational goal, not a purpose. The real purpose was exactly what we’d stated from the beginning: ‘help people—clients, employees, everyone—come together to explore what fulfilment means for each’.
This distinction changed everything:
Product scope: Instead of building exactly what clients specified, we looked for underlying needs they hadn’t articulated and opportunities to attend to them.
Technical decisions: Instead of choosing technologies based on familiarity, we chose based on long-term client value.
Team organisation: Instead of organising around skills (front-end developers, back-end developers), we organised around client needs and outcomes.
Success metrics: Instead of measuring delivery metrics, we measured client business impact.
This purpose-driven approach created what Ackoff called ‘interactive planning’—where everyone in the organisation could contribute to designing better ways to achieve the overall purpose.
The Synthesis: Mission Command Principles
What we discovered was that Deming, Goldratt, and Ackoff had independently arrived at principles that military strategists call ‘mission command’ (or auftragstaktik)
Shared understanding (Ackoff’s purpose clarity) meant everyone could make decisions aligned with organising intent.
Constraint focus (Goldratt’s bottleneck concept) meant we addressed the things that actually limited our effectiveness.
Fear elimination (Deming’s system thinking) meant people could take initiative without worrying about punishment.
The result was an organisation that could adapt faster than its environment changed because decision-making was distributed to where the information was best, but coordinated through shared principles and clear organising intent.
The Exemplar Results
By 2000, when I left Familiar, we had successfully demonstrated something remarkable: systems thinking and antimanagement principles could create a fundamentally different kind of software organisation where customer success and human fulfilment naturally aligned.
Our projects consistently came in ahead of schedule because we eliminated systemic delays, not because we worked faster or harder. Client satisfaction was exceptional because we attended to their real needs, not just their perceived problems. Our people were genuinely engaged because they understood how their work contributed to larger purposes, not just immediate tasks.
The Broader Implications
The Familiar experience proved that the insights of Deming, Goldratt, and Ackoff weren’t just applicable to manufacturing—they were fundamental principles of effective organisation that worked even better in collaborative knowledge work.
This became the foundation for what would later become Product Aikido: the recognition that organisations, like physical systems, have natural dynamics that you can work with or against. Fighting against these dynamics with command-and-control structures is exhausting and ineffective. Learning to work with them through systems thinking creates seemingly effortless effectiveness (and see also: wu wei 無為).
The control paradox I discovered at Familiar wasn’t really about learning to let go—it was about recognising that auftragstaktik principles, originally developed for military contexts, were perfectly suited to collaborative knowledge work. When you’re solving complex problems with uncertain requirements, the people closest to the technical details always have better insight into possible solutions than those managing from above.
Auftragstaktik Mirrored in Collaborative Knowledge Work
What military strategists call ‘mission command’ becomes even more powerful in collaborative knowledge work environments. Our programmer Sarah’s integration breakthrough happened because she understood both the client’s real needs and the technical possibilities better than I could from an oversight perspective. She had the context, the relationships, and the technical knowledge needed to craft an elegant solution.
This is auftragstaktik in its purest form: clear organising intent, defined boundaries (budget, timeline, integration requirements), and complete authority to determine the approach. The result was innovation that wouldn’t have emerged through traditional command-and-control.
The Product Aikido Framework
What emerged from the Familiar exemplar eventually crystallised into a comprehensive approach to product development that directly challenges everything conventional management teaches. Product Aikido (Marshall, 2013) recognises that every organisation operates within what Clausewitz called friktion—the resistant medium where organising intent meets entropy, where perfect plans encounter messy reality.
The core insight: Traditional command-and-control management doesn’t reduce friktion—it amplifies it.
Mission-Type Tactics (Auftragstaktik) in Collaborative Knowledge Work Instead of detailed instructions, you provide organising intent: what needs to be accomplished and why, along with clear boundaries and constraints. Teams closest to the work figure out how to achieve the intent. This eliminates the friktion of information travelling up hierarchies and decisions travelling back down—all whilst circumstances have changed. In collaborative knowledge work, this becomes even more powerful because the people doing the work always understand the technical possibilities and constraints better than those managing from a distance.
Distributed Decision-Making Authority flows to where the information and capability reside. When Sarah’s database expertise was needed for the integration project, she could act immediately rather than wait for approval. This creates what the military calls ‘surfaces and gaps’—you flow resources through areas of least resistance rather than pushing against obstacles.
Speed and Focus Product Aikido emphasises rapid, concentrated action over slow, distributed effort. You identify your ‘main effort’—the most critical work at any given moment—and converge resources there whilst accepting prudent risk elsewhere. Speed becomes a weapon because it outpaces entropy’s ability to disrupt your plans.
Generalising Specialists Instead of narrow specialists waiting in queues, you develop people with overlapping capabilities who can adapt as situations change. This reduces handoff friktion and keeps work flowing through natural bottlenecks.
Why Command-and-Control Fails
Traditional management approaches fail because they fight against the natural dynamics of complex systems:
Information Degradation: Every layer of hierarchy distorts the signal. By the time strategic organising intent reaches the people doing the work, it’s been filtered, interpreted, and diluted through multiple perspectives and agendas.
Response Lag: Problems that could be solved in minutes take hours or days whilst they travel up approval chains. Meanwhile, opportunities disappear and issues compound.
Initiative Paralysis: When people know that taking action without permission leads to punishment, they stop thinking strategically. They become order-takers rather than problem-solvers.
Bottleneck Multiplication: Every decision-maker becomes a potential chokepoint. The more control you try to exert, the more places where work can get stuck.
Friktion Amplification: Instead of reducing organisational resistance, command-and-control structures create more of it. They turn natural adaptation into bureaucratic procedures, transform quick conversations into formal communications, and replace contextual judgement with rigid processes.
Product Aikido recognises that in complex, uncertain environments, the highest form of control is not needing to exercise it. You apply concepts and evolve approaches that naturally produce desired outcomes rather than trying to control every action within poorly designed systems.
The antimanagement philosophy isn’t about being ‘nice’ to people—though it often brings that about. It’s about recognising that sustainable organisational effectiveness emerges when people find genuine fulfilment through meaningful work. This requires creating conditions where human flourishing and business success become naturally aligned rather than perpetually in tension.
The Learning Journey
Stage 1 – Resistance: People will initially try to control everything, getting frustrated when teams act ‘incorrectly’. The system must be patient here—show them the costs of over-control through experience, not lectures.
Stage 2 – Reluctant Delegation: People start giving mission-type orders out of necessity (too much happening simultaneously). They experience their first ‘pleasant surprises’ when subordinates handle situations well.
Stage 3 – Trust: People begin to see their role in setting doctrine and strategic direction rather than tactical execution. This is the breakthrough moment.
Stage 4 – Mastery: People understand that their job is building effective coordination systems, not controlling individual actions. They become genuine teamies rather than controllers.
The Pleasant Surprises
As I stopped trying to control every decision, something beautiful emerged: people began finding fulfilment through genuine contribution. Tom, our junior developer, figured out a caching approach that cut database load by 60%—not because he was assigned to optimise performance, but because he found meaning in elegant solutions. Lisa discovered a client workflow optimisation that saved the client two hours of daily manual work—because she genuinely cared about making their lives better. Mark built debugging tools that helped us troubleshoot problems in minutes instead of hours—because he found satisfaction in removing friktion for his teammates.
None of these innovations would have happened under command-and-control. I would have specified the solution, they would have implemented it, and we’d have missed opportunities for real fulfilment through creative problem-solving.
But the biggest surprise was how much more effective I became. Instead of reviewing every technical decision, I could focus on client relationships, business development, and strategic challenges that truly needed my attention. Instead of being a bottleneck, I became a force multiplier.
The Trust Dividend
By 1999, something remarkable had happened. Product development ran more smoothly with less oversight. Client satisfaction increased because problems got resolved faster. Our people were more engaged because they owned their solutions instead of just implementing mine.
Most importantly, the organisation became a place where people could flourish even when I wasn’t there. When I travelled to visit potential clients, work continued at full speed because people had found their own sources of meaning and motivation. When I took my first real vacation in three years, I came back to find two projects ahead of schedule and a third that had solved a technical challenge I’d been wrestling with for months—not through heroic effort, but through the kind of creative collaboration that emerges when people feel genuinely fulfilled by their work.
The team had become genuinely self-organising around our shared purpose: helping people find fulfilment through meaningful contribution.
The Ultimate Paradox – And Its Limitation
When I left Familiar in 2000, I discovered something humbling about the systems we’d built. Despite years of implementing antimanagement principles, eliminating fear, and distributing decision-making authority, the organisation I thought had become self-sustaining proved to be more dependent on my personal influence than I’d ever realised.
After 2000, Familiar became a hollow shell and eventually faded into oblivion. It seems the approaches we’d evolved were always dependent on my personal influence. The principles required my presence.
This reveals something profound about the limitations of organisational change, even when built on sound theoretical foundations. The organising intent that had seemed so embedded in our culture, the distributed decision-making that had felt so natural, the fear elimination that had created such innovation—all of it required ongoing cultivation that only I was providing.
The control paradox I’d discovered wasn’t complete. Yes, you can create conditions where people find meaning through meaningful work and where human flourishing aligns with business success. Yes, antimanagement principles can outperform command-and-control structures dramatically. Yes, organising intent and mission command can compensate for organisational friktion.
But creating truly self-sustaining organisations—ones that can maintain these principles without their architect—remains an unsolved challenge.
Looking back, I realise the Familiar proof of concept demonstrated both the power and the limitations of the antimanagement philosophy. The principles worked brilliantly whilst I was there to embody and reinforce them. They created genuine human flourishing and exceptional business results. But they weren’t truly embedded in a way that could survive my departure.
This reflects what I later came to understand as ‘reversion to the mean’ in organisational development. According to the Marshall Model, synergistic organisations—those operating with i.e. distributed decision-making, shared purpose, and intrinsic motivation—naturally tend to revert to the analytic mindset over time, unless actively maintained. Analytic organisations are characterised by command-and-control structures, individual blame rather than collective focus, and extrinsic motivation systems. They represent the dominant paradigm that our broader economic and social systems reinforce.
Without constant cultivation of synergistic principles, organisations drift back toward what feels familiar (sic) and is supported by conventional business thinking, recruitment practices, and societal expectations. The synergistic state requires ongoing energy and attention to maintain—it’s not a stable equilibrium in our current context.
Perhaps this is the deeper lesson: sustainable organisational transformation isn’t just about implementing better systems and principles. It’s about creating cultures that can continuously regenerate those principles without dependence on any individual—even their founder.
The systems thinking masters—Deming, Goldratt, Ackoff—provided the theoretical foundation. Familiar demonstrated their principles could work in practice. But the challenge of creating lasting change that survives leadership transitions remains one of the most gnarly problems in organisational development.
This doesn’t invalidate what we accomplished—it contextualises it. For four years, we created an organisation where people could explore what fulfilment meant through meaningful work, where business success and human flourishing naturally aligned, where the impact of friktion was minimised through distributed organising intent. That’s valuable, even if it wasn’t permanent.
The Continuing Proof of Concept
What started as a proof of concept in applying antimanagement thinking to software development became validation for a different way of organising knowledge work. The principles we validated at Familiar—shared purpose, constraint focus, fear elimination, distributed decision-making, meaning, agency—turned out to be fundamental to effectiveness in collaborative knowledge work environments.
The real insight wasn’t that these approaches were ‘nice’ or ‘people-friendly’—though they were. The insight was that they fundamentally outperformed traditional management approaches at achieving business outcomes. Antimanagement philosophy wasn’t about being softer—it was about being more effective.
Ahead of Its Time: Pioneering What Others Would Later Theorise
Looking back, Familiar pioneered the practical application of concepts that wouldn’t be widely written about until years after its demise. We were implementing these principles in 1996-2000, whilst the theoretical frameworks that would later validate our approach were still to come.
We did discover one contemporary kindred spirit: around 1999, we found Andy Law’s account of St. Luke’s advertising agency in Creative Company (1999), which described another organisation that had chosen a remarkably similar path—eliminating traditional hierarchy, distributing ownership, and organising around purpose rather than profit. It was validating to learn we weren’t entirely alone in our revolutionary approach, though such examples remained extraordinarily rare.
Agile Development: We applied and evolved Agile principles that I had first defined in Europe circa 1994—seven years before the Agile Manifesto was published in 2001. Familiar was implementing iterative development, customer collaboration, and responding to change whilst most of the software industry was still locked into waterfall methodologies or simply code hacking.
Self-Managing Organisations: Familiar operated as what Frederic Laloux would later call a ‘Teal Organisation’ in Reinventing Organizations (2014)—fourteen years after I left the company. We had already proven that distributed decision-making, elimination of traditional hierarchy, and purpose-driven work could create exceptional results.
Intrinsic Motivation: Dan Pink’s Drive (2009) would articulate the importance of autonomy, mastery, and purpose in knowledge work—concepts we had embedded in Familiar’s culture nine years earlier. Our focus on helping people explore what fulfilment meant was intrinsic motivation in practice.
Purpose-Driven Business: The idea that organisations can exist for more than profit maximisation, that they can serve human flourishing, would become mainstream business thinking decades later. Familiar’s stated purpose—helping people explore what fulfilment meant—was radically ahead of its time.
Constraint Theory in Knowledge Work: Applying Goldratt’s Theory of Constraints to software development and identifying systemic bottlenecks rather than individual performance issues wouldn’t become common practice until much later (hat tip to David Anderson). We were finding and managing the real constraints whilst others were, and still are, optimising on individual productivity.
Mission Command in Civilian Organisations: The application of military organising intent and auftragstaktik principles to business contexts was virtually unknown in the 1990s. We were demonstrating these concepts worked in collaborative knowledge work long before they gained wider recognition.
This timeline matters because it demonstrates that Familiar wasn’t following established best practices—we were pioneering approaches that would later be validated by research and adopted by a few progressive organisations worldwide. The proof of concept was genuinely ahead of its time.
The tragedy isn’t that the principles didn’t work—they worked brilliantly. The tragedy is that we hadn’t yet solved the deeper challenge of creating self-sustaining cultures that could maintain these principles without their original architect. That challenge remains largely unsolved today, even with all the theoretical frameworks that have since emerged.
Sometimes the most practical thing you can do is apply good theory.
“In theory, there is no difference between theory and practice. In practice there is.”
~ Yogi Berra
The lessons from Familiar shaped everything I did afterward, not because they taught me better management techniques, but because they revealed what becomes possible when you organise work in service of human fulfilment rather than mere productivity.
Further Reading
Ackoff, R. L. (1994). The democratic corporation: A radical prescription for recreating corporate America and rediscovering success. Oxford University Press.
Clausewitz, C. von. (1832/1976). On war (M. Howard & P. Paret, Trans.). Princeton University Press.
Deming, W. E. (1986). Out of the crisis. MIT Press.
Gerber, M. E. (1995). The E-Myth revisited: Why most small businesses don’t work and what to do about it. HarperBusiness.
Goldratt, E. M. (1984). The goal: A process of ongoing improvement. North River Press.
Goldratt, E. M. (1997). Critical chain. North River Press.
Immelman, R. (2003). Great Boss Dead Boss: How to exact the very best performance from your company and not get crucified in the process. Stewart Philip International.
Laloux, F. (2014). Reinventing organizations: A guide to creating organizations inspired by the next stage of human consciousness. Nelson Parker.
Law, A. (1999). Creative Company: How St. Luke’s became ‘the ad agency to end all ad agencies’. John Wiley & Sons.
Marshall, R.W. (2010, August 16). The starting of Familiar. Think Different. Retrieved from https://flowchainsensei.wordpress.com/2010/08/16/the-starting-of-familiar/
Marshall, R.W. (2020, August 24). Some Familiar experiences. Think Different. Retrieved from https://flowchainsensei.wordpress.com/2020/08/24/some-familiar-experiences/
Marshall, R.W. (2021, June 23). The naming of Familiar. Think Different. Retrieved from https://flowchainsensei.wordpress.com/2021/06/23/the-naming-of-familiar/
Marshall, R.W. (2022, April 24). How do you set up a salary model that has everyone’s approval? Think Different. Retrieved from https://flowchainsensei.wordpress.com/2022/04/24/how-do-you-set-up-a-salary-model-that-has-everyones-approval/
Marshall, R.W. (2013). Product Aikido: A manual for product development groups. Self-published. Retrieved from https://flowchainsensei.wordpress.com/wp-content/uploads/2013/04/productaikido041016.pdf
Pink, D. H. (2009). Drive: The surprising truth about what motivates us. Riverhead Books.
United States Marine Corps. (1989). Warfighting: Marine Corps Doctrinal Publication 1. Department of the Navy.
Think Different 