If you're a business leader, manager, analyst, engineer or in product development, you serve multiple stakeholders with competing priorities, selecting a use case based on BV is trouble, read why!
Definitely can’t just look at value without the tradeoffs to capture that value!
I try to minimise & collapse prioritisation dimensions as much as possible, to allow for head-to-head comparisons - typically starting with ICE (Impact / Confidence / Ease) and expanding where it’s important to break these down further (eg splitting ‘Ease’ into separate buckets based on different contributing parties like IT vs Ops vs Marketing). Otherwise there’s a lot more dimensions to populate or wonder if they’re relevant.
It's crucial to acknowledge the diverse stakeholder landscape and prioritize considerations such as complexity of deployment and criticality to the company's longevity. By focusing on engagement, resource availability, data integrity, and other factors, we ensure not only value delivery but as well operational excellence.
I commend the author for urging us to think beyond conventional metrics and consider broader strategic implications. Let's embrace this holistic approach to drive innovation and sustainable growth in our organizations. Truly insightful and inspiring! Thank you.
This is great. Completely agree to the complexity aspect. Many of the criticality elements either directly or indirectly are the reasons for or results in business values and outcomes. So I am wondering why BV should not be used for use case selection because if we do, wouldn’t we naturally consider those criticality aspects?
Hello Sol, I came here to ask you for the name of the app your Photographer friend used. Couldn’t find a way to message you directly on Substack for some reason. Also, I met you at the AI summit in New York City after your talk.
Thank you Sol for writing on a critical topic. These terms sometimes get treated very lightly without getting into the depth of what it actually means. There are lot of parts especially in a large organization that has to work well together to make this happen
The article serves as a solid reminder that real-life situations are far more complex than they appear on paper. A discussion on strategic approaches to navigating project complexities would be a valuable addition. Instead of completely discarding projects due to resource constraints or data gaps, we could consider laying the groundwork for future success if we believe the project is worth pursuing. This could involve clarifying the business value to stakeholders by linking it to critically important metrics, or initiating data collection efforts to refine our understanding of workflows and to prepare for future experiments, and so much more. Although the audience for the post has been broadly specified, it's crucial to recognize, regardless of the title, that without such an attitude, the success of a data function will be limited.
Definitely can’t just look at value without the tradeoffs to capture that value!
I try to minimise & collapse prioritisation dimensions as much as possible, to allow for head-to-head comparisons - typically starting with ICE (Impact / Confidence / Ease) and expanding where it’s important to break these down further (eg splitting ‘Ease’ into separate buckets based on different contributing parties like IT vs Ops vs Marketing). Otherwise there’s a lot more dimensions to populate or wonder if they’re relevant.
It's crucial to acknowledge the diverse stakeholder landscape and prioritize considerations such as complexity of deployment and criticality to the company's longevity. By focusing on engagement, resource availability, data integrity, and other factors, we ensure not only value delivery but as well operational excellence.
I commend the author for urging us to think beyond conventional metrics and consider broader strategic implications. Let's embrace this holistic approach to drive innovation and sustainable growth in our organizations. Truly insightful and inspiring! Thank you.
Finally real advice looking past the overused and unhelpful "focus on business value" cliche. Going to run with this, thanks Sol
This is great. Completely agree to the complexity aspect. Many of the criticality elements either directly or indirectly are the reasons for or results in business values and outcomes. So I am wondering why BV should not be used for use case selection because if we do, wouldn’t we naturally consider those criticality aspects?
Hello Sol, I came here to ask you for the name of the app your Photographer friend used. Couldn’t find a way to message you directly on Substack for some reason. Also, I met you at the AI summit in New York City after your talk.
Hi Robert, it’s ‘Face App’ !
This is awesome. I love tell it like it is Substacks for the business world.
You’re too kind 💗!
where and how does idea like design thinking play a role? shouldn't that help in the skate holder management?
Thank you Sol for writing on a critical topic. These terms sometimes get treated very lightly without getting into the depth of what it actually means. There are lot of parts especially in a large organization that has to work well together to make this happen
Yes, that's precisely it Eli!
The article serves as a solid reminder that real-life situations are far more complex than they appear on paper. A discussion on strategic approaches to navigating project complexities would be a valuable addition. Instead of completely discarding projects due to resource constraints or data gaps, we could consider laying the groundwork for future success if we believe the project is worth pursuing. This could involve clarifying the business value to stakeholders by linking it to critically important metrics, or initiating data collection efforts to refine our understanding of workflows and to prepare for future experiments, and so much more. Although the audience for the post has been broadly specified, it's crucial to recognize, regardless of the title, that without such an attitude, the success of a data function will be limited.