The Human Element Is the Starting Point
The systems that fail aren't usually broken by their architecture. They break where the design forgot who would be running them, and what state that person would be in.
Before computers were machines, they were people.
Chapter 13 of The Resonance Core Framework™ opens with the human computers at NACA, the agency before NASA: rows of people turning equations into flight paths by hand. When the stored-program machines arrived, the systems still didn't run themselves. The failures that came weren't about the hardware. They came from systems that weren't designed around the humans who had to operate, read and repair them.
One line from that chapter has stayed with me:
"Whenever a system is treated as self-sufficient, it fails."
I've spent more than 20 years in design, development, architecture, and product management. That pattern holds everywhere I've been.
What We Call "User Error"
A lot of what gets logged as user error is a design decision that forgot who the user would be, and what state they'd be in, at the moment it mattered.
Not their skill level. Not their training. Their state. Were they three hours into a stressful shift? Were they fielding two conversations at once? Was the interface demanding precision at the exact moment their attention was split?
Systems that perform well in controlled conditions, tested by rested people in a quiet room, often reveal their real failure modes when someone is tired, under pressure, or uncertain. The system didn't account for the person. And the person paid for it.
The Human Element
In The Resonance Core Framework™, The Human Element is the shared layer of emotion, sensation and intuition that shapes how people respond before they think or speak.
It's the part of every interaction that happens before language. The slight tightening in the room when a decision gets made that no one agrees with but no one says out loud. The signal someone gives with their posture before they say a word. The moment a team's energy shifts when trust breaks, even briefly.
Most system design treats these signals as noise, or as variables too soft to measure. The Resonance Core Framework™ treats them as the layer everything else runs on. When that layer is ignored in design, the system becomes brittle where it encounters real humans at real moments.
Three Questions I Now Ask
My view from 20+ years of building: the systems that last are the ones designed with The Human Element as a given, not a footnote.
Three questions I now bring to any system, whether it's software, a process or a team:
Who runs this, and what state are they in when they do? Not the trained operator at peak performance. The real person on a regular Tuesday, with incomplete information and six other things on their mind.
Where does it hand control back to a person? What are the moments where the system needs a human to decide, confirm or correct? Are those handoffs clear? Do they create pressure, or do they give the person solid ground?
What tells the person using it that they're on solid ground? Confidence spreads. So does uncertainty. A system that leaves its users unsure whether they're doing it right creates exactly the kind of tension that degrades performance over time.
Why It Spreads
This is where The Human Element gets more precise than most frameworks allow.
When one person in a team or system carries unaddressed tension, it doesn't stay with them. It spreads. Not through memos or meetings, but through the same signals that predate language: tone, timing, posture, attention. The tightening one person feels can create tightening in the next person they interact with.
The reverse is also true. Steadiness spreads. Calm is not passive. It is something others can actually feel. A person who is regulated in their own state, who has done the work of reading and managing their Somatic and Emotional Cues in real time, becomes a different kind of presence in a system. Not more powerful. More settled.
This is what psychology calls co-regulation: the way human nervous systems respond to each other's signals. It shows up in every kind of team setting, from operating rooms to leadership teams to customer support floors. The quality of presence one person brings into a system changes what the system produces.
The Place to Start
You can redesign the interface, the workflow, the org chart. And sometimes those things are exactly what needs to change.
But the systems I've seen fail most reliably aren't broken by their architecture. They break at the places where the design assumed a self-sufficient machine and found a person instead: carrying uncertainty, reading the room, managing their state, trying to hold it together well enough to make the right call.
That's where to start. Not with the process that failed, but with the person running it.
The Human Element isn't the soft part of a system. It's the starting point.
Going Deeper
This post expands on ideas from Season 2, Episode 1 of The Resonant Identity: The Outward Reach: The Human Element and Somatic Discipline. The episode includes a 7-day practice you can start this week.
The Resonance Core Framework™ is a practical system for making change that holds, built on alignment rather than force. The book is targeted for Q1 2027, and you'll hear about it at theresonantidentity.com first.
Explore related ideas: Behavioral Gravity · The DII Protocol
Structured Summary
Terence Waters draws on 20+ years in design, development, architecture, and product management to argue that systems fail where they treat themselves as self-sufficient. The Human Element, a concept from The Resonance Core Framework™, is the shared layer of emotion, sensation, and intuition that shapes how people respond before they think or speak. Three questions every builder should ask of any system: who runs this, where does control return to a person, and what tells them they are on solid ground.
Key Insights
- Connects Resonance Core Framework to practical identity-aligned growth.
- Connects The Human Element to practical identity-aligned growth.
- Connects Systems Design to practical identity-aligned growth.
FAQ
- What is the core idea of "The Human Element Is the Starting Point"?
- Terence Waters draws on 20+ years in design, development, architecture, and product management to argue that systems fail where they treat themselves as self-sufficient. The Human Element, a concept from The Resonance Core Framework™, is the shared layer of emotion, sensation, and intuition that shapes how people respond before they think or speak. Three questions every builder should ask of any system: who runs this, where does control return to a person, and what tells them they are on solid ground.
- Who is this post for?
- This post is written for creators, consultants, and growth-minded professionals seeking identity-aligned, practical insight.