eduKate SG

Three students in school uniforms work through open books at a classroom table, with textbooks and stationery nearby and study notes on the whiteboard behind them.

How to Categorise Problems | Symptoms, Causes, Scope, Constraints, Urgency and Solvability

A problem is a gap between a current state and a desired or required state.

A missed deadline, declining exam score, machine failure, traffic bottleneck, cash-flow shortage and scientific anomaly can all be called problems, but they differ in cause, scope, recurrence, urgency, uncertainty, constraints and solvability.

Quick answer: how should problems be categorised?

  • Symptom: what visible failure or gap is occurring?
  • Cause: what produces or sustains it?
  • Scope: local, system-wide, temporary, persistent?
  • Structure: well-defined, ambiguous, complex, wicked?
  • Constraints: what limits possible solutions?
  • Urgency: how quickly must action occur?
  • Impact: what happens if it remains unresolved?
  • Recurrence: one-off or repeated?
  • Ownership: who can act?
  • Solvability: preventable, manageable, reducible, reversible or currently unsolved?

This article applies the framework from How to Categorise Anything to problem diagnosis and problem-solving.

1. Define the desired state

Without a target or requirement, it is difficult to know whether a condition is actually a problem.

2. Separate symptom from problem

Low marks may be a symptom of weak knowledge, poor exam technique, language difficulty, attention loss or several causes together.

3. Separate problem from cause

A delayed shipment is a problem state; port congestion, missing documents or supplier failure may be causes.

4. Causes can be layered

Immediate causes, contributing factors and structural causes should not be collapsed into one label.

5. Scope determines containment

A local fault affects one component; a systemic problem crosses components or repeatedly reappears through shared structure.

6. One-off and recurring problems differ

A unique accident may need correction; repeated accidents may reveal a process or design problem.

7. Chronic and acute problems differ

Acute problems demand immediate response; chronic problems persist and often require structural change.

8. Well-defined problems have clear goals

Inputs, constraints and success criteria are known enough that candidate solutions can be tested directly.

9. Ill-defined problems contain ambiguity

The goal, constraints or even problem statement may be contested or incomplete.

10. Complex problems involve many interactions

Cause and effect may depend on feedback, delays, adaptation and network structure.

11. Wicked problems resist final definition

In some social and institutional problems, framing the problem changes which solutions appear reasonable.

12. Do not call every difficult problem wicked

Difficulty, complexity and wickedness are different properties.

13. Constraints define solution space

Time, money, law, safety, resources, ethics and technical limits can remove otherwise attractive options.

14. Hard constraints and preferences differ

A legal prohibition differs from a preference for lower cost. Keep mandatory and desirable conditions separate.

15. Urgency is not importance

An urgent task may be low impact; a major strategic problem may unfold slowly.

16. Impact is multidimensional

Cost, safety, learning, reputation, continuity and rights may be affected differently.

17. Problem severity needs criteria

Low, medium and critical are useful only when thresholds and consequences are explicit.

18. Ownership matters

A problem with no clear owner often persists because everyone can observe it while nobody can change the relevant system.

19. Authority and responsibility differ

The person responsible for the outcome may not have authority to change the root cause.

20. Evidence quality affects diagnosis

A problem statement based on anecdotes differs from one supported by repeated measurements.

21. Unknown cause is a valid state

Do not invent root causes merely to complete a problem template.

22. Multiple causes can interact

Problems may emerge only when several individually tolerable conditions combine.

23. Common-cause problems create clusters

Several visible failures may share one upstream cause and should not be solved independently.

24. Dependency problems propagate

A failure in one upstream system can create symptoms across many downstream systems.

25. Bottleneck problems limit throughput

Improving non-bottleneck stages may not improve total performance.

26. Coordination problems are relational

The components may each work correctly while handoffs, incentives or information flows fail.

27. Knowledge problems differ from execution problems

Not knowing what to do is different from knowing what to do but failing to execute it.

28. Capability problems differ from motivation problems

