Guru Onboarding: Build a Clear Path Through Team Knowledge
Give new teammates a short route through the knowledge they need, clear review owners, and a separate record of their current work.
Updated 5 min read
A useful Guru onboarding workflow gives a new teammate a short starting path, links each topic to an authoritative answer, and assigns someone to maintain it. Pair that reference knowledge with a record of what the person has tried, what remains unclear, and who should answer next.
Tools like fenbs keep current tasks and saved progress available to connected AI assistants, so each session can pick up the onboarding work without recreating its history. Start with one role rather than trying to organize every document in the company.
How do you build the first onboarding path?
- Choose one role and name the work the person should be able to do independently.
- List the questions they must answer before doing that work.
- Create a short start page linking to the relevant Guru Cards and source material.
- Assign a reviewer for each answer and test access with the intended audience.
- Pair the reading with a supervised task, then record the questions the task reveals.
For a hypothetical customer-support hire, the first path could cover finding an approved response, checking whether an exception needs approval, and handing an unresolved case to the correct person. The path succeeds when the hire can complete those actions, not when they have opened a large number of pages.
Keep company-wide introductions separate from role-specific instructions. A new teammate should not have to decide which of several general collections contains the next required answer. Put optional background after the essentials so curiosity does not turn into an accidental prerequisite.
How should you organize the knowledge in Guru?
Guru’s Collections guide (opens in a new tab) describes Collections as containers for knowledge organized by team or topic. Use that structure to give the onboarding material a clear home, with a short description of the audience and purpose.
Organize the starting path around actions: “Find the current answer,” “Request access,” and “Escalate a question.” A folder named for an internal department makes sense to an experienced employee but may mean little to someone arriving today. Use the words a new teammate would actually search for.
Guru Cards (opens in a new tab) provide short knowledge units that you can place in Collections and folders. Give each onboarding Card one clear purpose. Link to the maintained policy instead of creating a second policy copy inside the welcome material.
- Start here: the role’s first useful outcome and the order to follow.
- Required access: which systems are needed and who handles requests.
- Everyday guidance: the answers that support the first practice task.
- Help: the person or team responsible for unresolved questions.
- Next stage: what the teammate should attempt once the first task is checked.
Who should review an onboarding answer?
Assign accuracy to the person who owns the underlying process. The hiring manager may coordinate onboarding without being the right person to verify every IT or finance instruction. Name both the coordinator and the subject owner so a question does not disappear between them.
Guru’s verification documentation (opens in a new tab) explains designated verifiers and verification intervals. Set responsibilities deliberately, and inspect the settings your workspace uses. A badge is useful context, but your reviewer still needs to check whether the instruction matches the real process.
Review immediately after meaningful changes, such as a new approval route or a replaced internal tool. Also listen for repeated beginner questions: a technically correct answer may still be difficult to follow. Ask the reviewer to improve the confusing sentence rather than merely telling the next hire the missing detail aloud.
When a review creates work, keep that follow-up visible. In fenbs, a task can hold the correction plan while the approved source stays in Guru; saved handoffs explain how the next assistant can continue the follow-up.
How do you distinguish reading from readiness?
Use a small practice task with a visible result. A new support specialist might draft an answer to a fictional customer question using the approved guidance. Their reviewer can check the chosen source, the response, and whether the specialist recognizes the point where approval is required.
| Record | Useful example | What it tells the reviewer |
|---|---|---|
| Reading | Reviewed the escalation guide. | The source has been introduced. |
| Practice | Drafted a response to a sample exception request. | The person has applied the instruction. |
| Review | Correctly routed the exception for approval. | A specific judgment was checked. |
| Open question | Unclear who covers approvals during absences. | A knowledge gap still needs an owner. |
Do not turn this into a score for the person. The evidence helps you improve the path and decide what support comes next. If several hires miss the same approval condition, examine the instruction and exercise before assuming the readers are careless.
The steps belong in your ordinary agile workflow when the role involves project work. Keep the person’s current task separate from the reference page so completing a practice exercise does not accidentally change the general guidance.
What should an AI assistant know about the onboarding work?
Give the assistant the current goal, the sources the person is allowed to use, the work already checked, and the unresolved questions. Specify where a person must review the result. An assistant can help draft a practice response without becoming the authority on whether the teammate is ready for independent work.
For example: “The draft followed the standard procedure. The exception path remains untested. Ask the manager who covers approvals before writing the next exercise.” That is a useful starting point for another session. “Onboarding nearly done” hides the exact issue someone must resolve.
Keep the next onboarding step clear
Keep onboarding tasks, open questions, and Where we left off in fenbs. Ask a connected assistant to read that context before preparing the next exercise, then save what was reviewed and what still needs a person. The maintained reference material can stay in Guru.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account, free for one person with no credit card, and add a project for testing the onboarding path.
- Add the practice tasks and unresolved questions. Include selected Guru source links only where the intended readers should have access.
- Record the approved review requirements in Decisions and rules, including which results need a person’s approval.
- Connect a supported AI app from Integrations. Ask it to read the project context before helping, and save progress with the next step before stopping.
fenbs does not connect to Guru or import its Cards. It is not the right fit for delivering a formal course or issuing training credentials. Use it when the missing piece is a shared record of active work across people and assistants.
How do you improve the path after the first hire?
Ask the new teammate to identify one instruction they could follow and one that needed an explanation from a person. Review the second with its owner, revise the source, and try the task again. Remove obsolete links from the starting path so the next hire does not inherit a growing reading list.
Keep this review separate from building workflow automation or designing agentic workflows. The Guru SOP guide covers procedure upkeep, while the Guru Slack workflow covers conversation capture. Explore the team brain library for the shared context around those activities.