top of page

This process is based on an Agile approach and focuses on a way of working in full collaboration with multi-disciplinary teams on new projects or large impact initiatives. The process does not go down to the level of subtleties but gives contours.

Team Process

Screen Shot 2021-08-14 at 14.10.28.png

Team Process

This process is based on an Agile approach and focuses on a way of working in full collaboration with multi-disciplinary teams on new projects or large impact initiatives. The process does not go down to the level of subtleties but gives contours.

#1. Kickoff

 
 

Who should attend:

  • Product team (or a representative)

  • UX team (or a representative)

  • Tech writers team (or a representative)

  • R&D team (or a representative)

​​

Expected Outcomes:

  1. Why are we doing this?

  2. Jira requirements (epic/ initiative level)

  3. Time constraints

  4. Relevant customers (if known)

  5. Define success criteria

 
 

#2 Research

 
 

Each team will perform needed research regarding the initiative/ project

​

Expected Outcomes:

  1. Definition of what is required from each team/ role for the fulfillment of this project

 

#3 Ideation

Wide range Design Thinking workshop and/or Design Sprint lead by the UX team.

​

Expected Outcomes:

  1. How Might We

  2. User/ Customer Journey

  3. User flows

  4. ROI

  5. Wireframes

 

#4 Internal Validation

Feasibility validation of MVP by each team

#5 External Validation

Expected Outcomes:

  1. Final UI design

  2. Test plan

  3. List of participants

  4. Signed NDA/ PPA

  5. Usability tests/ Focus group/ Semi-structured interviews

 
 
 
 
 
 

#6 Development

Expected Outcomes:

  1. QA of the released product

  2. Definition of Done - accomplished

  3. Definition of analytics funnels

  4. Usability tests/ focus groups/ Semi-structured interviews

 
 
 
bottom of page