Problem Definition and Framing Questions
Turning an ambiguous prompt into a well-scoped, clearly-stated problem before proposing solutions. Covers structured decomposition, clarifying assumptions, identifying the real user and job-to-be-done, and framing the problem to fit the constraints. Assesses disciplined problem-first thinking under ambiguity.
A vice president requests an internal dashboard 'for visibility' without a clear problem statement. Describe how you would lead a discovery conversation with that executive to surface the actual decisions they need to make, collect evidence, and either reframe the dashboard request or propose an alternative. Provide the set of questions you would ask and a proposed discovery timeline.
Sample Answer
Direct answer
Rather than building the dashboard as specified, lead with a short discovery conversation aimed at one question: what decision are you trying to make, and how would you make it differently depending on what the data shows? A request "for visibility" almost always has a real decision hiding behind it, and surfacing that decision usually reveals a narrower, faster deliverable than a full dashboard.
Structured elaboration
The questions to ask, in order: (1) "What decision would you make differently if you had this data, versus if you didn't?" This is the single most important question, because if there's no clear answer, the request may genuinely be for situational awareness rather than a decision, which changes what "done" looks like. (2) "How often would you check this, and what would trigger you to act on what you see?" This distinguishes a need for a live dashboard from a need for a periodic report or even a one-time analysis. (3) "What's the smallest version of this that would already tell you something useful?" This surfaces whether a full dashboard is actually needed or whether a single number, refreshed weekly, would answer the underlying question.
If the VP's (vice president's) answers reveal a genuine, recurring decision (say, "I need to know weekly whether to reallocate budget between two initiatives based on their relative performance"), the request reframes into a much narrower, well-scoped deliverable, two specific metrics compared side by side, rather than an open-ended dashboard. If the answers reveal no specific decision, the honest reframe is proposing a lighter-weight alternative, such as a monthly summary email, and explaining why: building a full interactive dashboard for situational awareness alone is a larger and more expensive commitment (both to build and to maintain) than the underlying need justifies.
Worked example
Discovery timeline: a 30-minute conversation using the three questions above, followed by a one-page problem statement circulated back to the VP for confirmation before any build work starts ("I understand the need is: decide weekly whether to reallocate budget between initiative A and B, based on their relative cost-per-acquisition; is that right?"), rather than starting a multi-week dashboard build on the original vague request.
The identical three-step move, surface the actual intent, propose evidence to test the assumption, offer a non-dismissive path forward, applies just as well to a peer stakeholder as to a VP: when a stakeholder insists "users want a carousel on the homepage because competitors use it," the same sequence surfaces what problem the carousel is meant to solve, proposes a cheap way to test whether that problem is real, and avoids either building the carousel uncritically or dismissing the idea outright.
Trade-offs and pitfalls
Pushing back on a VP-level request "for visibility" carries real political risk if handled poorly: framing it as "I don't think you need this" reads as dismissive, while framing it as "help me understand the decision this supports, so I build the right thing the first time" reads as diligence. The pitfall to avoid is building the originally-requested dashboard anyway to avoid the conversation; that path optimizes for avoiding short-term friction at the cost of shipping something that may not get used, which is a worse outcome for both the requester and the team that built it.
A clear problem statement guides discovery and prevents premature solutions. Describe what a high-quality problem statement must include and explain why each part matters, then give a short one to two sentence example for a mobile app whose monthly active users dropped 12 percent after a design update.
Sample Answer
Direct answer
A high-quality problem statement names the specific target user, states the current measured condition, states the desired condition, gives a timeframe, and specifies the metric that will confirm the gap is closed. Leaving any one of these out is what turns "we should fix onboarding" into an unactionable slogan instead of a scoped, testable problem.
Structured elaboration
Walking through why each part earns its place:
- Target user: without a named segment, "users are dropping off" could mean everyone or one small cohort, and those two situations call for completely different investigations.
- Current vs desired state: this is the gap the rest of the process exists to close. Stated as two numbers (or two qualitative states with a clear boundary between them), it gives the team a shared definition of "done" before anyone proposes how to get there.
- Timeframe: both the window the current state was observed over, and the window given to close the gap. A statement with no fix-by date competes poorly for prioritization against work that has one.
- Metric: precise enough that two people computing it independently land on the same number. A metric like "engagement" without a computation rule invites disagreement later about whether the fix worked.
A statement that includes all four but is still too broad ("increase engagement, ever, by some amount") fails a different test: it can't be disproven, so nobody can ever say with confidence that it's been solved.
Worked example
For the scenario given: "Among users who received the design update, monthly active users (MAU, the count of distinct users active at least once in a 30-day window) dropped 12% in the 30 days after the update shipped. We want MAU for this cohort back to its pre-update baseline within 6 weeks, measured as the 30-day rolling MAU count for users on the updated design." That single sentence is specific enough that a different analyst, handed only the sentence, could pull the same number from the event logs.
The same components apply to a one-paragraph ML problem statement written for a product requirements document (PRD): target user, current versus desired state, and constraints carry over unchanged, with one addition, an ML problem statement should also name the evaluation metric and baseline the model will be judged against, since "success" for a model is otherwise undefined.
Trade-offs and pitfalls
The most common failure mode is a statement that smuggles in a cause or a solution ("MAU dropped because the new layout hides the main action, so we should revert it"), which shuts down investigation before it starts by presenting an unverified theory as settled fact. The second is treating this as a one-time exercise: the components matter because they are testable, not because they're a checklist to fill in once and never revisit if new evidence emerges during discovery.
You are presenting a problem statement to a non-technical executive. Draft a one-slide structure, a headline plus three bullets, that you would use to convey the problem, the business impact, and the proposed next steps so the executive can understand the situation and the decision needed in under 90 seconds.
Sample Answer
Direct answer
Headline states the problem and its business impact in one line; the three bullets cover the current state, the desired state with its timeframe, and the specific decision or resource being asked for. The whole slide should be readable, and the ask actionable, well within the 90 seconds an executive typically gives a single slide.
Structured elaboration
Headline: a single sentence naming the problem and why it matters in business terms, not a vague title. "Checkout abandonment is costing an estimated [$X] per month, concentrated in the shipping-cost reveal step" is a headline an executive can act on; "Checkout Improvements" is not.
Bullet 1, current state: the specific, quantified baseline, in one line, no supporting detail the executive doesn't need at this altitude ("Abandonment at the shipping-cost step is 31%, up from 22% two months ago").
Bullet 2, desired state and timeframe: what success looks like and by when ("Target: reduce to 24% within one quarter, based on early experiment results").
Bullet 3, the ask: the specific decision or resource needed from the executive, stated as an actual ask, not a status update ("Requesting approval for a two-week experiment testing earlier cost disclosure, no additional headcount required"). This is the part most commonly missing from executive slides that read as informative but leave the executive unsure what they're actually meant to do with the information.
Worked example
Headline: "Checkout abandonment at the shipping-cost step is costing an estimated [$X] per month, calculated as affected sessions times the abandonment-rate gap times average order value, and has worsened over the past two months." Bullet 1: "Abandonment at this step rose from 22% to 31% since early [month], concentrated among first-time buyers." Bullet 2: "Target: back to 22% within one quarter, informed by an early low-cost experiment already showing promise." Bullet 3: "Requesting sign-off to scale the experiment to 100% of traffic; no additional budget or headcount required, two-week rollout." An executive reading this in under 90 seconds knows what's wrong, how big it is (with the dollar figure traceable to a stated formula rather than asserted on its own), what "fixed" looks like, and exactly what they're being asked to approve.
Trade-offs and pitfalls
The most common failure is treating the slide as a status update rather than a decision request, ending with a description of the problem and the current investigation rather than a specific ask, which leaves the executive informed but with nothing concrete to do, and often means a second meeting is needed just to get to the actual decision. The opposite failure is overloading the slide with investigative detail (methodology, alternative hypotheses considered and ruled out) that belongs in a supporting document, not the headline slide; if an executive wants that detail, they'll ask, and a slide should be built to answer that follow-up rather than to pre-empt it by including everything up front.
A team keeps jumping to solutions before doing any research. Describe both behavioral and tactical approaches you would use to change this pattern. Include meeting structures, artifacts such as a 'problem brief' template, scripts or questions to use in discussions, and how you would measure adoption of the new practice.
Sample Answer
Direct answer
Changing a team's solution-first habit takes both a structural change (a lightweight artifact that makes framing visible and hard to skip) and a behavioral one (modeling and reinforcing the practice in the moments it matters most, like kickoff meetings), and either alone tends to fail: process without buy-in gets worked around, and buy-in without a structural forcing function fades under deadline pressure.
Structured elaboration
Tactical, structural change: introduce a lightweight "problem brief" that must be filled in and shared before any effort gets scheduled, with a small number of required fields (the problem, the evidence, who's affected) rather than a heavyweight document nobody will complete. Make it a genuine gate, work doesn't get calendared without it, not just a suggested best practice, because a non-enforced template gets skipped first under any deadline pressure.
Behavioral, meeting-level change: in kickoff meetings, ask "what problem does this solve, and how do we know" as the very first question, every time, consistently, until it becomes the team's own reflex rather than something only a lead asks. Use specific, non-judgmental scripts when a solution-first idea arrives ("that's a real idea, what's the underlying problem it addresses, so we can compare it against other ways of solving that same problem"), which redirects toward framing without dismissing the person's contribution.
Measuring adoption: track the share of new efforts that have a completed problem brief before work is scheduled (a simple, binary, easy-to-track process metric), and separately, spot-check a sample of briefs quarterly for actual quality, meaning whether the evidence field cites real data rather than being filled in as a formality after the fact, since a team can technically comply with a process metric while defeating its purpose.
Worked example
Three months after introducing the brief-before-scheduling gate and the kickoff-question habit, if 90% of new efforts have a completed brief (up from an informal baseline of roughly 20% before the change) but a quarterly spot-check finds a third of those briefs were filled in retroactively, after the work was already underway, that's a signal the structural gate succeeded at enforcement but the behavioral shift toward framing-first thinking hasn't fully taken, and it points at reinforcing the kickoff-meeting habit more directly rather than declaring the initiative complete based on the process metric alone.
Two complementary tactics belong alongside the template-and-meeting-structure approach above: a three-step coaching plan for individual contributors (a concrete exercise, a feedback ritual, and a tracked metric, repeated over three months) that builds the habit person by person, and a process for converting an existing backlog of solution-phrased requests into validated problem statements retroactively, with stakeholder workflows and guardrails so the backlog doesn't refill with the same pattern.
Trade-offs and pitfalls
A rigid, heavyweight brief requirement risks becoming exactly the kind of process theater it's meant to prevent, filled in after the fact to satisfy a gate rather than genuinely shaping the work; keeping the brief lightweight and the gate meaningfully enforced (not scheduling work without it, rather than just requesting it) is what keeps it from becoming theater. The behavioral change is the harder, slower half of this and is easy to under-invest in relative to the structural change, since a template is a one-time build while a habit shift requires sustained, repeated reinforcement over months.
Rewrite this product brief into a concise one to two sentence problem statement suitable for a design team, then write a second variant suitable for executives. Brief: customers say search results are irrelevant, engineering says ranking uses outdated signals, the PM wants to increase engagement, and there is no formal measurement in place yet.
Sample Answer
Direct answer
For the design team: "Search results feel irrelevant to users, and we don't yet know whether the cause is our outdated ranking signals, a design or discoverability issue, or something else; we want to identify the dominant cause and improve perceived relevance within [N] weeks." For executives: "Search relevance issues may be costing us engagement; we're investigating root cause now and will have a scoped fix plan within [N] weeks." Same underlying problem, different altitude and different information each audience actually needs to act on.
Structured elaboration
The design-team version needs enough specificity to guide investigation: it names that the cause is unconfirmed (avoiding the trap of asserting "outdated ranking signals" as settled, since that was engineering's theory, not a validated finding) and gives the team something to test against.
The executive version needs business framing and a commitment, not investigative detail: executives generally don't need to know whether the candidate cause is ranking signals or a discoverability issue, they need to know the business impact is being taken seriously and when they'll get a real answer. Including engineering's specific technical theory in the executive version invites a premature commitment to a fix nobody has confirmed yet, and it gives a busy executive a detail they can't act on.
Worked example
If the original brief's inputs turn out to conflict, customers say results are irrelevant, engineering says ranking is outdated, product wants more engagement, and there's no formal measurement yet, both rewritten versions deliberately do NOT pick a side on which input is correct. Instead they state the shared fact (search relevance is a live concern with unconfirmed cause) and commit to finding out, which is honest given that no measurement exists yet to confirm any of the three inputs' theories.
Trade-offs and pitfalls
The risk in writing two versions of the same statement is that they drift into actually describing two different problems if not written carefully from the same underlying facts; keeping both versions traceable to the same baseline problem (search relevance concerns, cause unconfirmed) is what prevents the executive version from over-promising or the design-team version from under-specifying. The other pitfall is defaulting to the technical version for both audiences, which is a common failure when the person writing the statement is closer to engineering than to executive communication; the tell is a statement executives read but can't act on, because it's full of implementation detail they have no way to evaluate.
Unlock Full Question Bank
Get access to all 32 Problem Definition and Framing interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.