A two-diamond design model that aligns engineering and product teams through divergence and convergence across four phases: Discover, Define, Develop, and Deliver.
While I have approached problems in a similar fashion, I didn’t have this framework at hand. Totally makes sense how this can resolve problems and get everyone aligned. So true that engineering tends to start at the second diamond while product is still in 1. Thank you for sharing.
Hi Karthik, I feel the same way! It was so good to find this framework and put some structure to the process that was causing so much unhappiness in our teams.
Yet another gem, Etienne! In your implementation section you talk about recurring meeting set side for problem definition. For a startup focused on one product would the recurring meeting be used to dissect different unknowns in the product? If so, would this not disrupt other features that are in delivery stage? How do you help the team make the context switch that is necessary for this session?
Thanks for writing this, it clarifes a lot. This insight into team friction is super valuable, much like your other pieces.
Thank you!
While I have approached problems in a similar fashion, I didn’t have this framework at hand. Totally makes sense how this can resolve problems and get everyone aligned. So true that engineering tends to start at the second diamond while product is still in 1. Thank you for sharing.
Hi Karthik, I feel the same way! It was so good to find this framework and put some structure to the process that was causing so much unhappiness in our teams.
Yet another gem, Etienne! In your implementation section you talk about recurring meeting set side for problem definition. For a startup focused on one product would the recurring meeting be used to dissect different unknowns in the product? If so, would this not disrupt other features that are in delivery stage? How do you help the team make the context switch that is necessary for this session?