Archive

Drucker

The Secret Career Advantage Most Developers Ignore

August 11, 2025
Action, Actionable Insights, Article, Careers, Drucker, Learning, Product development, Quintessence, Software development
Leave a comment

The Secret Career Advantage Most Developers Ignore

Why understanding foundational principles could be your biggest competitive edge

Whilst most developers chase the latest frameworks and cloud certifications, there’s a massive career opportunity hiding in plain sight: foundational knowledge that 90% of your peers will never touch.

The developers who understand systems thinking, team dynamics, and organisational behaviour don’t just write better code—they get promoted faster, lead more successful projects, and become indispensable to their organisations. Here’s why this knowledge is your secret weapon.

The Opportunity Gap Is Massive

Walk into any tech company and you’ll find dozens of developers who can implement complex algorithms or deploy microservices. But try to find someone who understands why projects fail, how teams actually work, or how to think systematically about performance bottlenecks. You’ll come up empty.

This creates an enormous opportunity. When everyone else is fighting over who knows React best, you can differentiate yourself by understanding why most React projects fail. Whilst others memorise API documentation, you can diagnose the organisational problems that actually slow teams down.

The knowledge gap is so wide that basic competency in these areas makes you look like a genius.

You’ll Solve the Right Problems

Most developers optimise locally—they’ll spend weeks making their code 10% faster whilst completely missing that the real bottleneck is a manual approval process that batches work for days. Understanding systems thinking (Deming, Goldratt, Ackoff) means you’ll focus on the constraints that actually matter.

I’ve watched developers become heroes simply by identifying that the ‘performance problem’ wasn’t in the database—it was in the workflow. Whilst everyone else was arguing about indices, they traced the real issue to organisational design. Guess who got the promotion?

When you understand flow, variation, and constraints, you don’t just fix symptoms—you solve root causes. This makes you dramatically more valuable than developers who can only optimise code.

You’ll Predict Project Outcomes

Read The Mythical Man-Month, Peopleware, and The Design of Everyday Things, and something magical happens: you develop pattern recognition for project failure. You’ll spot the warning signs months before they become disasters.

Whilst your peers are surprised when adding more developers makes the project slower, you’ll know why Brooks’ Law kicks in. When others are confused why the ‘obviously superior’ technical solution gets rejected, you’ll understand the human and organisational factors at play.

This predictive ability makes you invaluable for planning and risk management. CTOs love developers who can spot problems early instead of just reacting to crises.

You’ll Communicate Up the Stack

Most developers struggle to translate technical concerns into business language. They’ll say ‘the code is getting complex’ when they should say ‘our development velocity will decrease by 40% over the next six months without refactoring investment’.

Understanding how organisations work—Drucker’s insights on knowledge work, Conway’s Law, how incentive systems drive behaviour—gives you the vocabulary to communicate with executives. You’ll frame technical decisions in terms of business outcomes.

This communication ability is rocket fuel for career advancement. Developers who can bridge technical and business concerns become natural candidates for technical leadership roles.

You’ll Design Better Systems

Christopher Alexander’s Notes on the Synthesis of Form isn’t just about architecture—it’s about how complex systems emerge and evolve. Understanding these principles makes you better at software architecture, API design, and system design interviews.

You’ll build systems that work with human organisations instead of against them. You’ll design APIs that developers actually want to use. You’ll create architectures that can evolve over time instead of calcifying.

Whilst other developers create technically impressive systems that fail in practice, yours will succeed because they account for how humans and organisations actually behave.

You’ll Avoid Career-Limiting Mistakes

Reading Peopleware could save your career. Understanding that software problems are usually people problems means you won’t waste months on technical solutions to organisational issues. You won’t join dysfunctional teams thinking you can fix them with better code.

You’ll recognise toxic work environments early and avoid getting trapped in death-march projects. You’ll understand which technical initiatives are likely to succeed and which are doomed by organisational realities.

This knowledge acts like career insurance—you’ll make better decisions about which companies to join, which projects to take on, and which battles to fight.

The Learning Investment Pays Exponentially

Here’s the beautiful part: whilst everyone else is constantly relearning new frameworks, foundational knowledge compounds. Understanding team dynamics is just as valuable in 2025 as it was in 1985. Systems thinking principles apply regardless of whether you’re building web apps or AI systems.

Spend 40 hours reading Peopleware, The Mythical Man-Month, and learning about constraints theory, and you’ll use that knowledge for decades. Compare that to spending 40 hours learning the latest JavaScript framework that might be obsolete in two years.

The ROI on foundational knowledge is massive, but almost no one invests in it.

The Joy of True Mastery

There’s something else most developers miss: the intrinsic satisfaction of developing real mastery. Pink (2009) identified mastery as one of the core human motivators—the deep pleasure that comes from getting genuinely better at something meaningful.

Learning React hooks gives you a brief dopamine hit, but it’s shallow satisfaction. You’re not mastering anything fundamental—you’re just memorising another API that will change next year. There’s no lasting sense of growth or understanding.

