This makes a lot of sense. First, you gather all the use cases, and then only drill down with the canvas where you decide to prioritize higher. I ran many product canvas and metrics canvas workshops in the past and I find it to be similar.
I'd also like to invite you to my Substack "Signal to Product" where I talk about decision intelligence products. Seems like we have some things in common: signaltoproduct.substack.com
Interesting idea 💡 - when we worked through some examples, the vision statement was alwaysntheadt bit and was the culmination of all the sections, interested to know how they approached that instead. I think doing a lightweight version up front to help drive priorities makes a lot of sense
I find teaching people to fill out the canvas first and then the Vision Statement last, is much easier for people to pick up.
I think that is because the Vision Statement is populated from other parts of the canvas.
I was teaching a cohort of non data people my draft "Data Product Management" course a while ago and part of the hands on exercises was to create Vision Statements on its own as a way of doing initial prioritisation of the organisations Ideas.
I was pleasantly surprise how quickly they picked it up and the awesome Vision Statements they crafted.
But I had run my Information Product Canvas course for some of them before the Product manager one, but not everybody was on both courses.
This makes a lot of sense. First, you gather all the use cases, and then only drill down with the canvas where you decide to prioritize higher. I ran many product canvas and metrics canvas workshops in the past and I find it to be similar.
I'd also like to invite you to my Substack "Signal to Product" where I talk about decision intelligence products. Seems like we have some things in common: signaltoproduct.substack.com
Interesting idea 💡 - when we worked through some examples, the vision statement was alwaysntheadt bit and was the culmination of all the sections, interested to know how they approached that instead. I think doing a lightweight version up front to help drive priorities makes a lot of sense
I find teaching people to fill out the canvas first and then the Vision Statement last, is much easier for people to pick up.
I think that is because the Vision Statement is populated from other parts of the canvas.
I was teaching a cohort of non data people my draft "Data Product Management" course a while ago and part of the hands on exercises was to create Vision Statements on its own as a way of doing initial prioritisation of the organisations Ideas.
I was pleasantly surprise how quickly they picked it up and the awesome Vision Statements they crafted.
But I had run my Information Product Canvas course for some of them before the Product manager one, but not everybody was on both courses.
Today is the day I found out I can't edit substack comments. That should read "always the last bit"