Who Needs Diapers?
Creating moments for connection
Our hi-fidelity prototypes were research-informed and created to give users moments to experience emotional or practical appeal when purchasing diapers. Our main focuses while iterating on these concepts were:
Presenting diapers as personable and valuable items
Addressing the concern over buying duplicate items
Implementing tactics to combat the overwhelming UI
Through the process of Sketch, Implement, Evaluate, and Iterate we were able to introduce a few key features into the context of the Amazon Baby Registry interface using Figma. We transitioned quickly into hi-fidelity since the features we were creating were best understood in the context of Amazon’s site. Evaluation occurred using a survey of 8 mothers from the Pamper’s Advocacy Network (PAN).
Presenting Diapers as Valuable
We discovered that most Creators see the value of diapers and add them to their registries but Gifters do not purchase them. Perhaps the biggest challenge facing this goal is that Gifters think that diapers are a low-effort gift with no lasting permanence. We set out to ideate how the platform could combat that.
Creator Note Boards
Taking inspiration from competitor sites like Target and BabyList, this concept intends to bridge the gap between Creator needs and Gifter browsing, allowing the Creator to establish a more personal or emotional connection if they wish and highlight priority items. Initial sketches gave Creators the option to pin or add notes to items, thus breaking down the walls between Creator and Gifter.
Evaluation findings:
Our participants really liked this feature for its personal feel and focus on the relationship between Gifter and Creator.
Overall this concept earned a 5.0 out 5 in terms of Likelihood of Use. It was also the most liked concept of the five tested, earning the highest average of 4.3 out of 5.
Most participants (7 out of 8) assumed that this concept would encourage them to buy more diapers, however, the testing did not involve adequate situational testing in this area to make any stronger conclusions.
Final Design:
Since our participants really liked this idea, we did not make any further iterations on this concept and instead focused our iterative efforts on the other concepts.
Concern Over Buying Duplicate Items
Registry Analytics Feature
Building on the interview insight that Gifters were concerned about buying something that others had already bought, we wanted to implement an easier way for Gifters to see what other Gifters on the registry were doing. Amazon does not have a feature within their baby registry that shows which parts of the page and/or categories are being visited, so we took the liberty of creating one. This feature would show analytics of what other Gifters are purchasing from the registry.
Evaluation Findings:
While most participants liked this concept, they felt it was still a little ambiguous and needed a more digestible visualization.
Overall this concept earned a 4.5 out of 5 in terms of Likelihood of Use.
While some participants (4) expected to see how many diapers would be bought with the amount of money in the fund, 3 participants expected to see how many diapers had already been purchased from the registry, and one participant wanted to see both.
Most participants (7) either agreed or strongly agreed that this concept could encourage them to buy more diapers (further testing required).
Final Design:
To alleviate some of the issues that our survey participants found, we decided to add color coding to the bars to make them stand out more. The hope was that appeal-focused Gifters see that the items they like to buy are already purchased, it could motivate them to look at other categories and buy from there instead.
Project Plan: I specifically focused on creating and setting up the team’s timeline for the semester. After creating the milestones with the team, I inputted the important dates like presentations and documentation checks, created goals for each week, and filled in possible activities that we could use to achieve those goals.
Throughout the semester, as our problem space shifted, I tried to keep this document updated and crossed off activities as we completed them.
Daily Agendas and Delegation: My co-lead and I usually met every weekend to assess where the team was at and to determine goals for the coming week. Based off of our project plan, we would determine actions that needed to be completed each day of the week, and we also discussed plans for delegation of work.
since we had a large team and multiple different users/problem scopes, it was important that we delegated work well enough that every member felt that they could contribute substantially. We split the group into smaller groups of four and each group completed a process map from the viewpoint of one of our user groups: Creators and Gifters.