user acceptance - eit digital · 2 defining user requirements 1. desk study on dos and donts user...

Text Text

User acceptance

Annick Starren, POSTExpo 2015, 30 September

2

Defining User Requirements

1. Desk study on Do’s and Don’ts User Acceptance;

2. Consulting drivers on User Needs- via Interviews,

Focus Groups, Storylines;

3. MVP prototype trailing ‘in the field’;

4. System Architecture.

Visualisation of activities

1. Do’s and don’t s User Acceptance

2. Consulting drivers on user needs: interviews and focus groups with drivers.

Driving Break

Planning Getting up Administration Driving to the first

customer

loading the

vehicle

Driving to the

second customer

Unloading the

vehicle

Driving to the

third customer

Almost accident Lunch break Loading the vehicle Driving to the

fourth customer

Unloading the vehicle Driving home Private life Sleep

Positive

Neutral

Negative

Driver receives

planning on Friday

for the next week

Planning is strict.

Therefore the

truck driver has to

get up very early:

3:00.

Driver needs to

make a

calculation

himself for the

working time

regulations

The driver drives

with an empty truck

to the first loading

place.

Has a break from

driving. But often

has to do this task

himself.

The driver drives

with a full truck to

the unloading

place.

Customer invites

driver in to have a

coffee

Driver uses the

smartphone and

trasport radio to

communicate

with other drivers

Traffic is very

busy. A luxury car

gets in front of

the truck in a

dangerous way.

The tachograph gives

the driver a signal he

should have a break

for 3/4 minutes. He

has unhealthy lunch.

No contactperson at

the customer.

Customer works with

automatic briefing.

Driver has to wait a

long time.

Very long working

days. Shift of 15

hours (10 hours

drive) is normal.

Driver unloads the truck

at the unloading place.

Driver is 30

minutes from

home, but the

tachograph tells

him to stop…

Hardly any time

for social events

during the week

Driver needs to

sleep in the truck

Time off

Storyline Truck Driver

Journey elements

Tasks

Customer

Experience

What does the consumer do

Going to work Driving

Driving Break

Planning Getting up Administration Driving to the first

customer

loading the

vehicle

Driving to the

second customer

Unloading the

vehicle

Driving to the

third customer

Almost accident Lunch break Loading the vehicle Driving to the

fourth customer

Unloading the vehicle Driving home Private life Sleep

Positive

Neutral

Negative

Driver receives

planning on Friday

for the next week

Planning is strict.

Therefore the

truck driver has to

get up very early:

3:00.

Driver needs to

make a

calculation

himself for the

working time

regulations

The driver drives

with an empty truck

to the first loading

place.

Has a break from

driving. But often

has to do this task

himself.

The driver drives

with a full truck to

the unloading

place.

Customer invites

driver in to have a

coffee

Driver uses the

smartphone and

trasport radio to

communicate

with other drivers

Traffic is very

busy. A luxury car

gets in front of

the truck in a

dangerous way.

The tachograph gives

the driver a signal he

should have a break

for 3/4 minutes. He

has unhealthy lunch.

No contactperson at

the customer.

Customer works with

automatic briefing.

Driver has to wait a

long time.

Very long working

days. Shift of 15

hours (10 hours

drive) is normal.

Driver unloads the truck

at the unloading place.

Driver is 30

minutes from

home, but the

tachograph tells

him to stop…

Hardly any time

for social events

during the week

Driver needs to

sleep in the truck

Time off

Storyline Truck Driver

Journey elements

Tasks

Customer

Experience

What does the consumer do

Going to work Driving

Results Interviews: day overview

Focus groups

• Presentation of scenario’s on how truck drivers use the

coaching solution: does this motivate you? Why (not)?

Example of scenario

15 min

Jij

Henk

Paul

Meet colleagues:

Long haul drivers: Yes, that would be nice in the weekend.

Scenario Example

Feedback of customers: Distribution:

yes it would be nice to hear you’ve

done a good job. We almost never get

compliments.

On Time!

Friendly driver!

Example Scenario

Healthy food coach: - Long haul: want info about diabetes. - Distribution driver: I know I should do

something about it, but I don’t want someone to patronize me.

Persona Distribution Driver

Persona Long Haul Driver

Adventurer

“Driving itself is the best part of my work, being on road on your own is what I call such a freedom.”

- job with variation: - different customers - varying challenges

- social contact - financial compensation for

the extra hours

Motivators

- tight planning: - inflexible - unpredictable

- poor communication - delays on deliverable - little time for family

Frustrators

Persona 2: Distribution Driver

Speedy Gonzales

“I should act fast and finish the distribution list before the day ends.”

- “own” truck - job with variation

- varying challenges

- coffee with customers - out of office environment

Motivators

- loading/unloading cargo - heavy cargo - inappropriate cargo order

- too many paperwork - too many calls - fear of being replaced

Frustrators

3. MVP Prototype trials

The MVP Prototype

Mio FUSE Nexus Tablet + F2P app

Research Questions MVP trials

Physical and mental wellbeing

Social interaction

Personal preferences

Nutrition advice

Physical exercise

Sleep advice

Performance

What parts of the MVP add value to the

drivers?

In what form do drivers want to receive

advice/information?

When, how often, and where

Does the technology obstruct driving?

Does the technology interfere with

comfort?

Willingness to share personal information

on stress, fatigue and fitness with

employer?

The main screen

Energy level

20

Pop-ups

Stress overview

22

4. The F2P ICT architecture

Goal: F2P open value chain:

• Both FO’s and drivers can install F2P-related third party services.

• Physiological and driving data can be accessed by third party apps, both:

• locally, i.e. on the Android tablet

• in the back/end cloud

Two main goals: Open value Chain and Controlled Privacy

23

The F2P ICT architecture

Goal: Controlled Privacy

• Driver is in control over who / which app can access his (physiological) data

• Policy based

• Privacy is key for acceptance:

• For drivers

• For regulators: E.g. , the Dutch EHR-veto by parliament

Two main goals: Open value Chain and Controlled Privacy

24

The F2P ICT architecture High-level system architecture

Modular approach:

• data acquisition module,

• data control module,

• Trusted Third Party module,

• user management module .

Distributed implementation over:

• the local (in-cabin) Android tablet,

• the back-end (cloud) infrastructure.

eitdigital.eu

THANK YOU

annick.starren@tno.nl