5 most common questions about Product Design Workshops

Properly run pre-production part of the software development process always bears fruit but its advantages are usually being noticed and appreciated by the client during or after the workshops. Even if generally well-known, the values of this stage are often underestimated by companies outsourcing IT projects, especially when they already have their own designs and find any UX interference unnecessary. But to achieve a good project performance and provide on-time delivery this part should be conducted by a user experience specialist, even if they are not the full Product Design Workshops. To resolve all of the doubts we prepared answers for the most frequently asked questions that we receive from clients choosing the proper form of discovery stage.

00:00 → 00:03

In this short video, we are going to answer five most

00:03 → 00:07

common questions about product design workshops and

00:07 → 00:10

dispel all the doubts you may have about them.

00:11 → 00:14

Let's start with the most important question.

00:14 → 00:16

Why should you decide on product design workshops?

00:16 → 00:20

First of all, you are going to structure your ideas about the project and

00:20 → 00:23

have a better understanding of users' needs.

00:23 → 00:27

Another important thing is that developers and designers will

00:27 → 00:31

get a decent knowledge about both your product and business

00:31 → 00:34

goals and will help you validate them.

00:34 → 00:37

Also, getting to know the team you are about to work with

00:37 → 00:39

would be very beneficial.

00:40 → 00:44

Secondly, let us explain to you what the product design

00:44 → 00:45

workshops look like.

00:45 → 00:50

To be honest, every workshop is different and depends on the project needs.

00:50 → 00:52

But generally speaking,

00:52 → 00:54

we can distinguish two forms that we use at Merixstudio.

00:54 → 00:58

These are discovery and scoping sessions that we can run-in

00:58 → 01:00

house or remotely.

01:00 → 01:03

What are the differences between them?

01:03 → 01:05

Discovery sessions are usually led at the beginning of the

01:05 → 01:08

project when the idea is not clear yet.

01:08 → 01:12

It's a full sized product design workshop focused more on

01:12 → 01:14

searching for solutions to create a product.

01:14 → 01:18

Scoping sessions on the other hand are recommended for the

01:18 → 01:22

projects in a more advanced phase and their main goal is to

01:22 → 01:23

assess the scope of the project.

01:23 → 01:26

It can be done in many different ways,

01:26 → 01:29

but at Merixstudio we usually do story mapping during which

01:29 → 01:32

we focus on functionalities trying to allocate them to

01:32 → 01:35

specific roles, users and the system.

01:35 → 01:37

Let's move on to the next question.

01:37 → 01:40

How should you prepare for workshop session?

01:40 → 01:44

The more we know about the project or idea upfront,

01:44 → 01:47

the more effective a meeting with a customer will be.

01:47 → 01:50

That's why we look for benchmarks and inspirations.

01:50 → 01:55

It brings us closer to the idea you want to put in motion.

01:55 → 01:58

Think if you can provide us with an already existing solution.

01:58 → 02:01

Once something has been developed,

02:01 → 02:03

there is no need to reinvent the wheel.

02:03 → 02:06

Measuring movement on the website and observing what is

02:06 → 02:10

the biggest problem for the user is essential information

02:10 → 02:14

to design and implement key improvements.

02:14 → 02:17

If you've already done analytical research using tools

02:17 → 02:20

like Hotjar or Google Analytics,

02:20 → 02:23

we would be more than happy to take a look at this data.

02:23 → 02:26

Who takes part in workshops?

02:26 → 02:28

That's another question on our list.

02:28 → 02:30

There are no strict rules,

02:30 → 02:32

but diversity is priceless.

02:32 → 02:36

Merixstudio Studio is always represented by a full stack

02:36 → 02:38

team consisting of project manager,

02:38 → 02:42

UX and UI designers, front end and back end developers.

02:42 → 02:45

From the client side it differs,

02:45 → 02:48

but we value participation of CTOs,

02:48 → 02:50

product owners or even CEOs.

02:50 → 02:53

We would also appreciate the presence of people who have

02:53 → 02:57

knowledge about your users, like sales or client service.

02:57 → 03:02

The main deliverable for the scoping session would be a story map.

03:02 → 03:06

Additionally, we split the map into priorities to provide

03:06 → 03:06

MVP.

03:06 → 03:10

The discovery session covers also the bigger picture of the

03:10 → 03:14

project, meaning the business context captured in a useful

03:14 → 03:15

and clear cut form.

03:15 → 03:18

So these were the five most common questions about the

03:18 → 03:20

product design workshops,

03:20 → 03:23

but if you have more of them or want to schedule a workshop

03:23 → 03:26

session, feel free to contact us.

Let's connect and build together