SI | metaFox working principle: "Iterative Improvement"

Expert: Tobi

TLDR

Through a step-wise, iterative product & content development process, we gain speed and include perspectives of different people, resulting in high-quality products and services with a good fit for our customers' needs.

Information

According to the 80/20 (Pareto) principle, it takes you only 20% of the time to achieve an 80% of the effort. Fine-tuning the last details (the "last 20% greatness") is what takes a lot of effort and time. Consequently, the last 20% quality takes 80% of the effort!

How to apply the 80/20 principle to product development practice?

Process steps

1. Get from "research" to "drafting" early: As the lead product developer of a project, start getting drafts on paper (or Conceptboard) early, possibly while still familiarising yourself with the underlying concept of your product. Get your hands dirty early and produce an imperfect draft. Before you fall in love with your draft, pass it on to get an early review and a new perspective on your idea.
2. Pass your imperfect draft to your co-developer: As soon as you reach a first draft (80% version that took only 20% of your time) pass the working document (linked in an Asana card) to the co-developer/sparring partner of your project. They contribute with extensive feedback (e.g. as comments on Conceptboard) or make direct edits to your draft, building on your idea. If possible, run some tests with the products with real customers, or at least the foxes.
3. Back to you, repeat, repeat, repeat: After your co-developer's review/iteration, the draft goes back to you. Repeat this process various times, moving the Asana task back and forth between different people to include a variety of perspectives, ideally internally but also externally. Every time, the product will improve and benefit from these different perspectives. Also, present the draft to the rest of the team (via Slack message or during a meeting) to get more outside opinions.

What to keep in mind

1. Love the problem, not your solution/Don't take it personally. Receiving extensive feedback on your draft might be tough, especially when you already invested lots of time and energy. Don't take the feedback personally. Its intention is not to criticize you as a person but to improve the output of your collaboration process. Stay open and implement your co-developer's ideas in a reasonable way. That can also mean rejecting certain ideas! Meet up for a discussion if you're not on the same page.

2. Embrace a “growth mindset”. Rather than feeling like you need to be right the first time, assume imperfection so you remain open to improvements.

3. Do not get stuck iterating. There comes a point when making improvements and changes to the same activity or prototype over and over yields little additional benefit. Iterate until you feel that you are on the right path and move forward; s. also SI | metaFox working principle: speed vs. quality aka. the "good enough principle"
4. Let go. As product developers, we build our products from the ground up, so it will come to a point where you'll be overprotective and sentimental in the content of your project. Let other people see your project and be open to their perspectives. Welcome them with an open mind because the bottom line is that we all want to make the product better and more effective for our clients.
   

Theoretical background

This principle is loosely based on the idea of iterative improvement as coined in Lean Manufacturing by Toyota or in "The Lean Startup" by Eric Ries. Watch this video summary to learn more:

https:/youtu.be/RSaIOCHbuYw

History

At metaFox, we've been following this process already when creating the very first deep pictures sets. During our 2022 Team Retreat in Sorsogon, we've put it down as a "working principle".