A person or organisation may lack skill, resources, incentive or permission. Each implies a different repair.

29. Reversible and irreversible problems differ

Some failures can be restored completely; others can only be mitigated after loss occurs.

30. Prevention and correction are different strategies

Preventive classification asks how to stop recurrence; corrective classification asks how to restore the present state.

31. Some problems are optimization problems

No state is strictly broken; the goal is to improve performance under competing objectives.

32. Trade-off problems have no single maximum

Speed, cost, quality, fairness and resilience may conflict. The problem includes choosing among values.

33. AI can classify problem reports

Models can route tickets or detect recurring themes, but automated categories should not be mistaken for proven root causes.

34. Similarity can cluster recurring problems

Repeated incidents with shared features can reveal a hidden systemic issue.

35. Problem categories drift

New technologies and processes create new failure modes; old categories can become catch-all buckets.

36. Resolution status is a separate facet

Open, investigating, mitigated, resolved, accepted and monitored describe workflow state rather than problem type.

37. A practical problem record

  • problem ID;
  • desired state;
  • observed symptoms;
  • scope;
  • suspected causes;
  • evidence;
  • constraints;
  • urgency;
  • impact;
  • recurrence;
  • owner;
  • authority;
  • solvability;
  • status;
  • related risks and processes;
  • taxonomy version.

38. Categorisation should change the response

If two problem categories lead to exactly the same diagnosis and action, the distinction may not be useful.

39. Reframe when the category stops helping

A useful problem classification is provisional: it should improve as evidence reveals the real system.

40. The deeper idea

Problem classification is not about naming failure elegantly. It is about identifying which kind of gap exists so the next action becomes more intelligent.

A good problem category is a route toward diagnosis and repair, not a label that ends the investigation.

Final answer

Categorise problems by symptoms, causes, scope, structure, constraints, urgency, impact, recurrence, ownership, evidence and solvability. Separate symptom from cause, urgent from important, local from systemic, and correction from prevention. Let the classification evolve as diagnosis improves.

Continue through the series

Explore the connected learning guides

Choose the question that brought you here. Open one useful guide, try a small task, and stop when you have what you need.

Take one question further

The same learning habit can travel across subjects, while each subject keeps its own methods. These routes help you notice a difficulty, understand one part of it, and return to something you can do.

A word is familiar, but using it is difficult.

Move from recognising a word to retrieving it in a new context. Understand vocabulary plateaus.

Try it without the guide: Choose one word you already know. Close the guide and use it in a new sentence. Explain why it fits; try another context tomorrow.

A piece of writing has ideas, but the reader loses the thread.

Make the order of events and the links between sentences clear. Explore composition writing.

Try it without the guide: Choose one short paragraph. Read the relevant explanation, close it, and revise the paragraph. Ask someone to tell you what happened and why.

The Mathematics seems familiar, but marks still disappear.

Find the first point where the working stops being reliable. Find Secondary 4 A-Math mark leakage.

Try it without the guide: For a Secondary 4 A-Math question you have attempted, locate the first uncertain line. Repair that step, then try a comparable question without the worked answer.

A Science fact is remembered, but the explanation is incomplete.

Connect the evidence to a scientific idea and the resulting change. Follow the Primary Science learning route.

Try it without the guide: Choose a familiar Primary Science example. Explain the evidence, the idea and the result without notes. Then change one condition and explain your prediction.

Two accounts of the world seem to disagree.

Check the question, source, date and evidence before combining claims. Explore the World Knowledge research library.

Try it without the guide: Take one claim. Find the source best placed to support it, note its date, and state what remains uncertain. Return to your original question.

There is plenty of help, but independence is hard to see.

Check what the learner can understand and do after support is removed. Understand how education works.

Try it without the guide: Choose one small task the child has practised. Agree on a calm, brief attempt without prompts. Use what happens to choose one next step, then stop.

For the structure behind these connections, read the eduKateSingapore runtime manifest and the eduKate ecosystem boot contract. The reader map describes public navigation; those manifests preserve the wider ownership and return rules.