Workflows
Every PROM product moves through the same nine phases, in a loop. Each phase carries its own frameworks; every artifact links back to the same graph. Scroll to follow the road.
follow the roadDefine the hurt before you design a fix.
Get the topic out of your head, surface early beliefs and bias, and decide what's actually worth investigating. Captured once and pulled into every downstream artifact so the team never loses sight of what they signed up to solve.
Sharpen the picture before you spend a sprint.
Interviews, secondary sources, market sizing, competitive snapshots. The copilot turns transcripts into themes you can act on — every finding linked back to the problem it answers.
Turn signal into a problem you can defend.
Group insights, shape a proto-persona, fill a value-proposition canvas, and lock the validated problem statement before anyone designs a thing.
Generate options without judgment, score them with discipline.
Crazy Eights for breadth, structured voting for focus. Every idea keeps a trail back to the problem it answers, so the shortlist is defensible — not loudest-in-the-room.
Turn the chosen idea into a PRD the team agrees on.
Prioritize features, lock a North Star, and write the PRD with hypotheses and experiment designs attached. Frames link both ways, so a change shows up before production.
Prototype, MVP, or production — sequenced and instrumented.
Tasks generate from the PRD with acceptance criteria already attached. QA plans, ADRs, and monitoring come with the work, so engineering walks in with context, not questions.
Capture learnings, decide pivot / persevere / kill.
Test cards, usability logs, desirability and viability checks. Every hypothesis gets a status and a logged decision, so the verdict is honest — and lives in the graph.
Coordinate the release across product, comms, support.
One checklist ties the rollout, the comms, support readiness, and day-1 metrics together. Owners assigned, dependencies visible, rollback documented — no one waits on a Slack thread.
Maintain efficiently, and sunset cleanly when it's time.
North-star tracking, retros that link to the artifacts they critique, feedback clustered into the next problem worth solving. The graph keeps the lessons; the next cycle starts sharper.
Every retro, every metric, every customer signal lives in the graph and shows up the next time someone opens a Problem doc. The cycle gets sharper each lap.