Paper Prototype

• Early-stage startups validating their first product concept before any development begins
• Pre-development phase when you have wireframes or sketches but need to test user flows
• Limited budget situations where digital prototyping tools or development resources aren't available
• Complex user interfaces that require testing multiple interaction pathways and decision points
• Mobile app concepts where you need to understand touch patterns and navigation preferences
• B2B software solutions where you want to test workflow efficiency with potential enterprise users
• Physical product interfaces like dashboard layouts, control panels, or packaging designs
• When stakeholder alignment is needed and you want to gather consensus on core functionality before development

1. Define your testing objectives - Identify 3-5 specific questions you want to answer about user behavior, such as "Can users complete the checkout process intuitively?" or "Do users understand the main navigation?"

2. Create your paper screens - Draw or print individual screens/pages on separate sheets of paper, including all key interface elements like buttons, menus, forms, and content areas. Keep designs simple but include enough detail for users to understand functionality.

3. Prepare interaction elements - Cut out moveable pieces for pop-ups, dropdown menus, or dynamic content. Create sticky notes for user inputs and have multiple versions of screens ready to show state changes.

4. Recruit 5-8 target users - Find people who match your ideal customer profile and schedule 30-45 minute testing sessions. Offer small incentives like gift cards or product discounts.

5. Set up your testing environment - Choose a quiet space with good lighting and a large flat surface. Have a smartphone or camera ready to record sessions (with permission) and prepare a note-taking template.

6. Conduct user testing sessions - Present scenarios and ask users to "tap" on paper elements to navigate through tasks. Act as the "computer" by swapping out screens and revealing new elements based on their actions.

7. Document insights immediately - After each session, spend 10 minutes writing down key observations, pain points, and unexpected user behaviors while they're fresh in your memory.

8. Analyze patterns and iterate - Look for common issues across multiple users, prioritize the most critical problems, and create an improved version of your prototype for additional testing rounds.

Pros

• Extremely cost-effective - Requires only basic materials and can be completed for under €50
• Rapid iteration capability - Changes can be made instantly during testing sessions
• Encourages honest feedback - Low-fidelity nature makes users more comfortable suggesting improvements
• Tests core functionality - Focuses attention on user flows rather than visual design details
• Accessible to non-technical founders - No coding or design software skills required

Cons

• Limited realism - Cannot replicate true digital interactions like scrolling, animations, or responsive behavior
• Facilitator dependency - Requires a person to manually operate the prototype during testing
• Scalability challenges - Difficult to test with large numbers of users simultaneously
• Missing technical constraints - Users might request features that are technically impossible or expensive to implement
• Professional perception - Some stakeholders or investors might view paper prototypes as unprofessional