project story

cms case study

Project name: a cohesive story from problem to solution

Project name: a cohesive story from problem to solution

Role

Lead UX/UI Designer

Client

Placeholder Brand

Timeline

6–8 weeks

Platform

Responsive web

A concise opening paragraph that frames the project, the audience, and why the work mattered.

A concise opening paragraph that frames the project, the audience, and why the work mattered.

Use this space to introduce the situation in plain language. Describe what was happening before the project began, who was affected, and what made the problem worth solving.

identify the shift

01

The problem

Users were running into a clear point of friction. Placeholder text should explain the behavior, business constraint, or missed opportunity that made the experience difficult to understand or act on.

The solution

The design response translated the problem into a more focused flow. Placeholder text should describe the central idea, what changed in the interface, and how the solution reduced uncertainty.

how the story unfolded

02

01

Research the context

Capture the audience, workflow, constraints, and evidence that clarified what needed to change.

02

Define the approach

Turn insights into a clear design direction: the user path, content hierarchy, and interaction choices.

03

Build the experience

Show how the interface, prototype, or shipped system made the solution tangible and easier to use.

what changed

03

Outcome

Placeholder outcome: the redesigned experience improved clarity, reduced friction, and gave the team a stronger framework for future product decisions.

Reflection

Use this closing note to explain what you learned, what you would revisit, and how the project shaped your design approach moving forward.