Questions shaped by the role
Use the employee's responsibilities and team context to guide the conversation. A title alone rarely describes the whole job.
Product
Get the working knowledge out of someone's head.
A job description tells you what someone owns. Flamekeeper helps you ask how they do it, which decisions need context, and where a new owner will need more explanation.
One handover free during beta.
In practice
Give people a starting point they can answer.
Room for existing material
Add files, notes, and meeting transcripts to the capture process. Explain what each source means instead of handing over a folder of clues.
Follow the exceptions
Capture the judgment behind routine tasks: what changes the process, who makes the call, and which source to consult.
01Guided conversations
For product and engineering teams
Ask about the decisions behind the task list.
A task name is a useful starting point for an interview. The next questions need to establish what starts the work, which inputs matter, and how someone knows it is finished. Flamekeeper uses the role and the conversation so far to ask for more detail and organise the answers into the case knowledge.
Contributors can respond in the app or through an emailed link. A colleague may know about a dependency the manager has never seen; the employee can explain the exception behind it. Compare those perspectives while everyone is available, and ask for clarification where they describe the responsibility differently.
Make an answer useful to its reader
- Start with the task
- Explain how you prepare a translation release.
- Ask for the decision
- What makes a translated string ready to ship?
- Capture the detail
- Acceptance checks, reviewer, and unresolved languages
Illustrative conversation; contributors supply the facts.
02Source material & refinement
See how the knowledge is reviewed
Use the material you have, then explain what it leaves out.
Bring relevant files, working notes, or meeting transcripts into the conversation. Explain which responsibility each source supports and whether it reflects the current process. A source can preserve the original decision, but a new owner may still need to know which parts remain applicable.
Review the extracted knowledge before treating it as settled. Correct outdated details, add the missing explanation, and keep credentials or unrelated personal information out of the material you provide. The resulting inventory gives document drafting a specific account of the role, with fewer assumptions for the next reader to untangle.
Give each source a purpose
- Working notes
- Explain the steps used today
- Meeting transcript
- Retain the reasoning behind a decision
- Supporting file
- Provide the reference behind an instruction
Check what was extracted and correct the context.
Can the employee use documents they already have?
Yes. Existing files and notes can provide context for the handover. Add only relevant material, and leave passwords and unrelated personal information out.
Does it connect to all our tools automatically?
No. This workflow uses the context and source material you provide. It does not assume access to every system your company uses.
What if the answers are still vague?
Use the review and follow-up questions to request the missing detail. The employee or a colleague still needs to supply the knowledge.
Make the next transition easier
Get started for free