The IDEO Design Kit is a large public library of human-centered design methods organized by phase and intent. Its value is not in any individual method but in its function as a move-selection system — a way to think about what category of thing the team should be doing next, whether that is understanding, generating, testing, or making something tangible.
What transfers is the phase-oriented selection logic. The question 'what kind of move do I need right now?' is more useful than 'which method is most famous?' The Design Kit trains teams to think about their current position in a project before choosing a technique, rather than defaulting to the familiar methods they already know.
What does not transfer: the Kit's breadth is also its limitation as a Waypoint analogue. Individual methods in the library lack the fit criteria, failure modes, and portability analysis that make a specific method choice defensible. Use the Kit to identify the category of move needed, then use Waypoint's individual method pages to make the tighter selection.
The moment when a team knows they need a method but cannot name the right one. The Design Kit is a catalogue for orienting — not a set of methods to run directly.
The question it sharpens
Which phase of work are we actually in right now — observation, ideation, or testing? And what specific output does that phase need to produce before the team can move on?
In practice
When a team is stuck on method choice or running workshops that do not seem to produce the right output, use the Design Kit to name the phase first: are we trying to understand people, generate options, or test something? Once the phase is clear, use Waypoint to find a specific method that fits the time, room, and output required. The Design Kit is a map for orientation; Waypoint is the navigation once you know where you are.
Where it breaks: The Design Kit is not a facilitator guide. Running methods directly from it without adapting them to a specific client, team, or organizational context produces generic outputs. Its value is in building method literacy — the ability to name what kind of move is needed — not in providing ready-to-run sessions.
IDEO built the Design Kit as a public education resource to spread human-centered design vocabulary and practice beyond the consultancy context. It was designed for practitioners and educators who needed a starting point for introducing HCD methods to teams unfamiliar with the vocabulary.
The Kit functions well in that context — as a teaching tool and a first-pass selection system for teams building HCD literacy. It was not designed as a decision-quality system for teams that already have method vocabulary and need precise fit criteria. Organizations that adopt it as their primary methods reference often find that it generates enthusiasm for the approach while leaving the selection decision still open: there are so many methods, and the Kit does not tell you when each one is wrong.
The library is browsed for inspiration rather than used as a selection system. Teams open the Design Kit hoping to find the right method and spend the session discovering interesting options. The browsing produces no committed next move. Method abundance becomes a substitute for method selection. The useful behavior is to enter with a question — what kind of move do I need? — and exit with one specific method chosen for a specific purpose.
Method abundance is mistaken for rigor. Using many methods, referencing a broad library, and producing a varied output can feel thorough. A team that ran four HCD methods in two days and still cannot describe what they learned about their user's actual behavior has been active, not rigorous.
The Design Kit is used as a substitute for a sharper Waypoint method. The Design Kit is a category guide. It tells you what kind of move might be useful. Once a team knows it needs 'a method for understanding current behavior' or 'a technique for generating concept options,' the Kit has done its job. The next step is to find the specific method that fits the team's context — and that is what Waypoint's individual method pages are for.
Weak signals to watch for
- It is not a decision-ready shelf on its own.
- It is not useful if the team keeps browsing instead of committing to one next move.
- Do not mirror the whole library inside Waypoint.
- Do not let the library become a substitute for choosing one method and running it well.
Primary route
Use the Waypoint methods shelf once the move category is clear and the team needs a tighter fit decision.
Use this when you need a human-centered research or ideation move and can accept browsing a broad toolkit rather than getting a single prescribed method.
technique
Use this when the broad HCD impulse needs to resolve into a sharper problem frame.
Reviewed by Discovery Waypoint Editorial Team · 2026-04-04