One heuristic for “do I need a synchronous meeting” is transmitting vs transforming information. People meet to transform information (according to archetypes that show up in your boxes). Transmitting information (status updates, announcements with no discussion, etc.) should always be done asynchronously to fit the culture and info type.
And I thought we are on a good way to efficient meetings. Then came John and his meeting motions. Back to square one... seriously, thanks for the post! I will try to apply some of it in the next month, given we already have an inventory and owners it should be “easy”.
How it worked out? By my clients, this has become a true game changer. No meeting is taken for given anymore and the affected people are sitting in driver seat finally. Before, there wasn’t such a seat to take. Not even a spare one. That’s the point a realized once I put this to practice.
"But what if meetings were product features owned by product managers and designers? How would they approach meetings differently?" Yes! Instead of joining standup and listening to your peers try and recall what the hell they did yesterday (either vastly oversharing, or providing very little relevant detail)....What if we did the Status bit async? And then got together to discuss context and recalibrate in way less time? That's the mission at Spinach.io. To reimagine these ceremonies to be more efficient.
I‘ve been following the same idea for some time and it works perfectly well. The framing is little different and the approach goes beyond a single meeting:
First recently I have come across this post. I‘d like to connect with people doing the same stuff to share ideas and combine them for even better outcomes. Anybody out there willing to engage?
One heuristic for “do I need a synchronous meeting” is transmitting vs transforming information. People meet to transform information (according to archetypes that show up in your boxes). Transmitting information (status updates, announcements with no discussion, etc.) should always be done asynchronously to fit the culture and info type.
And I thought we are on a good way to efficient meetings. Then came John and his meeting motions. Back to square one... seriously, thanks for the post! I will try to apply some of it in the next month, given we already have an inventory and owners it should be “easy”.
How it worked out? By my clients, this has become a true game changer. No meeting is taken for given anymore and the affected people are sitting in driver seat finally. Before, there wasn’t such a seat to take. Not even a spare one. That’s the point a realized once I put this to practice.
"But what if meetings were product features owned by product managers and designers? How would they approach meetings differently?" Yes! Instead of joining standup and listening to your peers try and recall what the hell they did yesterday (either vastly oversharing, or providing very little relevant detail)....What if we did the Status bit async? And then got together to discuss context and recalibrate in way less time? That's the mission at Spinach.io. To reimagine these ceremonies to be more efficient.
I‘ve been following the same idea for some time and it works perfectly well. The framing is little different and the approach goes beyond a single meeting:
https://www.linkedin.com/pulse/meetings-products-new-perspective-organizational-vladimir-riecicky-dynve?utm_source=share&utm_medium=member_ios&utm_campaign=share_via
First recently I have come across this post. I‘d like to connect with people doing the same stuff to share ideas and combine them for even better outcomes. Anybody out there willing to engage?
🧐🧐🧐 Really loving this piece and what I’ve read so far! 🫶 happy for you to have a break from
Work! Happy new year!