Every task starts with a problem or unmet need. Record the jobs to be done (JTBD) and the pain points to address.

Add, create, design an interface, remove or adapt.

How should the metrics change?

Consider reputation, conversion, engagement or other relevant outcomes.

Explore direct and indirect competitors, including international examples, and record findings.

Define and segment the audience, then write user stories. If the problem is uncertain, speak to a few participants and share a short survey in relevant communities.

Record baseline metrics, current problems and user feedback.

Identify technical and legal constraints with developers and systems or business analysts.

Capture ideas from competitor research, audience analysis, reviews and problem areas.

Assess each idea's importance and implementation effort, then discuss a realistic delivery sequence with the team.

Explain the expected effect on metrics and the evidence behind each proposed solution.

Sketch each hypothesis to give the team a shared understanding during discussion.

Collect references, choose a design system or UI kit, and design the main journeys at one viewport size first.

Use a visual survey, task-based prototype, five or more user interviews, or quick usability sessions. Summarise the findings in a presentation.

Use testing to improve designs and clarify technical and legal constraints.

Cover screen sizes, light and dark themes, errors, states, full journeys and notifications.

Check implementation against the designs.

Ask the team to instrument the interactions you plan to measure.

Prepare social media and in-product communications to explain the new functionality.

Align the designs with what was actually released.

Review metrics and user feedback.

Compare results with expectations.

Improve the experience using what you have learned.

Present the new feature at a team demo.