SecondBite App
Waste less food from shopping to cooking
* 1-min summary
Problem: People feel guilty about wasting food, but they still keep wasting it.
Process: Researched and analysed the deep reason for food waste and how to change people’s behaviour.
Outcome: An App that motivates individuals and helps organise food.
See prototype
Duration
A 2 weeks sprint
Tools
Miro, Google Form, Paper and pencil, Figma
Team
Ivy, Marc, Setti
Deliverables
Prototype, client documentation, and a recommendation for what’s next.
Methods
Secondary research, user interview, user survey, affinity mapping, problem framing, competitive and comparative analysis, archetype and scenario creation, Minimum Viable Products, design studio, sketching, wire-framing, prototyping, usability testing.
1. The brief
SecondBite is an organisation that focuses on solving the food waste problem within Australia. They were sending the unsold food from farmers and large retailers to charities. Now, they want to raise awareness of the impact of food waste, they also want to encourage public and small businesses to reduce food waste. Household food waste constitutes the highest ratio in Australia.
How might we create a tool to encourage and support individuals to reduce food waste?
2. Key founding from research
Most people feel bad about wasting food because of wasting money in general, and they feel guilty about the undernourished people.
People don't have enough understanding leading to no motivation to change their habits.
3. The solution
Motivating people by educating them about the impact of food wasted.
Developing an app that can motivate people by saving money, help people manage their foods by providing recipes, generating shopping lists, monitoring food expiry dates, and providing bite-sized education.
4. Testing & result
We tested our sketches with 6 potential customers.
The result shows that we are on the right track with helping people to store their food by storing tips, planning, and cooking meals with recipes.
We added additional functions around the recipe and deleted some complicated technical functionality around the purchase recorder.
5. Next step
From the design perspective
More usability test
Flashing out more detail of the functionary
Consider gamification
From the business perspective
Consider providing recipe
Consider the social media
6. Reflection
We should not only focus on user needs and business goals while designing. We also need to consider the technical limits.
While prioritising the feature, we need to think of the easiest way to archive the primary goals of users and businesses.
