Quarterly review

Shaping the next chapter

Where we are, what we learned and the plan for the months ahead

Presented by {{author}}

Agenda

What we will cover today

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

What we learned

The headline

Customers who finish setup in one day stay twice as long as everyone else

So the first day matters more than any feature we ship this year.

Context

Why this matters now

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

Four things we will focus on

  • Cut setup from five steps to two
  • Make the first result visible in under a minute
  • Answer support questions inside the product
  • Share progress with the whole team every week

Approach

From feedback to a plan

What we heard

Teams want to start from something that already works, then adjust it, rather than begin with a blank page.

What we will do

Ship ready-made starting points for the five most common jobs, and make every one of them easy to change.

Overview

Three ways we make it simpler

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

What good looks like

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

The numbers so far

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%

of new teams are still active after 90 days

Up from 71% a year ago, driven by the shorter setup and in-product help.

Options

Two ways to get there

Build it ourselves

  • Full control over the roadmap
  • Slower start, about two quarters
  • Needs two more engineers
  • Lower cost after year one

Partner with a vendor

  • Live within six weeks
  • Roadmap shared with other customers
  • No new hires needed
  • Licence cost grows with usage

Roadmap

From pilot to general release

Phase 1

Pilot with three teams

Ship the core flow to a small group and measure time saved each week.

Phase 2

Open beta

Invite every customer who asked for it and fix what they run into first.

Phase 3

General release

Turn it on for everyone, with guides and a short launch video.

Phase 4

Measure and refine

Review adoption after a month and plan the next round of changes.

How it works

Three steps to a first result

01

Connect your data

Link the sources you already use. Nothing is copied until you choose what to import.

02

Pick a starting point

Choose one of the ready-made setups, or start from a blank workspace.

03

Share with your team

Invite people by email and decide who can view and who can edit.

In practice

Built for how teams work

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.

A closer look at the new studio

The ground floor opens onto the courtyard, with space for forty people.

Before and after

The same room, six weeks apart

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

The people behind the project

Sam Rivera

Product lead

Jordan Lee

Design

Priya Shah

Engineering

Chris Novak

Research and data

Under the hood

Publishing a deck in one call

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

Start small, and measure from the first week

Teams that picked one workflow and tracked it closely saw results twice as fast as teams that rolled out everything at once.

Overview

A title with room for your own content

Thank you

Questions, ideas and feedback are all welcome

hello@studio.example · 555-0100

Daylight

By Slide Templates

Daylight

The default light template: near-white slides in bold Open Sans with near-black text, one clear blue accent, pale grey panels and hairline rules on a strict 80px frame, with no decoration. Written as a product team's quarterly review.

  • 47