Key Takeaways
Turn customer research into collaborative play, not another round of asking what they want.
Make insight participatory. Innovation Games are structured activities that let customers show, build, rank, and discuss what matters to them. Instead of asking for a wish list, a team might have customers design a product package, map how products relate, or mark the problems slowing a product down. The activities are designed to make ideas visible and give customers something concrete to react to together.
Learn alongside customers. The product team prepares and observes the session rather than hiding behind a research report. In one example, customers shaped future products by drawing on large paper trees, then explained which features they added or removed. The aim is not entertainment for its own sake. Play gives customers a more active way to express needs and gives teams richer material to interpret.
What's striking is how the format changes the evidence being collected. A spoken answer can be polished, vague, or shaped by what a customer thinks the company wants to hear. A drawing, negotiation, or demonstration can expose priorities that are harder to articulate directly. This aligns with participatory design, where users help shape the problem representation itself. Still, engagement is not proof of representativeness. A lively session reveals possible needs and meanings, not how common they are across the whole market.
Start with a decision, then choose the evidence and game that can inform it.
Plan for action. The book treats market research as a sequence: decide what questions matter, identify what evidence could answer them, gather and interpret that evidence, then act. A game should not be scheduled merely because it sounds engaging. Before inviting customers, the team should know what decisions the results might influence, such as changing a roadmap, improving service, or exploring a new offering.
Match method to question. Existing records may reveal market size, while a customer activity can reveal how people use a product or define success. The book calls for research to be systematic, objective, focused, and actionable. It also recommends preparing the practical details early, from participant selection and materials to roles, schedules, and follow-up. A clear purpose makes it easier to choose the right game and avoid collecting interesting but unusable feedback.
This is a useful antidote to research as ritual. Decision science distinguishes information that is merely interesting from information that could change a choice. Naming the decision first makes that distinction explicit and improves the odds that a team will use what it learns. There is a tension, however: tightly defined questions can suppress discovery. A strong plan should specify the decision at stake while leaving room for findings that challenge the team's assumptions or reveal a different problem.
Have customers sell their ideal product to reveal the benefits behind features.
Make value visible. In Product Box, customers create a package for the product they would want to buy, using blank boxes and simple craft supplies. They can add product names, claims, images, prices, and anything else they think belongs on the package. Then they pitch the box to the team and to one another. That sales moment matters: customers often explain the benefit behind a feature when they have to persuade someone else to care.
Listen for the language. A team can compare customer-created claims with its own marketing and product plans. The book describes how common slogans across several boxes can give a team language customers already find meaningful. The exercise can also surface what customers value beyond a feature list, including ease of use, support, price, and confidence in the product.
The sales pitch turns an abstract preference into a small act of persuasion. That can help distinguish a feature customers merely tolerate from one they would actively use to explain a purchase. It also resembles a projective technique: people express their priorities through an imagined artifact rather than a direct interview answer. The limitation is that packaging rewards bold claims and neat stories. Teams should treat the box as a way to generate hypotheses, then check whether the promised benefits appear in actual use.
Offer outrageous ideas to see which impossible feature hides a practical need.
Use surprise carefully. Give Them a Hot Tub asks a team to present customers with proposed features, including deliberately outrageous ones. Customers can accept an idea, reject it, or transform it into something more useful. For example, a fanciful fountain pen that could cut glass might be reshaped into a request for a stronger, longer-lasting nib. The valuable information is often in that transformation, not in whether the original idea is feasible.
Follow the discomfort. An unusual proposal can prompt customers to explain why it is appealing, irritating, or irrelevant. The team should record both the original suggestion and the customer's revised version, then ask what problem the revised idea solves. This game requires careful preparation: if ideas are too ordinary, they may not provoke fresh thinking; if they are too absurd, customers may dismiss the exercise altogether.
The method resembles creative provocation: a deliberately distorted prompt can loosen assumptions and make a hidden requirement easier to name. The transformation is especially useful because it moves discussion from an entertaining concept toward the need beneath it. But novelty is not automatically insight. A clever response may reflect the social pleasure of improvising, rather than demand for a product change. The best interpretation asks what recurring task or frustration the transformed idea points toward, then checks that signal elsewhere.
Ask customers to remember a successful future, then trace how it came about.
Make success concrete. Remember the Future asks customers to imagine that a chosen date has passed and your product has helped them succeed. They describe what the product will have done, in as much detail as possible. Framing the question as a remembered outcome, rather than an open-ended prediction, encourages customers to explain the sequence of events that led to success.
Choose the horizon. A short horizon can illuminate near-term product decisions; a much longer one can support strategic discussion. The book describes using this activity to develop a five-year vision for an organization. The point is not to claim that customers can predict the future. Their imagined account reveals what they count as success and which changes they believe would help them reach it.
The exercise turns a vague future into a causal story. That is useful because people often understand desired outcomes more clearly when asked to explain what would have made them possible. It shares a logic with pre-mortems and scenario planning, which use imagined futures to surface assumptions. The method should not be mistaken for forecasting: confidence and detail can make a scenario sound probable without making it so. Its strongest use is uncovering success criteria and possible pathways, not treating the imagined future as a commitment.
Make customers negotiate scarce feature budgets to expose real trade-offs.
Create a constraint. In Buy a Feature, a team presents possible features with prices and gives customers a limited amount of play money. Customers purchase what they want, sometimes pooling their money to afford an expensive option. The constraint prevents every feature from being an easy yes. Discussion shifts from individual wish lists to trade-offs among customers with different priorities.
Read the negotiation. The team learns not only which features are purchased, but who argues for them, who joins a shared purchase, and what benefits customers cite. The book recommends enough features and pricing variation to make choices meaningful, while avoiding the false promise that a purchase guarantees delivery. The results can inform prioritization, but they should not be treated as a literal sales forecast or as proof that every customer would spend real money the same way.
Scarcity can reveal preferences that a simple rating scale conceals. When one person's choice competes with another's, priorities acquire a social and economic shape. This is close to a choice experiment, but the game adds negotiation and peer influence. That is both its strength and its caveat: customers may buy a feature to support a colleague or win a discussion. The exercise is most informative when observers capture the reasoning and group dynamics, not merely the final shopping list.
Compare features one at a time until customers can defend a clear priority order.
Force distinctions. In 20/20 Vision, the team writes one feature on each card and asks customers to place each new card above or below the features already ranked. Customers compare relative importance instead of assigning every item the same rating. They can also discuss design alternatives, such as choosing a cheaper plastic casing or a more durable metal one.
Check the technical picture. The customer ranking is an input, not the final roadmap. Engineering may identify dependencies: a feature customers rank low could be necessary for a higher-ranked capability. The book also suggests comparing priorities across customer groups and other stakeholders, then weighting those views according to strategic importance. The process creates a clearer order, while preserving the reasons and trade-offs behind it.
Relative ranking reduces the escape hatch of declaring everything important. It can also make disagreement useful: different groups may rank the same feature differently for understandable reasons. A single ordered list, though, can imply more precision than the discussion supports. Rankings can shift with wording, the features shown, or the order in which cards appear. Teams should preserve the reasoning, compare alternative weightings, and treat the ranking as a structured conversation rather than a mathematically final answer.
Watch customers in context; stated use misses timing, workarounds, and hidden effort.
Study real work. Several games uncover how products fit into customers' lives. Start Your Day uses calendars or timelines to show when a product is used. Show and Tell asks customers to bring artifacts they create or change with a product. Me and My Shadow involves observing customers as they work, while The Apprentice asks the product team to perform the customer's job. Each method makes a different part of use visible.
Look beyond the interface. A product may be used differently at home and at work, at the start and end of a day, or during routine and exceptional tasks. An artifact a customer never uses can be as revealing as one they rely on. Direct observation may uncover workarounds or friction customers forget to mention, but it requires respect for customer privacy, preparation, and careful recording.
These methods address the gap between what people say they do and what their setting makes possible. Contextual inquiry and ethnographic research use the same basic insight: behavior is shaped by tools, routines, other people, and local constraints. Observing work can reveal those forces, while asking the team to perform the job can build empathy. Still, observation changes behavior, and a short visit captures only a slice of practice. Repeated visits and customer review of interpretations can reduce overconfident conclusions.
Map the customer's product ecosystem before deciding where your offering should end.
Draw the connections. Spider Web places a product or service at the center of a page. Customers add related products, people, locations, companies, or systems, then draw connections and explain when and why they matter. The result may reveal relationships the product team had not considered, such as a software tool's dependence on another service or the way a product is used in a particular place.
Look for openings. Those connections can suggest partnership opportunities, integration needs, or a clearer boundary for the product. They can also reveal how customers organize a task across several offerings. The map is not meant to be a tidy technical diagram. Customers may produce messy, overlapping webs; that messiness can reflect the complexity of their actual environment and provide useful starting points for follow-up questions.
A product rarely competes or creates value in isolation. Ecosystem mapping helps teams notice complements, dependencies, and handoffs that feature-focused research can miss. In systems thinking, the connections often explain more than the individual components. The important caution is that a line on a map does not establish a causal or commercial opportunity. Teams need to ask what flows across the connection, who controls it, and what failure or improvement means to the customer before investing in an integration or partnership.
Treat roadmaps as living trees, including support roots, not just feature lists.
Shape the whole product. Prune the Product Tree represents a product as a tree. Existing features sit nearer the trunk, while future ideas extend toward the outer canopy. Customers add desired features, move or remove existing ones, and shape the growth of branches. The metaphor invites them to consider balance and development over time rather than simply vote on a list.
Include the roots. Support, training, service, and other infrastructure can be represented as roots that sustain the product. Customers may show that one area needs growth, another is already crowded, or a current feature should be pruned. The resulting trees can be compared with the existing roadmap. Differences help teams see where their plans reflect customer priorities and where the product's supporting services may be neglected.
The tree metaphor gives product evolution a spatial and temporal logic. It helps make dependencies and imbalance visible, and it reminds teams that a product includes the support system around its features. This is a stronger representation than a flat backlog for strategic discussion. Yet metaphors also constrain what participants notice: a tree suggests organic growth, while some products change through abrupt platform shifts or regulatory demands. The drawing is most useful as a lens on priorities, not as a literal model of the product's future.
Turn complaints into ranked anchors, not live arguments about who is right.
Give frustration a form. In Speed Boat, customers imagine the product as a boat held back by anchors. Each anchor records something they dislike or find obstructive; customers can estimate how much faster the boat would move if it were removed. They may also indicate agreement with other people's anchors. This gives criticism a shared, visible structure and helps identify which problems feel most consequential.
Listen before answering. The facilitator reviews the anchors without defending the product or promising an immediate fix. The team later sorts the feedback by issue, severity, and urgency, checking it against existing problem records where appropriate. A complaint may point to a product defect, confusing documentation, an unmet expectation, or a wider service problem. The aim is to understand what is slowing customers down before deciding what to change.
The metaphor makes negative feedback easier to discuss without turning the session into a courtroom. It externalizes the problem, helping customers compare concerns while giving the team time to interpret them. That psychological safety is valuable, especially when customers depend on the product. But visibility can make a single vivid complaint look more prevalent than it is. The number of anchors is not a market statistic. Teams should investigate severity and recurrence separately, then tell customers how the concern was handled.
Close the loop with customers, or participation becomes theater.
Turn observations into decisions. After a game, teams should photograph customer-created materials, organize observer notes, discuss what worked, and prepare an internal account of findings and intended actions. The book warns that post-processing takes real effort; one team estimated eight person-hours and ultimately needed more than eighty. Planning time for this work is part of running the research, not an administrative extra.
Report back. Customers should receive a timely summary showing what the team learned and how it plans to respond. The team should avoid making promises during the game before it has assessed feasibility and dependencies. It should also be candid when feedback will not lead to a change. This closes the relationship loop, manages expectations, and gives customers evidence that their contribution was taken seriously.
Feedback without response can erode trust more quickly than no invitation at all, because participation creates an expectation of influence. Closing the loop is therefore not merely courtesy; it is part of the research method. It helps participants correct misunderstandings and gives the organization a record of how evidence entered a decision. There is also a governance challenge: teams should distinguish listening from promising. Transparent explanations of trade-offs preserve credibility even when a requested change is declined.
Analysis
Innovation Games treats customer understanding as something a team constructs with customers, not something extracted by asking them for a feature list. Its central move is methodological: use a concrete activity to elicit forms of evidence that ordinary conversation often misses. A box makes value claims visible, a constrained purchase exposes trade-offs, a timeline restores context, and a drawing externalizes relationships. Each format changes what customers can express and what observers can notice.
The approach is strongest when the product is complex, use is situated, and customers struggle to articulate needs directly. It also brings product teams into contact with the raw material of customer experience, reducing dependence on filtered summaries. The book's emphasis on preparation and follow-through is essential because an engaging session alone produces only artifacts and impressions. The value comes from disciplined interpretation, comparison with other evidence, and visible action.
Its main limitation is one common to qualitative research: a vivid session is not a representative sample. Participants may self-select, group dynamics can amplify confident voices, and play money or hypothetical futures do not perfectly reproduce real buying behavior. The activities should therefore generate and refine hypotheses, not establish market prevalence or forecast demand. Teams can strengthen conclusions by including varied customer segments, recording dissent as well as consensus, and checking patterns against usage data, support records, or broader surveys.
The book's enduring contribution is to make customer research an operational practice rather than a periodic report. It offers a repertoire of structured ways to see what customers value, struggle with, and connect to their wider systems. The deeper lesson is that better products require more than listening politely. They require designing situations in which customers can reveal how they think, work, choose, and define success, then showing that the organization learned something consequential from the exchange.
Review Summary
Innovation Games receives mixed reviews, with an average rating of 3.96 out of 5. Readers appreciate the creative ideas for gathering customer input and the detailed explanations of each game. Some find the book practical and useful for product development, while others feel it oversimplifies concepts. The games are praised for their potential in requirements gathering, prioritization, and fostering collaboration. However, some reviewers note that the content isn't groundbreaking and may be challenging to implement effectively. Overall, it's seen as a valuable reference for product managers and marketers.
People Also Read
Glossary
Innovation Games
Collaborative customer researchStructured activities that help teams learn about customer needs through making, mapping, observing, negotiating, or prioritizing. Customers and product teams interact directly, producing both discussion and visible artifacts. The games can support market research, product planning, customer relationships, and new product discovery, but their qualitative results require interpretation rather than statistical generalization.
Product Box
Customer-designed product packageAn activity in which customers use a blank box and simple materials to represent the product they would want to buy. They add claims, images, features, and other details, then present the box as if selling it. The presentation can expose valued benefits, customer language, and expectations that a direct request for features may not uncover.
Give Them a Hot Tub
Transform outrageous feature ideasA game in which customers react to proposed product features, including deliberately outrageous ones. They can accept, reject, or transform each idea. The transformation can reveal an underlying need, such as changing an implausible feature into a practical improvement. The team records both the original idea and the customer's reasoning.
Remember the Future
Describe success retrospectivelyAn activity that asks customers to imagine a future date when a product has helped them succeed, then explain what it will have done. Framing the outcome as already accomplished encourages a more detailed account of the path to success. It is useful for exploring success criteria and possible product direction, not for predicting the future.
Buy a Feature
Negotiate feature prioritiesA prioritization game in which customers receive limited play money and purchase features priced by the team. Because the budget is constrained, participants must choose, negotiate, and sometimes pool money for expensive features. The results reveal preferences and trade-offs, while discussion helps explain why customers value particular capabilities.
20/20 Vision
Rank features comparativelyA game for ordering features by relative importance. Customers compare each new feature with those already ranked and place it above or below them, rather than assigning every feature an equal rating. Discussion can also explore design alternatives. The customer ranking informs planning, but dependencies and other stakeholder needs may affect the final roadmap.
Start Your Day
Map product use over timeAn activity in which customers use calendars or timelines to show when and in what circumstances they use a product. The time scale can range from parts of a day to seasons or recurring annual events. Mapping use over time can reveal changes in context, routines, and needs that a general question about product use may miss.
Show and Tell
Present product-created artifactsCustomers bring examples of materials created or changed through using a product, then explain when and why those artifacts matter. The materials might include reports, documents, or other outputs. Seeing actual work products helps teams distinguish essential outputs from unused ones and identify how customers rely on the product in practice.
Me and My Shadow
Observe customers at workAn observational activity in which a team member follows customers as they use a product or perform related tasks. The observer asks occasional clarifying questions and records the setting, actions, and work products. Its purpose is to uncover routines, workarounds, and needs that customers may not remember or know to mention in an interview.
The Apprentice
Perform the customer's workA technique in which product team members learn by doing the work their customers do, using relevant tools and working in the customer's environment where possible. The experience can build empathy and reveal practical constraints. It differs from simply using one's own product because the team attempts to understand the customer's task and context.
Spider Web
Map product relationshipsA mapping activity that places a product at the center and asks customers to draw related products, people, organizations, or places around it. Customers connect the elements and explain the relationships. The resulting map can uncover dependencies, integration needs, complementary offerings, and aspects of the customer's environment that shape product use.
Prune the Product Tree
Shape product evolution visuallyA roadmap activity that represents a product as a tree. Current features sit nearer the trunk, while proposed features extend toward the outer canopy. Customers add, move, or remove features to shape future growth. Roots can represent supporting services such as training or customer care, reminding teams that product evolution includes more than features.
Speed Boat
Identify product pain pointsA feedback game in which a product is pictured as a boat slowed by anchors. Customers write problems or frustrations on anchor cards and can indicate which concerns they share or how much each affects progress. The team reviews the issues without arguing in the moment, then assesses their causes, severity, and urgency.
FAQ
What's "Innovation Games: Creating Breakthrough Products Through Collaborative Play" about?
- Purpose of the book: "Innovation Games" by Luke Hohmann is about using collaborative play to engage customers in the product development process. It aims to help businesses understand customer needs and drive innovation.
- Games as a tool: The book introduces a series of games designed to gather insights from customers, which can be used to create breakthrough products and services.
- Customer-centric approach: It emphasizes the importance of viewing product development from the customer's perspective to ensure that the final product meets real market needs.
Why should I read "Innovation Games: Creating Breakthrough Products Through Collaborative Play"?
- Innovative approach: The book offers a unique method for engaging with customers that goes beyond traditional market research techniques.
- Practical applications: It provides actionable strategies that can be implemented in various business contexts to enhance product development.
- Customer engagement: By reading this book, you can learn how to build stronger relationships with customers and gain deeper insights into their needs.
What are the key takeaways of "Innovation Games: Creating Breakthrough Products Through Collaborative Play"?
- Games as research tools: Innovation Games are effective tools for qualitative market research, helping to uncover customer needs and preferences.
- Collaboration leads to innovation: Engaging customers through games fosters a collaborative environment that can lead to innovative product ideas.
- Understanding customer perspective: The book emphasizes the importance of understanding the customer's point of view to create products that truly meet their needs.
What are the best quotes from "Innovation Games: Creating Breakthrough Products Through Collaborative Play" and what do they mean?
- "Innovation Games is one of those books you don’t know you need until you read it." This quote highlights the book's unexpected value in transforming how businesses approach product development.
- "Luke’s book fills a gap in the bookshelf." This suggests that the book offers unique insights not commonly found in other product development literature.
- "The key to innovation isn’t some stuffy process; it is creating a collaborative, interactive, visually-oriented, fun, business-value-driven environment." This quote encapsulates the book's core philosophy that innovation thrives in a playful and engaging environment.
How do Innovation Games differ from traditional market research techniques?
- Engagement and fun: Unlike traditional surveys or focus groups, Innovation Games are designed to be engaging and fun, encouraging more honest and creative feedback from customers.
- Multidimensional communication: The games leverage multiple dimensions of communication, such as visual and spatial, to gather richer data.
- Direct customer interaction: The games involve direct interaction between the product team and customers, fostering a deeper understanding and empathy.
What are some examples of Innovation Games mentioned in the book?
- Product Box: Customers create a box for their ideal product, which helps reveal what features and benefits they value most.
- Speed Boat: Customers identify what holds back a product (anchors) and suggest improvements, providing insights into pain points.
- Buy a Feature: Customers use play money to purchase features they want in a product, helping prioritize development efforts.
How can businesses implement the strategies from "Innovation Games"?
- Select appropriate games: Choose games that align with your business goals and customer needs.
- Prepare thoroughly: Ensure you have the necessary materials and a clear understanding of the game's objectives before playing.
- Engage cross-functional teams: Involve team members from different departments to gain diverse perspectives and insights.
What is the process for planning and executing an Innovation Game?
- Define objectives: Clearly outline what you hope to achieve with the game and what questions you want answered.
- Select participants: Choose a representative group of customers who can provide valuable feedback.
- Facilitate effectively: Guide the game to ensure productive discussions and capture all relevant insights.
How do Innovation Games help in understanding customer needs?
- Direct feedback: The games provide a platform for customers to express their needs and preferences directly.
- Visual representation: Many games involve creating visual artifacts, which can reveal insights that might not emerge through verbal communication alone.
- Collaborative environment: The interactive nature of the games encourages customers to share ideas and build on each other's suggestions.
What are the potential challenges of using Innovation Games?
- Customer participation: Some customers may be hesitant to engage in games, requiring careful selection and preparation.
- Facilitation skills: Effective facilitation is crucial to ensure the games run smoothly and yield valuable insights.
- Data processing: The qualitative nature of the data collected can be complex to analyze and requires careful interpretation.
How can Innovation Games be customized for different business contexts?
- Tailor the games: Modify the games to fit the specific needs and goals of your business or industry.
- Adjust the format: Consider the size of the group and the setting to ensure the games are effective and engaging.
- Incorporate feedback: Use insights from previous games to refine and improve future sessions.
What role do facilitators play in Innovation Games?
- Guide the process: Facilitators are responsible for explaining the games, managing time, and ensuring productive discussions.
- Encourage participation: They help create an environment where all participants feel comfortable sharing their ideas.
- Capture insights: Facilitators ensure that all valuable insights are recorded and can be used to inform product development.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.