The HCD Toolkit · Free tools · Field-tested since 2011

Tools are how the method travels.

Every tool here has been used in real classrooms, offices and government rooms, and refined by what broke. Take them, adapt them, run them. All we ask is that you test with real people.

HCD Toolkit cards / tools
16Free tools
4Curated collections
4Phases of the process
14Books in the reading room

The process

Four phases. Every tool serves at least one.

Each tool below is tagged with the phases it serves.

01

Immerse

Observe and listen in the real context.

02

Frame

Agree whose problem it is and which problem to solve.

03

Create

Generate ideas and make them testable.

04

Deliver

Test with real users and act on what you learn.

All tools · For everyone

Eight tools any team can run today.

The Field Notebook Protocol · Immerse · 60–90 min
A disciplined way to observe: what to write, what to sketch, and how to separate what you saw from what you assumed. Materials: Notebook, pen. (1) Divide each page into two columns: Saw/Heard and Think/Feel. Nothing crosses columns. (2) Spend 45 minutes in the environment you're studying. Record only observable facts on the left: verbatim quotes, actions, workarounds. (3) Only after leaving, fill the right column: your interpretations and hunches. (4) Circle three left-column entries that surprised you. These are your research leads. Tip: The discipline is the tool. Mixing observation with interpretation is the most common research failure; the two columns make it impossible to do silently.
Ask Why Once More · Immerse · Frame · 30 min
An interviewing drill that trains you past the polite surface of an answer, where the real need usually lives. Materials: Two people. (1) Ask an open question about a real experience: "Tell me about the last time you…" (2) Whenever you receive an answer, ask "why" or "what made that matter?", even when it feels rude. (3) Track how many layers deep each thread goes. Most interviews stop at two; needs surface around four. (4) Debrief: at what layer did the answer change from fact to feeling? Tip: Silence is a question too. Count to five before filling a pause; the interviewee usually fills it with the truth.
The Problem Framing Canvas · Frame · 45 min
One sheet that forces a team to agree on who the problem belongs to, what it costs them, and what success would look like. Materials: A3 sheet, team. (1) Divide a sheet into four quadrants: Who (a specific person, not a segment), Struggle (in their words), Cost (time, money, dignity), Better (what they'd notice if it were solved). (2) Each team member fills it silently first; then merge. (3) Where the team disagrees on "Who", stop: you have multiple problems pretending to be one. (4) Rewrite the merged canvas as a single sentence and pin it above the workspace. Tip: If "Who" reads like a market segment ("urban millennials"), you haven't done research yet. Return to Immerse.
The How-Might-We Reframer · Frame · 30 min
Turn one flat problem statement into ten generative ones by systematically shifting scale, subject and assumption. Materials: Sticky notes. (1) Write your challenge as "How might we…" on one note. (2) Rewrite it five ways: zoom in (one moment), zoom out (the system), flip the subject (provider to user), remove the obvious solution word, and amplify the emotion behind it. (3) Vote as a team on the two versions that feel uncomfortable-but-true. (4) Carry both into ideation: parallel frames produce non-obvious ideas. Tip: "How might we reduce waiting time" and "How might we make waiting feel safe" lead to entirely different hospitals.
Idea Mela · Create · 60 min
A high-energy ideation format built on abundance: every participant must trade, combine and steal ideas like a market day. Materials: Notes, 8+ people. (1) Everyone writes eight ideas in eight minutes, one per note. Quality forbidden; quantity mandatory. (2) Open the mela: participants walk, read others' stalls, and must take one idea and leave one improvement at each. (3) After three rounds, each person builds one "combination idea" from at least three stalls. (4) Pitch combinations in 30 seconds each. Dot-vote for prototyping. Tip: The rule that makes it work: no idea belongs to anyone after round one. Ownership kills combination.
The One-Rupee Prototype · Create · 45 min
A frugal prototyping challenge: make your idea testable using only what's already in the room. Constraint is the teacher. Materials: Whatever exists. (1) State the single riskiest assumption in your idea, the one that kills it if wrong. (2) Build something in 30 minutes that tests only that assumption. Paper, role-play, a WhatsApp message: anything free. (3) Test it on someone within reach in the next 15 minutes. (4) Record one sentence: what did reality say? Tip: If your prototype needs a budget, you're prototyping the product. Prototype the assumption instead.
The Testing Table · Deliver · 20 min per user
A simple protocol for putting a prototype in front of real users without leading, defending or explaining. Materials: Prototype, 2 roles. (1) Two roles only: one host (speaks), one scribe (never speaks). Builders who can't stay silent stay home. (2) Host gives the scenario, not instructions: "You've received this. Do what you would naturally do." (3) Answer questions with questions: "What would you expect it to do?" (4) Scribe logs three columns: did, said, struggled. Review only after all sessions end. Tip: The urge to explain is the urge to protect the idea from the truth. The protocol exists to outvote that urge.
The Critique Circle · Create · Deliver · 15 min per piece
A feedback format that separates the work from the worker, so critique sharpens ideas instead of bruising people. Materials: Group of 4–8. (1) The presenter shows the work, states its intent in one sentence, then goes silent. (2) Round one: the circle answers only "What is this trying to do?" (Misreadings are data.) (3) Round two: "What's working towards that intent?" Round three: "What's working against it?" (4) Presenter responds only with "thank you" and one clarifying question. No defending. Tip: Feedback on intent, not taste. "I don't like the red" is taste; "the red reads as an error state" is critique.

For schools

Classroom formats.

Built for the school day.

Formats that fit a period or a double period, for facilitator-teachers running HCD Lab @ School.

School lab — making
Cardboard First · Create · 1 double period
A classroom prototyping format where every group builds in cardboard before anyone says the word "app". Materials: Cardboard, tape. (1) Ban digital solutions for the session. Every idea must exist as a physical, touchable thing. (2) Groups of 4–5 build for 40 minutes: the object, the space, or a cardboard "screen" with paper buttons. (3) Each group hands its prototype to another group, who must use it without explanation. (4) Builders watch silently and note every confusion. That list is the homework. Tip: "No explaining" is the whole lesson. If the user needs the designer standing beside them, the design isn't finished: a lesson better learnt at fourteen than at forty.
Classroom Empathy Sprint · Immerse · Frame · 1 period
A one-period fieldwork format where students research a real user inside the school: canteen staff, the librarian, a junior class. Materials: Question cards. (1) Pairs choose a person in school whose day they've never considered. (2) 10 minutes preparing three open questions (no yes/no questions allowed). (3) 15 minutes interviewing and observing their person at work. (4) Back in class: each pair shares one thing that surprised them and one problem worth solving. The board fills with real problems for the term's projects. Tip: The best design briefs in a school are already walking its corridors. No field trip budget required.

For professionals

Research, framing and critique for teams.

The Service Safari · Immerse · 2–3 hrs
Experience your own service as a first-time customer: end to end, undercover, with a scoring sheet. Materials: Scoring sheet. (1) Pick the journey a new customer takes: discovery, sign-up, first use, first problem. (2) Run it yourself with a fresh account and no shortcuts. Score each step 1–5 on effort and clarity. (3) Note every moment you used insider knowledge to proceed: each one is a wall a real customer hits. (4) Present the journey to the team as a timeline of scores, not opinions. Tip: Do the safari on a low-end phone with patchy data. That's the median Indian user's context, not your office Wi-Fi.
The Abstraction Ladder · Frame · 40 min
Move a problem up and down levels of abstraction until you find the rung where your team can actually act. Materials: Whiteboard. (1) Write the problem mid-board. Ask "why does this matter?" to climb a rung; write the answer above. (2) Ask "what's stopping this?" to descend a rung; write below. Build five rungs each way. (3) Mark each rung: can our team influence this within our mandate and budget? (4) Frame the project at the highest rung you can still act on. Tip: Teams fail high (problems they can't touch) or low (symptoms that regrow). The right rung is a strategic decision, not an accident.
Assumption Autopsy · Frame · Deliver · 90 min
Before a launch, or after a failure, lay every assumption on the table and grade it: evidence, hope or habit. Materials: Team, wall. (1) List every assumption baked into the project: about users, behaviour, channels, price, adoption. (2) Grade each: E (we have evidence), H (we hope), X (we inherited it and never checked). (3) Rank the H's and X's by damage-if-wrong. (4) Design the cheapest possible test for the top three before spending another rupee on build. Tip: Most projects carry more X's than E's. The autopsy is cheaper before the death.

For government

Tools for public services.

Citizens live journeys.

Field and mapping tools for government and policy teams, from the first walk to the reform agenda.

Management & policy workshop
The Panchayat Walk · Immerse · Half day
A structured community walk that turns a locality into a research site, for teams designing services people must actually reach. Materials: Team of 3–4. (1) Walk the route a citizen takes to access the service: from home to office, not office to home. (2) Assign roles: one navigates, one records distances and waiting points, one talks to people encountered. (3) At every point of friction (queue, form, closed counter, missing signage), photograph and time it. (4) End at the service point. Map the full journey on one sheet: time, cost, and number of people asked for directions. Tip: The direction matters. Officials walk office-outward; citizens live home-outward. Reversing the walk reverses the assumptions.
Stakeholder Constellation · Frame · 60 min
Map every actor around a public service by power and interest, and find the quiet actors who decide whether change survives. Materials: Wall, notes. (1) List every actor who touches the service, including clerks, contractors and middlemen, not just departments. (2) Place each on a wall: vertical axis = power to block, horizontal = daily contact with citizens. (3) Draw lines where actors depend on each other. Thick lines for money, thin for information. (4) Find the high-contact, low-power actors. Design with them first: they run the real system. Tip: The front-desk clerk has appeared in every constellation we have ever mapped, and been consulted in almost none of the failed reforms.
Journey Map for Public Services · Immerse · Frame · Deliver · Half day
Chart a citizen's full journey through a service (visits, documents, costs and emotions) on a single shared wall. Materials: Wall, field data. (1) From field research (see The Panchayat Walk), list every step a citizen takes, first attempt to final outcome. (2) For each step, log four rows: time taken, money spent, documents demanded, and the citizen's emotional state. (3) Mark every step where the citizen needed help from a tout, relative, or repeat visit. (4) Circle the single worst moment. Redesign starts there, not at the website. Tip: Departments map processes; citizens live journeys. The gap between the two maps is the reform agenda.

The reading room

Tools sharpen practice; books deepen it.

Two shelves, one from India's design tradition and one global, chosen for practitioners, not collectors.

The Indian shelf

  • The India ReportCharles & Ray Eames · 1958. The founding document of Indian design education, written for the Government of India. Its meditation on the humble lota remains the finest short argument for human-centred design written on Indian soil.Free online
  • Handmade in IndiaAditi Ranjan & M P Ranjan (eds.) · 2007. The monumental encyclopaedia of Indian crafts: six years of fieldwork mapping the country's making traditions state by state. India's craftspeople are its original human-centred designers.
  • Bamboo & Cane Crafts of Northeast IndiaM P Ranjan, Nilam Iyer & Ghanshyam Pandya · 1986. A classic study of material, maker and community, and a masterclass in how deep immersion in people's lives becomes design knowledge.
  • Design for IndiaM P Ranjan · blog, 2007–2015. Hundreds of essays arguing that design belongs in governance, agriculture and classrooms. The intellectual foundation HCD Institute is built on.Free online
  • Principles of Design through PhotographyDeepak John Mathew (Professor, IIT Hyderabad, India · Nodal Head, DIC Hub). Training the designer's most fundamental instrument, the eye, through the discipline of the camera.
  • Thinking DesignS. Balaram · 1998. Essays from one of India's most influential design educators on design's role in Indian society, from culture and identity to everyday objects.
  • Jugaad InnovationNavi Radjou, Jaideep Prabhu & Simone Ahuja · 2012. Indian frugal innovation for the world: do more with less, treat constraint as a design input. Read it alongside the One-Rupee Prototype.

The global shelf

  • The Design of Everyday ThingsDon Norman · 1988, rev. 2013. The book that gave the field its vocabulary: affordances, signifiers, feedback. Start here.
  • Design for the Real WorldVictor Papanek · 1971. The field's conscience: design that serves genuine human need over consumption.
  • The Field Guide to Human-Centered DesignIDEO.org · 2015. 57 methods with worksheets, developed for social-sector work in the Global South.Free PDF
  • Change by DesignTim Brown · 2009. Design thinking as an organisational capability: the book to hand a sceptical executive.
  • The Sciences of the ArtificialHerbert A. Simon · 1969. The foundational argument that design is a science of its own.
  • Frame InnovationKees Dorst · 2015. The best book on the hardest skill in this toolkit: reframing.
  • MismatchKat Holmes · 2018. Inclusive design made rigorous: every exclusion is a design decision. Essential for anyone designing public services.

Want the method, not just the tools?

Learn it with DIC Hub, IIT Hyderabad, India.

Explore programmes