I will be in Edinburgh and Hamburg in late June for Turing Fest and Product at Heart. Both are great conferences, and it would be great to connect in person while there. Short post this week. I strongly believe in the power of language to "hack" organizational challenges.
In the way you are thinking about stepping stones, is it fair to say you are asking teams to come up with an initial path for the next few months, but that the path may change as new options are "unlocked" along the way? Or are the teams asked to focus mostly on the next jump? In other words, do you expect these stepping stones to be mostly static or fluid? Thank you!
Yes! In a similar situation right now, milestone does the job but it's a loaded term with a history. Going to add 'stepping stone' to my arsenal. Thanks John!
Yes. Milestones are not gates or points of culmination. They are guide posts and way points for teams to drive their progress towards and through. They signals and warning signs for executives to know when a program is “on track”.
In the way you are thinking about stepping stones, is it fair to say you are asking teams to come up with an initial path for the next few months, but that the path may change as new options are "unlocked" along the way? Or are the teams asked to focus mostly on the next jump? In other words, do you expect these stepping stones to be mostly static or fluid? Thank you!
Yes! In a similar situation right now, milestone does the job but it's a loaded term with a history. Going to add 'stepping stone' to my arsenal. Thanks John!
“Inch pebbles”
Yes. Milestones are not gates or points of culmination. They are guide posts and way points for teams to drive their progress towards and through. They signals and warning signs for executives to know when a program is “on track”.