Like many engineers, one of my goals is to have as few meetings as possible. Not quite zero meetings because there are good reasons to have meetings but the key is to avoid the useless ones. Useless meetings are ones whose goals are better accomplished with some other mechanism — with the status meeting being the worst offender in the useless category. That weekly meeting where you go around the room, listening to each person talk about what they’ve done, most of which you already know, none of which you care that much about, everybody knows it’s a waste of time and yet they still occur.
In my organization, we don’t do status meetings: we only do decision meetings (and occasionally an alignment meeting). My philosophy is to make the best use of everyone’s time, all the time, and the best use of highly-intelligent humans is analyzing a situation and making a decision. Those are useful meetings.
But in order to make a decision, we need information (status), so I’m not saying that status is inherently bad, only that status meetings are inherently bad. So instead of status meetings, we communicate status with written pre-reads for status-like information, and then we jump off from there in our discussions and decisions. Some companies, such as (famously) Amazon, use this same mechanism but start each meeting with the reading of the pre-reads: I instead simply insist that everyone come prepared by having done the reading. Nobody fails to do the reading more than once.
Being a modern SaaS organization and fully in the cloud, we actually go one step further than simply having pre-reads: we use the collaborative editor Quip to write our pre-reads. This shared collaborative writing mechanism allows us to read and comment on each other’s pre-reads, and then revise and clarify our own contribution based on each other’s comments, all at our own pace and time. All of this is done in advance of the meeting and thus we arrive with a shared understanding of the status of the issues (because we’ve read all the pre-reads), as well as a complete understanding of the issues (because we’ve asked for clarifications via the Quip commenting mechanism), and are ready to dive into the discussion.
And because we come prepared, our meetings are enjoyable, efficient, and productive.
I am pleased to have convinced O’Reilly to bring back the Cultivate conference as place for engineering leaders to discuss and collaborate on how to be better engineering leaders. As I said in my introductory comments: “I believe great engineers deserve great managers” and that “management is a career you choose, not something you’re promoted into”. We all want to do great things and we can only do that when we are supported and a big aspect of that support is your manager and the company culture.
The lineup was outstanding including Liza Daly, CTO of Safari, and Molly Graham, COO of Quip, as well as, at my insistence, plenty of time for the attendees to talk and learn from each other. (I’m big on learning from one’s peers: my annual internal-to-New-Relic engineering conference is all about making the social connections to be maximally efficient throughout the year.)
There are hundreds of conferences every year where developers can learn to be better developers or architects can learn to be better architects, but almost none where managers can learn to be better managers and create a better company culture: hence the need for Cultivate.
I look forward to more.
As Zack from Github says “You can have the best, most comprehensive test suite in the world, but tests are still different from production”, amen! — and he says a lot of other useful things as well:
Twenty-two good pieces of advice for software engineers including:
- Everything takes longer than you think.
- Fix the known errors, then see what’s left.
- Assume no coincidences.
From American CEO, fifteen essential CEO skills:
- Attracting Employees
- Retaining Employees
- Employee Development
- Sales Knowledge
- Operational Knowledge
- Financial Knowledge
- Regulation and Governance Knowledge
- Market and Customer Knowledge
- Tying Strategy to Execution
- Attention to Detail
- Anticipate Organizational Needs
- Emotional Intelligence
- Build the Culture
And then, from one of the smartest, most inspiring, CEOs I know:
Unfortunately, I’ve definitely met these people:
From the article: “There’s a familiar path now to SaaS companies that start in the SMB (small-to-medium business) part of the market. Over time, they seem to inevitably begin serving larger customers. Box, Hubspot, Zendesk and among many others have exhibited this pattern. Why does this happen?” …
This is my model for feedback: frequent, followed up with writing, augmented with coaching, and always honest:
And finally, this statement is just too true. It’s not just because I’m a reader and prefer a book or a written report over a movie or a webcast, but because if you’re busy you can read a book incrementally:
My Indieweb experiment hasn’t been as successful as I wanted, mostly because I now realize that each of the different media I write in has a different purpose and thus trying to unify them all in blog posts is a mistake. So on to the next phase of the experiment which is that I’m going to still re-post some of my short-form entries here, but only the best of them.