From idea to impact,
in one connected place.

A roadmap prioritization & monitoring layer for MUV — linking discovery, delivery, and outcome so the roadmap reflects reality, not a spreadsheet.
Product Team SID Concept for review July 2026
1Root Problem

Our roadmap lives in a spreadsheet, disconnected from the work.

Today the roadmap, the PRDs, the research, the prototypes, and the dev work each live in a different place — held together only by memory, chat, and meetings. Nothing knows about anything else.

table_chartGSheet
Roadmap
Manual list, hard to prioritize
arrow_forwardcopy manual
descriptionDocs
PRD
Separate doc, not linked
arrow_forwardchat / meeting
scienceRISA
Research
Findings live apart
arrow_forwardchat / meeting
design_servicesPrototype
Design
Own library
arrow_forwardchat / meeting
codeClickUp
Dev
Status invisible to PM
low_priority

Hard to prioritize

No shared scoring — the loudest voice wins.

link_off

Disconnected from work

The sheet can't see a feature's real status.

history_toggle_off

No decision trail

Why something was committed — or dropped — isn't recorded.

replay

Loop never closes

After launch, nobody checks if the problem was solved.

2Proposed Solution

Muv Discovery — one connected layer from idea to impact.

Every roadmap item becomes an Idea. An Idea carries the why (problem, evidence, priority), links to the work (Muv Board & Engineer Tools), and closes with the outcome — all inside MUV, no new tool to log into.

insights

Prioritize with data

RICE score and an Impact × Effort matrix replace gut-feel debates. See the quick wins instantly.

sync

Live status, no manual updates

The Idea reads real build status straight from Muv Board / Engineer Tools. One source of truth.

replay

Close the loop

Decisions are recorded; after launch, an outcome review asks: did we actually solve it?

Today

  • close5 tools, connected by memory
  • closePriorities argued, not scored
  • close3 status trackers, all manual
    • trending_flat

    With Muv Discovery

  • check1 Idea ties it all together
  • checkRICE + matrix decide priority
  • checkStatus derived automatically
    • Lean  One new concept only — Idea — built on MUV's existing Board, Docs, RISA & Prototype Library. Not a second system.
    3User Journey — how it connects

    Discovery is the hub — it connects, it doesn't replace.

    Data flows between the tools automatically, with Muv Discovery in the middle. Each stage feeds the next, and the outcome feeds back into what we prioritize next.

    science3rd party · RISA
    Research
    Findings & insights
    arrow_forwardevidence in
    exploreMUV
    Muv Discovery
    Idea: problem · priority · decision
    arrow_forwardcommit → work
    view_kanbanMUV + Eng Tools
    Delivery
    Muv Board tasks · Engineer Tools / ClickUp dev
    arrow_forwardmetric
    monitoring3rd party
    Outcome
    Analytics & usage
    RISA → Discovery
    Research findings attach to Ideas as evidence.
    Discovery → Delivery
    A committed Idea links to Board / Engineer Tools work items.
    Delivery → Discovery
    Build status flows back, read-only. No re-typing.
    Outcome → Discovery
    Did it move the metric? Learning updates the next bet.
    replayThe learning loop: what shipped and whether it worked flows back to inform the next round of prioritization — the roadmap becomes self-correcting.
    4Sitemap

    Where it lives in MUV.

    Discovery is a new section alongside Board and Tugas Saya — not a separate app. It owns Ideas and views; it links out to the systems that own the work.

    appsMUV
    Board day-to-day tasks (existing)
    Tugas Saya my assigned cards (existing)
    Discovery new
    Docs · Prototype · RISA existing addons
    chevron_right
    exploreDiscovery
    Space e.g. Academic (T3), per tribe
    Views List · Board · Matrix · Roadmap
    Idea detail Overview · Insights · Delivery · Activity
    Inbox new ideas & requests
    chevron_right
    hubLinked (not owned)
    Muv Board card → delivery status
    Engineer Tools / ClickUp dev progress
    Docs / Prototype / RISA PRD · design · insight links
    3rd-party analytics outcome metrics
    5User Flow

    The flow, step by step.

    One Idea is the shared anchor. PM, Research, and Design all attach to it — instead of creating separate cards in separate places.

    1
    PM
    Capture the Idea
    From a roadmap discussion or stakeholder request — straight into the Discovery space.
    2
    PM
    Add context & score
    Link the PRD (Docs), set the problem, and give it a RICE score.
    3
    Research
    Attach evidence
    RISA findings link to the Idea as supporting insights.
    4
    Design
    Link the solution
    Prototype (Prototype Library) links in; its progress reflects back.
    5
    Reviewer · HoP/CPO
    Decision gate → Committed
    Recorded decision: problem + evidence + goal before it can proceed.
    6
    PM
    Hand off to build
    Link to Muv Board / Engineer Tools. Status starts flowing back automatically.
    7
    Tech
    Build (outside MUV)
    Dev happens in Engineer Tools / ClickUp; the Idea shows live progress.
    8
    PM / Owner · new
    Outcome review
    Shipped — did it solve the original problem? Closes the loop.
    flag In short

    One place where the roadmap, the work, and the outcome finally meet.

    Lean to start — one new concept, built on what MUV already has. It replaces the spreadsheet, connects the tools we already use, and closes the loop from idea to impact.

    bolt

    Prioritize with confidence

    RICE + matrix, transparent across the team.

    visibility

    See status live

    Derived from Board & Engineer Tools.

    verified

    Learn & improve

    Outcome review feeds the next round.

    The ask: align on the concept & green-light a lean v1 slice.
    exploreMuv Discovery
    1 / 7