Fabriq

Fabriq

Fabriq

2024

2024

2024

Launching the first step of a new product line to activate dormant knowledge in modern shopfloor

Launching the first step of a new product line to activate dormant knowledge in modern shopfloor

Launching the first step of a new product line to activate dormant knowledge in modern shopfloor

Role

Role

Lead designer

Lead designer

Product Team

Product Team

Adhémar de St Just - Junior PM

Adhémar de St Just - Junior PM

TL;DR : what we delivered

TL;DR : what we delivered

TL;DR : what we delivered

With insights from the field research and survey, we launched in 6 weeks a MVP that successfully solve a current pain point that has few competitors with advanced solutions on it, ensuring a steady growth with engaged users.

Following the launch, the closed beta was a great ground to learn from our customers and confirm our first hypothesis.

With insights from the field research and survey, we launched in 6 weeks a MVP that successfully solve a current pain point that has few competitors with advanced solutions on it, ensuring a steady growth with engaged users.

Following the launch, the closed beta was a great ground to learn from our customers and confirm our first hypothesis.

1

1

Context

Context

Context

Fabriq brings tools for industrial shopfloors to identify, communicate and resolve day to day issues faster.

They’ve been waiting to add a final product to their solutions that would store every solutions used to make them available when a similar issue would appear, either in the same location or in a different shopfloor using the same machines and processes.

The founders where uncertain of the business potentiel and wanted to validate quickly if that product line had any benefits, and set a timeframe of 3 months.

Fabriq brings tools for industrial shopfloors to identify, communicate and resolve day to day issues faster.

They’ve been waiting to add a final product to their solutions that would store every solutions used to make them available when a similar issue would appear, either in the same location or in a different shopfloor using the same machines and processes.

The founders where uncertain of the business potentiel and wanted to validate quickly if that product line had any benefits, and set a timeframe of 3 months.

Main tasks

Main tasks

  1. Understand the need through research

  2. Help create the product foundations and roadmap

  3. Design the MVP

  4. Plan & conduct user tests

  1. Understand the need through research

  2. Help create the product foundations and roadmap

  3. Design the MVP

  4. Plan & conduct user tests

2

Problem

Problem

Problem

Fabriq’s founder had in mind the end game for the new product : close the loop of shopfloor problem solving by having a solution database ready to propose pertinent solutions based on past experiences.

But we were starting from zero and competitors were ahead, and even more problematic, they were present within Fabriq’s clients toolkit.

How to find the right angle to make this and advantage, and fit in our timeframe ?

Fabriq’s founder had in mind the end game for the new product : close the loop of shopfloor problem solving by having a solution database ready to propose pertinent solutions based on past experiences.

But we were starting from zero and competitors were ahead, and even more problematic, they were present within Fabriq’s clients toolkit.

How to find the right angle to make this and advantage, and fit in our timeframe ?

3

Research

Research

Research

We conducted 1 survey, a dozen interviews and 3 field studies to have a better understand of what the reality. Example of questions :

  • What was documented ?

  • Who did it ?

  • Was it based on templates ? How many were there ?

  • How was the documentation stored ?

  • Was it re-use ? If yes, why, when and how ?

  • What are today biggest issues ?

We conducted 1 survey, a dozen interviews and 3 field studies to have a better understand of what the reality. Example of questions :

  • What was documented ?

  • Who did it ?

  • Was it based on templates ? How many were there ?

  • How was the documentation stored ?

  • Was it re-use ? If yes, why, when and how ?

  • What are today biggest issues ?

4

Scope

Scope

Scope

The key insights found helped rethink our scope to fit our timeframe and take advantage on the context :

  1. Competitors were already working with our clients to digitalize their documentation to create knowledge based, and spending months on standardizing all of them.

  2. A recurring issue for line manager were to show during the audits to prove that everyone on the team was up to date with the documentation.

So the problem was reframed around team leaders that have no reliable way to prove that their teams are up to date on process changes :
How might we help team leaders have trustworthy tracking of their teams' awareness and updates on information?

The key insights found helped rethink our scope to fit our timeframe and take advantage on the context :

  1. Competitors were already working with our clients to digitalize their documentation to create knowledge based, and spending months on standardizing all of them.

  2. A recurring issue for line manager were to show during the audits to prove that everyone on the team was up to date with the documentation.

So the problem was reframed around team leaders that have no reliable way to prove that their teams are up to date on process changes :
How might we help team leaders have trustworthy tracking of their teams' awareness and updates on information?

5

Persona

Persona

Persona

Malik, 43 - Shopfloor line manager

Malik, 43 - Shopfloor line manager

His job is to give daily tasks to the line operators to meet the line’s goals. He‘s the one whom people go to when there is a issue to solve or a question is raised.

Needs :

  • Ensure that new documentation is read and understood by the right people

  • Share during or after an audit proof than he shared and verified that his team got every informations needed

His job is to give daily tasks to the line operators to meet the line’s goals. He‘s the one whom people go to when there is a issue to solve or a question is raised.

Needs :

  • Ensure that new documentation is read and understood by the right people

  • Share during or after an audit proof than he shared and verified that his team got every informations needed

6

User journey

User journey

User journey

Base on our new scope and key user, we map his journey and ideate on possible solutions.

Base on our new scope and key user, we map his journey and ideate on possible solutions.

7

Solution

Solution

Solution

How might we help Malik have a trusted accountability of his team acknowledged and up to date informations ?

How might we help Malik have a trusted accountability of his team acknowledged and up to date informations ?

How might we help Malik have a trusted accountability of his team acknowledged and up to date informations ?

Make acknowledgement easy to setup for him

Make acknowledgement easy to setup for him

Make it even simpler to use by his team

Make it even simpler to use by his team

Keep track of current version

Keep track of current version

Keep track of previous versions

Keep track of previous versions

8

Validating idea

Validating idea

Validating idea

After 6 weeks, we layed out the first prototype version, and conducted weekly meetup with clients than shown an interest to test prototypes and then have direct feedback from the beta testeurs

After 6 weeks, we layed out the first prototype version, and conducted weekly meetup with clients than shown an interest to test prototypes and then have direct feedback from the beta testeurs

Next project

Next project

Agicap

Agicap

contact@fabiencazals.fr

contact@fabiencazals.fr