Notes before designing:
• Our stakeholders all shared the fear of their roles/reach being reduced if we consolidated applications
• It was impractical to combine the entire backend architecture without creating an unruly monolith, thus resulting in the "hub & spoke" model
• Currently, all applications are designed by individual designers, which ultimately creates a lack of consistency among apps in our stores
In this demo, our stakeholders were able to visualize:
1. How a "hub and spoke" model reduces the threat to our backend architecture, while still giving the user the appearance of a singular app
2. How a user can either begin the highest-priority system-directed task, or create a new task based on human observation
3. How we might incorporate metrics and gamification for our users as an encouragement
4. How we could integrate exception flagging into a user's in-progress task without app-jumping
5. How we can utilize pause & recovery to ensure customers are still the highest priority while task metrics remain accurate