From Friction to Diagnosis
How to move from identifying friction to diagnosing its root causes.
The Core Argument
Identifying friction is not enough. We must diagnose its root causes. Diagnosis is what enables us to design effective solutions.
We have seen how friction manifests in many forms — organisational, decision, knowledge, coordination, and execution. We have also seen how it translates into real costs.
But identifying friction is only the first step. To solve it, we must understand its root causes. We must move from symptoms to diagnosis.
Diagnosis is the bridge between problem and solution.
The Diagnostic Process
A structured approach to diagnosis.
1. Observe
Observe the friction. What is happening? Where is it happening? Who is affected? What are the patterns?
2. Investigate
Investigate the causes. What is creating the friction? What structures, processes, behaviours, or beliefs are involved?
3. Analyse
Analyse the information. What are the patterns? What are the relationships? What are the root causes?
4. Synthesise
Synthesise the findings. What is the diagnosis? What are the key insights? What are the implications?
5. Validate
Validate the diagnosis. Does it explain the friction? Does it point to a solution? Is it credible?
The Acacia perspective:
Diagnosis is not a one-time event. It is an iterative process. As we learn more, we refine our diagnosis. This is how we build understanding over time.
The Diagnostic Mindset
The attitudes and habits of effective diagnosis.
Curiosity
Approach friction with curiosity, not judgment. Ask "Why is this happening?" rather than "Who is to blame?"
Humility
Recognise that you may not know the answer. Be open to being wrong. Be willing to learn.
Systems thinking
See the bigger picture. Understand how different elements interact. Look for patterns and relationships.
Patience
Diagnosis takes time. Do not rush to conclusions. Let the evidence guide you.
Key insight:
The diagnostic mindset is not just about solving problems. It is about building a culture of learning. When we diagnose well, we learn. And when we learn, we improve.
The Role of ContextOS
How ContextOS supports diagnosis.
Structure
ContextOS provides a structured way to understand situations. This structure supports diagnosis.
Documentation
ContextOS documents decisions and the context in which they were made. This creates a record that can be analysed for diagnosis.
Analysis
ContextOS provides tools for analysis — helping you identify patterns, relationships, and root causes.
Learning
ContextOS enables learning by capturing what happened and why. This supports ongoing diagnosis and improvement.
The Acacia perspective:
ContextOS is designed to support diagnosis. It provides the structure, documentation, analysis, and learning that diagnosis requires.
Reading path: