# Questioning

Turn Curiosity Into ClarityEvery signal starts with a question. Questioning turns curiosity into measurable clarity. It transforms hunches into testable direction and helps teams prove whether their ideas truly make sense.When questioning is strong, it reveals not just what people say, but what they actually understand, expect, and value. Weak questions collect noise. Strong ones expose truth. They uncover the gap between what users intend to do and what the design allows them to do.Questioning is where ideas take shape. It links Concepts to Hunches, converts them into Questions, and produces Findings that become usable signals.What Good Questioning DoesSurfaces hidden user challenges.Avoids bias so feedback reflects reality, not team assumptions.Guides the design process with targeted insights.Translates raw curiosity into measurable data.Here’s how to start questioning:Getting StartedBegin QuestioningMake It PracticalSee It in ActionApply and EvolveGETTING STARTEDWhy Questioning MattersQuestioning gives shape to curiosity. It turns the first spark of an idea into something measurable. When done well, it reveals how people think, where they hesitate, and whether the design makes sense.In Glare, Questioning lives in theMeasurelayer. It connects early hunches to evidence and makes sense of what users show and say.Strong questioning is not about asking more. It is about asking with intent. Each question defines what you need to learn and what kind of evidence will make that learning useful. This is where ideas stop being assumptions and start becoming measurable signals.ElementWhat It Focuses OnHow It Connects to QuestioningConceptsThe initial ideas or experiences that need understanding.Questioning defines how these ideas will be evaluated.HunchesEarly beliefs about what might work for users.Questioning helps expose whether those beliefs hold true.QuestionsFocused prompts that clarify what to measure and why.Questioning turns curiosity into structured investigation.FindingsPatterns that emerge from user responses and behaviors.Questioning provides the input that becomes measurable proof.When these four elements work together, teams move from guessing to learning with purpose. Concepts and hunches feed into questions that generate findings.Findings then guide decisions and shape the next round of work.What Kind of Questions Are You AskingEvery project begins from a different angle. The questions you ask depend on what you want to uncover. These four types help you see where to focus and how to connect questions to measurable outcomes.TypeWhat It Focuses OnPurposeExamplePeopleThe motivations, preferences, and habits of your users.Learn who your users are and what drives their behavior.“How often do users complete this workflow?”ProcessThe steps and decisions users make to achieve a goal.Understand where friction occurs and what slows progress.“What steps do users take to upload a file?”ProductThe clarity and usefulness of what has been designed.Evaluate how users understand and interact with your solution.“Do users understand the purpose of this page?”ProblemThe barriers that prevent success or satisfaction.Uncover what breaks down, confuses, or causes frustration.“What prevents users from completing checkout?”Good questioning combines these types. People and Process questions give you context. Product and Problem questions give you clarity. Together they expose both how users behave and why they behave that way.What Makes a Question TestableA testable question:Defines a gap in understanding.Points to observable behavior or perception.Can be measured and acted upon.❌ “Do people like our homepage?”✅ “Can users find pricing info on the homepage within 5 seconds?”Strong questions are not opinions. They are hypotheses that lead to proof. They reveal what to test, what to measure, and what change will matter next. Before finalizing, test your questions with teammates or even users.Ask a colleague or team member to review your questions.Try running a small dry test.Check if users understand what’s being asked.What Mode of Questioning Fits Your GoalOnce you know the type of question, choose the mode of learning that matches your goal. Modes describe the intent behind the question, whether you are discovering, evaluating, or comparing.ModeWhen To UseCore QuestionWhat You GetExploratoryEarly discovery, before you have firm hypotheses.What should we learn or improve?Patterns, context, and unmet needs.EvaluativeMid-cycle, once ideas or designs exist.Does this design work for users?Clarity, comprehension, and usability metrics.ComparativeLater, when choosing between directions.Which version performs or communicates better?Confidence and measurable proof of improvement.Exploratory work builds understanding. Evaluative work strengthens clarity. Comparative work provides confidence in what to move forward with. When teams choose the right mode for their goal, every question becomes a step toward a usable signal.BEGIN QUESTIONINGA stepped process for creating testable questionsEach step in Questioning brings your hunches closer to evidence. Strong questions emerge through focus, not guessing, not consensus, but clarity about what you need to learn and how you will prove it.Each step follows the rhythm of Measure:Concepts→Hunches→Questions→FindingsSTEP 1Clarify the conceptStrong questions begin with clarity. Use the hunches and assumptions defined in your earlier activities to shape what you need to prove or disprove.At this stage, your concept is the focus, the product, flow, or message you want to understand. Your hunches are the beliefs that guide it. Your goal is to make those beliefs visible so you can test them.Ask yourself:What assumptions are we making about how users will act or respond?What part of this concept do we most need to understand?What outcomes are we hoping to confirm or challenge?What would success look like if our hunch is correct?Clarity comes from defining what you believe now, so you can see what needs to be questioned next.STEP 2Identify knowledge gapsNow turn those hunches upside down. This step surfaces what youdon’tknow, the spaces where understanding is weak or uncertain.Ask:What assumptions haven’t been tested?Where do we lack proof or confidence?What do we think we know but can’t yet show with data?What would surprise us if it turned out to be false?Identifying gaps creates focus. You move from broad curiosity to specific uncertainty, and that uncertainty becomes the seed of a testable question.STEP 3Define learning goalsLearning goals translate uncertainty into direction. They describewhat kind of learningis needed: exploratory, evaluative, or comparative.ModeWhen to UseLearning GoalExampleExploratoryEarly stages, when little is known.Discover unmet needs or behaviors.“Understand how users choose between two plan types.”EvaluativeMid-stage, when testing an existing concept.Measure clarity, usability, or comprehension.“See if users can complete checkout without confusion.”ComparativeLater stages, when choosing between options.Decide which version performs better or builds more trust.“Compare two headlines to see which drives more sign-ups.”Learning goals define intent. They help you decide what kind of question to ask and what kind of signal to look for.STEP 4Write open-ended research questionsOpen-ended questions explore user perception and experience without assumption. They should help you understand behavior, language, and decision-making.Examples:What do users expect when they first see this page?How do they describe the purpose of this feature in their own words?What steps do they take when they get stuck?Avoid confirming what you already think. Instead, use questions that let users reveal how they actually understand the concept.Avoiding Bias and Leading QuestionsBias often sneaks in when teams write questions that reflect their own expectations. It leads users toward “right” answers and creates false confidence. Effective questioning stays neutral. It focuses on learning, not validation.Bias Check:Is this question leading users to say “yes”?Does it echo our internal assumptions?Is the language emotionally charged or too technical for real users?Neutral questions surface what people actually experience. They turn curiosity into honest feedback.STEP 5Translate into testable questionsOnce your research questions are clear, turn them into measurable prompts. A testable question should show observable behavior or perception.Examples:Can users find the pricing information within five seconds?Can users complete checkout without help?Do users understand what this feature does after reading the headline?Testable questions point directly to data. They make it possible to gather real evidence, not opinions.STEP 6Align questions with UX metricsEvery testable question should connect to a UX metric. This is how questioning links to measurement and signals.UX Metric TypeWhat It RevealsExample QuestionExample MetricBehavioralWhat users do.Where do users click first?First Click SuccessAttitudinalWhat users think or feel.How satisfied are users after completing the task?Satisfaction or Sentiment ScorePerformanceHow efficiently users succeed.How long does it take to complete checkout?Time on TaskPerceptualWhat users understand or interpret.Do users understand the purpose of this page?ComprehensionA good alignment makes every answer measurable and every result comparable across projects.STEP 7Prioritize and RefineMost teams have more questions than time, people, or budget to answer them. Prioritization ensures your effort goes where it matters most.Consider these filters:FactorWhat It RevealsHow to Use ItGap SizeThe degree of uncertainty or risk in your current understanding.Focus on areas with the least clarity or highest unknowns.ImpactThe potential value of answering the question.Prioritize questions tied to decisions that affect users or outcomes directly.FeasibilityThe time, cost, and resources available.Choose what can realistically be tested in the current cycle.ConfidenceThe team’s belief in current assumptions.Address low-confidence areas first to strengthen overall direction.Questions that sit at the intersection of large gap + high impact + feasible effort should rise to the top. Refine them for clarity. Remove duplicates or overlap. Keep only those that lead directly to action.STEP 8Match Questions to TechniquesSelect the technique that will produce the clearest signal for your question.Technique FocusCommon MethodsTypical MetricsExample QuestionBehavioralFirst-click tests, task success analysisCompletion, engagement, navigation clarity“Where do users click first on this page?”AttitudinalSurveys, desirability studies, satisfaction scoringTrust, sentiment, satisfaction“How confident do users feel after completing this task?”PerformanceUsability tests, time tracking, error rateEfficiency, error reduction“How long does it take to complete checkout?”Define Collecting TechniquesThe Glare Questioning Canvas has been designed as a full-featured Figma-style layout using React components with form-style input boxes and a light theme.MAKE IT PRACTICALPlan Your Questioning CycleUse this worksheet to guide your next cycle of questioning. Each step helps you move from idea to measurable clarity.StepActionOutput1. Clarify the ConceptIdentify the idea or assumption you want to explore.Clear articulation of what you believe and want to learn.2. Identify GapsList the uncertainties or missing knowledge areas.Focused list of what you do not yet understand.3. Define Learning GoalsChoose whether you are exploring, evaluating, or comparing.Framed goals that define what success looks like.4. Write QuestionsDraft open-ended questions that will reveal user understanding.Structured list of user-focused prompts.5. Make Them TestableTranslate each question into a measurable version.Test-ready questions linked to metrics.6. Align With UX MetricsAssign metrics to track clarity, satisfaction, and success.Consistent measurement plan across studies.7. PrioritizeEvaluate which questions are most valuable or feasible now.Ranked question list ready for testing.8. Match to TechniquesSelect the right testing or research methods.Plan of which tools and techniques to use.When complete, this worksheet becomes your roadmap for running focused, measurable questioning cycles.Quick ChecklistBefore you run your next round of questioning, confirm the essentials:We’ve defined a single concept or assumption to explore.We’ve identified what we don’t understand yet.Our learning goal is clear — exploratory, evaluative, or comparative.Each question connects to a UX metric.We’ve prioritized based on gaps, impact, and feasibility.Our techniques and tools are ready to run.The results will connect to findings that move design forward.Strong questioning is less about volume and more about precision.If each question is linked to an assumption, a method, and a measurable outcome, you are ready to collect meaningful data.How to Integrate Questioning Into WorkflowQuestioning becomes powerful when it is built into your daily and weekly work. Instead of a one-time activity, it becomes a habit that shapes how your team frames every problem and measures every outcome.Each round of questioning strengthens clarity.You learn which questions surface real insight, which ones stall, and which lead directly to measurable signals. Over time, this practice builds discipline, you stop guessing and start learning with purpose.Turn Questioning Into a Repeatable RoutineWeekly Discovery ReviewBegin each week by identifying which assumptions or user behaviors need clarity.Frame these into questions you can test or observe within the week.Sprint PlanningPair every major design or product task with at least one measurable question. Make it visible on the board,  “What do we need to learn before we move forward?”Post-Test ReflectionEnd each sprint or test cycle by reviewing which questions produced usable signals. Note which ones were too broad or biased, and refine them for the next round.Share the Questions, Not Just the AnswersWhen findings are shared, include the questions that led to them. This helps others understand your intent and replicate the method.Build a Question LibraryOver time, collect well-framed, tested questions in a shared workspace. Reuse them as templates for future projects to keep consistency in your measurement approach.Questioning drives measurable improvement across teams.When questions are clear, design moves faster, research becomes actionable, and results connect directly to user needs.BenefitWhat It DeliversFocusTeams align around what to learn next instead of debating opinions.SpeedClear questions shorten the time between testing and decisions.ConfidenceEach question backed by metrics creates evidence leaders can trust.ScalabilityReusing question frameworks builds consistency across projects.Questioning becomes the foundation for every signal you collect. When your process is disciplined, curiosity becomes proof , and design gains the credibility it deserves.SEE IT IN ACTIONHow a single question turned confusion into clarityAPPLY AND EVOLVEGetting It to StickWhen questioning becomes a regular practice, design transforms from assumption to evidence. Teams stop debating what to do and start proving what works. Each round of questioning creates sharper hunches, clearer findings, and stronger signals that guide design.The goal is not just to ask better questions, it’s to build a culture where every decision starts with clarity and ends with measurable proof.Business ImpactConsistent questioning creates measurable advantages across design and product teams.BenefitWhat It CreatesExample ImpactFaster FocusClear learning goals eliminate wasted research.Teams cut discovery cycles by identifying what to test within hours instead of weeks.Better DecisionsQuestions tied to metrics create credible findings.A single comprehension test clarifies which layout works best, saving development time.Cross-Team AlignmentShared questioning frameworks connect research, design, and product decisions.Product, design, and marketing use the same questions to test message clarity.Proven ValueMeasurable questions link user insight to business results.Improved comprehension leads to higher conversion and reduced churn.Questioning helps leaders show evidence of progress and gives contributors confidence that their work drives impact.ReflectionBefore moving to the next phase, take a moment to reflect on what you learned through questioning.Ask yourself and your team:Did our questions address the biggest gaps in understanding?Which questions produced strong findings, and which stayed too broad?Did we link each question to a clear UX metric and measurable outcome?How did the answers change what we decided to do next?What will we ask differently next time?Reflection turns questioning into an evolving skill. Each project becomes easier to frame, test, and measure with confidence.Next StepsQuestioning sits in theMeasurefacet of Glare,  it connects hunches to findings. From here, you transition into synthesizing those findings into clear, comparable signals that inform future design work.If You Are HereMove ToWhat You GainConcepts→HunchesClarify what you believe and what you need to learn.Clear intent for what to test.Hunches→QuestioningTurn beliefs into measurable prompts.Defined questions linked to UX metrics.Questioning→FindingsCollect results and analyze them through metrics.Actionable insights grounded in data.Findings→ SignalsCombine metrics into patterns that prove design impact.Clear, comparable signals that build design credibility.Each question you ask moves you closer to confidence. When teams learn to question with precision, they see patterns faster, share evidence more clearly, and build proof that lasts beyond a single project.Closing ThoughtGood questions are the foundation of design measurement. They connect curiosity to clarity, intent to evidence, and intuition to influence. When your team questions well, design stops being opinion and becomes proof that earns trust.ResourcesUser Research Questions | UX Research Field Guide, by User Interviewshttps://www.userinterviews.com/ux-research-field-guide-chapter/user-research-questionsThe Best User Research Questions (+ How to Ask Them), by Mazehttps://maze.co/blog/research-questions/A Step-by-Step Guide to Writing Better Research Questions, by dscouthttps://dscout.com/people-nerds/guide-better-questionsHow to ask good questions and level-up your user research skills, by Envoy Designhttps://medium.com/envoy-design/how-to-ask-good-questions-and-level-up-your-user-research-skills-19fd28b275a4Crafting good UX research questions for qualitative research, by PlaybookUXhttps://www.playbookux.com/crafting-good-ux-research-questions-for-qualitative-research/The NCredible Framework — UX research questions prioritised, by UX Insighthttps://uxinsight.org/a-practical-tool-for-prioritising-research-questions-and-ensuring-that-they-dont-all-end-up-in-a-usability-test/How to ask the right UX questions and avoid the wrong ones (Reddit)https://www.reddit.com/r/userexperience/comments/oorfjq/how_to_ask_the_right_ux_questions_and_avoid_the/How to write effective UX research questions (With Examples), by Hotjarhttps://www.hotjar.com/ux-research/questions/AI PromptThis prompt helps you turn a research challenge into a set of questions that will actually produce usable signals.Start with a hunch, design decision, or area of uncertainty your team needs to investigate. It guides you to:Sort your questions into the four types: People, Process, Product, and ProblemChoose the right mode for where you are: Exploratory, Evaluative, or ComparativeRun a bias check so no question leads, assumes, or confusesMatch each question to a UX metric and a collection techniqueYou'll end with a prioritized, bias-checked question set ready to use in a test or research session.Use this before any research session or usability test to make sure your questions will produce signals rather than confirmation.AI SkillsThe Questioning skill file teaches your AI the full eight-step process and question taxonomy so it can help you write and refine research questions for any design challenge.Load it when you need to go deeper on the bias check criteria, testable question standards, or building a reusable Question Library across projects. It gives your AI:The four question types with definitions and examples for eachThe three measurement modes with guidance on when to use eachThe full bias check criteria across leading, assumption, emotional, and jargon dimensionsThe metric-and-technique mapping tables for turning questions into collection plansDownload the skill file below to use the full Questioning framework with your AI assistant.