Designing a Behaviour-Led Cooking App for Novice Cooks

Project: Noms

Noms is a mobile-first product design created to help novice cooks confidently decide what to cook, how to prepare it, and what to buy, without overwhelm. Simply delicious food. Seasoned with love.

The challenge wasn’t to build another recipe app. It was to design a decision-support product for people who feel uncertain, rushed, or intimidated by cooking, and to do so with clarity, empathy, and simplicity.

I approached Noms as a product UX and behaviour problem, not simply a visual or content exercise.

As Product Designer and UX Lead, I owned the full MVP lifecycle, from discovery and research through information architecture, interaction design, usability testing, optimisation, and high-fidelity prototyping across mobile and desktop.

The result was a focused, testable MVP that demonstrated how thoughtful UX product design can turn friction, hesitation, and indecision into confidence and momentum.

The Project in a Nutshell

This project started from a very real problem. For many people, cooking isn’t about passion, creativity, or exploration. It’s about uncertainty:

  • Not knowing what to cook

  • Feeling overwhelmed by instructions

  • Struggling to translate recipes into action

  • Forgetting steps mid-way

  • Buying ingredients without a clear plan

Most cooking apps assume a level of confidence users simply don’t have. Noms was designed for people like me at the time: novice cooks who want inspiration, but need reassurance, structure, and simplicity to move forward. That insight shaped every design decision.

What Worked and What I’d Build Next

What Worked:

User engagement centred strongly around discovery and learning, which made navigation and hierarchy critical. By keeping the interface deliberately simple and visually calm, the product allowed imagery to lead, helping users feel inspired rather than instructed. This approach encouraged exploration while reducing cognitive load, especially for novice cooks.

Think-aloud usability testing offered clear insight into how users moved through the experience, where they felt confident, and where friction appeared. Observations were captured and synthesised through affinity mapping, allowing recurring patterns to surface quickly. These insights informed iterative refinements to flows and interactions, ensuring changes were grounded in behaviour rather than assumption.

Conceptually, the MVP performed well. Users described the experience as intuitive, approachable, and visually engaging. Most importantly, it delivered the features users expected without overwhelming them, reinforcing that the product focus was right for its intended audience.

What I’d Add Next:

Future iterations would explore deeper personalisation and health-related insights, including calorie tracking or nutritional context per recipe. Several users also expressed interest in lightweight social sharing, allowing them to save or share recipes within their existing networks. These features were intentionally excluded from the MVP to preserve clarity and focus, but they form a natural next step once core behaviour is validated.

Leading UX Product Design for a Novice-First Cooking Platform

What I Learned, the Challenges I Met, and My Biggest Takeaway

This project fundamentally shaped how I approach product UX design. It reinforced that the most impactful products aren’t built around ideal behaviour, they’re built around real hesitation. Designing Noms meant understanding uncertainty, decision fatigue, and low confidence, and then turning those moments into structured, supportive experiences that help users move forward.

I learned that great UX doesn’t eliminate complexity, it organises it into something people can handle. Confidence isn’t created through encouragement or clever copy, but through clear structure, predictable steps, and visible progress. Working within an MVP constraint sharpened my product thinking, forcing prioritisation around a single, meaningful problem rather than feature accumulation.

The biggest challenge was resisting over-design. Research revealed many opportunities, but the real work was deciding what not to build. Every interaction had to earn its place by reducing friction at the exact moment a user might hesitate. That discipline is where product clarity emerged.

My biggest takeaway is this: strong product UX starts where people pause. When you design for uncertainty rather than confidence, you unlock momentum, trust, and genuine engagement. That principle has stayed with me across every product I’ve designed since.

If This Resonates…

If you’re building a product that needs to simplify complexity, support learning, or guide people through decisions with confidence, I’d love to collaborate.

Let’s design something that feels intuitive, useful, and genuinely human.