We put a lot of the weight of becoming a customer-centric organization that manages to outcomes and "tests and learns" on the shoulders of our leaders and executives. But it's a two-way street. Our teams also need to change how they work to increase the likelihood of change 1/n
Teams want their stakeholders to trust them to solve problems, allow them to listen to customers and empower them to make tactical day-to-day decisions. In many organizations this is a radical shift for these stakeholders. What do we give them in return for that trust? 2/n
Transparency. Radical transparency is the proactive sharing of information on a regular cadence both up to your leaders and out to your colleagues. Candidly putting on display your work, wins, failures & learnings is key to building the trust that enables agility. 3/n
This proactive communication with stakeholders reduces stakeholder anxiety of not knowing "what the team is working on right now." If they were dictating features to you, they'd have that answer. If you're continuously discovering the best path forward, they don't. 4/n
If stakeholders get anxious, they ramp up control and increase micromanagement. Radically transparent communication eases concerns about what the team is doing at the moment and provides them that answer for when they get asked that question by their boss. 5/n
What does radical transparency look like?
Weekly status emails
Daily outcome/OKR updates (+/- from day before)
Information radiators
Slack channel updates (automated/manual)
Hallway conversations
Office "pop in"
Etc
6/n
It's easy to blame execs for not "being agile" or "trusting the team." Take a look at it from their pov. What would you want to know if you were in their shoes? Then start sharing it, regularly, w/o being asked. Err on the side of overcommunication. Your boss will thank u. /fin
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Corporate innovation labs fail regularly. The way I see it there are 4 reasons for this:
1/ Talent -- intrapreneurship is a tough quality to find in your teams. When it is found, it needs to be recognized and nurtured in ways most big corps treat as theater.
2/ Equity -- innovation comes from creative entrepreneurs. These folks won't give up their best ideas to their employer for the promise of another 2 weeks' worth of pay. How big orgs compensate in-house innovators makes or breaks the "lab."
3/ Exit strategy -- on the off chance that a corp innovation lab finds a big idea, what will they do with it? Without a clear sense of how an idea "exits" the lab most intrapreneurs won't pursue true innovation.
There were some clear themes coming out of the presentations at #productized in Lisbon yesterday about #prodmgmt and #design and #culture. Here is a brief summary of what I heard:
1/ Very little mention of #agile as a problem or a choice. It was just assumed by all speakers that this is the way everyone works.
When we wrote #leanux we wanted to help product design and development teams collaborate more effectively and ultimately build better products for their customers. The overwhelming feedback from readers has been (no surprise) that they want to work this way. However...
What we didn't expect was the amount of teams out there telling us things like "my boss won't let me work this way" or "my company would never let us talk to customers." Hearing this again and again gave us the sense that there was (at least) another conversation to be had. So...
We wrote another book - #senseandrespond . That book took the conversation up a level to leaders and makes the case that to stay competitive in today's business world you have to build continuous learning loops with your customers. I believe many orgs heard this message but...