Feedback on the work, not on a meeting slot

The work is walked through once, one decision is requested, and stakeholders answer on their own time.

A design file with three onboarding screens and the designer explaining one of them
Onboarding v3: the interests stepMei, 0:11, watched by 4

Videos product teams send instead of meetings

The reviews and updates that used to fill Tuesday afternoons.

  1. 3 min
    Design review

    Walk through the flow and ask for one decision. Comments land on the frame.

  2. 5 min
    Spec walkthrough

    Talk engineering through the edge cases before they start.

  3. 4 min
    Weekly product update

    The metric, what moved it, what is next.

  4. 6 min
    Research readout

    Clips and patterns from customer calls, without the 60 minute meeting.

  5. 2 min
    Stakeholder sign-off

    The final version, and the question that needs a yes.

Why it works for product and design

Feedback with a timestamp

Comments point at the moment, so “this button” means the same button to everyone.

Decisions without the calendar

A specific question at the end brings answers that can be read when they arrive.

Knowing who has actually seen it

Before the launch meeting, check that every stakeholder watched to the end.

Product and design: common questions

Something missing? Questions sent through the contact page get an answer within a working day.

Does it work with design tools?

Yes. Any app on the screen can be recorded. Links also preview in the tools where you share, like Slack, Notion and Linear.

Can stakeholders comment without an account?

Yes. They add their name once and comment on the moment.

How long should a design review video be?

Under five minutes. One flow, one question. Long reviews get skimmed.

The next design review can be a video.

The first one needs no account and no install, and the link is ready when recording stops.