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.
Users
Primarily female solopreneurs and small business owners.
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
My team started off with a stakeholder interview, where we were introduced to the client and her goals for Bella Scena, a project management system. As we sat, listened, and asked our questions, I was able to get a sense for our client, better understanding her priorities and expectations.
[state about project, goals, few things learned]
Then before we began to dig into the material, my team quickly re-familiarized ourselves with each other. Since we would be working in close concert with each other, being mindful of ourselves, our teammates, and our differences would help our team run smoothly.
So, prep work done, we immersed ourselves in the current site, learning Bella Scena’s ins and outs. Trying to find the gaps between what currently existed and what could exist, I created a journey map showcasing an idealized course of events for a primary user.
With Bella more understood, we then rapidly ideated sketches for website features. My goal was to brainstorm features that would create new value. Essentially, I listed ideas based on both gaps in function I saw from the site and on the goals that the client had given us, then physically sketched out ideas as to how they could take form.
What
Rapid ideation of potential website features
Why
To get ideas out of my head, brainstorming new value for the site
How
Listed ideas based on gaps in function I saw from the site and on goals that the client had given us, then physically sketched out variations as to how they could take form
Everyone having created several sketches, we then worked with the client and a developer representing their programming team to understand the feasibility of our ideas. Given the development team had a limited budget of both time and money, this period of collaboration was able to clarify what features we UXers should focus on. Additionally, we were able to learn if a similar feature was already in production, or if our sketches needed further clarification for further development.
Having gained that valuable feedback, my team then clustered our ideas together by affinity diagramming, in order to discuss which ones to prioritize moving forward. Now that we had a better idea of our client’s capabilities and desires, it was time to turn to the users themselves. But before any more time was invested into these features, we had to judge what was both feasible, within our client’s budget of hours, and worth giving as a survey. After all, not overwhelming our survey takers with questions would increase completion rates.
So, we then conducted a Kano analysis survey in order to get concrete data as to what primary users required, enjoyed, didn't care about, or actively disliked having in their to-do lists.
Synthesizing that data, we found that […]
With that in mind, I chose, created, and annotated wireframes of potential features, in order to visually convey a narrow focus for the development team in a two week sprint. From sketching in my sketchbook to inputing the ideas into Sketch,
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
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