› dschool › resources › SAP Materials › DST workshop... · A Workshop on Design Led...

1

Version 2.0

A Workshop on Design Led Innovation

Welcome the participantsExplain that today is their day, and that they will work with their teams most of the time today.

In India: Yes It is Design Led Innovation or DLI, not Idli [a small round Indian Rice roll]

Clarify all organizational points:-Please reduce usage of mobile phones and participate actively-Timing from 9 a.m. to 6 p.m.-Training language is English, also in Walldorf if there is a complete German group-Food is served at lunch, cookies, coffee, tea and drinks will be available throughout the day

Overall: The facilitator should underpin as many points as possible with concrete examples from projects and previous experiences (however, focus on the point you want to make)

2

Introduction360 ViewFocusIdeasAlternatives & IterationDesign Led Innovation for You

Explain that we will go through the components of Design Led Innovation step by step, explain each of them in detail and most important: Practice them yourself.Also mention that the time slots are not announced on purpose, because it is sometimes necessary to adjust the parts of the training to the design challenge.

Mention that the afternoon is divided into 3 work sessions, each of them kicked off by a theoretical introduction of the component, and that breaks should be taken by the teams during these work sessions as required.

3

© SAP AG 2006, Overview of Design Led Innovation / 3

Team Warm-Up

You will be given a set of LEGO building blocks.

In your teams, assemble all the LEGO blocks into a vehicle.

You have 5 minutes so time is of essence.

Start with a warm-up game. Explain the rules:•You have to use all the blocks, so be creative•The result has to be a vehicle•Do not forget, every person in the team may have great ideas. •And to put a little bit of realistic touch on the exercise: Deadline is in 5 min. So let’s go!•If you need to change the room setup, please feel free to do so.

After the game, let the teams briefly present their vehicle.Do a short recap on how tight timelines drive results and how well the teams worked together to achieve a common goal.

4


OBJECTIVES

Now lets talk a bit about the objectives of today.

5


Objectives

This workshop will allow you to explore key components of DesignLed Innovation.

You will:Learn more about key values of Design Led InnovationExperience Design Led Innovation with a design challenge

Just recap briefly from the day before that the workshop is intended to •give the participants an overview of Design Led Innovation •give them the opportunity to immerse themselves into this theme for a whole day by working on a specific task or “design challenge”

6


Details

You will split into teams for the hands-on exercises.

Each team will be given the same design challenge, and will compete for the best and most innovative solution.

Each team will have a moderator.

The designed solutions will be evaluated by a panel of judges atthe end of the session.

Explain the working mode of the day to the participants as detailed out in the slide

7


Your Design will be Evaluated based on

Creativity of the Prototype Design

Does the Prototype meet the Use Case

How well was the Prototype presented

Simplicity of the Design

(Thoughts on simplicity and “Lean consumer experience”by Shai Agassi in November 06, 2006, SAP TechEd interview),

Explain the four evaluation criteria of the jury, and why each of them is important:•Creativity –important point for this workshop, that the participants use their creative energy when thinking about solutions•Match with use case - Important because this ensures that the design of the solution meets the needs of the end users•Quality of the presentation – It’s just a fact that it matters a lot how well something is presented (coming to the main points) to convince an audience (just as if I want to convince my management about an idea)•Simplicity – this goes along the lines of what Shai calls the “lean consumer experience”. Shai gives the example of Colgate and that they do not sell the ingredients and the recipe for a toothpaste, but that they sell toothpaste ready to use. Shai uses this analogy to explain what he means with consumer packaged software. No matter how complicated the technology behind the scenes, the consumer experience has to be as simple as possible.

Also announce that each team has 6 minutes to present, just as if they were on the demo jam.

8


DESIGN LED INNOVATIONThis section will summarize the basic principles of Design Led Innovation.

Before you jump to the next slide, ask the participants what they recall from the previous day. What are the Core Values of DLI and why are they important?

9


The core Values of Design Led Innovation

1. Have an Outside-in Perspective

2. Use Empathy for Users & Stakeholders

3. Embrace diversity

