Prototyping and Testing Methods
Expert-defined terms from the Professional Certificate in Introduction to Social Impact Design course at London School of Business and Administration. Free to read, free to share, paired with a professional course.
A/B Testing #
A/B Testing
Concept #
Comparative experiment where two versions of a design element are shown to different user groups to determine which performs better.
Explanation #
In social impact design, A/B testing can compare two service delivery models—e.g., a digital sign‑up form versus a paper form—to see which yields higher participation. The test runs simultaneously, and data such as completion rates and user satisfaction are collected.
Example #
A nonprofit tests two fundraising page layouts; one uses a prominent story image, the other uses a testimonial video. After two weeks, the variant with the video shows a 12 % higher donation amount.
Challenges #
Requires sufficient sample size to achieve statistical significance; ethical considerations arise when testing interventions that affect vulnerable populations.
Affinity Diagram #
Affinity Diagram
Concept #
Visual clustering of ideas, observations, or data points to identify patterns and themes.
Explanation #
After field research, designers write observations on sticky notes and group them by similarity, creating a map that highlights user needs and pain points. In social impact projects, this helps prioritize which community challenges to address first.
Example #
During a community health study, notes about “long wait times,” “lack of transportation,” and “language barriers” are clustered under a broader theme of “accessibility barriers.”
Challenges #
Grouping can be subjective; facilitator bias may influence how notes are organized, potentially overlooking minority perspectives.
Black Box Testing #
Black Box Testing
Concept #
Evaluation method that focuses on inputs and outputs without examining internal structures or processes.
Explanation #
Designers present a prototype to users and observe how they interact, noting whether the intended outcomes occur. The internal logic—such as algorithmic decision‑making—is hidden from the tester. This is useful when the underlying technology is proprietary or complex.
Example #
A mobile app for job seekers is tested by asking users to complete a job search; testers observe whether users can find relevant listings without needing to know the app’s recommendation engine.
Challenges #
Limited insight into why failures occur; may miss hidden bugs that only surface under specific internal conditions.
Card Sorting #
Card Sorting
Concept #
User‑centered method where participants organize cards representing content or features into categories that make sense to them.
Explanation #
By observing how users group and label cards, designers infer intuitive structures for a service’s digital or physical interface. In social impact design, card sorting can reveal culturally appropriate ways of organizing resources.
Example #
Participants sort cards labeled “food assistance,” “housing support,” and “employment training” into groups they feel best represent community needs.
Challenges #
Results can vary widely between participants; requires careful moderation to avoid leading participants toward preconceived categories.
Contextual Inquiry #
Contextual Inquiry
Concept #
In‑situ interview technique where designers observe and ask questions while users perform real tasks in their natural environment.
Explanation #
This method uncovers authentic workflows, constraints, and motivations, providing deep insight for prototype development. It is especially valuable in low‑resource settings where assumptions may not hold.
Example #
A researcher watches a community health worker administer vaccinations, asking probing questions about paperwork, equipment, and time pressures.
Challenges #
Intrusiveness can affect natural behavior; requires skilled interviewers to balance observation with respectful engagement.
Design Sprint #
Design Sprint
Concept #
Time‑boxed, intensive process (typically five days) that moves a team from problem definition to validated prototype.
Explanation #
The sprint compresses ideation, decision‑making, and testing into a focused schedule, allowing teams to quickly assess feasibility and impact. In social impact design, sprints can accelerate solutions for urgent crises.
Example #
A team uses a design sprint to prototype a disaster‑relief communication tool, building a clickable mock‑up on day three and testing it with affected residents on day five.
Challenges #
Requires full‑team commitment; limited time may constrain depth of research, leading to superficial insights.
Empathy Map #
Empathy Map
Concept #
Visual tool that captures what users say, think, feel, and do, helping designers develop a nuanced understanding of user experience.
Explanation #
By plotting observations into four quadrants, designers identify emotional drivers and barriers, informing prototype features that resonate with users’ lived realities.
Example #
An empathy map for senior citizens using a public transport app reveals concerns about “fear of technology” (think) and “desire for independence” (feel).
Challenges #
May oversimplify complex motivations; requires diverse data sources to avoid bias.
Feasibility Prototype #
Feasibility Prototype
Concept #
Early‑stage model that tests whether a solution is technically, operationally, and financially viable.
Explanation #
Unlike high‑fidelity prototypes that focus on user experience, feasibility prototypes evaluate constraints such as infrastructure, supply chains, and cost. They help determine if scaling is realistic before extensive user testing.
Example #
A solar‑powered water purification system is built at half scale to test component durability and power requirements in a remote village.
Challenges #
May neglect user desirability; technical success does not guarantee adoption without community buy‑in.
Feedback Loop #
Feedback Loop
Concept #
Continuous process where data from testing informs iterative improvements to a prototype.
Explanation #
Effective feedback loops capture qualitative insights (e.g., user comments) and quantitative metrics (e.g., task completion time) to refine design decisions. In social impact projects, loops may involve stakeholders beyond end‑users, such as funders or policymakers.
Example #
After a pilot of a nutrition‑tracking app, developers analyze usage data, conduct focus groups, and release an updated version addressing identified pain points.
Challenges #
Over‑reliance on feedback can cause “design by committee,” diluting core impact goals; balancing competing stakeholder priorities is essential.
Guerrilla Testing #
Guerrilla Testing
Concept #
Low‑cost, informal usability test conducted in public spaces with opportunistic participants.
Explanation #
Designers set up a laptop or paper prototype in a café or community center, inviting passersby to try it and comment. This method yields quick insights and validates assumptions without extensive recruitment.
Example #
A team tests a voting information kiosk prototype by placing it in a university lobby and observing how students navigate the interface.
Challenges #
Sample may not represent target users; limited time for in‑depth feedback; privacy concerns in public settings.
Heuristic Evaluation #
Heuristic Evaluation
Concept #
Expert review method where evaluators assess a prototype against predefined usability principles (heuristics).
Explanation #
Specialists examine the interface for issues such as consistency, error prevention, and visibility of system status. In social impact design, heuristics are adapted to include accessibility and cultural relevance.
Example #
An evaluator checks a health‑service portal for compliance with the “recognition rather than recall” heuristic, noting that users must remember a complex code to access records.
Challenges #
Relies on evaluator expertise; may miss problems only real users encounter; cultural heuristics may be under‑developed.
Impact Prototype #
Impact Prototype
Concept #
Prototype specifically designed to test the measurable social or environmental impact of a solution.
Explanation #
Beyond usability, impact prototypes embed metrics such as reduced carbon emissions, increased employment, or improved health outcomes. They often incorporate data collection mechanisms to track changes over time.
Example #
A low‑cost water filtration prototype includes sensors that record daily usage, enabling researchers to calculate liters of clean water provided per household.
Challenges #
Impact data can be slow to materialize; requires longitudinal studies and ethical data handling; attribution of outcomes to the prototype may be complex.
Journey Mapping #
Journey Mapping
Concept #
Visual representation of the steps a user takes to achieve a goal, highlighting touchpoints, emotions, and pain points.
Explanation #
By charting the entire experience—from awareness to post‑service follow‑up—designers identify opportunities for intervention and prototype enhancements.
Example #
A journey map for a refugee resettlement program shows stages such as “initial application,” “housing search,” and “community integration,” each with associated stressors.
Challenges #
Requires comprehensive data; may oversimplify non‑linear behaviors; risk of focusing on dominant narratives while ignoring outliers.
Low‑Fidelity Prototype #
Low‑Fidelity Prototype
Concept #
Rough, inexpensive representation of a design—often paper‑based or using simple digital tools—to explore concepts quickly.
Explanation #
Low‑fidelity prototypes prioritize speed and flexibility, allowing designers to test ideas without extensive development. They are ideal for early validation of layout, flow, and content hierarchy.
Example #
Designers draw hand‑sketched screens of a mobile health app on index cards, then ask community members to arrange them in the order they would use them.
Challenges #
Limited realism may obscure usability issues that appear in higher fidelity; participants may not take the prototype seriously, affecting feedback quality.
Mockup #
Mockup
Concept #
Mid‑to‑high fidelity visual representation of a product’s appearance, often static but detailed.
Explanation #
Mockups convey branding, typography, color, and layout, helping stakeholders evaluate aesthetic alignment with cultural expectations. They are commonly used before functional development.
Example #
A mockup of a community banking website shows a warm color palette and iconography reflecting local cultural symbols.
Challenges #
Can create false confidence if visual polish masks functional shortcomings; may lead to “design fixation,” delaying functional testing.
Narrative Prototype #
Narrative Prototype
Concept #
Story‑driven prototype that presents a solution within a contextual storyline to evoke emotional resonance and assess acceptance.
Explanation #
By embedding the prototype in a realistic narrative, designers gauge how users perceive the solution’s relevance and feasibility within their lived experience.
Example #
A video prototype shows a mother using a solar‑powered cooking stove during a power outage, highlighting convenience and safety.
Challenges #
Storytelling may bias participants; separating narrative influence from prototype evaluation requires careful debriefing.
Paper Prototype #
Paper Prototype
Concept #
Physical, hand‑drawn model of an interface used for early usability testing.
Explanation #
Paper prototypes allow rapid iteration; users can manipulate pages, flip cards, or draw on them to simulate interaction. They are especially useful in contexts with limited digital resources.
Example #
A team creates paper screens of a budgeting app, letting community members place sticky notes on features they would use most.
Challenges #
Lack of interactive feedback (e.g., animations) can hide usability problems; participants may treat the prototype as a final product, leading to unrealistic expectations.
Pilot Study #
Pilot Study
Concept #
Small‑scale implementation of a solution to assess feasibility, effectiveness, and potential impact before full rollout.
Explanation #
Pilots generate real‑world data on adoption, performance, and unintended consequences, informing refinements. They often include mixed‑methods evaluation (quantitative metrics and qualitative interviews).
Example #
A pilot of a micro‑loan platform runs with 50 entrepreneurs for three months, tracking repayment rates and business growth.
Challenges #
Limited sample may not capture broader variability; pilot costs can be significant; ethical considerations arise if participants experience sub‑optimal services.
Qualitative Testing #
Qualitative Testing
Concept #
Evaluation approach that gathers non‑numeric data—such as observations, interviews, and open‑ended feedback—to understand user experiences and perceptions.
Explanation #
Qualitative insights reveal motivations, cultural nuances, and emotional responses that quantitative metrics miss, guiding empathetic design decisions.
Example #
After testing a mental‑health chatbot, researchers conduct semi‑structured interviews to explore users’ feelings of trust and stigma.
Challenges #
Data analysis is time‑intensive; findings may not be generalizable; researcher bias can influence interpretation.
Rapid Prototyping #
Rapid Prototyping
Concept #
Accelerated creation of functional prototypes using tools like 3D printers, CNC machines, or low‑code platforms.
Explanation #
Rapid prototyping enables designers to test physical form, ergonomics, and functionality in a short timeframe, facilitating quick feedback loops. In social impact contexts, it can produce tangible solutions for hard‑to‑reach populations.
Example #
A 3‑D printed prosthetic limb component is printed within hours, allowing a user to try it and provide immediate feedback on fit.
Challenges #
Material costs can be high; prototypes may not reflect final production quality; rapid cycles can pressure teams to overlook thorough testing.
Remote Testing #
Remote Testing
Concept #
Usability or impact evaluation conducted with participants who are not physically co‑located with the research team, typically via video conferencing or online platforms.
Explanation #
Remote testing expands reach to geographically dispersed or hard‑to‑access users, reduces travel costs, and can capture natural usage contexts. It requires careful planning to ensure reliable data capture.
Example #
Researchers observe participants in a rural village using a mobile health app via a mobile hotspot, recording screen interactions and verbal commentary.
Challenges #
Connectivity issues can disrupt sessions; limited ability to observe non‑digital cues; participants may feel less comfortable sharing honest feedback remotely.
Scenario Testing #
Scenario Testing
Concept #
Method where participants are asked to act out or discuss a specific situation that the solution is intended to address.
Explanation #
By grounding the test in a realistic scenario, designers assess whether the prototype supports the intended tasks and decision‑making processes.
Example #
Participants are given a scenario where a family needs to locate emergency shelter after a flood, then asked to navigate the prototype to find resources.
Challenges #
Scenarios may oversimplify complex real‑world dynamics; participants might imagine idealized behavior rather than actual actions.
Service Blueprint #
Service Blueprint
Concept #
Detailed diagram that maps out front‑stage and back‑stage activities, resources, and touchpoints involved in delivering a service.
Explanation #
Service blueprints help designers visualize how a prototype integrates with existing systems, identify bottlenecks, and allocate responsibilities. They are crucial for scaling social impact solutions that rely on multiple partners.
Example #
A blueprint for a community clean‑water initiative shows user interactions with a water kiosk (front‑stage) and backend logistics like filter replacement schedules (back‑stage).
Challenges #
Complexity can make blueprints difficult to maintain; over‑detail may obscure strategic insights; requires cross‑organizational collaboration.
Stakeholder Walkthrough #
Stakeholder Walkthrough
Concept #
Collaborative review where designers present a prototype to key stakeholders (e.g., funders, community leaders, policy makers) and solicit feedback on feasibility, alignment, and impact.
Explanation #
Walkthroughs ensure that the prototype meets diverse expectations and that implementation constraints are identified early. They also build ownership among partners.
Example #
A team demonstrates a digital literacy training module to local school administrators, discussing curriculum integration and resource needs.
Challenges #
Power dynamics may silence less influential voices; feedback can be contradictory, requiring careful synthesis; time constraints may limit depth of discussion.
Usability Testing #
Usability Testing
Concept #
Structured evaluation where participants perform tasks with a prototype while observers record performance metrics and user feedback.
Explanation #
Usability testing measures effectiveness (task success), efficiency (time on task), and satisfaction (subjective ratings). It is a core method for refining social impact tools to be accessible and intuitive.
Example #
Participants are asked to locate the “apply for assistance” button on a social services website; success rates and time taken are logged.
Challenges #
Recruiting representative users can be difficult; testing environments may not reflect real‑world conditions; observers must avoid leading participants.
Value Proposition Canvas #
Value Proposition Canvas
Concept #
Strategic tool that articulates the benefits a solution delivers to users, aligning product features with user pains and gains.
Explanation #
The canvas helps designers clarify how a prototype solves a specific social problem, guiding feature prioritization and messaging. It is especially useful when pitching to funders or partners.
Example #
For a renewable‑energy microgrid, the canvas identifies “reliable electricity” as a key gain, while “high upfront cost” is a pain addressed through a pay‑as‑you‑go model.
Challenges #
Over‑emphasis on market language can overlook community‑specific values; assumptions may be untested until prototype evaluation.
Wireframe #
Wireframe
Concept #
Simplified schematic of a digital interface that outlines layout, navigation, and content placement without detailed visual design.
Explanation #
Wireframes focus on structural elements, allowing designers to test flow and hierarchy before investing in visual design. They are essential for early validation of user pathways in social impact platforms.
Example #
A wireframe for a job‑matching portal shows a search bar at the top, filter options on the side, and job listings in the main area.
Challenges #
Users may find wireframes too abstract, leading to disengagement; lack of visual cues can hide usability problems that appear only with final design.
X‑Ray Testing (optional) #
X‑Ray Testing (optional)
Concept #
In‑depth analysis that examines the internal workings of a prototype—such as code, data flows, or hardware components—to identify hidden issues.
Explanation #
While not a user‑focused method, X‑Ray testing ensures that the underlying system can support the intended scale and reliability, which is critical for impact‑driven solutions.
Example #
Engineers run performance profiling on a cloud‑based health data platform to detect latency spikes under high user load.
Challenges #
Requires technical expertise; may uncover issues that are costly to fix; must be balanced with user‑centric testing to avoid over‑engineering.