But learning to think systematically about complex problems? Understanding how teams and organisations actually function? Grasping the deep principles behind why some software succeeds and others fail? That’s true mastery. It changes how you see everything.

You’ll find yourself analysing problems differently, spotting patterns everywhere, making connections between seemingly unrelated domains. The knowledge becomes part of how you think, not just what you know. This kind of learning is intrinsically rewarding in a way that framework tutorials never are.

How to Build This Advantage

Start with the classics:

  • The Mythical Man-Month – Brooks (1995)
  • Peopleware – DeMarco & Lister (2013)
  • The Design of Everyday Things – Norman (2013)
  • Notes on the Synthesis of Form – Alexander (1964)
  • The Goal – Goldratt & Cox (2004)
  • The Effective Executive – Drucker (2007)

Apply immediately:

Don’t just read—look for these patterns in your current work. Practise diagnosing organisational problems, identifying constraints, predicting project outcomes.

Share your insights:

This isn’t about positioning yourself or impressing managers—it’s about thinking aloud, finding likeminded peers, and building mental muscle memory. Writing and teaching helps to articulate fuzzy understanding into clear principles, which deepens your grasp of the material.

Write to clarify your own thinking. When you read about Conway’s Law, don’t just nod along—write about how you’ve seen it play out in your own teams. Trying to explain why your microservices architecture mirrors your organisational structure forces you to really understand the principle. The act of writing reveals gaps in your understanding and solidifies genuine insights.

Teach to expose what you don’t know. Explaining systems thinking to a colleague immediately shows you which parts you actually understand versus which parts you’ve just memorised. Teaching helps to develop intuitive explanations, real-world examples, and practical applications. You’ll often discover you understand concepts less well than you thought.

Build pattern recognition through articulation. Each time you write about a problem through the lens of Peopleware or analyse a workflow using Theory of Constraints, you’re training your brain to automatically apply these frameworks. Writing about the patterns makes them become more like second nature—mental muscle memory that kicks in when you encounter similar situations.

Create your own case studies. Document your experiences applying these principles. “How I used Goldratt’s Theory of Constraints to diagnose our deployment bottleneck” isn’t just content for others—it’s also cognitive practice. You’re building a library of patterns that your brain can reference automatically.

Think through problems publicly. Whether it’s a blog post, internal wiki, or even just detailed notes, working through organisational problems using foundational frameworks trains your mind to see systems, constraints, and human factors automatically. The more you practise applying these lenses, the more natural they become.

The goal is developing intuitive expertise—reaching the point where you automatically think about team dynamics when planning projects, or instinctively spot organisational dysfunction. This cognitive muscle memory is what separates developers who’ve read the books from those who’ve internalised the principles.

Connect the dots:

Use this knowledge to explain why projects succeed or fail. Make predictions. Build ability and credibility as someone who understands the bigger picture.

The Secret Is Out

The tragedy of developer education is that we’re taught to optimise for looking productive whilst systematically avoiding the knowledge that would make us actually productive. Organisations reward visible coding whilst discouraging the learning that would prevent project failures.

But this creates opportunity. Whilst everyone else chases the same technical skills, you can build knowledge that’s both more valuable and more durable.

The secret career advantage isn’t learning the latest framework—it’s understanding the timeless principles that determine whether software projects succeed or fail.

Most developers will never figure this out. But now you know.

Ready to build your secret advantage? Pick one foundational book, or even just a precis or summary, and start reading today. Your future self will thank you.

Further Reading

Ackoff, R. L. (1999). Ackoff’s best: His classic writings on management. John Wiley & Sons.

Alexander, C. (1964). Notes on the synthesis of form. Harvard University Press.

Brooks, F. P. (1995). The mythical man-month: Essays on software engineering (Anniversary ed.). Addison-Wesley Professional.

Conway, M. E. (1968). How do committees invent? Datamation, 14(4), 28-31.

DeMarco, T., & Lister, T. (2013). Peopleware: Productive projects and teams (3rd ed.). Addison-Wesley Professional.

Deming, W. E. (2000). Out of the crisis. MIT Press. (Original work published 1986)

Deming, W. E. (2000). Out of the crisis. MIT Press. (Original work published 1986)

Drucker, P. F. (2007). The effective executive: The definitive guide to getting the right things done. Butterworth-Heinemann. (Original work published 1967)

Goldratt, E. M., & Cox, J. (2004). The goal: A process of ongoing improvement (3rd rev. ed.). North River Press.

Marshall, R. W. (2021). Quintessence: An acme for software development organisations. Leanpub.

Norman, D. A. (2013). The design of everyday things (Revised and expanded ed.). Basic Books.

Pink, D. H. (2009). Drive: The surprising truth about what motivates us. Riverhead Books.

Seddon, J. (2008). Systems thinking in the public sector: The failure of the reform regime… and a manifesto for a better way. Triarchy Press.

Senge, P. M. (2006). The fifth discipline: The art and practice of the learning organisation (Revised ed.). Random House Business Books.

