Design thinking / process:

In an end to end process I always start defining the user (personas) and the problem (definition). From there I ideate, detemine user flows, draw up some lo fi wireframes, then hi fidelity mock ups and lastly clickable prototypes. Next is user testing and then refine and re build.

I used the above framework for this recent whiteboard demonstration. The problem involved a group of supervisors that wanted and easy way to keep informed about their employees progress, what issues they were facing and how satisfied their customers left. I decided to create a data visualization dashboard with two sections, an employee side and a customer side. Every time customer satisfaction was low, based on nps surveys, the supervisor will get an alert. Similarly if a catogory of problem, say “connectivity”, kept showing up, they would also get alerted. Every employees customers and issues could be drilled down into a seperate table which rolls up underneath. All documentation would also be linked to the ticket numbers.

Healthy Habits App, Mindshift

Problem:

Frank is about 30 pounds overweight and not physically fit.  He’s not really motivated to make losing weight/ getting healthy a priority. He Needs an easy rewarding experience he can come back to on the reg.  Frank wants to use a credible diet program that helps him slowly add healthy habits into his life. Lets design an App to meet his need.

How Might We:

See how I am doing, (i.e. Visit my program dashboard)
Explore other healthy habits I could adopt
Find out what to do next

Design direction:

The app name should be mind shift as the user must already have established habits that can be

Modified
Acquired
Discarded

As the path of least resistance this will keep the user more engaged with small gains
This is primarily to be a healthy habit app vs hardcore dieting app.