You have a great product idea that you want to bring to the world. You have the resources (people, funding) necessary to move forward. You dream of creating a first prototype (MVP) and taking it to market.
Unfortunately translating business and market requirements into engineering specifications is not straightforward. There are plenty of decisions to be made, questions to be answered, and details to be considered. A lot can get lost in translation. This is why it is important to follow a proper process.
At Emerging Humanity we believe that a good methodology creates clarity for everyone involved and ensures that things don't fall through cross-functional cracks. It also helps your product vision carry through from the high-level functionality to the individual development tasks. This guarantees that what you bring to the market aligns with your higher goals.
Emerging Humanity's approach follows a step-by-step 3-Phase process and creates a clear execution path. All you have to do is to walk it!
This phase builds shared understanding of what the product is (and what is not). Starting point is the business functions that the product will perform, ideally delivered through a Product Vision Board. These functions are expanded into product features and prioritized into an initial roadmap that ensures important stuff is done first. (Sounds obvious but unfortunately it is quite uncommon).
Phase I delivers a clear description of what the product will do. This can become the basis for defining and executing validation experiments, and ultimately for creating your MVP feature set. This is also the time to make an initial assessment regarding product architecture and technology selection, and to get a rough budget estimate for development.
“Success nowadays is not about what you do but about who you are.
To reach higher in business you have to become grander as a person.
Your inner strategies are as important as your outer ones.”
Emerging Humanity is using simple but effective tools in order to distill the broader product idea into detailed product features. These tools can bridge the gap between business and engineering and turn the product vision into tangible product definition. The are mentioned here as a quick reference.
“Christos knows the right tools and methods to use and helps you formalize a clear road map for development through a process of engaging discussion and analysis.”Karl Björnsson, Cofounder/CEO, Hefring LLC
Phase 2 complements the text-heavy Product Definition (Phase 1) with necessary visual information (layouts, flows etc). This delivers a clear picture of how the product will look & behave and it allows sign-off by both the business and engineering teams. You are ready for development!
In this phase the process moves to engineering. Technical decisions about the architecture are getting finalized, the developer team is put together per the required skillsets, and the product is getting developed. This phase also includes deployment of the product and all related DevOps activities.Phase 3 includes:
Emerging Humanity advocates Agile/Lean product development. The phases mentioned above build on top of each other, but the overall process is not sequential; there is some initial bulk work needed to define the product and its roadmap (Phase 1), but development then progresses in iterations, each one including a bit of all three phases. If the groundwork is done properly, this approach maximizes ROI of the development effort.
In addition, the iterative process can be combined with milestones for conducting market experiments and validating initial implementation of the various product features. This delivers invaluable feedback on the product, allows early course adjustments, and helps get a more valuable product faster to market.