The On It StudioProduct Development Steps: A Practical Workflow
Product development steps are the six stages that take an idea to something you can sell: idea generation, concept development, prototyping, design, testing, and launch. Skip the prototype stage on a card deck or classroom kit to save a week, and you don't save anything. You just move the failure to after the print invoice. Say a run of 500 units has a 10% misprint rate, our assumption for a design nobody proofed on paper first: that's 50 wasted units before the product reaches a kid's hands.
That's the whole case for following product development steps in order, and for knowing exactly which stage to return to when something doesn't work.
What Are the Product Development Steps?
Six stages. Each has its own tool, its own time cost, and its own way to fail. This is the workflow we use when we help a founder take a physical product from idea to print-ready files.
| Stage | Tool | Time estimate (stated assumption) | What breaks |
|---|---|---|---|
| Idea Generation | Shared Google Sheet, one row per idea | 15 ideas x 10 min = 2.5 hrs, if audience research is already done | No one kills the weak ideas; 3 "maybes" carry forward instead of 1 strong pick |
| Concept Development | One-page brief in Google Docs | About 1 hr per concept, once the idea is picked | The spec stays vague on size or material, so the prototype doesn't match what printing allows |
| Prototyping | Paper mockup, no print run | 36-card paper prototype: about 3 hrs, if the content is already written | The first print run becomes the prototype; mistakes now cost print money, not paper |
| Design | Sample from the print vendor | 5-10 business days for one physical sample, standard (non-rush) turnaround | Feedback scatters across email instead of one doc; round 2 repeats round 1's mistakes |
| Testing | Airtable base, one row per tester | 8 sessions x 30 min = 4 hrs, plus about 2 hrs logging | Bugs get found but not written down; the same issue resurfaces at launch |
| Launch | Shopify Flow + Stripe | About 30 min to set one low-stock alert, store already live | Inventory and customer service fall out of sync; a sold-out product still takes orders |
Two of these stages deserve more than a table cell.
Prototyping is where most teams cut the corner that costs them later
A prototype isn't the finished product. It's the cheapest version that still answers the real question: does this work? For a card deck, that's 36 index cards with the text written in marker, cut by hand, no print run involved. Budget about 3 hours if the content already exists; most of that time goes into deciding what fits on a card, not into making it pretty.
Skip this step and your first print run becomes the prototype. A sizing mistake, a font too small to read across a table, a rule nobody tested out loud: now it costs you the invoice instead of a sheet of paper.
Testing is where feedback either gets used or gets lost
Testing means putting the product, or the prototype, in front of people who aren't you and watching what they actually do, not what they say they'd do. Run 8 sessions at 30 minutes each and that's 4 hours of sessions, plus roughly 2 hours logging what broke in a shared Airtable base (one row per tester, columns for what broke, how bad, fixed or not), assuming you don't need follow-up calls.
The part teams skip isn't the testing. It's the logging. The feedback lives in someone's notebook or a Slack thread, the fix gets made, and six weeks later the same bug "gets discovered" again at launch because nobody wrote it down anywhere searchable.
Why Does a Clear Process Matter?
A process doesn't make the product better by itself. It moves the cost of being wrong to the cheapest stage available, catching a bad idea at the Google Doc stage instead of catching it at the print invoice stage.
Here's the trade-off: running six stages properly takes longer than skipping straight to "just build it." For a card deck or classroom kit, concept to print-ready files usually runs about eight weeks, assuming the content already exists and you don't need more than one sample round. That's slower than winging it. It's also the difference between one print run and three.
When Should You Loop Back to an Earlier Stage?
Loop back one stage, not ten. If testing shows the product doesn't solve the problem, go back to concept, not idea generation; the idea was probably fine, the spec wasn't. If prototyping shows the design can't actually be printed or built at the size you specced, go back to design, not concept.
The mistake is treating any setback as proof the whole thing needs rethinking. Usually it's one step back, one fix, and forward again, not a full restart.
FAQ
What's the first step in product development? Idea generation, logged one row per idea in a shared sheet with the problem it solves and who it's for. Reviewing 15 ideas for 10 minutes each takes 2.5 hours, assuming the audience research is already done.
How long does product development take for a physical product like a card deck or plush toy? For a kids' product going from concept to print-ready files, budget about eight weeks if the content exists and you don't need more than one sample round.
Is a prototype the same as an MVP? Not quite. A prototype can be a drawing or a paper mockup, cheap and fast, built just to test whether the idea works. An MVP is a basic working version built with real or near-final materials, used to test whether the thing can actually be manufactured or run.
The Step Most Teams Skip
The step that gets cut under deadline pressure is almost never idea generation or launch. It's logging feedback from testing somewhere other people can search later. Write it down in one place, even a plain Airtable base, and the next product you build starts from what actually broke on this one, not from memory.
If you're building a card deck, classroom kit, book, or plush and want someone to run these six stages for you, from spec through print-ready files to checked samples, our product development for kids brands and creators does it in eight weeks. We ran the same workflow on our Yogapalooza case study, a kids wellness brand moving from concept to a printed product. If you'd rather start by mapping where your week actually goes before committing to a build, the free ops audit is the faster first step. For more playbooks like this one, see /resources.
