Prototype, Test and Scale

The Need for Prototyping

Generating many ideas (quantity yields quality) is only the first step. With potentially 100,000 ideas, you cannot take every one to market. The challenge is to sift through them and identify the gems — not by listening to the loudest voice or testing each exhaustively, but by running small, fast experiments.

Prototyping Mentality

Prototyping is a mindset of trying things out before full market launch — ideally with customers. The goal is to fail cheap and fail early, gathering feedback through low-fidelity setups (rough, inexpensive models of a product or service). This minimizes risk and cost while learning what works.

Three Core Aspects of Module 4

Creativity vs. Innovation

• Creativity – generating novel ideas.
• Innovation – scaling those ideas to create real impact.
  Scale is the only proof of innovation. Without multiplication, an idea remains in the realm of creativity.

Design Thinking Process (Connection to Previous Modules)

The overall model runs:

Module 4 covers the final two steps: validating ideas through prototyping and then scaling.

Real-World Application: The Cafeteria Case

Throughout the design thinking journey, a live test case is used — the staff canteen (or cafeteria). By now, students should have:

• Understood current and potential issues.
• Developed candidate ideas.
• (If in Bangalore) visited the actual cafeteria to observe problems in native context.

The module expects quick and dirty prototypes to solve these complex, real-world problems.

Exam tip: The distinction between creativity and innovation is a high-yield concept. Remember: scale is what turns creativity into innovation. Prototyping is the bridge that allows you to fail cheaply before committing to scale.

Key takeaways

• After ideation, use prototyping to filter the best ideas — not all 100,000.
• Prototyping mentality: test early, fail cheap, get customer input via low-fidelity setups.
• Only winning protos get scaled; scale is the proof of innovation.
• Design thinking flow: Inspiration → Empathize → Ideate → Prototype → Scale.
• The cafeteria case provides a concrete, live context to apply these concepts.

Idea Shortlisting

When faced with a large pool of ideas (e.g., 500 from a workshop), the goal is to reduce them to a manageable set (e.g., 50) using disciplined mental heuristics. Two complementary rubrics guide this filtering.

Rubric 1: Desirability, Feasibility, Viability (DFV)

At the core of design thinking is the trinity of human desirability, technical feasibility, and business viability. All three must be evaluated simultaneously — not sequentially — to find the global optimum rather than a local one.

• Human desirability (not customer centricity): Does this solution address an implicit, future-oriented human need? Classic fallacy: reducing design thinking to customer centricity. The “human” includes sellers, buyers, and all stakeholders — the aim is a solution that humans truly crave, beyond stated wants.
• Technical feasibility: Does the necessary technology exist? Can the project be executed within time and budget given current technological base? If not, an otherwise desirable idea must be parked until the technology matures.
• Business viability: Does the idea make commercial sense? This is the Achilles’ heel of many startups — customer happiness and technical capability do not guarantee profitability. Example: quick commerce in 2025 – customers are delighted, but companies bleed money.

The three dimensions do not always have equal weight. An organization strict on ROI may double down on viability; a startup focused on traction may double down on desirability. The key is to apply the rubric as a simultaneous filter to distill only ideas that meet all criteria.

Rubric 2: Impact–Time Matrix

Plot every idea on a 2×2 matrix of potential impact vs. time to results (based on prior knowledge). No single “silver bullet” can cure all ailments; an organization needs a portfolio of ideas across four quadrants:

Exam tip: Do not treat DFV as a weighted average or a sequential checklist. The strength of the rubric comes from simultaneous evaluation. Similarly, the impact–time matrix demands a portfolio view — never chase only stars.

Key takeaways

• DFV rubric filters ideas by human desirability (stakeholder-centric), technical feasibility, and business viability — all three at once.
• Impact–Time matrix classifies ideas into starters, stars, pipeline, and pipe dreams; build a balanced portfolio.
• Human desirability ≠ customer centricity; includes all stakeholders and implicit future needs.
• Technological leapfrogging allows late entrants to become stars.
• Design thinking brings discipline and method to creative idea selection.

