Trunk-Based Thierry

@tdpauw
924 Followers
107 Following
1.3K Posts
most outspoken shy and introverted engineer 🙌 💪
former electromechanical engineer ⚙️
consulting CTO 🤵
founder https://thinkinglabs.io
I writehttps://thinkinglabs.io/
I codehttps://github.com/tdpauw
pronounsthey/them
Or, in my view, we are still in the bureaucratic hangover from the industrial days. #OpenSystemsTheory #SocioTechnical #OrgDesign

RE: https://mastodon.social/@tdpauw/116788624683537888

"To conclude, the tech industry spent decades trying to fix management processes, only to realise they were fighting a losing battle against the structural gravity of Conway’s Law and its implications on innovation and market leadership. Mediocrity is the default. Success is optional. Just saying …"

While pulling the research together, I discovered Henderson and Clark’s 1990 paper, which was a massive eye-opener.

They essentially laid the groundwork for how organisational structure freezes tacit knowledge.

If Conway's Law dictates what we build, Henderson and Clark prove it dictates what our firm is even capable of knowing.

It's a brutal look at why established firms are structurally blind to innovation.

The link to the paper is in the bibliography of the article 👆

Is Conway's Law just a hunch? Or is it a law? Conway didn't include a proof in 1968.

However, decades later, research from the automotive/aerospace industries and the software industry tells a different story.

If organisations are misaligned with the product architecture, they will have quality problems and decision latency.

Part 2 of "Beyond the Shades of Conway's Law" is out now:

Validation: The Research and Reality Check

#ConwaysLaw #SystemsThinking

https://thinkinglabs.io/articles/2026/06/20/beyond-shades-of-conways-law-validation.html

Beyond the Shades of Conway's Law - Validation: The Research & Reality Check

ThinkingLabs:: Thierry de Pauw
When we bring good work to the attention of others, we’re tending the community garden of ideas :)

Rage writing is the best writing?? You tell me.

> Testing slows you down, on purpose! It's methodical, meticulous. I thought that's what you wanted. The slowness is not a flaw! Software is a credence good, highly dependent on reputation. Skip or shortcut on testing enough times, and you'll piss away all the goodwill you have among your user base.

https://www.maaikebrinkhof.nl/testing-slow-yeah-thats-by-design-you-dipshit/

#testing #softwareengineering

Testing = slow? Yeah, that's by design, you dipshit.

Can you tell I'm mad? Here goes: Software testing is always done within constraints, the biggest ones usually being time and budget. Arbitrary deadlines usually put the most pressure on testing, and the allure of taking a shortcut by expediting testing has surely been observed by many of you, my

Maaike Brinkhof's blog

Organisational Dysfunction of the Day

Change agents of the status quo

Context: The organisation is struggling with its agile transformation. Teams are frustrated, delivery is slow, and the gap between the agile principles on the wall and the daily reality is hard to ignore. Leadership responds by bringing in agile coaches. Sometimes it is an external consultant. Sometimes it is a team lead who rebrands as a servant leader or agile enabler, sensing that the old role needs a new name to survive. The coaches run workshops, facilitate retros, introduce new ceremonies, and work hard to make things better. The teams appreciate the attention. Things improve slightly at the edges. The fundamental structure does not change. A year later, the same problems are present in slightly different forms. New coaches are brought in.

OST explains: Agile coaches are hired by management, which means the coaches who survive in the role are those comfortable operating within DP1. Those who challenge the structure too directly lose the engagement. Over time, the role selects for people skilled at making DP1 more bearable, not at replacing it. The coach becomes a buffer: absorbing frustration from the teams, translating it into something leadership can accept, and returning something that resembles a response. The energy that might have driven structural change is consumed in the process. For team leads and managers who sense that DP2 threatens their position, coaching offers a way to remain relevant, embracing the language of empowerment and self-management while preserving the hierarchy that sustains their career. When they cannot do it themselves, they hire consultants who can do it for them. The result in both cases is the same: a DP1 organisation with a DP2 vocabulary, which is laissez-faire. The coaches are not the villains here. They are the rational product of a system that needs the appearance of change more than it needs change itself. As Gerald Weinberg observed, organisations are perfectly designed to get the results they get.

#OpenSystemsTheory #SocioTechnical #OrgDesign #agile

Thoroughly loved what you shared @tdpauw. It introduced me to a few authors I was not familiar with (and will explore more) and felt very similar to the research @testobsessed and I did for our upcoming book.

Plus - I also am a huge Alexander fan😀

Very excited to see @tdpauw's post -- so good to see the various threads informing org design tracked down, with useful coverage of some of the important ideas and their history.

(Kind words for me, though we're all just figuring stuff out. Plenty of failures and missteps along the way.)

And thank you @joeltosi -- very kind.

And more exciting days ahead for all of us as "Signals and Levers" gets into hands and heads soon now (Sept 22, for those who are counting).
https://bookshop.org/p/books/signals-levers-systems-thinking-tools-to-unblock-software-delivery-elisabeth-hendrickson/bf2d9d17012f909f

RE: https://mastodon.social/@tdpauw/116709030423523606

"Yet, at the boundaries, the organisation must adapt and respond to changes in the environment. Therefore, it has to be open to environmental signals. As such, at its boundaries, it is an open system."

...

"While Emery & Trist define the external textures and Thompson explains the organisational structure to survive the environment and isolate the core work, Jay R. Galbraith articulates organisation design using a micro-level dimension: the flow of information."