capstone
Case Study
MODE: Rideshare
Sitemap
Now the fun starts. With clear user stories, I could start creating a clear map of how these stories would integrate at the level of screens. From a bird’s eye view, where does the user begin? Where would the user feel they achieved the goal of the story they are experiencing?
By visualizing these structures, new opportunities appear. Where can I create simplicity by allowing screens to be leveraged for more than one story? In the same breath: where are moments where clear separations between screens or paths are necessary?
One of the key things to keep in mind is that simplicity doesn’t mean that one screen does everything.
Simplicity can just as often mean limiting the level of demand my design places on the user’s cognitive bandwidth.
Sometimes I needed to streamline sequences of screens to maintain the momentum of engagement. Sometimes I needed to align the hierarchy of tasks with the structure of screens, keeping mind which tasks from user stories deserved major real estate on screen, and which made more sense to move into sub-menus.
USER FLOWS