Why Prototyping

A prototype is worth a thousand meetings. Instead of pitching an idea with slides, put a simple prototype on the table – people play with it, discover unexpected uses, and become convinced faster. This section explains why prototyping is essential, what a prototyping mentality means, and how to use different types of prototypes to learn, sell, and improve.

The Prototyping Mentality

Prototyping requires being okay with imperfection. We naturally seek clarity and certainty, but that kills creativity. A prototyping mentality means:

• Having a provisional attachment to your ideas – you are willing to change or abandon them.
• Being willing to fail publicly – every post, every model is a chance to learn.
• Soliciting feedback early and often – it saves wasted effort, time, and reputation, even though it takes courage.

“Learn to kill your darlings.” – Stephen King. If you don’t kill your own pet ideas, they will die with you when the market rejects them.

Key Reasons to Prototype

Two Types of Prototypes

Prototypes serve two distinct purposes: functional (works like the final product) and aesthetic (looks like the final product). Both are essential.

Worked Example: Titan Edge Watch

In 1997, Titan wanted to launch the world’s thinnest watch – so thin the case matched the bracelet width, with 50 m water resistance. International experts dismissed it (“only for a museum”).

The team built two prototypes:

1. Functional prototype – a working movement that could be submerged, frozen, heated, and shaken. It did not look like a watch.
2. Aesthetic prototype – a beautiful thin case without a working movement. It looked exactly like the planned product.

Both were given to Titan employees to wear. Feedback revealed that customers were willing to give up a second hand (and even a day/date calendar) to have the ultra-thin design. The watch became a runaway success.

Exam tip: The Titan case illustrates how functional and aesthetic prototypes together uncover trade-offs (fewer features vs. slimmer design) that no amount of PowerPoint could reveal.

Key Takeaways

• A prototype conveys an idea faster and more honestly than a presentation – “a prototype is worth a thousand meetings.”
• Five core purposes: gain clarity, build investor confidence, find issues early, solicit feedback, and soft-sell.
• Use both functional (works like it) and aesthetic (looks like it) prototypes to learn different things.
• A prototyping mentality means embracing imperfection, failure, and the courage to kill your darlings – your own cherished ideas.

Rules of Prototyping

Three core rules guide effective prototyping in design thinking. Each aims to maximize learning while minimizing wasted time and resources.

1. Do the last experiment first

Test the most difficult, highest-risk hypothesis before anything else. In a chain of assumptions, the one that will break the entire project is the one to validate first.

Intuition: People naturally start with easy tasks to build confidence. Design thinking flips that — tackle the hardest part first, because if it fails, everything else is irrelevant.

Worked example: ATM development
The critical hypothesis for ATMs was: Will consumers trust a machine to give them cash? Not the counting mechanism, security, or connectivity. To test this, Diebold and NCR built a facade ATM with a human behind the wall counting and handing out money. Customers believed it was a machine. Once comfort was validated, all other technical challenges became secondary.

Another example is the privacy concern: customers wanted to be sure nobody watched them enter their PIN. Instead of installing expensive cameras, designers placed a convex reflector (like a rear-view mirror) on the ATM. The reflector gave the user a quick visual check of their surroundings, creating a sense of privacy at near-zero cost.

Worked example: PhD or teaching?
A student wanted a PhD to become a good teacher. The "last experiment" — teaching — was deferred until after the PhD. The advice: teach now. If you discover you don't enjoy teaching, the PhD is wasted. Do the hardest test (do you actually like teaching?) before committing years of effort.

Worked example: Writing a book
Would-be authors often seek a publisher before writing. The last experiment is writing itself. Start writing first; if you can’t produce content, a publisher will not help.

---

2. Maximize learning per unit time and dollar

A prototype's real output is not a thing — it is learning. Therefore, design experiments to pack as many tests as possible into a limited budget (e.g., one day, $1,000).

Method: Use quick and dirty prototypes — simple, low-fidelity models made from readily available materials. Do not aim for elegance; aim for speed of insight.

