OpenClassrooms - Product Design Workflow Template

Owned by Audrey Hacq
Last updated: Jan 11, 2022 by Asma Suleiman (Deactivated)
7 min read

 

Hi there and welcome,

In this page, you will find the public version of the template that OpenClassrooms’s Product Design team use for any design work. You can copy/paste all the content below in your own Confluence space, and customize it to make it yours!

Enjoy!

 

HOW TO USE THIS TEMPLATE?

(Remove this panel once you don’t need it anymore)

This page is a Toolbox for Product Design workflow

→ Choose the sections you want to use, and remove the others ( some are mandatory )

→ For each section, you’ll find more info in the expandable section below it

 

When you complete a step:

→ Summarize the key takeaways inside the colored panel and use the expandable section to put all the details

→ Then, click on the panel and change the panel in “done” (green)

→ Don’t forget to delete all the info you don’t need anymore in the expandable section

Thanks to this page, in the blink of an eye, you will see all the sections already done (in green) and all the sections to do (in purple)

 

Current state of the project TO START

Estimated total duration: to fill

Estimated retro-planning:
(Add an estimation date for finishing each step)

Kick-off date: tape /date to add a date
Part #1 (Empathize) done :
Part #2 (Define) done :
Part #3 (Ideate) done :
Part #4 (Prototype) done :
Part #5 (Test & checkpoints) done :
Part #6 (UI final solution & checkpoints) done :
Part #7 (Next steps) done :

1 - EMPATHIZE

AUDIT OF EXISTING

0.5 to 1 day

Audit of existing should be done if the goal of this sprint is to modify an existing page or feature. It can be an analysis of the page or an analysis of the statistics.

Best practices

Record or screenshot current pages or features


Useful links and tools

DATA COLLECTION

TO DO WITH PM

Useful links and tools

0.5 day TO DO WITH PM

The goals of a stakeholder workshop are to review with them the business objectives of the feature, to be sure that everybody is aligned and to keep the objectives in mind as long as you work on your feature.

1 DAY to 2 days (depending on the number of interviews, you should plan 1 day for preparation + restit and 1h per interview)

Interviews should be made when you need qualitative feedback and insights from users.

Best practices

Define the goals of your interviews → which info are you looking for?
Create an interview guide that you will follow during each interview

Useful links and tools

1 day TO DO WITH PM

Surveys should be made when you need quantitative asynchronous feedback from users.

Best practices

Define the goals of your surveys → what are you looking for?
Always ask open questions
If you offer several options, always use the option “Other” with the possibility for the users to write a free answer

Useful links and tools

 

2 - DEFINE

3 - IDEATE

4 - PROTOTYPE & USABILITY TESTS

5 - UX CHECKPOINTS

 

6 - UI FINAL SOLUTION & SPECIFICATIONS

7 - WHAT’S NEXT?