Your Team Is Not the Problem. Your Design Is.
Founders rarely say it out loud.
But many think it.
“Why do my people keep making the same mistakes?”
The sales team enters data incorrectly.Managers forget approvals.Operations miss steps.Onboarding feels chaotic.Deadlines slip in predictable ways.
The instinct is almost universal:
We need better people.We need more training.We need more accountability.
But human factors research tells a different story.
Repeated mistakes are rarely a competence problem.
They are usually a design signal.
And if you ignore the signal, you will keep replacing people instead of fixing the system.
The Shift From Blame to Design
For decades, organizational failures were attributed to “human error.”
But modern research has increasingly moved away from blaming individuals and toward examining system design.
Two major academic streams are important here:
Human error research in safety science
Don Norman’s work on design, visibility, and feedback
Let’s unpack both.
Human Error Is Often a Design Failure
In safety science, researchers like James Reason demonstrated that repeated errors are typically symptoms of poorly designed systems rather than individual incompetence.
If you are new to this area, start with:
Reason, J. (1990). Human Error
Overview of human error theory: https://www.sciencedirect.com/topics/psychology/human-error
The Swiss Cheese Model explanation: https://www.psychologytoday.com/us/blog/the-science-behind-behavior/202012/the-swiss-cheese-model-how-accidents-happen
The core insight is simple:
When the same error happens more than once, it is rarely random.
It is structural.
If three different employees mis enter the same field in your CRM, that is not three bad hires.
That is one flawed design.
Norman’s Design Principles Apply Inside Companies
Most founders are familiar with UX in customer facing products.
Fewer apply UX principles internally.
Don Norman’s foundational work in The Design of Everyday Things explains why people make predictable mistakes when systems are poorly designed.
A summary of his principles can be found here:
https://jnd.org/books/the-design-of-everyday-things/
Norman’s core design principles overview: https://www.interaction-design.org/literature/topics/don-norman
Four principles are especially relevant to founders:
1. Visibility
Important information should be visible.
If managers routinely miss approvals, ask:
Are pending approvals visible in one clear place?Or buried in email threads and Slack messages?
If something is invisible, it will be forgotten.
Not because people are careless.Because humans are limited.
2. Mapping
The relationship between action and outcome should be intuitive.
If sales reps keep entering data incorrectly, ask:
Does the CRM field layout match how they actually think about deals?
Or does it force them into categories that feel unnatural?
Poor mapping increases error.
3. Feedback
Systems must clearly show the result of an action.
If onboarding feels chaotic, ask:
Do new hires receive immediate confirmation that tasks are complete?
Or are they left guessing whether they are progressing correctly?
Without feedback, people improvise.
Improvisation creates inconsistency.
4. Constraints
Good systems prevent bad actions.
If finance errors occur repeatedly, ask:
Does the system allow incorrect entries?
Or does it constrain them?
Well designed systems make errors hard to commit.
Poor systems make errors easy.
Founder Translation: Where This Shows Up in Growing Companies
Let’s translate this directly to scaling founder led companies.
If Sales Reps Keep Mis Entering Data
It may not be a discipline problem.
It may be:
Too many required fields.
Poor field naming.
Inconsistent stage definitions.
No visible data validation.
Incentives that reward speed over accuracy.
Before retraining the rep, audit the interface.
If Managers Miss Approvals
It may not be a leadership gap.
It may be:
No centralized approval dashboard.
Notifications lost in Slack noise.
No deadline visibility.
No escalation path.
Before coaching time management, redesign the workflow.
If Onboarding Feels Chaotic
It may not be weak HR.
It may be:
Unclear task sequence.
No structured checklist.
Implicit tribal knowledge.
No feedback loop.
No visible milestones.
Chaos is often the absence of structured visibility.
Why Employees Keep Making Mistakes
Founders often search:
“Why do employees keep making mistakes?”
The more useful question is:
Why does our system make mistakes easy?
Research in cognitive psychology consistently shows that humans are highly sensitive to environment design.
See:
Cognitive load theory overview: https://www.sciencedirect.com/topics/psychology/cognitive-load-theory
Fundamental attribution error: https://www.simplypsychology.org/fundamental-attribution.html
We tend to over attribute errors to personality and under attribute them to structure.
That bias costs founders money.
A Simple Diagnostic Framework for Founders
If you want to fix broken processes, use this four step structure.
Step 1: Audit Recurring Mistakes
List errors that have occurred at least twice.
Not dramatic one offs.
Patterns.
Examples:
Wrong pricing entered.
Missed invoice approvals.
Delayed client onboarding.
Inconsistent proposal formatting.
Recurring errors are system signals.
Step 2: Map the Task Using a Simple HTA
HTA stands for Hierarchical Task Analysis.
It is a human factors method used to break down tasks into smaller steps.
If you are unfamiliar, here is an introduction:
You do not need academic rigor.
Simply map:
GoalSub tasksSequenceDecision points
Write out each step in the process.
Most founders are shocked by what they discover.
Gaps.Ambiguity.Hidden dependencies.
Step 3: Identify Where Visibility or Feedback Is Weak
Ask for each step:
Is the next action obvious?Is completion clearly confirmed?Is ownership visible?Is error detectable immediately?
If not, redesign before retraining.
Step 4: Redesign Before Retraining
Training addresses skill.
Redesign addresses structure.
Redesign examples:
Simplify CRM fields.
Add approval dashboards.
Introduce checklists.
Reduce tool switching.
Add automated validation.
Create visible task boards.
Only after redesign should you consider retraining.
Because often, retraining without redesign just creates frustration.
Systems Thinking for Founders
Systems thinking shifts leadership from:
“Who failed?”
to
“What in our design made this outcome likely?”
Peter Senge’s work in The Fifth Discipline is foundational here:
https://thesystemsthinker.com/the-fifth-discipline/
Scaling companies require founders to become architects of environments, not supervisors of individuals.
When you repeatedly intervene to fix the same mistake, that is not leadership.
That is a design flaw.
Improving Operational Discipline Without Blame
Operational discipline does not come from pressure.
It comes from clarity.
If you want improving operational discipline:
Make expectations visible.
Reduce cognitive friction.
Add constraints where risk is high.
Ensure feedback is immediate.
Design workflows that match real behavior.
When design improves, performance often follows without additional pressure.
Founder Reflection Questions
If you are wrestling with recurring errors inside your company, ask:
What mistake has happened three times this quarter?
Where are we relying on memory instead of structure?
Where is the next action unclear?
Where is feedback delayed?
What process works only when I personally oversee it?
Your team may not be the problem.
Your design may be.
And the founder’s role at scale is not to monitor people.
It is to engineer clarity.