New Hire Knowledge Ramp (Onboarding)

New Hire Knowledge Ramp (Onboarding)

1. 01

   Map the role's first 30 days to five recurring client questions before the hire starts

   Pull the five questions the delivery team answers most often in Slack and email, then confirm each has a written answer in the knowledge base. If any answer is missing, that gap becomes the hire's first documentation task.

2. 02

   Assign a named knowledge buddy separate from the reporting manager

   The buddy owns answer quality for the first two weeks and reviews every question the new hire routes to the team. Keep the buddy on a different account than the manager so the hire learns cross-client context.

3. 03

   Run a 45-minute search drill on live client questions, not sample data

   Have the hire answer three real questions using only the knowledge base and connected search, then log every dead end. Dead ends found in week one are cheaper to fix than dead ends found in month three.

4. 04

   Convert every dead end into a tagged entry within 48 hours

   The hire writes the entry, the buddy edits it, and the entry gets a topic tag plus an owner. Tools like Slab use topic structures and unified search across Slack, Google, and Asana to make these entries findable later.

5. 05

   Set a 14-day checkpoint against three measurable ramp signals

   Track time to first independent client deliverable, number of questions escalated to the buddy, and count of entries authored. A hire who has authored three entries by day 14 typically stops escalating routine questions by day 30.

6. 06

   Hand the hire ownership of one recurring internal answer by day 30

   Pick a question the team answers weekly and make the hire the named owner of its entry. Ownership converts passive reading into maintenance behavior, which is the habit that keeps a knowledge base alive after the hire is no longer new.