Template90-Day Results Report
The first measured proof of value, comparing live departments against baseline, with adoption, governance and the case for the next departments.
#What this is for
Ninety days in, leadership needs to know whether this is working, in numbers. This report is the internal case study: what changed in the first live departments against the baseline captured before launch, how people are adopting, how governance held up, and what that means for the rest of the year. It is also the document that gets the next departments asking for Clones, so it is written to be read beyond the steering committee.
#When to use it
Assemble it in the final week of Month 3, after at least four weeks of post-launch data in Department 1. Present it at the Month 3 steering. A shortened version (sections 1, 3 and 7) becomes the company-wide results message from the sponsor.
#Who's involved
- Solutions Partner writes the narrative and presents.
- Business owners validate their department's numbers.
- InfoSec lead confirms the governance check.
- Champions supply quotes and stories.
- Executive sponsor signs off and shares the summary.
#How to fill it in
- Pull baseline and actuals for every metric on the Year-1 Success Metrics for live departments. Use the same definitions and sources as the baseline.
- State the measurement window and any changes that could affect the numbers (seasonality, staffing, process changes).
- Convert time measures to hours given back per week, and say what the team did with that time.
- Complete the governance check with InfoSec: audit log review, overrides, exceptions, risk register updates.
- Collect two or three short quotes from users and Champions.
- Write the executive summary last.
- Update the roadmap and record the decisions you need.
#The template
#1. Executive summary
| Field | Entry |
|---|
| Measurement window | Day 48 – Day 86 |
| Departments live | InfoSec, Customer Support |
| Clones live | 5 |
| Headline result | Support first-response time down 78% against baseline; 46 agent hours a week given back |
| Governance | Zero incidents above agreed severity; 1 promotion approved |
| Recommendation | Proceed with Finance (Day 95) and HR (Day 120); promote Support routing at Day 126 if evidence holds |
#2. What we set out to do
| Problem statement (from the register) | Department | Clone(s) | Success metric |
|---|
| Tickets wait half a day before anyone reads them | Support | Support Triage Clone | Median first-response time |
| Security questionnaires take a week each | InfoSec | Questionnaire Clone | Turnaround per questionnaire |
#3. Results against baseline
| Department | Metric | Baseline | Day 90 actual | Change | Year-1 target | Confidence |
|---|
| Support | Median first-response time | 9.5 hrs | 2.1 hrs | −78% | 3 hrs | High: same helpdesk report |
| Support | Agent hours on triage / week | 58 | 12 | −46 hrs | −40 hrs | Medium: time study sample |
| InfoSec | Questionnaire turnaround | 6 days | 1.5 days | −75% | 2 days | High |
| | | | | | |
Confidence scale: High = same system report as baseline · Medium = sampled or time-study based · Low = estimate, to be firmed up.
#4. Where the time went
| Department | Hours given back / week | What the team now does with it |
|---|
| Support | 46 | Proactive outreach to at-risk accounts; cleared backlog of complex cases |
#5. Adoption
| Department | Users in scope | Weekly active | Tasks completed | Avg Power Rating | Training complete | Champion active |
|---|
| | | | | | |
#6. Governance check
- InfoSec reviewed audit logs for the window (date: ____)
- Overrides reviewed and categorized
- Exceptions and incidents reviewed; none above agreed severity (or listed below)
- AI Risk Register updated
- All connections still match the approved Connections & Permissions Plan
| Item | Count | Note |
|---|
| Actions taken by Clones | | |
| Overrides | | |
| Override rate | | |
| Escalations | | |
| Incidents above agreed severity | | |
#7. Stories and quotes
"I used to start every shift sorting the queue. Now I start with the customers who need me." Support agent, Tier 2
| Story | Department | Owner | Use in comms? |
|---|
| | | Yes / No |
#8. What we learned
| Worked well | Did not work | Changing for the next departments |
|---|
| Champion-led pilot surfaced knowledge gaps fast | Baseline for hours was a guess in one team | Time study in week 1 of every rollout |
#9. Roadmap update and decisions
| Item | Current plan | Proposed change | Decision needed |
|---|
| Department 3 | Procurement | HR onboarding (higher score after diagnostic) | Yes |
#Good looks like
- Every number has a baseline, a source and a confidence rating. Leaders trust reports that show their uncertainty.
- Same definitions as the baseline. Changing the metric after launch undermines the whole report.
- Time saved is translated into what people did with it. "Hours given back" means nothing if nobody can say where they went.
- Governance results sit next to business results, not in a footnote.
- Includes what did not work. A report with no lessons reads like marketing.
- Common mistake: reporting usage (logins, messages) as results. Usage is adoption; results are the business metrics.
#How Clone helps
The Project Clone drafts the report from the Success Metrics Baseline, Adoption Dashboard and portal history, and computes the change columns. The GRC Clone prepares the governance check from audit logs and the risk register. The Enablement Clone collects Champion stories and turns the approved summary into a company-wide win message. The report is stored in the portal as the 90-Day Results Report deliverable.
#Sign-off
| Role | Name | Date | Decision |
|---|
| Executive sponsor | | | Accepted; roadmap decisions recorded |
| Business owner, Department 1 | | | Numbers validated |
| InfoSec lead | | | Governance check confirmed |
| Solutions Partner | | | Issued |