meet journey driven design breaking down complex ui …€¦ · meet journey driven design breaking...

MEET JOURNEY DRIVEN DESIGNBREAKING DOWN COMPLEX UI IN ACTIVE WORKSPACEPLM EUROPE,OCTOBER 30, 2018

MEET JOURNEY DRIVEN DESIGN.AGENDA

Meet Journey driven Design Breaking down complex UI in Active Workspace | BMW Group, Siemens Industry Software GmbH | 30.10.2018 Seite 2

1 Introduction

2 Project Context at BMW Group

3 Usability vs OOTB Product vs Complext UI Requirements

4 Methodology

5 Challenges & Benefits



1 Introduction



4 Methodology


BMW GROUP.VIRTUAL AND PHYSICAL PRODUCT VALIDATION.

Meet Journey driven Design Breaking down complex UI in Active Workspace | BMW Group, Siemens Industry Software GmbH | 30.10.2018 4

Target and

Requirements

Functional

Design

Geometric

DesignVirtual

Validation

Physical

Validation

Functional

Validation

Production

Planning

Physical Assembly

Validation

Virtual Assembly

Validation

Maturity & Completeness

Validation of Virtual Cars

Static Geometric

Collision Check

Design-in-context

Target and

Requirements

Functional

Design

Geometric

DesignVirtual

Validation

Physical

Validation

Functional

Validation

Production

Planning

Thomas Schaz

BMW Group IT

Product Owner

Geometric

Validation

© Siemens AG 2018

Meet Journey driven Design Breaking down complex UI in Active Workspace | BMW Group, Siemens Industry Software GmbH | 30.10.2018 Siemens PLM Software

Introduction

Co-Presenter

Markus Glöckl

Solution Architect Teamcenter Active Workspace

Lead Community of Practice “User Experience”

Automotive OEM

Siemens Industry Software GmbH

Otto-Hahn-Ring 6

81739 München, Germany

[email protected]

PROJECT CONTEXT AT BMW GROUP


Easy to use and fast (seconds) vehicle

configuration

Enhanced with process data

Focus on geometrical integration

Allows for an interactive analysis work in

combination with ad-hoc configuration

Enables analysis of multiple variants in

one go when working in not fully

constraint configurations

Provides an integrated issue management

to connect all departments



1 Introduction



4 Methodology


© Siemens AG 2018


Overview

BMW Group GEPARD – IPD leverage

Tying together the virtual and the real

• 4G Product Master as natural target data

model for

• ERP (SAP) driven Part BOM

Management

• Part breakdown („Baukasten“)

• Part Master variancy

• 4G Design as natural target data model for

• CAD (PRISMA) driven Design BOM

• Design breakdown

• Multi-view BOM

• Physical, functional and assembly-

based structure partitioning

• Design BOM variancy

• Visual issue management driven change

process

• Data model extension for support of

AW based VIM GUI extensions

• Intuitive, visual product configuration

(„Configure based on selection“)

• ERP (SAP) driven architecture and

program mgmt

• Traceability of variant / part configuration

dependencies



1 Introduction



4 Methodology


© Siemens AG 2018


Tension: Usability in a standard product vs. Complex UI

requirements

Enterprise application clients all fall into similar

patterns:

The client offers plenty of Features & Functions..

• In menus, toolbars, buttons

• Placed all over the UI

• Not intuitive to a casual or new user

Content is aggregated in multiple places

• In multiple windows (are they linked?)

• Behind multiple tabs

© Siemens AG 2018


Web based clients offer great UI

customization, but:

• They tend to start out simple

• They are also prone to feature creep

• Not every user might need every

function

Web based clients alleviate a lot of our problems

But beware!

Just because it’s web based doesn’t mean

things can’t get complicated!

© Siemens AG 2018


Complex workflows risk to become „what-if?“s and

edge cases may creep into your UX design

Not all UI‘s are created equal

Simple workflows with few functions are easy to

implement

So how can we take the ‘Simple Workflow’ approach to our complex process?

How many

major functions

do you see?

© Siemens AG 2018


Build the Simple Thing first

It’s the Simplest Way to do something:

