top of page

Design Process

As a Product Designer, I typically use the Design Thinking Methodology when starting a project. However, when I'm working with a multidisciplinary team, it's essential to define clear roles to make sure the work gets done on time. To achieve that I created this process which is a mix of Design Thinking + Agile Framework.

​

I have used this process with various teams and have found it to be very effective. Also, I understand that every team/organization is unique, which is why this process is flexible and can be modified to fit the spirit and values of a particular team or organization.

Step 1

UNDERSTAND THE PROBLEM

Owner: Product Manager | UX Team Leader

​

Define problem statement. In order to know what the team is trying to solve.

FYI: This stage can include discovery and research work to help identify the problem and to define future product updates or features.

Meeting: Planning Session.
Attendees:

  • Project Manager

  • Scrum Master

  • UX Representative

  • Engineering Representative


Outcome: Requirements and product specifications.

Step 3

START DESIGN PROCESS

Owner: UX Designer

​

It's important to follow a UCD methodology like Design Thinking or Double Diamond.

 

Deliverables:

  • First design proposals.

  • Navigational flows.

  • Use cases.
     

First Meeting: Internal for UX Team. Feedback Session.
Attendees:

  • UX Team

  • UX Manager


Meeting Purpose: Expose and defend design decisions. Receive feedback from teammates and iterate the proposal if necessary.

Second Meeting: First Official Design Review.
Attendees:

  • Project Manager

  • Scrum Master

  • UX Team

  • Engineering Representative. To provide technical feedback.


Meeting Purpose: Space to provide feedback, find gaps in the design and help refine the proposal if necessary.

Step 5

DESIGN HANDOFF

Owner: UX Designer

Deliverables:

  • Navigational flows.

  • Use cases.

  • Final assets.

 

This Figma link must be placed in the original ticket assigned to the UX Designer or Engineer in charge.


FYI: At this stage no more changes can be requested, if a change is required a new ticket will be created.

Meeting: No meetings are required at this stage.

Step 2

DEFINE PRODUCT SPECIFICATIONS

Owner: Product Manager

​

Deliverables:

  • User stories with clear requirements.​


Meeting: Grooming Session.
Attendees:

  • Project Manager

  • UX Team

  • Engineering Representative. To clarify or share possible technical constraints

​

Outcomes:​

  • Team alignment

  • User stories

Step 4

DESIGN REFINEMENTS

Owner: UX Designer

Deliverables:

  • Final and polished UX work. Ready for design handoff.

  • Prototype.

​

Meeting: Demo day

Attendees:​

  • Stakeholders

  • Product Owner

  • Project Manager

  • Scrum Master

  • UX Team

  • Engineering Team


Meeting Purpose: Final UX work is presented in front of the entire team. At this stage is when all team effort and UX work shines.

Step 6

MONITORING

Owner: UX Designer

Deliverables:

  • Design feedback to Engineers.


FYI: Designers need to have access to test environment to be able to review the following:
 

  • Correct implementation of the design solution.

  • Interaction design. Motion design.

  • UX flow.


To summarize, this stage is to find differences between the original design proposal and the implementation.

If issues arise at this stage, a new ticket will be created (design bug) along with a document containing feedback for the Engineers to modify the implemented design.


Meeting: Flexible.
Schedule a meeting with an Engineer if necessary to improve communication and move faster.

bottom of page