← All projects

Product discovery & iterative delivery

Gym and fitness application

A gym and fitness web product used to practise taking a broad product idea through discovery, backlog prioritisation, iterative delivery, testing and feedback.

  • Working product project
  • User stories and acceptance criteria
  • Feedback-led iteration
Case study 03Working product · Documentation in progressProfessional portfolio · Non-confidential
01

Project overview

A gym and fitness web product used to practise taking a broad product idea through discovery, backlog prioritisation, iterative delivery, testing and feedback.

Working product projectUser stories and acceptance criteriaFeedback-led iteration
02

Problem

The project began with a broad fitness-product idea. The product challenge was to turn that idea into a focused, testable experience with explicit priorities rather than treating the website as a collection of unrelated screens and features.

03

My role

I worked across product discovery and iterative delivery: clarifying user needs, translating them into user stories and acceptance criteria, prioritising the backlog and reviewing each iteration before deciding what should come next.

04

Delivery approach

  1. 01Clarified the intended user problem before defining the product scope
  2. 02Used stories and acceptance criteria to make each proposed increment testable
  3. 03Prioritised the backlog rather than attempting to build the full idea in one pass
  4. 04Reviewed the working product and captured feedback to inform subsequent iterations
05

What I produced

  • A working gym and fitness web product
  • A prioritised backlog to sequence the product work
  • User stories and acceptance criteria to make requirements testable
  • An iterative feedback and testing loop to inform the next release
06

Evidence & business value

The project provides another practical example of moving from an early product idea into structured, prioritised delivery and validation. It demonstrates how I organise product work before expanding the feature set.

  • A working product has been built
  • Product artefacts and delivery decisions are being documented for a fuller future case study
  • Current evidence focuses on product discovery, prioritisation and the working prototype
07

Technology & working methods

Web productProduct discoveryUser storiesBacklog prioritisationFeedback & testing
08

What I learned

A product becomes easier to build and evaluate when the problem, priority and acceptance conditions are explicit before each iteration begins.

Current status: working prototype, with the detailed case study and usage evidence still being documented.

Next case study

UCD transformation