This is a guest blog post from execution and velocity guru Christina Wodtke, who is currently writing a new book about using OKRS (objectives and Key results), predictive roadmaps, and a cadence of celebrations to build high performance teams.
I remember the first time I had to write one of these puppies.
I had just been promoted to manager at Yahoo back in 2000, and was running a small team. I was told to “write a status email covering what your team has done that week, due friday.” Well, you can easily imagine how I felt. I had to prove my team was getting things done! Not only to justify our existence, but to prove we needed more people. Because, you know, more people amiright?* So I did what everyone does: I listed every single thing my reports did, and made a truly unreadable report. Then I started managing managers, and had them send me the same, which I collated into an even longer more horrible report. This I sent to my design manager, Irene Au and my GM, Jeff Weiner (who sensibly requested I put a summary at the top. Go Jeff!)
And so it went, as I moved from job to job, writing long tedious reports that at best got skimmed. At one job, I stopped authoring them. I had my managers send them to my project manager, who collated them, sent it to me for review, and after checking for anything embarrassing, I forwarded it on to my boss. One week I forgot to read it, and didn’t hear anything about it. It was a waste of everybody’s time.
Then I got to Zynga in 2010. Now say what you want about Zynga (and much of it was true) but they were really good at some critical things that make an organization run well. One was the status report. All reports were sent to the entire management team, and I enjoyed reading them. Yes, you heard me right: I enjoyed reading them, even if when were 20 of them.
Why? because they had important information laid out in a digestible format. I used them to understand what I needed to do, and learn from what was going right. Please recall that Zynga, in the early days, grew faster than any company I’ve seen. I suspect the efficiency of communication was a big part of that. When I left Zynga, I started to consult. I adapted the status mail to suit the various companies I worked with, throwing in some tricks from Agile. Now I have a simple, solid format that works across any org, big or small.
This format also fixes another key challenge large organizations face: coordination.
To write a status report the old way, I had to have team status in by Thursday night in order to collate, fact check and edit. But with this system, I know what my priorities are, and I use my reports’ status only as a way to making sure their priorities are mine. I send out my report Friday, as I receive my report’s. We stay committed to each other, honest and focused.
Work should not be a chore list, but collective push forward toward shared goals. The status email reminds everyone of this fact, and helps us avoid slipping into checkbox thinking. This system is so effective in helping me get things done, I’ve even adapted it for my personal life.
Coordinating organizational efforts critical to a company’s ability to compete and innovate. Giving up on the status email is a strategic error. It can be a task that wastes key resources, or it can be a way that teams connect and support each other. Change your status email today, and transform your teams.
— Christina Wodtke, velocity guru for WorkBoard, Coach and consultant at Elegant Hack
This article was originally published on Elegant Hack.
Christina Wodtke’s goal is to bring great products into the world. She is an Advisor at WorkBoard and was General Manager of Zynga.com and of Social at Myspace, Principal Product Manager at LinkedIn, and Senior Director of Design at Yahoo. Wodtke is currently working on her second book—The Executioner’s Tale—about using OKRs, predictive roadmaps, and a cadence of commitment and celebration to build higher performance teams. She writes at www.eleganthack.com