--- title: "How to Prioritize Features with MaxDiff and Kano | Minds" canonical_url: "https://getminds.ai/guide/how-to-prioritize-features-with-maxdiff-and-kano" last_updated: "2026-07-02T00:17:30.688Z" meta: description: "How to Prioritize Features with MaxDiff and Kano for market researchers using Minds as a planning layer before formal fieldwork." "og:description": "How to Prioritize Features with MaxDiff and Kano for market researchers using Minds as a planning layer before formal fieldwork." "og:title": "How to Prioritize Features with MaxDiff and Kano | Minds" "twitter:description": "How to Prioritize Features with MaxDiff and Kano for market researchers using Minds as a planning layer before formal fieldwork." "twitter:title": "How to Prioritize Features with MaxDiff and Kano | Minds" --- Minds Guide·Minds Team # **How to Prioritize Features with MaxDiff and Kano** How to Prioritize Features with MaxDiff and Kano for market researchers using Minds as a planning layer before formal fieldwork. [Try Minds](https://getminds.ai/?register=true) Feature Prioritization Research is a research planning workflow for combining feature importance and satisfaction reactions. It gives a research team a disciplined way to turn a vague business question into choices, scales, tasks, or prompts that respondents can answer consistently. The value is not the label of the method. The value is the discipline it forces: a defined target group, a clear decision, realistic stimuli, and an analysis plan that is chosen before the answers arrive. For a Minds workflow, treat Feature Prioritization Research as a planning template before fieldwork. Select the target group first, then ask Minds to suggest the right subsections, question wording, segment cuts, and interpretation risks for that audience. This is useful when a team has research intent but has not yet translated it into respondent-ready language. ## When to use it Feature Prioritization Research fits when the research decision is which product features are must-haves, differentiators, or low-priority ideas. It is strongest when the team can describe the population and the stimulus clearly. If the audience definition is fuzzy, the first task is not to write survey questions. The first task is to use Minds to pressure-test the target-group definition, surface missing subsegments, and identify which assumptions need evidence before a human study is fielded. Feature Prioritization Research is less useful when the team only wants a broad brainstorming session. In that case, a panel discussion or qualitative interview flow will usually produce more useful material. This template should be used when the answer has to be compared, ranked, scored, diagnosed, or converted into a structured research brief. ## Questions and configuration Start with the target group: who should answer, what context they are in, and what they already know about the product, category, or brand. Then define the stimulus. A stimulus can be a concept paragraph, a landing page, a pricing table, feature list, message set, customer journey, prototype screenshot, or diary prompt. Finally, define the output format. For Feature Prioritization Research, the useful output is a better feature-prioritization research plan. Minds can suggest draft subsections such as screener logic, warm-up questions, core tasks, follow-up probes, segmentation cuts, and analysis notes. The safest pattern is to ask for one section at a time. Ask Minds to critique each question for leading wording, double-barreled phrasing, unrealistic assumptions, and missing answer options before the instrument is used with real respondents. ## Method vocabulary Use the product-facing terms deliberately so the template matches how market researchers already frame the work: - MaxDiff, Best-Worst Scaling, Kano, must-be features, performance features, and delighters. - feature trade-offs, roadmap priority, satisfaction risk, and indifference signals. - a method sequence that separates feature classification from relative importance. In Minds, these terms should appear as configuration hints and critique criteria. The practical value is that a target group can react to clearer instruments before the team spends time on survey programming or respondent recruitment. ## How Minds fits the workflow Minds should sit before the formal research system of record. Use it to turn a brief into a stronger method design, to rehearse how different segments may interpret the stimulus, and to find the objections that the final questionnaire should measure. The platform is especially useful for deciding whether the method is the right one for the target group before budget is spent on programming, recruiting, or moderation. A practical workflow is simple. Create or select the target group. Select Feature Prioritization Research as the research frame. Paste the stimulus or describe the decision. Ask Minds for suggested sections, questions, and configuration. Review the draft like a researcher would review a junior analyst's first pass. Then move the final instrument into the human-fielded survey, interview, or specialist tool when the decision requires formal evidence. ## Limits and validation Feature Prioritization Research still needs methodological judgment. Minds can help with wording, target-group reasoning, and likely interpretation, but it should not be used as the final source for representative statistics, regulatory claims, precise market sizing, formal utility estimation, or final price elasticity. The higher the financial or compliance stakes, the more important it is to validate with real respondents and a qualified research design. The main risk is false precision. A polished synthetic answer can sound more certain than the underlying evidence allows. Counter that by asking Minds to list assumptions, identify where human data is required, and separate qualitative interpretation from quantitative measurement. ## Starter template - Target group: current users, target buyers, or buying committee members. - Research decision: which product features are must-haves, differentiators, or low-priority ideas. - Core stimulus: a product roadmap list and feature descriptions. - Main task: classify features with Kano logic and rank trade-offs with MaxDiff logic. - Analysis lens: must-have status, delight potential, relative importance, and ambiguity. - Validation note: use real respondents or a specialist statistical workflow when the output must support a final external claim. ## Next step Use this page as the first draft of the in-product template. The product version should let a user choose the target group, choose Feature Prioritization Research, and receive suggested sections, questions, configuration defaults, and warnings that match the audience and the decision at hand. ## **Frequently asked questions** ### **What is Feature Prioritization Research best for?** Feature Prioritization Research is best for combining feature importance and satisfaction reactions. Use it when the team needs a structured instrument rather than a loose discussion prompt. ### **Can Minds replace the final Feature Prioritization Research field study?** No. Minds is best used to draft, rehearse, and refine the research design before formal fieldwork. When the decision needs representative statistics, recruit real respondents or use the required specialist tool for final estimation. ### **What should I configure before using this template?** Define the target group, the decision you are trying to make, the stimulus or product options, the answer scale, and the success criteria before asking Minds to suggest questions or subsections. ### **What output should I expect from Minds?** Expect better hypotheses, sharper wording, segment-level objections, and a cleaner survey brief. Treat the output as directional research planning input, not as a certified measurement on its own.