Sketched a research roadmap on a Miro board — a titled three-phase plan with two colour-coded workstreams, sticky notes with real work items in each phase frame, a legend, cross-phase dependency arrows between individual stickies, and a diamond decision milestone.
Current operation
Task
Sketch a research roadmap on a Miro board
Build a research roadmap on a Miro board — a three-phase plan with two workstreams and the
dependencies between them, the kind a team puts up at a kickoff. Do everything in the Miro
web app (app.miro.com). About seven minutes.
Open app.miro.com and create a new blank board. Rename it Research Roadmap (double-click the board name, top-left).
With the Text tool (T), place a heading across the top: Research Roadmap — 2026, large enough to read as the title.
Add three Frames side by side (F), one per phase, titled:
Q1 · Discovery
Q2 · Experiments
Q3 · Rollout
This roadmap has two workstreams, told apart by sticky colour: Research (yellow) and Engineering (blue). In each frame add two sticky notes — one of each workstream — with a real work item typed on each:
Q1: User interviews (Research, yellow) · Data pipeline setup (Eng, blue)
Q2: Prototype A/B test (Research, yellow) · Model eval harness (Eng, blue)
Q3: Beta feedback study (Research, yellow) · Production rollout (Eng, blue)
Add a small legend in a corner so the colours are readable: a text box (or two small coloured shapes with labels) mapping yellow → Research and blue → Engineering.
Draw the dependencies — arrows between the specific sticky notes that depend on each other, across phases. Hover over a sticky note until a blue arrow handle appears on its edge, then drag from there onto the target sticky; Miro snaps the arrow to it. Draw at least these two: These arrows are the roadmap's flow — the left-to-right frames already show the phase order, so you don't need to connect the frames themselves.
Data pipeline setup (Q1) → Model eval harness (Q2)
Model eval harness (Q2) → Production rollout (Q3)
Add one diamond shape near the Q2/Q3 boundary and label it Go / No-Go — end Q2 — a decision milestone gating the rollout. A shape, not a sticky note.
How it's graded
These criteria define the outcome each recording is checked against.
✓Board has a title -- a Text element (not a sticky) reading as 'Research Roadmap'
✓Three Frames exist, each titled for a phase (e.g. Q1 Discovery / Q2 Experiments / Q3 Rollout)
✓Each frame contains 2 sticky notes with real work items typed in -- one Research, one Engineering -- not empty stickies
✓Stickies are colour-coded by workstream, consistently across all frames: Research one colour (yellow), Engineering another (blue) -- so colour reads as workstream, not phase
✓A legend/key is present -- a text element or small labelled shapes mapping the two colours to Research and Engineering
✓At least 2 dependency connectors join individual sticky notes across different phases (e.g. Data pipeline setup -> Model eval harness -> Production rollout) -- item-to-item; these arrows are the roadmap flow (the left-to-right frames already convey phase order)
✓A shape (a diamond, not a sticky) with a text label marks a decision milestone, e.g. 'Go / No-Go'