Module 4: Prototyping, Rapid Prototyping, and Pitching Strategy
Foundations and Definitions of Prototyping
Prototyping: An experimental step to materialize an idea into a sample version of a product, enabling iterative testing, user feedback, and refinement before final production.
Smith (2019): Defines prototyping as constructing a primitive representation or version of a product during the design process to test design flow and establish feedback loops.
University of Missouri-St. Louis: Defines it as the process of building a tangible, limited working model of a system during the analysis phase of the systems development life cycle (SDLC) to modify existing requirements and formulate new ones.
Techopedia: Identifies prototyping as an initial software release stage—often referred to as a beta phase or beta testing—where developmental evolution and defect fixes occur with a select user base prior to full deployment.
Key Advantages of Prototyping
Direct User Involvement: Engages end users during testing phases, reducing misunderstandings, clarifying expectations, and integrating direct user modifications.
Capital and Resource Savings: Draft versions allow low-cost experimentation before substantial investments are committed, preventing expensive errors from oversight.
Elevated User Satisfaction: Fosters bidirectional communication between designers and users, cultivating an emotional investment and sense of product ownership.
Exposure to Future System Enhancements: Uncovers defective or suboptimal components while identifying new opportunities for product innovation.
Prototype Classification: Fidelity and Form
Prototype Fidelity: Refers to the intricacy of detail and functional depth embedded within a prototype.
Low-Fidelity (Lo-Fi) Prototypes:
Constructed using paper, hand-drawn sketches, or printouts to visualize concepts and stimulate design brainstorming.
Advantages: Simple, inexpensive, and encourages honest critique from users.
Limitations: Lacks realism and requires users to imagine workflows, potentially limiting feedback depth.
Examples: Paper prototypes, sketches, journey maps, behavior maps, system flow diagrams, and storyboards.

High-Fidelity (Hi-Fi) Prototypes:
Digital, computer-based representations developed via software such as Tinkercad, Sketch, or Adobe XD.
Advantages: Highly engaging, delivers a realistic user experience, and accurately tests complex features.
Limitations: Demands technical software proficiency, specialized tools, and longer creation times.
Examples: Interactive prototypes, digital wireframes, and coded prototypes.
Prototypes by Form:
Role-Playing (Experiential Prototyping): Physically acts out use cases and operational scenarios to capture empathetic, emotional user responses.
Physical Models: Converts two-dimensional sketches into three-dimensional planes using materials such as cardboard, paper, clay, or foam to examine form factor.

Rapid Prototyping and Lifecycle Models
Rapid Prototyping Concept: Utilizes an iterative spiral cycle or layered approach, progressing incrementally from low-fidelity media to high-fidelity outputs through continuous design-evaluation loops.
Waterfall (Classic) vs. Rapid Prototyping (Spiral) Lifecycle:
Waterfall Model: Concept definition Requirements definition Preliminary design Detailed design Code implementation Test and acceptance Late discovery of omitted requirements.
Rapid Prototyping Spiral: Concept definition Skeletal system implementation User evaluation and concept refinement Refined requirement implementation in a continuous cycle.
Functional Coverage Types:
Vertical Prototypes: Provides deep, end-to-end functionality for a limited sample of specific features.
Horizontal Prototypes: Demonstrates the broad interface or entire screen surface without underlying functional logic.
Idea Pitching and Presentation Strategy
Pitch Definition: Delivering an idea, plan, or product to individuals holding green-light authority (investors, customers, management, or colleagues) to secure funding, adoption, or partnership.
Seven-Step Pitch Roadmap:
Step 0 (Create and Refine the Idea): Clarify the core problem, its real-world evidence, and delivery feasibility.
Step 1 (Scope the Idea): Match the pitch depth to the project scale.
Step 2 (Identify Decision-Makers): Target stakeholders who possess green-light authority.
Step 3 (Adopt Their Perspective): Tailor the narrative to the audience's direct motivations and needs.
Step 4 (Structure Three Depth Levels): Prepare a elevator statement, a methodology explanation, and a detailed plan.
Step 5 (Test the Pitch): Gather external feedback from peers to eliminate bias.
Step 6 (Deliver): Execute presentation and prepare follow-up actions for positive outcomes.
The WISDOM Audience Analysis Framework:
W: What they should learn
I: Interest in the pitch
S: Sophistication regarding the technical subject
D: Detail level desired
O: Ownership assigned to the information
M: Motivation to listen
Elevator Pitch Execution:
Lasts between and .
Hook: Piques immediate interest by addressing a specific user pain point.
KISS Principle: "Keep It Simple Stupid"—eliminate technical jargon ("geek speak") and prioritize customer-centric benefits.
Essential Components: High enthusiasm, concise delivery, and a direct request (e.g., feedback or follow-up permission).
Standard Pitch Formula: FOR [target customer] WHO [statement of need], THE [product name] IS A [category] THAT [key benefit]. UNLIKE [primary alternative], OUR PRODUCT [primary differentiation].