Example: Apple iPhone icon size
Before the iPhone (2007), touch icons did not exist. The team needed to find a single icon size that worked for thumbs of all sizes (American, Japanese, Indian; men, women, children). In a top-secret project (Project Purple), they built a simple game: different-sized icons appeared on screen, and users had to press them as fast as possible. The speed of response determined the optimal size. Result: three square pixels — the standard still used today. This was a quick, dirty, and cheap experiment inside a high-security environment.

Exam tip: "Quick and dirty" does not mean sloppy; it means fast and focused on the essential question. The fidelity of the prototype should match the risk of the hypothesis.

3. Fail faster to succeed sooner

Accelerate the learning cycle by embracing failure as data. Each failure is a prototype that taught you what doesn't work. The faster you fail, the sooner you converge on a solution.

Example: James Dyson’s bagless vacuum cleaner
Dyson ran over 5,000 prototypes before perfecting the cyclone-based design. He did not see failures — each was a step toward the principle of using a miniature tornado to separate dust (no bag, no suction loss). The same approach gave him the Airblade hand dryer (air jet, not hot air).

Example: Thomas Edison
Edison meticulously documented every failed prototype. He treated failure as a necessary part of the path to success.

The IDEO Tech Box
IDEO, a leading design consultancy, keeps a physical repository of failed prototypes — the tech box. When a new client arrives, the team first raides the tech box: can a previous failure be repurposed for this new context? This cuts learning curves and prevents trashing ideas that may work elsewhere.

Example: Google Glass → Google Lens
Google Glass failed because it invaded privacy and required wearing a device. But the same technology, embedded into a phone camera, became Google Lens — a widely successful app. The failure of one form factor became the success of another.

Key insight: No prototype is a failure; it is a learning event that may find its use later.

---

Summary of the three rules

---

Key takeaways

• Prototyping is about learning, not building a finished product.
• The most powerful rule: test the riskiest assumption first.
• Use quick and dirty prototypes (available materials, simple tests) to generate insight rapidly.
• Embrace failure — document it, store it, and reuse it in new contexts.
• A failed prototype today may become a successful innovation tomorrow (Google Glass → Google Lens).

Prototyping Methods

Prototypes are low-fidelity, throwaway models that bring an idea to life using whatever materials are available. Their purpose is exploration, not perfection — low fidelity makes it easy to discard and move to the next iteration. This applies equally to physical products and services (experiences, emotions, service processes).

Product Prototyping Methods

Exam tip: Paper prototyping is especially powerful for UI/software products because it lets you test user flows before writing any code — and the cost of change is zero.

Service Prototyping Methods

Services are intangible; they unfold over time and involve human interactions. Four methods reveal how the service will be experienced:

Storyboarding

Borrowed from advertising. Draw the service “frame by frame” as a sequence of scenes (e.g., a bank re-designing the account-opening process: first scene – customer enters, second scene – greeter directs, third scene – form filling, etc.).

Skits and Plays

Act out the service in real time. Roles are assigned, physical layout is simulated. Helps identify pain points (e.g., an elderly person withdrawing cash: does the process feel secure?).

Storytelling (SCQA Framework)

Narrate the idea as a coherent story using the SCQA structure:

• Situation: The current state (e.g., “300–350 people dine in the staff canteen during lunch in 2 hours.”)
• Complication: The problem (e.g., “At 1 pm, long queues form at billing and food counters.”)
• Question: The design challenge (e.g., “What technological or people-based solution can reduce queue length and improve convenience?”)
• Answer: The proposed idea(s) (e.g., weekly coupons, QR code scanning, punch‑card authentication)

If the listener finds the story coherent, the idea is roughly on the right track — no physical prototype needed.

Scenario Analysis

Test the idea against three possible scenarios:

For each scenario, ask: which ideas make sense here? This filters ideas by robustness — the same solution may not suit all situations.

Key takeaways

