ACTIVITY FEED – Playbooks


PRODUCT GOALS
To build a notification engine that dynamically generates relative information about a customer’s service, computers, users, events, suggestions, and reminders.

THE RESULTS
This agile process from MVP through Vision was executed flawlessly. And by introducing the detail panel, I simplified the experience by eliminating the need for the user to drill down to another page. Press had early access to the platform. View

1. DIAGRAM FLOW
I created this high-level user flow to align the user journey and UI model with the product goals.

2. CONCEPT ITERATIONS
Through whiteboard sessions the team was able to understand a holistic view which helped synthesize the product features.

3. MVP — LEARNING LESSONS
My original feed design was rough by necessity but flexible, allowing the team to focus on more important features. We had to ship with an MVP product, which basically was an amalgam of all individual feed types and events. This is agile thinking — recognizing you can’t expect to build everything, or we would never ship.

4. CUSTOMER FLOW
My process was designed to maximize communications with developers. I printed out a UI site map on a large format printer, then got the developers in a room to walk them through the user journey. This approach helps to speed up the development process, so everyone is on the same page.

3 thoughts on “ACTIVITY FEED – Playbooks”

  1. Pingback: stromectol cost

Comments are closed.