Bella Scena
A friendly, supportive project management system that unifies to-do lists, meetings, and calendars.
Challenge
Increase Bella's user engagement and retention, as well as her sharability, while reflecting her helpful, human personality.
Solution
Several high-fidelity prototypes, researched and determined feasible to create, outlining useful and desirable functions.
Key Deliverables
Methods
Journey mapping
Rapid ideation
Affinity diagramming
Surveys
Kano analysis
Prototyping
Tools
Paper + pencil
Otter
Sketch
Axure
What
-stakeholder interview, client introduction, listened, what they said they wanted, goals
Why
-get a sense for the client, understand their priorities and thoughts around expectations
How
-team sat, listened, took notes, asked questions, asked for permission to record talk for later perusal to ensure we didn't miss anything
What
-engaged with team, went over our general thought processes when stressed and how to knock each other out of it
Why
-to prompt awareness, both in ourselves and of our teammates, to be more mindful of our differences, and to be familiar with our crisis points so we can react
How
-thoughtfully wrote down a few topics on post its to talk about
What
-immersed ourselves in the site
Why
-learn the ins and outs of Bella Scena and how it impacted her users, to find the gaps between what currently exists and what could exist
How
-browsed the site and created journey maps
What
-rapidly ideated sketches for website features
Why
-to brainstorm what new value might be created, simply getting ideas out of my head
How
-I listed ideas based on gaps in function I saw from the site and based on the goals that the client had given us, then physically sketched out ideas as to how they could take form
What
-worked with client and developer representing team; looked at our ideation sketches
Why
-learned what is feasible for the development team to create; helped prioritize new features, given limited budge and time; learned if the idea was already being worked on; if idea needed clarification before the dev team could make it a reality
How
-they came in, my team posted up all of our sketches using affinity diagramming to organize, and they went over each sketch one by one while we took copious notes; also asked for permission to record voices
What
-voted what to prioritize and learn from Kano user surveys
Why
-trying to figure out what was both feasible, within client's budget of hours, and worth giving as a survey, so as to not overwhelm our survey takers and increase completion rates
How
-posted ideas, clustered them (again using affinity diagramming), and discussed which ones to continue with
What
-conducted a Kano analysis survey and synthesized data
Why
-to get concrete data, not just opinions, as to what primary users require, enjoy, don't care about, or actively dislike having in their to-do lists
How
-survey designed for a Kano analysis, which we then sent out to a group of primary users
insight Gained
If a survey respondent gives consistently contradictory results, it's most likely due to confusion over a question's wording.
Story
While examining our survey's data, my team noticed one respondent who gave several contradictory answers in a row.
What
-chose, created, and annotated wireframes, ideating further function/stages of prototypes, sketching based on design points, and digitizing
Why
-narrow down a focus for the development team to focus on in a two week sprint
How
-used data from previous survey and meeting with dev team/stakeholder, sketched in sketchbook, and input into Sketch