Invent a believable sponsor with constraints, goals, and risks. For example, a marketplace PM worried about churn before peak season, limited engineering bandwidth, and a strict privacy policy. Designing for these tensions shows business fluency and ethical judgment, demonstrating you can translate competing pressures into pragmatic, testable decisions.
Cap timelines, data sources, and technologies to simulate real trade-offs. Maybe you restrict yourself to public datasets, one design system, and two weeks of development. Constraints illuminate priorities, helping reviewers see how you handle scarcity. Clear boundaries also prevent scope creep and preserve energy for storytelling and iteration.
List concrete outputs: research memo, journey map, technical architecture sketch, working prototype, test plan, and metrics summary. Each artifact gives a reviewer a different angle on your reasoning. Order them to mirror a decision-maker’s workflow, making it easy to skim, verify, and trust your conclusions without extra prompting.
All Rights Reserved.