Quarterly review
Where we are, what we learned and the plan for the months ahead
Presented by {{author}}
Agenda
01
Where we are
A short look at results and what changed since the last review
02
What we learned
Three findings from customer interviews and usage data
03
The plan
Priorities, owners and milestones for the next two quarters
04
Questions
Open discussion and decisions we need from this group
Part two
The headline
So the first day matters more than any feature we ship this year.
Context
Over the last two quarters, customers have asked for the same thing in different words: fewer steps between an idea and a finished result.
This plan focuses the whole team on that single outcome, and sets aside the work that does not move it forward.
Priorities
Approach
Teams want to start from something that already works, then adjust it, rather than begin with a blank page.
Ship ready-made starting points for the five most common jobs, and make every one of them easy to change.
Overview
Faster setup
Two steps instead of five, with sensible defaults so most people never open settings.
Clearer results
Show the first result within a minute, and explain what happened in plain words.
Help in place
Answer the ten most common questions right where they come up.
Principles
Speed
Pages load in under a second on a typical connection.
Reliability
Fewer than one failed request in ten thousand.
Clarity
Every message says what happened and what to do next.
Access
Works with a keyboard, a screen reader and on small screens.
Results
38%
fewer support requests after the new setup flow
4.2×
more projects finished in the first week
12k
teams using the product every day
Retention
92%
Up from 71% a year ago, driven by the shorter setup and in-product help.
Options
Roadmap
Phase 1
Ship the core flow to a small group and measure time saved each week.
Phase 2
Invite every customer who asked for it and fix what they run into first.
Phase 3
Turn it on for everyone, with guides and a short launch video.
Phase 4
Review adoption after a month and plan the next round of changes.
How it works
01
Link the sources you already use. Nothing is copied until you choose what to import.
02
Choose one of the ready-made setups, or start from a blank workspace.
03
Invite people by email and decide who can view and who can edit.
In practice
Most of the work happens in short sessions between meetings, so every screen is designed to be picked up and finished in a few minutes.
The ground floor opens onto the courtyard, with space for forty people.
Before and after
Before: one long table and no natural light at the back.
After: smaller tables, a quiet corner and a skylight over the desks.
The best tools disappear into the work. People stop talking about the software and start talking about what they made with it.
Alex Morgan, Head of Design
The team
Sam Rivera
Product lead
Jordan Lee
Design
Priya Shah
Engineering
Chris Novak
Research and data
Under the hood
async function publish(deck) {
const slides = await render(deck);
const url = await upload(slides, {
visibility: 'team',
});
notify(deck.owner, `Published: ${url}`);
return url;
}Rendering and upload run in parallel, and the owner is notified as soon as the link is live.
Key takeaway
Teams that picked one workflow and tracked it closely saw results twice as fast as teams that rolled out everything at once.
Overview
Questions, ideas and feedback are all welcome
hello@studio.example · 555-0100