Innovation Accelerator Hub
All playbooks
Practice

Prototyping workflow

The end-to-end flow from a raw problem to a shareable prototype — Ramble Refiner, build vs plan mode, tests, and collaboration.

Published
Owner · Director, InnovationUpdated · 2026-07-19
1

Kickoff — from ramble to prompt

Every project starts by listening. A sponsor or stakeholder describes a problem — often messy, sometimes half-formed. Don't try to structure it in the conversation. Capture it raw.

Take the raw notes into ChatGPT and run the Ramble Refiner prompt. Its job is to:

  • Refine the idea into something coherent
  • Surface what the sponsor actually means vs. what they said
  • Produce a first-draft prototype prompt you can paste into Lovable
Rule of thumb
Always record the conversation with the sponsor or requester. Your job in that room is to pay attention — pick up on what they mean, not just what they say. Taking notes pulls you out of the conversation; the recording is your notes.
2

Build loop — pick the right mode

Once the prototype is up, changes come in three sizes. Pick the mode that matches the size, not the one that feels fastest.

Small tweaks
Build mode
Copy fixes, layout nudges, color swaps, single-component changes. Ship it.
Bigger features
Plan mode
New page, new flow, non-trivial data change. Generate a plan, save it to documents/features.
Complex features
Plan + ChatGPT
Ambiguous or high-stakes. Ping-pong between ChatGPT and Plan mode until the plan holds up. Then save.
Why save the plans
Plans in documents/features/ become the audit trail of how the prototype evolved — useful for handoff, retros, and onboarding the next Accelerator.
3

Testing — free by default, deeper on demand

Plans generated in Plan mode include tests by default. That's usually enough for a prototype. When you need more coverage — a critical flow, a regression you keep hitting, a feature going to real users — run a dedicated test plan.

  • Create a plan whose only goal is to generate tests
  • Let it write the tests, run them, and produce a coverage matrix
  • Save the resulting test plan to documents/tests/
4

Collaboration — two paths

Who's giving feedback determines how you share it.

Internal Accelerators, technical partners
Lovable users
Invite them directly to the project. They can view, comment, and edit inside Lovable.
Sponsors, business stakeholders, external users
Everyone else
Publish and share the URL via markup.io. They can browse the live prototype and toggle to comment mode without needing an account.
5

Artifacts checklist

By the end of a prototyping cycle, these should exist:

  • Refined prompt (in the project or the Ramble Refiner chat)
  • Feature plans in documents/features/
  • Test plans in documents/tests/
  • Live prototype URL (Lovable or markup.io depending on audience)
  • A short list of what you learned — the whole point of the exercise