• Product prototypes: paper, Lego/clay, quick and dirty — all low-fidelity and disposable.
• Service prototypes rely on storyboarding, skits, storytelling (SCQA), and scenarios.
• SCQA narrates the problem → solution story; a coherent story validates direction without building anything.
• Scenarios test ideas under best‑, usual‑, and worst‑case conditions, revealing where each idea fits.
• Playfulness (Lego, clay) and cheap materials (Post‑its, cardboard) keep iteration fast and psychological attachment low.

Models of Scaling

Traditional design thinking stops at prototyping and testing, leaving a gap: what happens after a validated idea? Scaling addresses that gap by giving structure to the transition from prototype to real-world impact. Two key techniques: the Business Model Canvas and OKR (Objectives and Key Results).

Business Model Canvas (BMC)

The BMC, pioneered by Alexander Osterwalder, provides a one-page framework that forces clarity around how an idea becomes a functioning business. It answers three fundamental questions:

• How does the business generate value? (value-creating activities)
• How does the business deliver value? (value-delivering activities)
• How does the business appropriate value? (profit-making activities)

These map onto three streams: upstream (value generation), midstream (value proposition), and downstream (value delivery and capture).

BMC Components

Exam tip: The BMC reveals gaps you never considered – especially in go-to-market, cost structures, and revenue models. Use it to decide whether to pursue or pivot.

Worked Example: Cafeteria

• Resources: cooks, serving staff, machinery, raw material.
• Activities: cleaning, cooking, serving, billing.
• Partners: grocery suppliers, LPG providers, deep-cleaning services.
• Costs: salaries, rent, licenses.
• Revenue: product sales.

Once you fill each block, you often discover missing pieces – e.g., no clear sales channel or underestimated fixed costs.

Objectives and Key Results (OKR)

OKR (Andy Grove, Intel; adopted by Google) provides a disciplined way to measure progress and translate ambition into actionable metrics. It contains two parts:

• Objective – the what: a qualitative, aspirational goal.
• Key Results – the how: quantifiable milestones that define success.

OKR Structure

Example 1: Design Thinking Course

• Objective: Students understand and practice design thinking in life and career.
• Key Results:
  1. 80% of students participate in live projects.
  2. 70% pass the subjective exam.
  3. 800 of 1000 students attend live classes and engage in discussions.

Example 2: Weight Loss

• Objective: Shed 5 kg in one month and maintain loss for one year.
• Key Results:
  1. Eat small meals five times a day (tick).
  2. Avoid greasy items for one month (tick).
  3. Walk 10,000 steps daily (tick).

Exam tip: OKRs make the subjective objective. Peter Drucker said, “What cannot be measured cannot be managed.” Always define 3–5 key results per objective; achieving all KRs guarantees the objective.

Key Takeaways

• Scaling requires a structured business model (BMC) and a measurement system (OKR).
• BMC covers value generation, delivery, and capture – each block must be filled before scaling.
• OKR uses measurable key results to track progress toward a qualitative objective.
• Both techniques force discipline and reveal blind spots (e.g., missing channels, unrealistic costs).
• Use BMC to validate viability; use OKR to monitor execution and pivot when metrics don’t align.

Applying Design Thinking to Career, Rejection, and Innovation

Design thinking is often misunderstood as a process for designers only—a misconception that limits its application. In reality, design thinking is a systematic model of thinking that applies to anyone, anywhere: homemakers, students, entrepreneurs, government leaders, and individuals solving everyday problems. It is not about designing physical objects; it is about designing your own thinking. The core principles apply across fields, from career planning to product innovation in IT and R&D.

Misconceptions About Design Thinking

• “I need to be a designer.” — False. The term “design thinking” originates from design, but its modern application spans problems of any kind.
• “It’s only for startups or tech.” — False. It works in large companies, government, NGOs, and even personal life (e.g., exam preparation, household challenges).
• “It requires youth.” — False. Age and background are irrelevant. Design thinking is for everyone at any stage.

Exam tip: The most common exam trap is equating design thinking with visual design or engineering. Always remember: the “design” here refers to designing the thinking process, not artifacts.

Career Planning with a Design Thinking Mindset