Tribus, M. (1992). The germ theory of management. SPC Press.

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:

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.

The Catch-22 of Productivity

September 26, 2023
Article, Business, Culture change, Deming, Drucker, Familiar, Giants, Organisational effectiveness, Organisational Therapy, Quintessence
Leave a comment

The Catch-22 of Productivity

What Fuels Top-Performing Software Companies?

The secret sauce of top-performing software companies often lies in their willingness to explore and implement ideas that fall outside the mainstream. Unlike many companies that stick to orthodoxy and status quo practices, these high-performers embrace the works of thinkers like Deming, Ackoff, Buckminster Fuller, Goldratt, Drucker, Seddon, and Trybus. They find value in methods and theories that many businesses either don’t know about or choose to ignore. This approach fosters a culture of continuous improvement and innovative problem-solving, setting them apart from their competitors.

Why Aren’t These Ideas More Widely Adopted?

There’s a paradox here: The ideas from these thought leaders are available, and their effectiveness has been demonstrated, yet few companies make the leap to implement them. This is usually not due to a lack of resources or information but stems from organisational inertia compounded by ignorance. Companies often feel safer sticking to conventional methods, even when evidence suggests that non-mainstream ideas could lead to significant improvements. This risk-averse mentality can create a barrier to adopting transformative approaches.

How Do Beliefs Impact Productivity?

The collective mindset or shared beliefs within an organisation can serve as either a catalyst or an obstacle to productivity. In high-performing software companies, you’ll often find a culture that not only welcomes but also thrives on unconventional wisdom. This creates a fertile ground for out-of-the-box methods to take root and flourish, driving the company forward in ways that more conventional organisations can’t easily replicate. If you’re curious, my recent book “Quintessence” catalogues and maps over seventy of the unorthodox memes of these top-performing companies.

Can We Simply Adopt Another Company’s Methods?

Transplanting methods from one company to another might seem like a straightforward way to boost productivity. However, those methods were developed within a unique ecosystem, shaped by specific challenges, goals, and culture. Attempting to graft them onto an organisation with differing assumptions and beliefs leads to misalignment, cognitive dissonance, resistance from team members, and even failure of the adopted methods to deliver the expected benefits. “Agile” is a classic example in this regard.

Has Benchmarking Any Value Here?

Many companies rely on industry-standard metrics to gauge their performance, but this approach has its limitations, particularly when comparing against top-performers who use unconventional approaches and thus metrics. These high-performers often evaluate success based on measures specifically tailored to their methods and organisational beliefs. This makes traditional benchmarking ineffective and even misleading when trying to measure up to these high-performing companies.

How Do You Close the Productivity Gap?

If you’re looking to close the productivity gap, tweaking existing methods won’t be sufficient. What’s required is a fundamental shift in organisational beliefs and assumptions that pave the way for consideration and implementation of radical, unorthodox ideas. Companies that are willing to examine their own culture critically, and to challenge the industry status quo, stand a much better chance of making significant strides in productivity.

What’s the Cost of Inaction?

Ignoring the widening gap between your company and high-performers comes at a steep price. As these leading companies continue to innovate and improve, companies that stick to conventional methods risk stagnation. In a worst-case scenario, they become increasingly irrelevant in their industry, losing out on both market share and talent to more forward-thinking competitors.

Drucker On The Collective Memeplex

June 6, 2023
Alien tech, Article, Drucker, Management, Memeology, Organisational effectiveness, Organisational Therapy, Quintessence
Leave a comment

Drucker On The Collective Memeplex

Peter Drucker, one of the most influential management thinkers of the 20th century, had a lot to say about collective assumptions and beliefs in business. In his opinion, these elements are often deeply foundational to an organisation’s culture, influencing its strategy, operations and performance.

Drucker argued that the assumptions and beliefs shaping a business’s actions aren’t always explicit. They’re often unconscious, becoming part of the organisation’s culture. He referred to these implicit beliefs as the “theory of the business”. According to him, every organisation, whether it knows it or not, operates on such a theory.

For Drucker, this theory was essentially a set of assumptions about what a company gets paid for. It’s about understanding the reality of the business, its markets, its customers, its core competencies, and its societal role. These assumptions guide behaviour, decisions, and the direction of the organisation. They set boundaries and establish guidelines within which decisions are made and actions are taken.

However, Drucker warned of the dangers of clinging too tightly to these assumptions. He believed that businesses get into trouble when their environments shift but their theories of the business don’t. This, he argued, is why innovation and ongoing analysis are critical. Companies must continually question their assumptions, keeping them in line with changing realities.

He also believed that it’s important for these collective assumptions and beliefs to be shared across the organisation. If employees don’t understand or don’t buy into these beliefs, there’s likely to be confusion, inefficiency, and a lack of coordination. This can result in subpar performance.

In sum, for Drucker, collective assumptions and beliefs play a crucial role in shaping an organisation’s actions and performance. However, businesses must also be ready to challenge and adapt these assumptions as conditions change, ensuring that their theory of the business remains relevant and effective.