You’re tasked with designing a new wearable health monitor, but the product brief only states ‘innovative, user‑friendly, and cost‑effective’ with no clear functional specs. How would you navigate this ambiguity to deliver a viable design?

CIRCLES + RICE + Design Sprint (120‑150 words, no story)

First, I apply the CIRCLES framework to map all stakeholders and clarify the high‑level vision: what problem we’re solving, who the users are, and what success looks like. Next, I conduct rapid user research—contextual inquiries and low‑fidelity sketches—to surface concrete needs that translate the vague brief into measurable requirements. I then use the RICE scoring model to prioritize features against impact, reach, confidence, and effort, ensuring that the design remains cost‑effective. With a prioritized backlog, I run a design sprint, producing iterative prototypes that are tested in real‑world scenarios. Feedback loops with engineering and marketing keep the solution aligned with manufacturability and brand guidelines. Finally, I document the decision rationale and deliver a design brief that balances innovation, usability, and cost, ready for production. Throughout the process, I maintain a transparent communication channel, using shared design systems and version‑controlled assets to avoid scope creep. The result is a product that satisfies user needs, stays within budget, and can be scaled across multiple market segments.