Get Started. It's Free
or sign up with your email address
exercise by Mind Map: exercise

1. 2. get to know the problem

1.1. why a communication tool?

1.2. what's behind a communication feature?

1.3. what data or information to back up the initiative?

1.3.1. do we need user research?

1.4. what are the user's pains?

1.5. have users reported this need?

1.6. are there any alternatives?

1.6.1. what other ways we could solve this problem?

2. 3. ideate

2.1. Design Sprint-like workshop

2.1.1. set up stage logistics team sales/marketing product UX dev facilitator

2.1.2. day 1 - understand/refine the problem set a long-term goal why are we doing this project? where do we want to be in the next 6mo, 1yr list sprint questions how could we fail? assumptions be pessimistic make the map customers on the left, objective on the right ask the experts is the vision correct? what have we tried before? what do we have from customer research? HMW frame problems into opportunities prioritise and choose which ones to target

2.1.3. day 2 - solutions lightning demos look into alternatives from other companies analogous inspirations sketching gather information from other activities create a lot of different ideas

2.1.4. day 3 - solutions vote on strongest solutions storyboard fill in the storyboard with winner sketches from last activity

2.1.5. day 4 - prototype

2.1.6. day 5 - test the idea interview 5 users collect feedback find patterns plan the future

3. 1. get to know the costumers

3.1. the driver

3.1.1. mobile? can they text while driving? how's the legislation in Germany/other countries door2door operates? how many of them use voice-command control? can they perform "super simple" interactions through the phone screen? example/idea: respond with a quick-one-tap “thumbs-up” emoji what are the simmilar apps they use? what are the other constraints?

3.2. the passenger

3.2.1. mobile?

3.2.2. when does the passenger needs to talk to the dispatcher? why?

3.3. the dispatcher

3.3.1. desktop?

3.3.2. what else do they use?

3.3.3. when does the dispatcher needs to talk to the passenger? why?

3.4. do we need more user research?

4. slides

5. 4. execute

5.1. future plan from Sprint's day 5

5.1.1. epics most important user stories break down dev team backlog measures of success

5.1.2. milestones what's the MVP? releases

5.1.3. roadmap

5.1.4. team capacity how many people we got for the initiative?

5.1.5. capabilities needed what skills are needed to get the work done?

5.1.6. deadlines?

5.1.7. approval?

5.1.8. other constraints?