Short answer
To capture employee knowledge across a large workforce, begin with one work question rather than a broad request for ideas. Invite the people closest to that work, ask for a specific example and its conditions, then have an accountable owner validate what can be reused. Scale the method in cohorts and retain the source, context and review condition for every practice you share.
Choose a work moment that needs learning
“What do employees know?” is too broad to produce useful evidence. Start with a repeatable work moment where a local practice could help another team: a shift handover, first-week onboarding, a customer return, a safety check or an exception process.
Write the capture question as a decision:
What should a new shift lead do when the incoming team inherits an unresolved return, and what conditions make that practice workable?
This makes the expected contribution concrete. It also tells people why they are being asked and helps the work owner decide what needs validation.
The UK government's Lessons Management guidance recommends a sequence of capture, analysis, validation, reporting and sharing. Its public-sector setting is different from a retail or service operation, but the structure is practical: a lesson is not ready to spread until context and evidence have been examined.
The scaled capture sheet
Use one short, accessible contribution form or conversation prompt for every cohort:
| Field | Prompt |
|---|---|
| Work moment | What task, handover or exception are you describing? |
| Situation | When and where did it happen, and what constraint mattered? |
| Practice | What did you or the team do? |
| Observed result | What changed in that situation? |
| Limits | When would this practice not apply? |
| Validation route | Which role can check the process before it is reused? |
Do not ask people to state a skill label and treat it as verified. Ask for a work example, the conditions around it and permission to follow up. A useful contribution can be incomplete; it is a starting point for validation, not a talent ranking or a universal instruction.
The interview and practice-card template provides the detailed prompts and review fields for an individual contribution. Use it to test the question before inviting the next cohort.
Scale with cohorts, not one giant launch
For thousands of people, divide the work by the question and the operating context. A warehouse handover and a store return should not use the same prompt merely because they share a country or business unit.
Start with one defined cohort and one work moment. Check whether people can access the invitation during paid work time, understand the prompt in the language used for that work and contribute without relying on a personal device. Review the first set with the process owner before expanding it.
The National Archives' guidance advises matching capture techniques to the situation and focusing capture where knowledge has wider application or may be lost. At scale, this is a valuable constraint: do not collect everything because a system can store it.
Fictional example: a return handover across stores
Fictional example: twelve stores describe how they handle damaged-return cases at closing time. Several associates mention taking a photo and logging the next owner, but one store has a local policy that prohibits the photo step. The operations owner reviews the accounts, confirms the shared need is an auditable next owner and creates an approved handover note that permits different evidence routes by store policy.
The result is not “the best store’s method.” It is a validated practice with a stated purpose, known exceptions and an owner. The next cohort can test whether the note is usable in its own setting and report what requires adaptation.
What to review before sharing a practice
Before turning an account into guidance, check:
- whether the example is specific enough to understand the work;
- whether the stated result is an observation rather than a claim of cause;
- whether a process or subject-matter owner has checked it;
- which populations, locations or conditions it does not cover;
- what local validation is needed before another team uses it;
- when the practice should be reviewed again.
Aim for contributions that can support a defined next step, rather than judging the campaign by the number of ideas collected. It also keeps operational learning separate from an individual performance assessment.
Where Lontra fits
Lontra can support a focused employee conversation around one work question and give managers an action-oriented brief rather than raw conversations. Use that context with the process owner to validate a practice before sharing it. Lontra does not automatically infer individual skills, rank people or publish a practice without human review. Explore the product.
Frequently asked questions
How do you capture employee knowledge without creating a giant survey?
Start with one work question, invite the roles closest to it, ask for specific examples, validate a small set with the work owner and share only approved practice.
Can a knowledge-capture programme identify the best employees?
No. It can collect examples of work in context. People should validate whether a practice is useful before it is reused.