Called Shots... a cautionary tale
…point I was trying to make with the note about [[Called Shots]] , I'd like to share with you a story about…
Given what I aspire to in regard to people management ( Leadership Questions or Vetoes ) and product management ( Continuous Value Delivery form of the Product Operating Model ), it goes without saying that telling teams what to build is NOT the way.
So anytime I have to tell a team, specifically what solution to build, one of three things has happened.
Another way of saying that is… Called shots are born of (1) an opportunity for improvement in Product Leadership (2) an opportunity for improvement in Company strategy / environment (3) a sign of psychological safety / Squad health / transformation process.
So when we are confronted with a Called Shot, we have three paths;
Note: Why are the three options an acronym for the word FEAR? Wellllllll… I’m unapologetically corny at times with how I try to show up. So in this instance, since I see Called Shots as – both – inevitable AND a part of the feedback loop system that indicates an opportunity for improvement… Called Shots represent a trial we must not shy away from, but face head on… I am reminded of Pit Bull’s I Believe (world anthem) where he says: When it comes to fear you can either… Forget Everything And Run… or Face Everything And Rise. Yeah… goosebumps yet?
So when faced with a Called Shot. We have a choice. None of which are bad… but I’d be lying if I didn’t say I have a favorite 😉.
To drive this point home, I’d like to share with you a story about a team that was faced with a Called Shot… seen here: Called Shots… a cautionary tale
…point I was trying to make with the note about [[Called Shots]] , I'd like to share with you a story about…
…is Dark Side to be output-focused. Story points, sprints, [[Called Shots]], velocity, SAFe, Waterfall... all evil. In modern Product... It is…