Each clue includes an accepted answer and a short explanation for the reveal.
Customer Problem
100: This statement describes the customer difficulty a product is designed to solve. Answer: Problem statement. A useful problem statement focuses on the customer's situation rather than the product's features.
200: This research activity asks customers about their workflow, frustrations, and desired outcomes. Answer: Customer interview. Customer interviews reveal language and context that analytics alone cannot provide.
300: This framework describes the progress a customer is trying to make in a specific situation. Answer: Jobs to be done. Jobs-to-be-done thinking keeps teams focused on the customer's desired progress.
400: This signal shows that a problem happens often enough or hurts enough to deserve attention. Answer: Problem severity. Frequency and impact help teams distinguish urgent problems from occasional inconveniences.
500: This document summarizes the target user, problem, evidence, constraints, and expected outcome. Answer: Product brief. A product brief gives a cross-functional team a shared definition of the work.
Features
100: This is what the product can do; it should be connected to a customer benefit before a sales conversation ends. Answer: Feature. Features describe capability, while benefits explain why that capability matters.
200: This small in-product explanation helps a user understand a control at the moment they need it. Answer: Tooltip. A tooltip can reduce confusion without forcing the user to leave the current task.
300: This capability lets multiple people work with the same information while controlling access. Answer: Collaboration. Collaboration features should make ownership, edits, and permissions clear.
400: This connection passes information between two products so users do not have to repeat work manually. Answer: Integration. Integrations reduce duplicate entry and help products fit existing workflows.
500: This release approach makes a new capability available to a limited group before a broad launch. Answer: Beta. A beta creates room to learn from real usage before the feature reaches everyone.
Value
100: This outcome reduces the amount of time a customer spends completing a task. Answer: Time savings. Time savings are most persuasive when the before-and-after workflow is measurable.
200: This calculation compares the value received from a product with the cost of using it. Answer: Return on investment. ROI connects the product to financial or operational outcomes.
300: This proof shows how a real customer used the product and what changed afterward. Answer: Case study. A case study makes a product claim more credible by showing context and evidence.
400: This short sentence explains the customer, problem, benefit, and reason to choose the product. Answer: Value proposition. A strong value proposition is specific enough that the intended customer recognizes themselves.
500: This comparison describes the customer's workflow before and after adopting the product. Answer: Before-and-after story. A before-and-after story makes product value concrete and easy to remember.
Demo
100: This is the customer outcome a product demonstration should establish before showing individual controls. Answer: Demo goal. A demo goal keeps the presentation focused on the customer's reason for attending.
200: This short story connects several features into one realistic customer workflow. Answer: Use-case scenario. A scenario makes separate features feel like one coherent solution.
300: This question checks whether the demonstration matches the audience's priorities before moving on. Answer: Confirmation question. Confirmation questions keep a demo interactive and reveal when the presenter should adjust.
400: This prepared backup protects a live demonstration when the network or test environment fails. Answer: Fallback recording or screenshots. A tested fallback keeps the meeting useful when technology does not cooperate.
500: This final demo step ties what was shown to a specific owner, action, and date. Answer: Next step. A clear next step prevents a strong demonstration from ending without momentum.
Feedback
100: This feedback method asks a customer to describe what happened instead of rating a hypothetical idea. Answer: Behavioral interview question. Questions about real behavior tend to produce more reliable evidence than predictions.
200: This metric measures how many people complete a desired step in a workflow. Answer: Conversion rate. Conversion rate helps teams locate friction between intent and action.
300: This research session asks a participant to complete tasks while observers note confusion and success. Answer: Usability test. Usability testing shows where product language or interaction patterns break down.
400: This ranked list balances customer impact, business value, confidence, and effort. Answer: Prioritization. A shared prioritization method makes tradeoffs easier to explain.
500: This loop collects feedback, identifies a pattern, makes a change, and tells customers what happened. Answer: Closed feedback loop. Closing the loop shows customers that their input led to a considered response.
host guide
Turn the idea into a game that fits the group.
Use these practical recommendations while you customize the board and prepare the room.
How to use this template
Click the board tiles to preview every clue and answer. Open the template in the builder to customize it, choose teams, test one clue, and launch the private host controls.
Remote variation
Share the player display, keep host controls private, and choose device buzzers, chat answers, or one captain per team.
In-person variation
Project the board, place participants into teams, rotate the spokesperson, and prepare one tie-breaker before the event starts.
Make it specific
Replace generalized examples with accurate company details, remove confidential information, and add explanations that reinforce the purpose of the session.
more workplace templates
Compare another complete board.
Work template
New Hire Onboarding
Help new employees learn the people, tools, customer habits, security basics, and first-week routines they need to get started.