1-hour free remote workshop to make faster, informed, and de-risked decisions.
Remember? Experimentation is the scientific approach we learned in high school, which consists of making hypotheses and testing them one by one.
In the context of innovation development, it's much more fun. Experimentation is a mosaic of tools and common sense to collect unique customer behavior data — frugally — even before investing heavily in development resources.
An experiment is, for example, how Drew Houston shared a 2-min explainer video to adjust and validate his concept even before developing Dropbox. It's also how Brian Chesky went out of the building to personally serve users so that he understands how to improve Airbnb.
More insightful stories here 🔥
In 1 hour, I will help you map out an experiment for your innovation.
As a way of introduction, I’m a product manager and mentor based in Paris, specializing in design thinking and lean startup methods.
I have worked with innovation leaders from large companies for seven years, helping them launch user-centric digital products effectively.
I am convinced that innovation is not reserved for startups. Innovation teams in large companies also adopt an entrepreneurial mindset to push boundaries, test breakthrough ideas, and shape the future.
It's an absolute pleasure discussing agile and product management with Adam.
Adam quickly delivers tangible results by engaging with end-users and key stakeholders.
I appreciated Adam's rigor, listening skills, and the quality of his deliverables.
An experiment is not about redirecting users to a landing page or sending a satisfaction survey.
Identifying the correct hypotheses and testing them with the appropriate methods is crucial to avoid any wrong decisions influenced by bias.
This is what we are going to do during this 1h workshop!
10 min
We will clearly define the challenge and at what stage of the funnel the innovation is in to select relevant experiment types to validate various aspects of the solution.
10 min
Regardless of the innovation stage, we will map out the assumptions, prioritize the most critical ones, and convert them into hypotheses ready to be tested.
10 min
Once we have ranked the assumptions and defined key hypotheses we want to test, we can select the most suitable experiment to test and validate (or not) the hypotheses.
30 min
We will get our hands dirty and start developing the materials for experimentation using the best prototyping and no-code development tools.
By the end of this mini-workshop, you'll have a better definition of the challenge and the experiment to run. I'll share with you a document of the outputs to keep and share with your team.
Fill in this form, and I’ll get back to you in the next few days.