MDIA1007 Chap.2 Problems, Niches and Value Propositions
Problems, Niches and Value Propositions
Week Two connects design thinking and unmet needs to the first version of a venture idea. This chapter shows how a niche, problem statement and value proposition constrain one another. A useful niche describes a shared situation rather than a huge demographic category. The problem is written without embedding the preferred solution, and the value proposition promises one credible change.
Together these elements give later prototypes and interviews a clear question, while leaving room for the proposed solution to change as evidence arrives.
What this chapter covers
- 01
Niche definition through a shared situation
- 02
Problem statements without embedded solutions
- 03
Current behaviour and workarounds as research evidence
- 04
Value propositions built around a concrete benefit
- 05
Alignment between audience, friction, mechanism and action
- 06
Alternative explanations for a weak response
Worked example · free
Rewriting a broad sustainability idea
- +1Select a situation: renters in older apartment buildings who cannot change shared waste facilities.
- +1Describe the friction: item-specific disposal guidance is scattered, so residents postpone or guess when an item is unfamiliar.
- +1State the value claim: a building-aware lookup may provide a faster confident disposal choice than searching several generic pages.
Key terms
- Niche Context
- A focused situation shared by people whose problem and behaviour can be investigated together.
- Problem Statement
- A concise account of an audience, situation and observable friction that does not assume one solution.
- Current Workaround
- The method people already use to manage a problem, including its costs and limitations.
- Value Proposition
- A testable claim about the benefit a proposed mechanism may deliver to a defined audience.
- Claim Alignment
- Consistency among the niche, problem, promised benefit, prototype and requested action.
Problems, Niches and Value Propositions FAQ
How narrow should the first niche be?
It should be narrow enough that participants share a recognisable situation, problem frequency and motivation. The niche is a learning boundary, not necessarily the venture's permanent market. A focused group makes response patterns easier to interpret and allows later expansion to be supported rather than assumed.
Why avoid mentioning the solution in a problem statement?
Embedding the preferred product makes the claim circular and can hide other explanations. A solution-free problem can be checked through recent behaviour, workarounds and consequences even if the final mechanism changes. This keeps the team open to evidence that the real friction sits elsewhere.
What makes a value proposition testable?
It names a specific benefit for a defined audience and connects that benefit to a plausible mechanism. Words such as innovative or seamless are too vague. A testable proposition lets the team decide what behaviour would indicate recognition, understanding or willingness to act.
Can the niche change after the first interviews?
Yes. Treat the initial niche as a learning boundary rather than a permanent market declaration. If evidence shows that the problem is rare there but urgent in a related context, document the finding and why the boundary changed. Do not quietly replace the audience after weak results, because that erases the reasoning the assessment asks you to show.
Compare both groups using the same problem language where possible, and make the next proposition explicit about which audience it now serves and why.
Assessment move
Build a three-column notebook headed niche, problem and value. For each venture idea, write one sentence in each column, then draw arrows showing how the value answers the stated problem for the same audience. Audit the statement by removing the proposed solution from the problem clause and replacing flattering adjectives with observable changes.
In interview preparation, write prompts about recent episodes and current workarounds rather than asking whether people like the idea. Use mismatches as practice: if a café discount attracts attention but the problem concerns event discovery, explain why that action cannot validate the original claim. Finally, connect the value proposition to one landing-page action.
If the action reflects a different benefit, revise the claim before building the prototype. Create three counterexamples for every draft: a person in the niche without the problem, a person with the problem outside the niche and a response that signals curiosity without valuing the proposed benefit. Use those cases to tighten the boundary and select better evidence.
Rewrite the proposition at three levels of specificity and identify which version gives a participant the clearest reason to act. Then produce a solution-free problem statement, one recent-behaviour interview prompt and one observable action for the same audience. Check that all three refer to the same friction. This routine prevents attractive language from replacing alignment among audience, problem, benefit and action.
Working through Problems, Niches and Value Propositions in MDIA1007? Sia is AskSia’s AI Management tutor — ask any MDIA1007 Problems, Niches and Value Propositions question and get a clear, step-by-step explanation grounded in how MDIA1007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
