Dive Into The UI/UX Design — Management

Zara Soltani
3 min readNov 18, 2020

Management is a crucial part of a project, especially in user experience and user interface design. In this article, we will learn how to manage and break down a software design project into User Stories, Features List and Page Detail.

User Story

A user story is the smallest unit of work in an agile framework. It’s the goal that our potential customer desires to experience with our product, With user story, we divide a bigger goal into smaller stories.
The first step is to determine every tiny actions and collect them in a user story chart. Each story must have 3 criteria:

  • ID — Id is a naming system that includes letters with numbers that reflects the identity of the story.
  • User story — The actual story that includes user type with the need and the achievement in the end. It starts with “As a [persona], I [want to], [so that].”
  • Category — Category is the segment that is affected by the story.
Part of a dietary application user story and related features.

Features List

As I mentioned above, A user story is an informal, general explanation of a software feature written from the perspective of the end user or customer. So the next step is to exclude features from the stories and collect them in the features list. Each feature must have this information:

  • ID
  • Feature name — We need a name to call this feature.
  • User persona — Does it affect all our personas?
  • Category
  • Priority — Highest/ High / Moderate/ Low/ Lowest. So we know when is the time to implement this feature in our process.
  • Addressed user task — Describe the story or mention related User story ID.
  • Definition — Describe how this feature works.
  • Flow — Mention or link it to its flow.
  • Best practice — Best example in the market or in competitors.
Sample of A feature details

Page Detail

In this step we have to think and write all the essential data for each page. This will help us not to miss any tiny detail in our page and prevent gaps in our further flow. We have to clarify these data:

  • ID
  • Name
  • Description
  • Components — Name every single input-field-button etc.
  • States — Any other state of our page like errors.
  • Navigation — It describes the page’s connection with other pages.

Thanks for the clap 👏 if you liked this article! Also tell me what do you think in the responses

--

--

Zara Soltani
Zara Soltani

Written by Zara Soltani

Senior Product Designer | Streamlining Design for Brand Harmony | Fostering User-Centric Solutions.. https://www.linkedin.com/in/zara-soltani/

No responses yet