.comThis is falkster.com, the notebook. Falkster.AI is the company.Go to falkster.ai

60-Minute Prototype Workflow

✓ Did you learn something? ✓ Does the team understand the idea now? ✓ Did you validate or invalidate an assumption?

prototype-workflow.md3 KB545 words

The template


60-Minute Prototype Workflow

Timeline Overview

Minutes  Block              Activity
0-5      Setup              Define success, gather context
5-15     Design             Create wireframe/mock
15-30    Build              Tool or clickthrough
30-45    Test               Use it, break it, refine
45-55    Iterate            One quick fix
55-60    Present            Demo & next steps

Stage 1: Setup (0-5 minutes)

Define Success

  • What problem does this solve?
  • Who is the user and what do they do?
  • How will you know if it works? (One key metric or behavior)

AI Prompt

I'm prototyping [feature description].
Success looks like: [describe the outcome]
Build for: [user type and their context]
Give me a simple wireframe outline.

Decision Point: Is the scope realistic for 60 min? If not, descope.


Stage 2: Design (5-15 minutes)

Create a wireframe (hand-draw or use AI to generate ASCII art)

AI Prompt

Create an ASCII wireframe for [feature].
User flow: [describe steps]
Key elements: [list what must be on screen]
Keep it simple and annotated.

Output: Wireframe sketch + user flow notes


Stage 3: Build (15-30 minutes)

Tool depends on your prototype:

  • Figma for visual design (10 min mockup)
  • Docs/Slides for interactive clickthrough
  • Google Sheets for data workflow
  • Simple HTML/CSS for web
  • Loom/ScreenFlow for walkthrough video

Key Rule: Fake it till you make it. Use placeholder content. Links don't need to work.

AI Prompt (if needed)

Generate [HTML/CSS/pseudo-code] for:
[paste your wireframe]
Style: clean and minimal
This is a prototype, so it's okay if it's rough.

Stage 4: Test (30-45 minutes)

Use It Yourself

  • Follow the user flow you designed
  • Can a first-time user understand it?
  • Does it feel fast or clunky?
  • Are there confusing moments?

Break It

  • Try edge cases (what if there's no data?)
  • What happens on mobile or slow connection?
  • Try extreme inputs

Document Issues

  • Note 3 biggest friction points
  • Rate each: cosmetic / nice-to-have / blocking

Decision Points

  • Does it solve the problem? (Yes → move forward)
  • Too complex? (Descope → remove features)
  • Missing something critical? (Add it if <5 min)

Stage 5: Iterate (45-55 minutes)

Pick ONE fix (not three)

  • Biggest blocker from testing
  • Takes <5 minutes to implement

AI Prompt (if you're stuck)

I tested this and got stuck on: [describe the issue]
Quick fix ideas?

Then iterate once. Don't try to polish everything.


Stage 6: Present (55-60 minutes)

Ship It Checklist

  • Take a screenshot or recording
  • Write the one-sentence problem it solves
  • List what you tested
  • Note the #1 thing to improve next
  • List unknowns (what you didn't test)

Demo Script (2 minutes)

Problem: [1 sentence]
Solution: [1 sentence]
How it works: [walkthrough, 30 seconds]
Next steps: [what we learned, what to build next]

Share with team in Slack or scheduled meeting


Success Criteria

✓ Did you learn something? ✓ Does the team understand the idea now? ✓ Did you validate or invalidate an assumption?

If yes to all three: prototype worked.

More from the toolkit


All templates →