A practical framework to help engineers and leaders understand the real problem before jumping into solutions.
Not every problem in engineering is solved by more effort, more process, or more pressure.
Sometimes a team is stuck because the goal is unclear.
Sometimes a person is struggling because they need more skill, context, or support.
Sometimes everyone knows what needs to happen, but nobody wants to say it out loud.
This diagnostic helps you pause and ask: are we dealing with a clarity problem, a competence problem, or a courage problem?
Use it as a reflection tool before giving feedback, escalating a risk, changing a process, evaluating performance, or proposing a solution.
When to use this diagnostic
Use this framework when:
- A delivery is blocked or delayed.
- A decision keeps being postponed.
- A teammate is struggling to meet expectations.
- A team keeps revisiting the same issue.
- A meeting ends without clear direction.
- A conversation feels avoided.
- A technical issue keeps returning.
- A stakeholder expectation feels misaligned.
- A solution is being proposed before the problem is understood.
How to use this resource
- Name the visible symptom.
- Check whether the issue is mainly clarity, competence, courage, or a combination.
- Choose a response that fits the real problem.
The three diagnostic lenses
- Clarity
A clarity problem exists when people do not fully understand:
- What matters.
- Why it matters.
- What success looks like.
- What decision needs to be made.
- What trade-offs are involved.
- Who owns what.
- What direction the team is taking.
Signals of a clarity problem
- People interpret the goal differently.
- The team is busy but not aligned.
- Priorities keep changing without explanation.
- Success is not clearly defined.
- Decisions are revisited repeatedly.
- People ask the same questions in different meetings.
- Work progresses, but confidence is low.
Useful questions
- What problem are we trying to solve?
- Why does this matter now?
- What does success look like?
- What are we optimizing for?
- What trade-off are we making?
- Who needs to be involved?
- What assumptions need to be made explicit?
- What is unclear but currently being treated as obvious?
Helpful response
- Create context.
- Align expectations.
- Summarize decisions.
- Define success.
- Clarify ownership.
- Make assumptions visible.
- Competence
A competence problem exists when people understand the direction but do not yet have the skill, knowledge, experience, context, or support needed to execute well.
Signals of a competence problem
- The person understands the goal but struggles with execution.
- Similar mistakes keep happening.
- Feedback is acknowledged but not translated into improvement.
- The task requires experience the person has not yet developed.
- The team lacks domain knowledge.
- Standards exist, but people do not know how to meet them.
- Someone is expected to own something without enough preparation.
Useful questions
- Does the person understand what good looks like?
- Have they seen examples?
- Do they have the technical knowledge needed?
- Do they understand the domain context?
- Have they received timely and specific feedback?
- Is training, coaching, pairing, or mentoring needed?
- Is the task appropriate for their current level of experience?
- What support would help them grow into this responsibility?
Helpful response
- Coach.
- Mentor.
- Pair.
- Teach.
- Give examples.
- Create learning opportunities.
- Provide specific feedback.
- Keep the standard, but support the growth needed to reach it.
- Courage
A courage problem exists when people know enough to act but avoid a necessary conversation, decision, disagreement, escalation, or responsibility.
Signals of a courage problem
- People discuss the issue privately but not in the right forum.
- Risks are known but not escalated.
- A decision is needed but repeatedly delayed.
- The team avoids disagreeing with a stakeholder.
- Feedback is softened so much that the message becomes unclear.
- Meetings stay polite but unresolved.
- People protect harmony at the cost of progress.
- The same tension keeps returning.
Useful questions
- What are we not saying out loud?
- What conversation are we avoiding?
- What decision needs to be made?
- What risk are we hoping will disappear?
- Who needs direct feedback?
- What is the cost of staying silent?
- What would respectful honesty sound like here?
- What needs to be named with care?
Helpful response
- Name the tension respectfully.
- Create safety.
- Say the true thing clearly.
- Escalate when needed.
- Make the decision visible.
- Address the real issue without attacking people.
Quick diagnostic
Clarity
You may notice: confusion, misalignment, repeated questions.
Avoid: pressure.
Try: context, direction, explicit expectations.
Competence
You may notice: struggle, repeated mistakes, lack of skill or context.
Avoid: blame.
Try: training, coaching, mentoring, feedback, examples, support.
Courage
You may notice: avoidance, silence, delayed decisions, hidden tension.
Avoid: more process only.
Try: respectful honesty, escalation, direct conversation.
Reflection prompts
Use these prompts before acting:
- What am I assuming about this problem?
- What evidence do I have?
- What is the visible symptom?
- What might be underneath it?
- Is this mostly clarity, competence, courage, or a combination?
- What response would make the situation better instead of just making me feel more in control?
- What is the smallest useful next step?
Simple usage example
Situation
Your team’s delivery speed is consistently below stakeholders’ expectations.
Surface diagnosis
“The team is bad at estimation.”
“The stakeholders have unrealistic expectations.”
Better diagnostic
Is it clarity?
Maybe the scope was not clear, the success criteria changed, or the priority was misunderstood.
Is it competence?
Maybe the team lacked domain knowledge, technical experience, or support with the architecture.
Is it courage?
Maybe people knew the timeline was unrealistic but avoided raising the risk early.
Better next step
Bring the pattern to the next retrospective or planning conversation. Start by clarifying the real cause together before changing the estimation process or adding more pressure.
Closing
The goal is to understand the situation well enough to respond with more care, precision, and impact. Better diagnosis creates better action.
And better action is one of the simplest ways to amplify problem-solving impact.