When a team is trying to do something strategically important, it should have a bet charter attached with the actual pot of money that we need to bet. Most corporate projects assume a hundred percent success because they're just like, this will be a hundred percent successful and it'll hit plan. That's not how bets work. And so I think playing, playing with that math a little bit in the bet charter will allow the team later to justify expense or not.
Picture it: Your company’s landed on an important and shiny new project and it needs a team to bring it to life. Cue the barrage of big questions—questions like: “So…who’s on this team? What support will they receive? When will they meet? Wait, is this extra work or something different?”Welcome to the wonderful world of cross-functional teaming. Standing up a cross-functional team is a place where plenty of organizations stumble—because it’s asking most systems to play a game they aren’t designed to play well.
In this episode of Brave New Work, Aaron Dignan and Rodney Evans team up (see what we did there?) to answer questions like:
- How should cross-functional teams—as well as the projects they work on—be chartered?
- Should the size and scope of an idea impact how a team is designed?
- What level and kind of authority should cross-functional teams be given?
- What are the first moves cross-functional teams always need to make?
- How can we bake experimentation into this cake?
Our book is available now at bravenewwork.com
We want to hear from you. Send your thoughts and feedback to podcast@theready.com
Looking for some help with your own transformation? Visit theready.com