I agree with the idea that you don't need to get too fancy with frameworks and all the associated buzzwords.
I will say, though, that I recently walked into a team with zero structure/alignment with any semblance of a framework, and man...it's just straight chaos.
I should clarify, I'm not anti framework. I think frameworks are important. Last week at a Product Breakfast, the group was talking about process and when the right time to bring in process, or in this case, frameworks is. We determined it was highly contextual but once you start hiring people further from your company’s “why,” process becomes essential. I really liked that POV. Thanks for sharing, Mike!
In a product discovery workshop I ran this morning, I reminded the team: these are tools but take what's helpful and leave what you need. So often, people get rigid about sticking to a tool or framework, but the reality is, every team is different. Frameworks, tools and kits are meant to be adapted!
I agree with the idea that you don't need to get too fancy with frameworks and all the associated buzzwords.
I will say, though, that I recently walked into a team with zero structure/alignment with any semblance of a framework, and man...it's just straight chaos.
I should clarify, I'm not anti framework. I think frameworks are important. Last week at a Product Breakfast, the group was talking about process and when the right time to bring in process, or in this case, frameworks is. We determined it was highly contextual but once you start hiring people further from your company’s “why,” process becomes essential. I really liked that POV. Thanks for sharing, Mike!
Amen.
Talking in frameworks makes you sound junior, too.
In a product discovery workshop I ran this morning, I reminded the team: these are tools but take what's helpful and leave what you need. So often, people get rigid about sticking to a tool or framework, but the reality is, every team is different. Frameworks, tools and kits are meant to be adapted!