4. Think holistically

5. Collaborate in multi-disciplinary teams

6. Generate many new ideas

7. Find & iterate alternatives

8. Fail early and often

Design lead innovation is hard to define, and most people do not even share a consistent notion of design (which by the way do not exist). Yet, despite the differences in notions, practitioners of Design Lead Innovation share a common set of values that embraces the inherent ambiguity of design’s definition.

The process of designing normally requires considering aesthetic, functional, and many other aspects of an object, which usually requires considerable research, thought, modeling, interactive adjustment, and re-design.

Briefly go through the core values and repeat the most important traits of each core value.

Before you jump to the next slide, ask what the participants recall from the previous day about the DLI components.

10


Design Led Innovation Components

Recap that DLI consists of four phases, of which building is that last.

11



Recap the Design Led Innovation Components with the participants. Ask about details they remember.

12


360° ViewThis section will introduce you how to explore the solution space.

13



Show Pipeline Performance Management video (Beta_clip_01_NoHasso.mov)For the video, explain that it is taken from one of the first projects that the DST has been doing on Sales Pipeline Performance Management. This part illustrates how the 360° View was gathered during this project.

Recap from video:•Importance to observe people in their work environment. Observe how they organize their work, what are their workarounds, what are their sources of information. What do they do before and after using the system.•Capture peoples ideas and understand what they think. •Document as much as possible (use video and audio whenever possible)•Get inspirations from other sources.

14


360° View – Exploring the Solution Space

Gather Competitive InfoWhat are software and service competitors providing in this solution space?

Consider Analysts & Thought LeadersWhat have industry and subject matter analysts written about thesolution?What is the press writing about the solution space?

Research User and Customer NeedsWhat are the needs of the true end users of the solution?What are the needs of others such as IT, implementation teams, partners in the solution space?

Contact Internal Subject Matter expertsIs a department at SAP working with the solution you are researching?Are there colleagues that have worked in the solution space previously?

Depending on how much you were able to talk about this slide on the first day, keep this short.

Explain why the points mentioned in the slide are important:

Gather Competitive Info - It is important to know what the competition is doing and offering. Point out that it does not make sense to just copy the competition, because you can not be sure that they are able to really meet their user’s need with what they offer.

Consider Analysts & Thought Leaders – Analysts are important as they know the market pretty well since they talk to our customers and competitors on a regular basis. Based on this they also make recommendations about software purchasing decisions. They spot technology trends and are the opinion makers out there. Thought leaders as e.g. academia and press are also important opinion makers and trendsetter who influence peoples thoughts.

Research User and Customer Needs – Make clear the difference between end-user (the people really working with the software on a regular basis) and customer (the company buying the software, decision makers) and stakeholders (implementation teams, partners in the solution space). Point out that it is important to get all these views on the solution space!

Contact Internal Subject Matter Experts – Find groups within SAP that use software related to the solution space, or try to find people who have previously worked in the solution space. Also mention that it is perfectly OK to use personal networks and “friends and family”.

15


Share your Research

Present and discuss key points such as:

Market revenue trendsChanging customer needsCompetitive offeringEmerging technologiesMarket readiness

Use this information to:Understand the solution space, constraints and opportunitiesPlan further research

When the research is done, share the findings with the team, to start creating a team knowledge about the available knowledge of the solution space.

Explain that this information 1. Helps to get an understanding of the solution space, informs about non-negotiable constraints,

e.g. already made technology decisions, market opportunities.2. Helps to plan your further research with the end-users, what is it that we want to find out.

16


Planning Research: Customer and User Needs

Plan your ResearchWhat does your market research tell you?What does your team want to achieve?Which users does your team want to see?Which tasks should your team address? Where does your team need to fill in gaps in its knowledge?

What you get(End) User Roles of focusList of research questionsResearch approach

Next step then is to plan the research of customer and user needs. First point out that a good preparation is very, very important, because you may not get more than 60 min with a user / stakeholder, so better make sure to use this time effectively.

