A SPECIALIZED OFFERING · IT & ENGINEERING LEADERS

Human System Architecture™

A systems-architecture analogy for leaders in IT and engineering organizations, used to examine recurring problems with communication, conflict, cooperation and leadership.

For leaders who understand systems, but keep meeting people problems

Your engineers can debug a complex technical system. Yet an apparently aligned meeting turns into four different interpretations, or the same argument returns every month.

Human System Architecture™ uses familiar architecture language to investigate those recurring leadership situations. It gives technical leaders another set of questions about beliefs, interpretations, habits, capabilities, attention and the working environment.

The approach grew in part from my work with technical audiences, including DSC Europe 2025 in Belgrade.

Four situations worth examining

The avoided conversation

A senior engineer repeatedly shuts down during cross-team meetings. Colleagues start working around the difficulty instead of addressing it. What makes the conversation hard to begin, and what might change its course?

The recurring conflict

Two experienced managers argue about the same responsibilities every month. The disagreement may involve interpersonal habits, but it may also be sustained by decision rights, competing targets, or information each side does not have.

Agreement that doesn't become coordination

A team agrees on priorities in the meeting. Different interpretations emerge once the work begins. Before arranging another alignment workshop, we might look at what was actually decided, who owns the trade-offs, and what each group has reason to optimize.

The load carried by one leader

A manager becomes the unofficial destination for every difficult conversation and unresolved conflict. We can examine the manager's habits, but also the organizational arrangements that keep making them the bottleneck.

The architecture analogy

The framework borrows familiar terms from computing and engineering. These give technical audiences a starting vocabulary for situations that otherwise attract vague labels such as “difficult person” or “poor communication.”

OS / Kernel: beliefs and early patterns

The OS stands for personality, values and beliefs that influence interpretation. The Kernel represents unconscious patterns shaped by earlier experience. They can lead two equally competent people to assign different meanings to the same event.

CPU: interpreting input

The CPU represents the parts of our mind that interpret incoming information and give meaning to events. A technical manager can use this image to ask how an observation became an interpretation before it turned into a response.

Database, experience and memory

People bring memories, emotional archives and past experiences into present situations. The same remark can be interpreted differently by two people with different histories. What experience might each person be drawing on?

Apps, learned skills and capabilities

Listening, negotiating, giving feedback and making decisions are learned skills. The question is whether the person can access and apply them in the situation at hand.

Algorithms, recurring patterns

We all develop thinking and behavioral routines. A particular remark may trigger an interpretation and a familiar reaction. Noticing the sequence gives us something to investigate and try changing.

RAM / Battery / Fan: attention, energy and regulation

RAM stands for attention and working memory. Battery stands for energy and motivation. Fan stands for emotional regulation. Together they invite questions about overload, depleted attention and the way a leader manages a rising emotional temperature.

How I use the framework

The analogy offers one way into an investigation. Depending on the situation, the work might involve:

  1. Describing what happened, separating observations from interpretations.
  2. Looking at the people involved, their relationships, the decisions at stake, and the organizational conditions surrounding them.
  3. Considering more than one explanation and checking it against what can actually be observed.
  4. Choosing a conversation, practice, decision, or organizational adjustment worth trying.
  5. Looking at what happened afterward and changing our explanation if the evidence points elsewhere.

The useful change may be a different conversation, a personal habit, a reporting arrangement, an incentive, a decision right or better information. The investigation tells us where to look.

I explored this approach with a technical audience at DSC Europe 2025 in Belgrade. The original essay, A DSC/AI guy and a donkey walk into a meeting…, shows where the analogy came from.

Where this can be used

Keynotes and leadership talks. An introduction to the architecture analogy for technical audiences, using concrete management situations.

Workshops and applied modules. Working through leadership and collaboration situations relevant to a specific team or organization, with the scope agreed beforehand.

One-to-one executive mentoring. A way to examine recurring patterns in the leader's decisions, relationships and environment as part of a broader mentoring engagement.

Where the analogy stops

People aren't software. The framework helps us ask better questions; it doesn't read minds.

In a keynote, workshop or mentoring engagement, we agree which situations to investigate and what participants should be able to take away.

A place to begin

What are you dealing with?

It may be a decision, an organizational problem, or a situation you cannot yet explain well. A few sentences are enough to start.

Discuss your situation