Z-Dash Udacity Product Management Nano-Degree

1. Sketch

2. DEFINESKETCH
Crazy 8’sCrazy 8’s

3. DEFINESKETCH Crazy 8’s
Solution
Sketch 1
Solution
Sketch 1

4. DEFINESKETCH
Solution
Sketch 2
Solution
Sketch 2

5. Decide
© 2019 Udacity. All rights reserved.
Picking the final
concept to develop
into a prototype

6. Decision MatrixDEFINEDECIDE
High
Effort
Low Value
Low
Effort
High Value

7. YES - Why?DEFINEDECIDE
Restaurant Dashboard:
Though it wasn’t on my crazy 8’s, this is our first
and most important product goal
“Provide a one-look value: .
All needed info in one place, live.” .
Issue Pop-up:
As part of the dashboard, handling issues must be
combined. It is also our second product goal
“Allow users to handle most software .
issues on their own, without the IT team” .

8. NO - Why?DEFINEDECIDE
Backend of issue handling:
We need the front-end team to start working.
Also, the issues theme should wait for another
sprint with more developers on the team.
Custom Reports:
I feel pretty good about the solution sketch,
I don’t think we need to invest a full sprint
to complete it.
Also, reports use come after the first usage
of the system, so that can wait for a P1 sprint
if needed.

9. Final Prototype GoalsDEFINEDECIDE
HMW allow
users to solve
software issues
without IT or
support team?
HMW create map
layers for users so
that all needed
info is available in
1 shot?
HMW show all
bots tracking for
users to be
alerted on issues
immediately, so
they can handle
ASAP?
Data Visualization
Handling
Issues