What does your market research tell you? What insights did you derive from your market research and how does it influence your user research?What does your team want to achieve? What is it that you want to find out during your research? Make sure you create the right expectations, when you see end-users or stakeholders. Explain in detail what you want to do, e.g. that you want to engage with users and stakeholders in the context of their work environment. Which users does your team want to see? It is important to think thoroughly about the type of user people want to meet. This type should be described in detail. Sometimes a so called “Screener” is used, when e.g. external agencies recruit end-users. They need very detailed descriptions about tasks, responsibilities, experience with systems and processes etc. Point out that it may still happen, that some of the assumptions may prove false while researching, then go back and refine the types of users you may have to see (e.g. many secretaries run the bulk of system work for their managers)Which tasks should your team address? It is also important to have a clear idea about the tasks you want to learn about. Otherwise, you may still be able to gather a general idea of what the person is doing, but you may miss many important points.Where does your team need to fill in gaps in its knowledge?

Make clear that it is fine to change the research questions if necessary, and point out that the researchers should be very organized and professional.

17


Conducting Research with Users

FocusBe flexible to expand your focus as necessaryPlay back what you heard while you are with the interviewee

ContextObserve users in their real (work) situations

Partnership Throughout the interview, assume the user knows much more than you do. You are the student, not the teacher!The interviewee is in control – may stop or interrupt at any time

Observations versus InterviewsAsk questions to understand the interviewees’ work process, but do not influence them Never give a solution to a problem! Help only at the end of the observation, if requested by the user

Explain now HOW to conduct the researchFocus – Importance of focusing on the research questions, being flexible if something unexpected happens. Explain that rephrasing in your own words is a powerful way of reaching a good understanding of the situation.Context – Importance of in-context observation and engagement Empathy! People do many things unconsciously and will not be able to explain what they are doing.Partnership, Observations vs. Interview – Explain a few rules how to behave during the interview: the interviewer is trying to learn from the interviewee, so non-judgmental listening is appropriate, and that the interviewer should never try influence the interviewee during the interview.

Go through the points in the slide, in addition explain the power of open-ended questions. Do a role play that prepares the participants about the kind of users they may meet during the user research.•Have two moderators help you with the role play.•Approach the first one and ask whether you may ask some questions. Have him just say something like “I am so much in a hurry, can’t talk to you…”•Approach the second one in the same way. Have her start talking a lot, talking about everything, from how her mother experienced the challenge last year, and that her sister knows someone who has had the worst experiences with the challenge in question…. As the facilitator try to bring the person back to the focus topic.•Recap that those role plays showed the extremes you have observed in the past, and that everything between them is possible. Also mention that people usually react very friendly.

18


Design Challenge

What?Imagine your team has been hired to design an information service for Bangalore’s expatriates and visitors that helps them to organize their weekends.

Your design challenge is to come up with a concept and/or design of this service based on your research findings.

Welcome to SAP Labs India, Bangalore

Placeholder, exchange withtoday‘s design challenge

Explain the design challenge. Be very specific about the expected outcome. Point out that the participants should not jump to any solution ideas during their research but concentrate on understanding what the end-users do today, and what (additional) needs they have

19


Planning your User Research

Characteristics of the userWhy are you in Bangalore? How long are you staying? First trip?

GoalsWhat do you typically do on a weekend when you are in Bangalore? Do you use any special artifacts or online information?

Activities and TasksHow do you know/decide where to go on a weekend? What methods oforientation do you use? What information do you need?What type of information did you gather before you came? Where and how did you find information? What have you seen so far?

EnvironmentHow does the physical space work to your advantage or disadvantage (accommodation, office)? What type of experiences you have with other people?

Competitive InformationWhat other solutions exist? What advantages/disadvantages do they offer? What are the market and technology trends?

Placeholder, adjust to today‘s design challenge

Use this slide to explain what type of questions to ask the interview partner. Also point out the categories of information that you want to explore:•Characteristics of the user (First time traveler, visitor, real techie…)•Goals and responsibilities (wants to spend a weekend in Dheli)•Activities, tasks (searches the internet, google maps, asks colleagues)•Pain points (could not find information about best travel options to the airport)•Environment•Artifacts and tools they use (Lonely planet travel guide, mobile phone,…)

