Skip to main content
A four-week plan that gets one team live properly and then repeats. It stitches together the Day one track, the announcement templates, and the handbooks. Copy it, put dates and owners on it, and cut anything that does not apply. The sequence matters more than the timing: pick one team, get it genuinely working, and use it as the reference implementation for everyone else.
The most common rollout failure is going company-wide in week one. You get volume before you have knowledge, an agent with nothing to retrieve, and a first impression you have to earn back.

​
Week 0: before the setup call

Owned by whoever is sponsoring the rollout.
Learn more about what to have ready

​
Week 1: get requests flowing

The goal for the week is a real request arriving and being worked in Ravenna. Nothing intelligent yet. By Friday, the responders should be working real tickets in Ravenna rather than in Slack threads. That habit is the actual dependency for everything after this.
Learn more about the Day one track

​
Week 2: make it smart

Learn more about writing agent rules and knowledge for AI

​
Week 3: announce and watch

Expect the first week of real volume to expose two or three things you got wrong. That is the point of running one team first.
Learn more about going live

​
Week 4: steady state and the next team

Learn more about reporting and briefs and closing knowledge gaps
For team two, start from that team’s department playbook rather than repeating Day one from scratch. The workspace, categories, and forms are different, and everything you learned about knowledge and agent rules carries over.

​
What good looks like at 90 days

Rough targets rather than promises, because the mix depends heavily on how much of your knowledge was written down before you started. If the agent’s resolution rate is flat, the answer is almost always knowledge, not configuration.

​
Next

Announcement templates

Copy, edit, post.

Playbooks

Pick the department you are launching next.
Last modified on September 17, 2026