Culture
Numbers to Know for Managing (Software Teams) 5 minutes read.
This post reminded me of the post "Latency Numbers Every Programmer Should Know." While the figures and stories (as in this case, most are just stories) are interesting to consider, they mostly made me know which numbers I deem right. What are your numbers and the stories behind them? Is it working for you, or do these figures hold you hostage for making better decisions and taking accountability?
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Using Cultural Survey Data 8 minutes read.
There are a lot of gems within the data we gather in surveys. People trust the leaders to act upon this feedback and make needed improvements. This is an excellent advice to follow up on when starting the next survey: "Make sure to mention these improvements [ones you made due to the previous sruvey] when you introduce the next round of cultural surveying. The team will take the survey much more seriously if they know you took action last time."
Read it later via
Instapaper.
Share
it via
Twitter
or
email.