20


What to do to remind you and share with others?

Take pictures and sketch

How to capture problems, opportunities, ideas and insights?

Make notes

How to identify with the people you see?

Empathize

How to observe and ask questions without judging?

Be unbiased, open-minded

What do you see, beyond the obvious?Be curious

How does process unfold?Notice processHow to capture all their behavior?Consider all senses

How to notice specific details and events?Look and listen carefully

How to approach the end user?Prepare your research

Some Observation Tips

Give some more observation tips:•Introduction to the interviewee: e.g. “Good morning, may I talk to you briefly? I am a participant of adesign class at the PMA and we want to help the DB to improve the ticket purchasing experience/process. I see you are just using this machine. Would you mind if I observe you doing that? •Split into teams of 2 or 3, assign tasks, who is taking pictures (camera), who observes and writes notes, who engages with the user•Make notes: Write like crazy, you will have forgotten half of what you heard after 5 min.•Bring artifacts, e.g. schedules, bills, print-outs, or take pictures of the artifacts

21


If You Return Early …

Do ThisGet back in your teamsPost your market research, pictures and artifactsShare your stories with your team

Don’t Do This YetDon’t try to connect the dotsDon’t jump to solutions yet

Put up this slide after you return from lunch and leave it on the wall.

22


FOCUSThis section will introduce you to interpret the results from your market and end-user research

23



Point out which is the next step in the process: Focus

Show Pipeline Performance Management video (Beta_clip_02.mov)Remember participants that it is taken from one of the first projects that the DST has been doing on Sales Pipeline Performance Management. This part illustrates how they went through the focus section, during which the research results are analyzed and synthesized to gather clarity about the user needs and motivations.

Video recap:•Share the stories with your team to identify user requirements and motivations, and unmet user needs•Do not jump to solutions at this point in time, but try to understand the solution space in it’s entirety first

24


Focus

Define solution space to what is desired by users and the marketbased on your findings

What did you learn from your market research?What did you observe during your user research?Who did you observe?

Prioritize needs and motivationsWhat needs and motivations exist?What is the use case for the user role?

Explain the details of the Focus component

25


What did you Learn from your Market Research?

Consider:Market revenue trendsChanging customer needsCompetitive offeringEmerging technologiesMarket readiness

Use these facts to:Help prioritize needs and motivations and solution aspects Inspire your solution design

Reviewing this information throughout this project to clarify desirability, viability and design aspects.

26


What did you Observe?

For the users you saw, share their storiesTake turns telling your most memorable storyOther team members capture key points on post-it notes per user, for example:User Characteristics

User Goals Activities and tasksPain pointsObservations on the environmentArtifacts and tools they use

Post your data by user

How the focus component works:

Explain storytelling: • Explain that it is important to walk in the users shoes and take his or her position, best to

tell in the I-form. • Other people in the team (ideally only 2 or three) capture key points on Post’its and post

them on wall.• One color per user• One key point per post-it • Write in big characters• Use sharpies, not pen or pencil

Do a little role play for illustration: • One person reporting out in third person, assuming, guessing and judging all the time.

Write only very few post-it’s and explain why you could not write more.• One person telling a rich story in I-form. Write many post-Its and explain why you could

write so many.

Sometimes – and you can not really avoid that – ideas will come up too while you share your stories. Our best experience is to keep them separately for now, like in a parking lot and come back to them later.

27



User N User M User …

This illustrates how the wall will look like, when storytelling is done.

28


Who did you Observe – Identify the User Roles

For the users you saw, identify the user rolesIdentify similarities (and differences) between user goals & activitiesCreate user roles based on similarities between usersIf there are many roles, pick the one you saw most of today.Combine the relevant post-its into a new column for this user roleIf necessary, create clusters within tasks & activities.

Explain the approach of identifying a user role1.go through the points in the slide2.use the following slides to illustrate visually how this process unfolds

