Stockertim Dictionary · Project management
Symptom
Also called symptoms (of a problem), presenting problem
In short
A visible effect of a problem, such as a complaint or a delay, that signals something is wrong without explaining why.
- Beginner
- Concept
- Checked
In detail
A symptom is what people notice: long queues, rising complaints, missed deadlines, staff overtime. It is real and often painful, but it is the result of a cause somewhere else in the system. A rise in complaints about late refunds is a symptom; a manual approval step that waits for a weekly meeting may be the cause.
Distinguishing symptoms from causes is one of the first jobs in business analysis. Treating symptoms, for example by adding staff to answer complaint calls, can relieve pressure for a while but leaves the cause in place, so the problem returns or moves elsewhere. Root cause techniques such as the five whys and fishbone diagrams are designed to trace symptoms back to their sources.
Symptoms are still useful. They are often the easiest things to measure, and a change that fixes the root cause should make them improve. Tracking a symptom before and after a change is therefore a practical way to test whether the cause has really been dealt with.
In practice
Problem statements in discovery work describe the symptoms observed with data, then list hypotheses about causes to be tested.
Watch out
- Several symptoms can share one cause; fixing them separately wastes effort.
- A request for a solution is often a symptom described in disguise.
Learn it properly
Official sources
- Using five whys to review a simple problem · NHS England (Quality, Service Improvement and Redesign tools)
- How the discovery phase works · GOV.UK Service Manual
Facts last checked on 3 November 2026.
Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.