Skip to content

Rollout and Adoption

The difference between a Corporate Memory deployment people use daily and one that quietly stalls is rarely technical: it's the rollout. This guide describes the pattern that works: start small, seed the knowledge base before anyone judges it, put champions in every team, measure honestly, and feed what you learn back into curation.

Roll out in phases

Resist the org-wide launch. A phased rollout finds problems while they're cheap to fix and builds a base of advocates before skeptics arrive.

Phase 1: Pilot team (2 to 4 weeks). Pick one team of 5 to 15 people with real, recurring questions the knowledge base can answer: a support desk, a planning group, an engineering team with deep documentation. Invite them, watch how they use Copilot, and fix what they trip over.

Phase 2: Early departments. Extend to two or three departments whose document sources you've already connected and curated. Each department gets a champion (below) and a short kickoff.

Phase 3: Organization-wide. Open invitations broadly once the knowledge base reliably answers the pilot teams' questions and your curation rhythm is running.

At each phase, expand the knowledge base scope along with the audience: a department joining without its documents connected will ask questions Copilot can't answer, and first impressions don't get a second chance.

Seed the knowledge base before launch

Never launch into an empty or thin knowledge base. Before each phase's users arrive:

  • Connect the sources that answer their likely questions: the incoming department's procedures, specs, and reference material. See Knowledge Base Curation for scoping guidance.
  • Run the top-20 test. List the twenty questions the incoming group asks most often (ask their manager; they know). Put each one to Copilot yourself. If fewer than about fifteen get a good, well-cited answer, fix the gaps before inviting the group.
  • Clear the approval queue so newly synced documents are actually live at launch.

Recruit champions and hand out starter prompts

Adoption spreads person to person, not by announcement email.

  • One champion per team. A respected, curious team member (not necessarily a manager) who uses Copilot daily, demos it in team meetings, and collects the questions it fumbles.
  • Give every new user starter prompts. Copilot supports starter prompts on its landing page; make sure they reflect real questions for your organization ("What is our RMA process?", "Summarize our onboarding checklist for new hires"). A blank chat box is intimidating; three good example questions get people over it.
  • Show, don't describe. The single most effective adoption tool is a two-minute live demo of a real question getting a cited answer, run by a peer.

Measure adoption and act on it

Corporate Memory gives admins and management a Copilot Usage view: who is using Copilot, how often, and how usage trends over time. Use it as a rollout instrument, not a scoreboard:

  • Watch trend, not raw counts. Healthy adoption grows week over week within each newly launched group.
  • Look for silent teams. A team whose usage never starts, or starts and dies, has hit a problem: usually missing documents, an unconvinced manager, or nobody who's seen a demo. Go find out which; the fix is different for each.
  • Set a review cadence. A monthly fifteen-minute look at usage alongside your curation review keeps both honest.

The Vision Dashboard's Copilot adoption views can complement this with a broader picture of tool usage across the organization.

Close the feedback loop into curation

Rollout and curation are the same flywheel:

  1. Users ask questions.
  2. Champions collect the misses: wrong, vague, or unanswered questions.
  3. The curation owner fixes each miss: add a document, update a stale one, widen a source's scope.
  4. Champions tell the users their question now works.

Step 4 matters most. When people see their reported gap fixed within days, they keep reporting, and the knowledge base compounds. When reports vanish into a void, they stop, and so does improvement.

Point people at training resources

Keep the ask small; most users need ten minutes, not a course:

  • Getting Started: first sign-in and orientation
  • The how-to guides: task-by-task instructions for admins
  • Copilot: how answers, citations, and threads work
  • Your champions: the best training resource is a colleague one desk away

For admin onboarding, tailored training sessions, or rollout planning help, contact your WorkDone implementation contact or support.

Announce with a question, not a feature list

The launch message that works isn't "We've deployed an AI knowledge platform." It's "You can now ask 'What's the change-control process for released drawings?' and get the answer with the source document in ten seconds; here's the link."