Explain that in a real-world software project, there are more than one role, e.g. in the Pipeline Performance Management project, we looked at Sales Representatives, Sales Manager, and Sales Executives. Today, we want to focus on just one in favor of a timely end of day at 6 p.m.

29


Tasks & Activities

Environment

Artifacts/Tools

Pain Points

Goals

User Role NM

Characteristics

User MUser N

Sim

ilar

itie

s be

twee

n

use

rs

Who did you Observe – Identify the User Roles

This illustrates how the wall will look like, while identifying the user roleIdentify similarities (and differences) between user goals & activities and use these to identify the user role.The user role is a collage of users with identical or similar roles.

30


This is an example how a user role was identified during a class in Bangalore. Pretty obvious that the blue post-Its did not flow into the user role. In this case the design challenge was to design an information service for expatriates and visitors (at SAP Labs Bangalore) that helps them to organizer their weekends. While the green, pink and yellow post-it’s were collected from visitors, the blue ones were from Expats, which obviously have different goals than visitors.

31



Pain Points

Artifacts/Tools

Environment

Tasks & Activities

Goals

Characteristics

User Role NM

Clusters

Where to shop?

Medication and Doctors

If necessary, refine subcategories for your user role. At this point in time, Post-its from tasks & activities, Pain-points, environment and artifacts may mix again.

32


Prioritize What you want to Address ?

What needs and motivations can you derive for this user role, based on categories you identified.

Prioritize needs and motivations for this user type based on frequency and importance for the user role (and other)

Pain Points

Artifacts/Tools

Environment

Tasks & Activities

Goals

Characteristics

User Role NM

Where to shop?

Medication and Doctors

If there is lots of data you may have to prioritize goals, issues or activities to focus on. Decide what the group wants to vote on – themes or single post-its or both. Usually we use five voting dots per team member – they can be all on one post-it or distributed between themes.

33


Main Elements of a Use Case

Introductory InformationUser: The primary user, any secondary users, and brief

descriptions of their roles.

Goal: A generic description of the primary usage objective(Include specific parameters for success.)

Preconditions: Any user interaction or requirement that must be true before the use case can begin (e.g., other use cases that precede the use case).

Triggers: Specific actions or events that begin the use case.

User Interaction TableMain interaction task flow

Alternative steps and extensions

Failures, that can end a use case

A use case is a definition of use, from the end-users' perspective, for accomplishing a specific goal within a system. A single use case describes a set of steps -- a sequence of user interactions -- to successfully accomplish the goal. (A use case also shows alternative paths to success, failures, and associated data used in the interactions.) A set of use cases defines all user interaction for an entire product.

Explain the different parts of a use case in detail. Also explain that use cases can be of different granularity. A high level “parent” use case and several “children” use cases. Very often, one use-case ends, and its result is the prerequisite of a following usecase, e.g. •High level use case: Process leave requests•First “child” use case: Enter leave request: Describes how an employee creates a leave request. The result is, that the leave request in the status “to be approved” is saved in the system and a notification has been forwarded to the manager’s inbox. •Second “Child” use case: Manager approves leave request: Prerequisite is, that the manager has a notification in the inbox. The use case itself is then about the approval process.

34


Sample Use Case: Get travel information and buy ticket

User purchases tickets5.

4.

3.

2.

1.

Step

User decides for an option

Train types, connections, price and schedule options

User receives several options for children friendly travel to Mannheim

Destination, Children friendly travel assistance, time between connecting trains, children-cabins

User gives his destination and also that s/he wants to travel children friendly

User wants to inquire about train schedules

User interaction dataUser Interaction

User: Bahn traveler

Goal: Find the ideal travel option to travel to Mannheim with children

Precondition: User knows approximate travel time and destination; user knowswhere to buy tickets and get information;

Trigger: User wants to visit his/her mother who lives in Mannheim together with his/her children

Present another example of a simple use case more related to the training

Discuss also importance of the following parts in full-blown use cases-Failure conditions-User interaction

Leave this slide on the wall during the following session.

35


Tips how to Focus

Share your market research

Share your stories, pictures and artifacts

