Imagine a family working with a tight budget. At the beginning of the week, they prepare a shopping list, but when they reach the supermarket, several items cost more than expected. They have to leave some things behind, and the same problem returns the following week despite their efforts to plan more carefully.
Now imagine being asked to design a product that helps this family manage its weekly shopping.
Would a digital shopping list be enough? Should the product highlight discounts? Or should it help the family work out what they can realistically afford before they start shopping?
That is the decision a Product Manager needs to make before discussing features.
The Interview Question and What It Tests
Day 15 interview question:
"Create a weekly shopping planning experience for a family on a tight budget."
This is a product sense and design question. The interviewer is assessing whether you can identify the underlying user problem, select a meaningful target segment and propose a solution that can be tested without excessive investment.
A strong answer demonstrates the ability to define the problem before choosing features, make assumptions explicit, evaluate competing approaches, identify meaningful trade-offs and measure changes in user outcomes.
It also explains what evidence would justify changing the original recommendation.
The objective is not simply to design a shopping application. It is to help a family make better purchasing decisions under financial constraints.
1. What Problem Are We Really Solving?
The first mistake would be to assume that the family needs a more sophisticated shopping list.
A list is merely a way of recording items. The underlying problem might be that the family cannot anticipate the total cost, distinguish essential purchases from flexible ones, or respond confidently when prices change.
I would begin by clarifying four areas.
Who is the primary user? Does one parent manage the shopping, or do several household members contribute to purchasing decisions?
How is the budget determined? Is there a fixed weekly allowance, or does the family allocate whatever remains after other essential expenses?
Where does the greatest difficulty arise? Is it unpredictable prices, forgotten items, unexpected purchases, limited time or difficulty comparing alternatives?
What does the family do today? Does it rely on handwritten lists, messaging applications, phone notes or memory?
For this exercise, I will assume we are designing for households that primarily buy groceries and everyday household essentials once a week, have limited available spending money and cannot always predict final prices accurately.
This is a deliberate scope decision, not a claim that every low-income household behaves in the same way.
Translate the Problem Into an Observable Outcome
The user's underlying need might be expressed as follows:
"I want to know what I really need this week, roughly how much it will cost, and what I can change if I cannot afford everything."
That leads to a more useful product objective:
Help households obtain their essential weekly items within a manageable budget without making purchasing decisions unnecessarily difficult.
This objective is stronger than increasing the number of shopping lists created because it focuses on a result that matters outside the application.
2. Understand How Families Actually Shop
Demographic information alone will not explain purchasing behaviour.
Knowing that a household has four members or limited income does not tell us how it makes trade-offs at the supermarket.
We need to speak with families experiencing the problem and understand their existing shopping journeys.
I would ask participants to walk through their most recent weekly shopping trip. How did they decide what to buy? Which items were removed? When did they realise the budget might not be sufficient? How did they account for food and supplies already at home?
With permission, previous shopping lists or receipts could help us understand the difference between planned expenditure and actual expenditure. Access to bank accounts would not be necessary for this research.
Three dimensions are particularly useful.
Severity: How consequential is a budget overrun? Does it merely mean postponing a discretionary purchase, or does it prevent the household from obtaining something essential?
Frequency: Does the problem occur every week or only during unusual shopping trips?
Existing alternatives: What workaround has the family developed, and where does that workaround fail?
Research must also account for households with limited digital confidence, inconsistent internet access or little experience using applications.
An additional consideration is that shopping on a tight budget does not always mean choosing the cheapest available item.
A larger package may offer a lower unit price while requiring more cash upfront. A cheaper substitute may not meet a family's dietary requirements or preferences. An apparently economical purchase may even create waste if the product cannot be consumed before it spoils.
The US Department of Agriculture's guidance on affordable healthy eating similarly emphasises planning, comparing unit prices and making effective use of purchased food.
The product should therefore optimise for affordability in the context of actual household needs, rather than price alone.
3. Compare the Possible Solutions
Once the problem is clear, several credible approaches emerge.
Option A: A Comprehensive Intelligent Planner
The application could generate weekly meal plans and shopping lists using household size, budget, dietary preferences and existing food supplies.
This could be valuable, but it introduces significant development and maintenance costs.
It also depends on sufficiently reliable information about products, package sizes, prices and household requirements.
Without dependable data and genuine user acceptance, the product could become more complicated without delivering a corresponding improvement.
Option B: A Budget-Aware Shopping List
Users set a weekly budget, add essential items and see an estimated total.
The product indicates how much of the budget has been allocated, which purchases matter most and what could change if the projected total exceeds the available amount.
This approach is simpler, less dependent on external data and easier to validate through inexpensive prototypes.
Option C: A Price and Discount Comparison Engine
The product could compare prices across retailers and recommend the lowest-cost combination.
For households with access to several shops and reliable pricing information, this might be useful.
However, discounts do not automatically translate into savings. Travel expenses, delivery minimums, impulse purchases and price fluctuations could outweigh the apparent benefit.
My Recommendation
For the initial target segment, I would start with Option B: the budget-aware shopping list.
This does not mean it is universally the best solution.
It means we do not yet have sufficient evidence to justify the complexity of automated meal planning or real-time retail price comparison.
A smaller product lets us test the central assumption: does making estimated costs and purchasing priorities visible genuinely improve household decisions?
If discovery shows that families primarily struggle to identify the cheapest accessible retailer, I would reconsider this choice.
4. What Should the First Product Experience Look Like?
Rather than building a large collection of features, I would design a short, practical journey.
Set the Weekly Budget
The user enters the amount available for weekly shopping.
Household size, dietary preferences and specific requirements can be added optionally. These should not become compulsory onboarding obstacles.
Check What Is Already Available
Before preparing the list, the application prompts the household to consider what is already in its cupboards, refrigerator or freezer.
The purpose is to avoid unnecessary duplicate purchases.
This should be quick and optional. Users should not have to maintain a complete digital inventory of their kitchen.
Build and Prioritise the List
Items are divided into two broad categories.
Essential items are purchases the household considers necessary for the coming week.
Flexible items are purchases whose quantity, brand or timing can potentially change.
These classifications must remain under the family's control. The software should not make definitive judgements about what individual households ought to consider essential.
Show the Estimated Total
The estimated shopping cost updates as items are added.
Where dependable prices are unavailable, users can enter approximate amounts or reuse information from previous purchases.
One principle is particularly important:
An estimated price must never be presented as a guaranteed price.
If information is incomplete or outdated, the interface needs to make that limitation clear. The experience could accommodate uncertainty and allow a small contingency for unexpected price changes.
Suggest Alternatives Without Taking Control
When the planned total exceeds the budget, the application could suggest reducing the quantity of a flexible item, choosing a suitable substitute or postponing a non-essential purchase.
However, suggestions must be dismissible and respect dietary restrictions, allergies and household preferences.
Support the Actual Shopping Trip
The final list should remain accessible in a shop, including when internet connectivity is poor.
Users can tick off purchased items and optionally enter actual prices. The total can then be updated when prices differ from expectations.
Afterwards, the application can offer a brief, optional review of what went according to plan, which items cost more and what should change next week.
The initial version does not require bank account integration, mandatory registration or extensive behavioural profiling.
5. Hypothetical Software Product Scenario
Consider a hypothetical product team developing a household shopping management application.
The target user is a family of four. One parent usually does the weekly shopping, while another household member occasionally contributes items to the list.
In this fictional research scenario, a recurring pattern appears: families often prepare lists but struggle to determine whether the total cost will fit their weekly budget.
The design team creates two prototypes.
The first is a conventional shopping list that allows users to add and tick off items.
The second combines the same list with a budget, purchasing priorities and estimated costs.
Several families are asked to use both prototypes to prepare for their next shopping trip. The team observes where participants hesitate, which items they reconsider and whether the additional information helps them decide what to remove or substitute.
Product hypothesis: Showing estimated spending alongside item priorities makes purchasing decisions easier before the shopping trip.
That is a hypothesis to test, not an established research finding.
Responsibilities and Decision Ownership
The Product Manager decides which user problem, target segment and outcome deserve priority.
The Product Designer develops and tests the experience. Engineers assess feasibility, storage and offline functionality. Operations or data specialists help evaluate the reliability of available prices.
If the team uses Scrum, the Product Owner is accountable for maximising product value and effective Product Backlog management. This accountability does not necessarily correspond to a separate Product Manager job title.
A Project Manager, where the organisation has one, would generally focus more on delivery coordination, schedules and project constraints.
In this scenario, deciding whether budget control matters more than retailer comparison is fundamentally a product decision, rather than simply a delivery-planning decision.
6. How Would We Measure Success?
Downloads, lists created and time spent in the application can tell us something about product usage.
They do not, by themselves, establish whether the family is shopping more effectively.
Primary Outcome: Essential Shopping Within Budget
My proposed primary metric is the proportion of weekly shopping trips completed within the pre-set budget while fulfilling the household's planned essential purchases.
The denominator consists of eligible shopping trips where a budget was recorded before shopping and sufficient outcome information was subsequently provided.
The numerator consists of those trips meeting both conditions: spending within budget and fulfilling planned essential needs.
This metric has limitations.
Not every user will report their final spending, and those who do may differ systematically from those who do not.
We must therefore monitor outcome-reporting rates and investigate incomplete data rather than treating missing results as successes or failures.
Diagnostic Metrics
Planning time: How long does it take a household to prepare a useful list and make purchasing decisions?
Estimated versus actual spending: How accurately does the projected cost reflect the final expenditure?
Substitution behaviour: Which suggestions are accepted or rejected, and for what reasons?
Repeat usage: Do households find enough value to use the product in subsequent weeks?
Guardrail Metrics
Lower spending must not come at the expense of essential needs.
We should monitor whether users are increasingly unable to purchase necessities, whether discounts encourage unnecessary purchases, whether planning becomes more burdensome and whether privacy concerns emerge.
A product that persuades families to spend less by sacrificing essential requirements is not achieving its intended outcome.
I would examine behaviour over several weeks rather than drawing conclusions from a single trip.
Where feasible, I would compare results against previous household behaviour or a suitable comparison group.
A small early test can produce valuable learning, but it cannot by itself establish that the product causes financial savings.
7. What If You Only Had Two Weeks?
This is the first follow-up question in the source material.
With only two weeks, I would not attempt to develop a complete shopping platform.
During the first week, I would interview a small number of representative families, examine their current shopping journeys and prepare two lightweight prototypes.
In moderated usability sessions, participants would be asked to plan a shopping trip with a limited budget and decide what to change when the estimated cost rises.
During the second week, I would test the more promising approach through a genuine shopping cycle or a tightly scoped pilot.
I would prioritise observing actual behaviour and discussing decisions after the shopping trip rather than relying only on opinions about the interface.
The UK Government's guidance on moderated usability testing supports observing users completing realistic tasks with prototypes to identify practical usability problems.
At the end of the two weeks, the expected outcome would be a decision: develop further, change the proposed solution or revisit the problem definition.
8. What Evidence Would Make You Reject Your Solution?
This is the second follow-up question from the source material, and it is just as important as the design itself.
If families consistently plan more quickly and confidently with paper lists, the digital product may not offer sufficient additional value.
If price estimates are repeatedly inaccurate and lead to poor decisions, I would redesign or temporarily remove that capability.
If households continue exceeding their budgets despite using the application, I would investigate whether the underlying issue is insufficient information or simply insufficient money to cover essential needs.
In the latter case, an application cannot solve the family's broader financial circumstances. The product's role must be defined realistically.
And if research reveals that households care significantly more about comparing accessible retailers than managing a shopping list, I would change the roadmap accordingly.
Being willing to abandon an unsuitable solution is a sign of sound product judgement.
9. Example of a Natural Interview Answer
The following is an illustrative spoken response, not a quotation from an actual interview.
"Before designing features, I'd want to understand where the family actually struggles during weekly shopping.
"My initial assumption is that the problem isn't simply remembering what to buy. It's deciding which purchases matter most and keeping the total cost manageable before getting to the shop.
"I'd speak to a few families and understand how they currently plan their shopping. Then I'd compare two approaches: a comprehensive intelligent planner and a simpler shopping list that shows the budget, item priorities and estimated spending.
"I'd start with the simpler option because we could test its value much more quickly and at a lower cost.
"I wouldn't judge success by the number of lists people create. I'd look at how often families complete their essential shopping within budget, whether their needs are met and how accurate the estimates are.
"If people don't find the tool useful, the pricing information isn't reliable or we can't demonstrate an improvement over their current approach, I'd adapt the solution or reconsider the product direction."
10. What Makes an Interview Answer Weak?
Starting with features: Suggesting artificial intelligence, barcode scanning, meal recommendations and price comparison does not explain which user problem those capabilities address.
Designing for every household: A family with a fixed allowance, one with irregular income and one where several people shop may require different experiences.
Assuming accurate real-time prices: Without dependable retailer data, promising exact prices can undermine user trust.
Optimising only for lower spending: A smaller bill is not a positive outcome if the family can no longer obtain essential food or household items.
Relying on vanity metrics: More installations or shopping lists do not prove that households are managing their budgets more effectively.
Defending the first solution regardless of evidence: A Product Manager should be able to explain exactly which findings would change or invalidate the recommendation.
Conclusion
Designing a weekly shopping experience for a family on a tight budget begins with identifying the actual source of difficulty: planning, estimating costs, prioritising essential needs or comparing alternatives.
If the main problem is uncertainty about spending before a shopping trip, I would initially recommend a straightforward shopping list with a clearly defined budget, item priorities, transparent cost estimates and flexible alternatives.
This approach is cheaper and quicker to validate than a comprehensive intelligent planning system, while providing a useful foundation for subsequent improvements.
The recommendation remains conditional. If the product cannot help households fulfil their essential needs within budget without introducing additional effort or misleading information, we should reconsider the design or even the original problem definition.
A successful product should do more than organise a family's shopping list. It should help people make better-informed decisions with the limited resources available to them.