Career in decades — a fundamental shift from thinking in years to decades. A decade is a vast stretch of time; underestimate what can happen in a year, overestimate what can happen in a decade. Plan life in five-decade blocks: e.g., work in a large company, then dabble in startups, then contribute to society, then explore spirituality.

Own your career — do not delegate career responsibility to parents, HR, or teachers. Most possibilities (e.g., tattoo artist, nail painter) did not exist a generation ago; 50% of future jobs do not exist today. Only you can navigate this landscape.

Focus on what will not change — rather than chasing trends, anchor on enduring fundamentals: education, health, mental and spiritual hygiene. These remain valuable regardless of disruption.

Handling Rejection: Input, Not Identity

Rejection is inevitable—24 out of 25 PhD applications were rejected for Dr. Pavan Soni; the one acceptance (IIM Bangalore) turned into a blessing in disguise. The key is to treat rejection as input for learning, not as a verdict on worth.

• If you are clear about your objectives, rejection strengthens resilience.
• It is okay to be confused about what you want, but be very clear about what you don’t want.
• Every rejection is an opportunity to learn something new—absorb it, don’t bulldoze through.

Saying No: Zone of Concern, Zone of Influence, Non-Negotiables

Young professionals often say “yes” to impress others, leading to diluted efforts and loss of reputation. The antidote is understanding two zones:

• Zone of concern: things that perpetually bother you but are outside your control (e.g., how others perceive you, global events). Shrink this zone.
• Zone of influence: things you can actively do something about. Say yes only to items within this zone.

Non-negotiables are personal boundaries that protect reputation and integrity. One mistake can destroy a reputation built over a lifetime. Examples from Dr. Soni: never attending parties with only eating/drinking as the goal, never accepting kickbacks.

Exam tip: “Say no more than you say yes” is a tested concept. Explain why: overcommitting leads to poor delivery, loss of trust, and self-doubt. Say “yes” only if you can do that thing better than anyone else.

Design Thinking in IT: Lessons from India’s Large-Scale Innovations

India’s success with FASTag, Digi Yatra, and UPI demonstrates three principles of applying design thinking at scale:

1. Human-centric simplicity – technical complexity is masked from the user. Even an illiterate person can use the interface (e.g., facial recognition at airports with minimal instruction).
2. Indigenous platforms – self-reliance (Atmanirbhar Bharat) reduces dependency on foreign technology (e.g., homegrown GPS, Aadhaar). This ensures adaptability to local contexts.
3. Technology + human, not technology minus human – human assistance always remains available (e.g., a human at every FASTag boom barrier). Technology augments, not replaces. Evidence: cash circulation in India increased alongside UPI adoption.

Exam tip: The “technology plus human” insight is a common point of discussion. Contrast with the fear that AI displaces labor—in India, technology complements human skills (proven by concurrent growth of UPI and cash usage).

R&D and Sustained Creativity: The Need for Multiple Affiliations

R&D professionals face mental blocks when they focus exclusively on their field. The antidote is multiple affiliations—cultivating hobbies, artistic pursuits, and diverse interests.

• Nobel laureates are 20% more likely to have an artistic hobby than their peers (e.g., Richard Feynman played drums, Einstein played violin).
• Hobbies provide fresh perspectives and mental dispersion.
• Examples from India: Dr. APJ Abdul Kalam was a prolific writer, poet, and lifelong learner; he was reading Stephen Covey when he died while lecturing.

R&D gratification is deferred (years, not quarters). A long-term view, a holistic life, and patience are essential. Avoid rushing; life is long.

Key Takeaways

• Design thinking is for everyone, not just designers or startup employees.
• Plan your career in decades, own it, and invest in what will not change (education, health).
• Rejection is learning input; clarity of purpose neutralizes its sting.
• Say no to shrink your zone of concern and protect your reputation; say yes only where you excel.
• In IT, build human-centric, indigenous solutions that augment human effort rather than replace it.
• For R&D, cultivate multiple affiliations (hobbies, arts) to sustain creativity and avoid burnout; develop a long-term perspective.