Tell your teammates who you saw and what you saw

Use Post-it notes to record observations

Organize them into common themes for each user

Identify the user role for which your solution is intended

Prioritize based on frequency and importance

Select the three strongest opportunities

Create a narrative of what the user role is trying to accomplish

36


GENERATE IDEASThis section will introduce you how to rapidly generate many ideas around a potential solution for your use case.

37



Point out which is the next step in the process: Generate Ideas

38


Ideas

Based on identified solution space explore many, rough ideas, possibilities and potential answers

How can we fulfill the needs of the users and use case(s) we focus on?

Focus on a portfolio of best solution ideasWhich of the solution ideas are most promising?

Explain the details of the Generate Ideas component

39


How can we fulfill User Needs?

Use brainstorming techniques to Generate many ideas and expand the portfolio of solution alternatives

Avoid drawing pre-mature conclusions

Inject insights from a broader group

Build enthusiasm for a project

How to brainstormUse the insights you gained and prioritized (pain points, needs,motivations, use cases) during previous phases as a basis for brainstorming.

Individually document your solutions on post-it notes – use words or sketches to illustrate your thoughts

Share your ideas as a team

Go through the points in the slide, and explain what you can achieve with brainstorming, and how to do it. Mention that there is various ways of brainstorming and brain writing, and one them will be presented and practiced today.

40


Which of the Solution Ideas are most Promising?

Once you are done with brainstormingCluster your ideas and name the clusters

Prioritize which clusters are most important because they best address the use case(s) you developed

Explain that after brainstorming, the ideas need to be sorted, analyzed and prioritized.

41


The Rules(yes, there are rules!)

42


DEFER JUDGEMENT“criticism is hard to take, particularly from a relative, a friend, an acquaintance or a stranger “franklin jones

Rule 1

Explain the reason why this rule is important:•slows the flow•hinders building on ideas•makes people hesitant

43


DEFER JUDGEMENT“criticism is hard to take, particularly from a relative, a friend, an acquaintance or a stranger “franklin jones

Rule 1

This is the slide for India

44


encourage wild ideas“if at first an idea doesn’t sound absurd, then there’s no hope for it”

albert einstein

ENCOURAGE WILD IDEAS

Rule 2

Explain the reason why this rule is important:opens up new avenueskeeps it funyou never know…

Example in India: Send child for a fancy dress competition wrapped in aluminum foil

45


Rule 3

BUILD ON THE IDEAS OF OTHERS

Explain the reason why this rule is important:•half of an idea is better than none•be generous•jump starts the next idea•keeps the energy going

46


Rule 4

STAY FOCUSED ON THE TOPIC

Explain the reason why this rule is important:•tackle the challenge at hand•let it go but bring it back•look for surprises

47


“it takes a great man to be a good listener“-calvin coolidge

Rule 5

ONE CONVERSATION AT A TIME

Explain the reason why this rule is important:•Listening is key to capture the idea•allows building on an idea•write it, sketch it, remember it

48


BE VISUAL“draw a crazy picture…put something silly in the world that ain't been there before”

shel silverstein

Rule 6

Explain the reason why this rule is important:•use both halves of the brain•a picture is worth a 1000 words•quickly captures the idea•makes revisiting the idea easy

You can show two post-its as an example, one with small writing and another one with asketch that clearly communicates the idea.

49


“the best way to get a good idea is to get a lot of ideas”-linus pauling

Rule 7

GO FOR QUANTITY

Explain the reason why this rule is important:•pushes the process•every idea may spawn another•screening comes later

It happens all the time that during brainstorming more than one idea comes up to solve the same problem. That is great, alternatives can be tested later and a decision which idea to include into the prototype should be made later. It is not subject of brainstorming!

50


Summary of Brainstorming

Defer judgmentEncourage wild ideasBuild on the ideas of othersStay focused on the topicOne conversation at a timeBe visualGo for quantity

To set expectations, you can mention that other groups came up with as many as 100 ideas during the 45 min of brainstorming.

