3X: Technical practices to use (or not) in Explore, Expand, Extract.

What technical practices fit (or don't fit) in each phase of 3X? Are there some that we find are always valuable? Are some technical practices, that we once thought of as fundamental, actually slowing us down in certain 3X phases? How does the context change this – e.g. a feature in Explore for a product in Extract?

Format

6:30 - Arrive, grab a bite to eat and have a drink;
7:00 - Quick intro by Antony Marcano, outlining the workshop;
7:15 - Split into groups to explore practices that help or hinder in 3X phases;
8:00 - Play-back and open discussion, hang out, socialise, chat.

About 3x: Explore, Expand, Extract

Winning ideas proceed in three phases:

Explore – the risky search for a viable return on a viable investment through experimentation. If you’re lucky, one of your many experiments turns out to be unexpectedly successful, which leads to:

Expand – now things are going nuts (think Pokemon Go or Facebook Live Video). Now, all you have time for is to eliminate the next bottleneck just before it derails you. Once growth becomes routine, it’s time to:

Extract – now the shape of the problem and solution spaces are clear. One euro in equals three euros out. Playbooks emerge, economies of scale matter: delivering the service at lower cost is more profitable.

For more, start with the Product Development Triathlon (https://www.facebook.com/notes/kent-beck/the-product-development-triathlon/1215075478525314/), by Kent Beck; see also 3x – Navigating the Path of Winning Ideas (https://ideas.riverglide.com/3x-explore-expand-extract-b9aad6402a5a) by Antony Marcano, with Andy Palmer.

https://secure.meetupstatic.com/photos/event/6/d/c/e/600_459868110.jpeg