NIMBLE STORY
During this project, I helped with the development of new features for Throughline Inc’s internal website by conducting research, building wireframes, and creating prototypes based on user flows. Over four weeks, one other intern (Ena Sullivan) and I focused on creating a prototype of the “project planner” feature that would soon become an addition to Nimble Story, the internal website used to keep track of the company’s projects for employees as well as clients.
Over the course of this project, we worked through understanding the back-end of the site’s capabilities and limits, keeping these in mind while constructing the front-end design and user flow.
Collaborators: Jared Adams, Ena Sullivan
My Role: research, user mapping, user-flow, developing wireframes, prototyping
FINAL PROJECT PLAN LANDING PAGE
RESEARCH & USER-MAPPING
Before beginning to develop user flows, it was essential to research similar programs and ensure I had a grip on the existing Nimble Story site’s design.
​
One area of uncertainty I ran into at first was how the design was going to deal with existing plans versus adding new plans.
This also led to the question of if the user should be able to choose from templates, make custom project plans, or even edit existing templates.
​
Although difficult, I was motivated to figure out a way to let the user have all of these capabilities as I thought they were necessary elements for the employees to use.
.jpg)
USER-FLOW
WIREFRAME SKETCHES
After creating separate journeys for different user starting points, the next problem to solve was how to combine these into one single flow.
​
The user-flow pictured to the right is what we landed on after lots of editing, tweaking, and rearranging. And this flow still got edited as the next steps progressed.
​
The final step before moving into Figma, and surprisingly the most difficult, was sketching wireframes.
FINAL PROTOTYPE
Jumping from the rough wireframes into creating the pages in Figma, forced me to consider a broader range of details that didn’t seem as obvious previously -- such as the necessity of including a progress bar for the user to see where in the process they stand currently. I had expected the prototyping itself to prove more challenging than laying out the new pages in design with the existing pages. Yet the prototyping was relatively straightforward as a result of our user flowcharts.
The beginning user-testing stages did, however, cause debate over how the plans should be saved and allowed us to go back and make adjustments. The prototype featured below is the project planner design in the middle of user testing, before it was finalized.