Miro · Product sense · Entry · 45 to 60 minutes

Should Miro solve presenting inside the board?

Miro is a visual collaboration platform where teams create and organize work together on shared online boards. Answer this product management case and get it graded line by line against a weighted rubric.

product sense
prioritization
user empathy
metric thinking
written communication

The situation

You are an associate PM on Miro's core creation experience. The Head of Product asks you for a recommendation on a growing pattern, many teams use Miro to organize ideas, reviews, and stories, but when it is time to present that work, they often move the content into another presentation tool. Internal analysis shows that over 70 percent of users who indicate a need to present end up exporting their work first. Design and engineering agree this may be a meaningful product gap, but they disagree on what kind of solution would actually help. One group wants a new, distinctly Miro way to present from a board. Another group argues that users mainly need familiar presentation behaviors and lower switching cost from tools they already know. There is also a timing question. Miro has to decide whether the current product is mature enough to support this use well now, or whether solving it too early would create a weak experience. Your task is to recommend whether Miro should invest in this problem now, for whom, and what a sensible first version should and should not do.

What to produce

Write a 1 to 2 page product brief.

Your answer must

Define the primary target user and the specific job they are trying to get done when they leave Miro to present.
Make a clear recommendation on whether Miro should address this problem now or later, and explain why.
Propose a first version with 3 to 5 core capabilities and 2 explicit non goals.
Explain the main tradeoff between a distinctly Miro experience and familiar presentation patterns, and how your proposal would reduce switching cost.
Define success metrics, including one metric that captures reduced need to leave Miro and one way to validate demand before a full launch.

Constraints

Work within one quarter with a small team.
Do not assume Miro can match every feature of dedicated presentation tools in the first release.
Do not propose a separate new product or a major platform rewrite.

Format

Use headings for problem, target user, recommendation, first version, metrics, and risks.

How Miro actually played it

Miro's product team shows how Slides came from the finding that over 70 percent of people who wanted to present exported their content to another tool. The post covers the timing, the tension between innovation and familiar presentation patterns, and the aim of removing duplicate work. A small example of using an export metric to size a feature opportunity.

Export behavior can quantify how often users leave for another tool.
Build the feature where users are already working to avoid duplicate effort.
Timing matters: ship when the surrounding product is ready to support the use.
Support imports from familiar tools to reduce switching cost.

Built from How we built Slides by Sophia Chia, Miro.