Original article can be found here (source): Artificial Intelligence on Medium
How can food stores avoid waste by tapping into their local communities in real-time? Current channels run through in-store promotions, newspaper advertising and targeted social media ads… what if stores, instead could tap directly into the ingredients of preferred recipes being cooked by their local communities every day?
PlantJammer came to us wanting to explore how they could support retailers reduce food waste via their AI-driven app. They were already in early dialogue with a number of retailers, but needed to understand how they might serve them in the best possible way? We decided to run a 1-day ‘product-definition-workshop’ together with their development team to explore, define and design a viable solution to the challenge of “minimizing retail food waste”. The outcome should be a prototype that could validate the solution with real customers the following week, and provide the team with the insights required to prioritize the most important features to build.
Product definition workshop
The key purpose of the workshop was to create alignment within the development team, and rapidly arrive at a solution to be tested in the marketplace. Providing valuable market and user feedback, together with learnings that would inform the final solution.
The product definition workshop should be seen as a 1-day co-creation session tapping into the collective intelligence of the product team. We divide it into the following key four steps:
A. Define a shared team vision for the product (together with success criteria)
B. Define the key user(s) of a potential product (Their needs from it? Triggers for using it? What stops them using it?)
C. Develop ideas & prioritize features that meet key user needs
D. Create a paper-prototype & improve it through user testing
Here is the schedule from the day we ran with the PlantJammer team:
09.00 Check-in & desired outcomes (align expectations)
09.30 Product Vision, success & KPI’s (lego exercise)
10.15 Break (coffee/tea/snack)
10.30 Archetypes (define needs, triggers, barriers)
11.15 Rapid idea development (teams of 2)
12.00 Lunch & walk around the block (reset)
13.00 Key-feature prioritization (core, hero, park)
13.45 Paper-prototyping key features (parallel teams)
14.30 break (coffee/tea/snacks)
14.45 User testing + iteration (parallel teams)
15.30 Consolidate + next steps
15.50 Check out