Initial observation
The volume of internal documentation and knowledge was growing faster than the team's ability to find it.
Loading…
Case study · Sector: Professional Services
The answer already existed — in a document, a conversation, or someone's experience. Even so, work stopped until the right person turned up. As the team grows, that dependency turns internal knowledge into interruptions, waiting, and repeated work.
A recognisable way of reaching clarity
Work kept getting interrupted by questions the organisation had already answered before. The answer could be in a document, a tool, or someone's experience — but retrieving it still depended on knowing where to look, or who to interrupt.
What relationships kept the problem in place?
Knowledge scattered across documents and tools
The same search repeated for every question
Dependence on specific people
The answer stuck waiting on someone's availability
Content growing without a retrieval structure
The cost of finding things grows with volume
The path from first impression to the real problem.
We didn't start by picking a solution. We started by testing whether the apparent problem was the right one.
Editorial reconstruction of the reasoning, based on the documented challenges, goals, and results. Not a literal transcript of the Discovery sessions.
Initial observation
The volume of internal documentation and knowledge was growing faster than the team's ability to find it.
First hypothesis
IncompleteA more efficient search engine over the existing documents could solve the problem.
Why it looked right
The most visible difficulty was not being able to quickly locate a document or answer that already existed.
What changed our reading
Recurring questions kept interrupting the same people.
The information existed, but it was fragmented across different sources and formats.
Finding a document didn't guarantee getting the right answer to the question that was actually asked.
Why we changed direction
Better search helped locate documents. On its own, it didn't close the gap between a question and an answer built from the right context.
New direction
We moved from indexing documents to retrieving relevant context before building any answer at all.
Deep-dive notes
What principle answered each pattern?
Principle 01
Principle 02
Principle 03
What changed in the way of working?
From
Knowledge that depended on asking someone
To
Knowledge accessible from the right context
Finding an answer meant asking someone
Finding an answer means searching
Knowledge that only lived in people's memory
Knowledge traceable back to its source
Every question repeats the same effort
Every answer reuses what already exists
What was underneath the symptom?
Symptom
Lack of information
Real problem
The distance between information and whoever needs it
Principle
Bring knowledge closer to the moment the question is asked
“Knowledge that's only useful when the right person happens to be available is still an operational dependency. The value shows up when the team can retrieve context without interrupting, once again, whoever already solved the problem before.”
Related idea
When the team wastes time looking for answers the company already hasThe answer already exists — in an old document, a past conversation, someone's experience. Work doesn't stop for lack of knowledge. It stops because that knowledge isn't where it's needed, when it's needed.Explore the reasoningNext case study
Sector: Construction & Technical ServicesWhen understanding the state of the operation means piecing together information from everywhereThe context changes. The method holds.