Leave it to the teams how they do the brainstorming. Propose 2 possibilities:1. Team uses 5 min in silence to write down the ideas independently, then share them with

the team and start the open brainstorming session.2. Start open brainstorming immediately.

Make the point that

51


ALTERNATIVES & ITERATIONThis section will introduce you to methods how to generate rough solution alternatives, and improve them iteratively….

52



Point out which are the next steps in the process: Alternatives and Iterations

53


Alternatives and Iteration

Create rough examples or models (prototypes) to communicateyour solution ideas

What is a prototype?Why create alternatives?What are ways to create alternatives?

Refine your alternatives through several feedback cycles with potential users

What is the internal stakeholder feedback?What is the end-user feedback?

Identify Best Possible Solution

Explain the details of the Alternatives and Iteration components

54


What is a Prototype?

EngineeringPrototyping versus

Represents an early designLooks like… Behaves like… Works likeIs built to iteratively test the function of the new design before starting production of a product or the implementation of a process.

A prototype is an individual that exhibits the essentials of a later type. Websters New English Dictionary, 2003.In other product areas, like consumer products, or the automotive industry, 30-60% of the development time is spent on prototyping. Prototypes are a great way of •Validating story lines•Discuss concepts•Make the user understand that the design is still evolving•Engaging users and draw their attention to the overall conceptIf you come up wit a clickable, high fidelity prototype right away, the user focuses naturally on screen details, like this button should be in the upper right hand corner. This also very powerful and very important, but only in later stages of the design.

55


What is a Prototype – an Example

Philips Homelab

A house equipped with newly designed future products to which Philips invites customers to try out and provide feedbackon future products.

Explain the example of the Philips home lab and how they test new stuff by observing users interact with the devices in a semi-natural environment.

56


Why create Alternatives?

Explore and try out ideas to increase innovation and creativity

Allow alternative designs to be compared quickly

Unearths new possibilities

Reduces failure in the development process by making mistakes early

Focuses on the user interaction early when changes can be made easily

Demystify the design process

If you’re not failing, you’re not pushing hard enough.

Go through the points on the slide.

57


Ways to create Alternatives

PhysicalBuild a hard model

Virtual Model interactions

Experimental Model the experience

Select from different methods and tools depending on your goals and skills

Prototyping methods according to Ahrend and Arnowitz:•Card Sorting•Wireframes•Storyboard•Paper prototypes•Digital prototype•Blank model prototyping•Wizzard of Oz prototyping

You should mention that the choice of prototyping tool is also dependent on the skills of the “prototyper” and the available software. According to Michael Ahrend, it is better to use any tool for prototyping and prototype, instead of not prototyping at all.

58


How to create Alternatives

FocusedFocus on the issueRemove other factorsBreak down concerns and combine them laterCompare ideas

•Use wireframes if you want to prototype possible information organization•You may discuss about a possible solution for days. Why not making it a research question and trying to find the right solution jointly with your customers.

59



RapidDo them fastCreate many iterationsTest many different ideas


60



RoughProvide only essential detailsReduce emotional attachmentAllow quicker iterationsUse flexible media


61


Alternatives and Iteration

IterationsGather stakeholder and end-user feedback on solution alternativesTest and refine your prototypes rapidlyEvaluate feedback honestlyCommunicate results to stakeholdersPlan next iteration (method, fidelity… )


62


Your Design will be Evaluated based on

Creativity of the Prototype Design

Does the Prototype meet the Use Case

How well was the Prototype presented

Simplicity of the Design

(Thoughts on simplicity and “Lean consumer experience”by Shai Agassi in November 06, 2006, SAP TechEd interview),

Ask the participants to start prototyping. Explain that •They can use all the supplies in the room•The prototype can be anything from a role play to a physical prototype, a conceptual design or whatever seems appropriate to the team.Remind the teams about the evaluation criteria for the prototype and that the end users will be available at about a quarter to 5.

63


THANK YOU

› dschool › resources › SAP Materials › DST workshop... · A Workshop on Design Led...

Documents

Transcript of › dschool › resources › SAP Materials › DST workshop... · A Workshop on Design Led...