• Everyone will use it

• Everyone will understand it

• It won’t take any explaining

• Focus on one task

• Reduce the number of things to learn, instead of just reducing

clicks

Focus on the most common, most understandable way to do

something.

The Simplest Thing is NOT:

• It would be “useful” to…

• If there isn’t a frequent need to act on it, don’t add it.

• The user “might” want to…

• If it isn’t the typical way to do something, leave it out.

Build simple tools everyone can use…

…before advanced tools someone might use



1 Introduction



4 Methodology


METHODOLOGYUSER JOURNEYS - SEE THE APPLICATION FROM A USERS PERSPECTIVE


RAC

Step 1 Step 2 Step 3

User Journey

• What steps does the user have to reach his/her goal?

• Which functions and what data is needed in each step?

• How weel can steps be reused for other scenarios?

Finding the right balance between steps and

functionality is the key to better usability


METHODOLOGY AGILE JOURNEY DRIVEN DESIGN

Sprint

Continious

Backlog-

refinement

Project DEV: Clickable prototype with focus on

usability and workflow.

Siemens PD DEV: Presentations on development

system with focus on new features and

functionality

BMW Group IT together with Vendor

product development (PD) and BusinessBusiness

and IT

Collecting feedback

Design adjustments using

parallel prototyping.

Workshops also including business users not

continuously involved in the project (‚real users‘)


METHODOLOGYPARALLEL PROTOTYPING

1. Candidates are provided with a

scenario description for which they

are asked to create a paper UI

prototype (everyone gets the same)

2. Everyone starts to create their

prototype in parallel

3. Everyone presents their

solution to the rest of the

team.

NO feedback allowed!

4. Everyone creates a new

(improved) version of the

prototype

5. Present

6. Repeat

Timed activity!

Timed activity! Timed activity!

© Siemens AG 2018


Parallel Paper Prototyping

From Mockup to Interactive Prototype with Axure RP8

Using Axure RP8 to transform the paper mockup

into an interactive, real-feeling prototype:

• Quick & Easy prototyping of web-based UI‘s

• Many built-in widgets & icons

• Build & share your own widgets with others

• Real interactivity

• Scripting capabilities

• Host prototype online or export locally

• Capture user feedback directly in prototype

• Supports version control for collaboration with

other UX designers

© Siemens AG 2018



Recipe for a UX validation workshop

You‘ll need:

Real users

Interactive prototype

Enough time

Preparation:

• Prepare scenarios you want the user to go through

• E.g. „Configure a car with certain type attributes and save your result“

• A scenario is not a step-by-step walkthrough!

• Have neutral observers to take notes

(the prototype is under scrutiny, not the user)

• Have your users walk through your scenarios and take notes:

• Are they getting stuck somewhere?

• How do they approach the task?

• Do they have questions or feedback?

• Ask users for feedback after every exercise.

• Plan a slot for internal discussion on user feedback.

© Siemens AG 2018



Influencing the core product

The Challenge: Starting early in the core product‘s development

phase with our requirements

• There‘s almost no existing UI that can be used as a starting point

• Product features are not committed yet

Our Approach:

• Demo the prototype to development and challenge them:

Does it fit the future vision for Active Workspace?

What technical & design constraints would you consider for

implementation?

This approach goes both ways: Influence your development but also

adapt your UX vision!

How can our solution integrate into the core product in

3-4 versions time?

Project team development

iterate



1 Introduction



4 Methodology


CHALLENGES & BENEFITS


Better fit UI for users

Mindset change on user side – from simply

demanding deliveries to actively conributing to the

solutions

Better focus on actual value drivers instead of feature

overkill

Better understanding of the business process and

user needs on IT side

Valuable feedback for PD for future versions (real

world feedback)

Complexity:

The more interactivity and complexity your protoype

has, the more work updating it will become.

Tunnel vision:

Keep focus on the product, not on the capabilities or

shortcomings of your prototype

Time commitment:

Not just you, or your Product Owner. Business user

time is a valuable resource!

Challenges Benefits

THANK YOU.

meet journey driven design breaking down complex ui …€¦ · meet journey driven design breaking...

Documents