This document discusses framing the problem and understanding the goals for a product to provide food delivery by robots. The problem is that demand for this service is increasing due to the pandemic and need for contactless delivery options. The product goals are to provide all necessary information in one place, allow users to handle most software issues themselves without IT assistance, maintain error documentation and handling procedures, and present detailed reports and insights. Two key users are identified - a 21-year-old restaurant manager and a 52-year-old restaurant owner. Nine potential sprint goals are identified relating to data visualization, handling issues, and the human-bot relationship. The focus is chosen to be on the data visualization theme to provide the main functionality of tracking delivery

1. Framing the Problem

2. PROBLEM New market
Food delivery by robots was first introduced in 2018
Increasing demand
Due to the pandemic and need of affordable contactless delivery options
Product Goals:
● Provide one-look value: all needed info in one place, live.
● Allow users to handle most software issues on their own
without the IT team
● Maintain errors documentation and the handling flows
● Present detailed reports and useful insights

3. Understand
A shared
understanding
Of the space,
The problem,
And the goals.

4. UNDERSTANDUNDERSTAND
The product we’ll design here,
will be the base product for the
Doordash control team as well.
But in this sprint, we’re focusing on
users on the restaurant-end only,
since they’re “the market” itself.

5. SER
B
USER
A
UNDERSTANDUNDERSTAND
Lisa, 21
- Restaurant Manager
Also a student at UPenn
- Managing a team of
4 people on-site
- Used to manage 3 more drivers
for deliveries, but recently
started using bots for that
- As techy as 21 year olds
come nowadays
- Main device: Doordash iPad
- Some network issues/delays
to be expected in a busy
restaurant in Philly
Bob, 52
- Restaurant Owner
28 years in the family business
- Managing a team of 2 people
including his wife
- Started offering deliveries via
Doordash during covid-19
- Scared of technology because
he feels “too old” for that
- His grandaughter can’t stop
talking about robot deliveries,
so he signed up for the service
- Main device: Doordash iPad

6. UNDERSTAND
It was a process,
But we have the finalists:
9 aspiring sprint goals
UNDERSTAND

7. UNDERSTAND
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?
HMW deliver
insights to a user
so their job is
made easier /
smarter?
HMW deliver
extra content for
users so that
Doordash can
have a new
revenue stream?
HMW explore
the bot abilities
(video, voice,
screen) for
interaction with
end users?
Data Visualization
Human-Bot
Relationship
HMW create a
ticketing
hierarchy for
errors and
issues, so that all
of them are
handled
properly?
HMW build a tool
for tracking &
reporting speed
issues with bots
so that we can fix
them?
HMW solve
hardware issues
from afar for our
users so we
could provide
360-support?
Handling Issues
HMW allow users
to solve software
issues without IT
or support team?
UNDERSTAND

8. UNDERSTAND
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?
HMW deliver
insights to a user
so their job is
made easier /
smarter?
HMW deliver
extra content for
users so that
Doordash can
have a new
revenue stream?
Data Visualization
Handling
Issues
I chose to focus on the
data visualization theme,
because this is the
main functionality of
the system.
This is the real P0 for a
new product like Z-Dash.
Part of the theme also
relates to handling
issues, so we earn both
by focusing on the
visualization theme first.
UNDERSTAND