Published on 18 Apr 2022 11:44AM / 2557 words
I rarely had a useful meeting. I can count on the fingers of one hand the truly important, making-things-go-forward meetings I had in the last year. And yet, I regularly have to endure them. Daily.
As a Technical Writer, you’d expect meetings to be worthwhile sources of info and insight. And don’t get me wrong, they can be. But they aren’t in the form that most companies hold them nowadays. I am largely referring to the daily stand-ups that a good share of companies nowadays have implemented (read, forced). Most of these meetings are managers asking for updates, then each member of the team talking about their “stream” and what are their progresses or lack thereof. This for a good 15 minutes, usually. Sometimes 20. Then the manager tries to micromanage everybody or asks stupid questions because no one apparently puts managers that know what their subordinate do every day in charge anymore.
Then, perhaps, 5-10 minutes of the manager giving us “updates” on anything from where the project is heading towards to how his dog felt yesterday evening during the usual walk out (seriously).
None of this can not be an email or a 1-minute Teams message. None. I dare you to think otherwise.
So why do we have meetings like this on a daily basis, spending 30 minutes for what can be written in 1, max 2?
What Agile should be
The Agile Alliance defines the stand-ups as:
Each day at the same time, the team meets so as to bring everyone up to date on the information that is vital for coordination: each team members briefly describes any “completed” contributions and any obstacles that stand in their way. Usually, Scrum’s [Three Questions](https://www.agilealliance.org/glossary/three-qs/) are used to structure discussion. The meeting is normally held in front of the [task board](https://www.agilealliance.org/glossary/taskboard/). This meeting is normally [timeboxed](https://www.agilealliance.org/glossary/timebox/) to a maximum duration of 15 minutes, though this may need adjusting for larger teams. To keep the meeting short, any topic that starts a discussion is cut short, added to a “parking lot” list, and discussed in greater depth after the meeting, between the people affected by the issue.
First of all, these stand-ups should be timeboxed. Max 15 minutes. Never had any being that short, unless it was a truly slow day. Nor any that was clearly defined as 15 minutes. It may have been my bad luck with managers.
Also, any topic that starts a discussion is cut short. Ah, I wish I knew one year ago when I joined my current company. I would have cut many discussions which arose during the stand-ups. Chat either privately or in another meeting, as the Agile Alliance suggest. Don’t waste everybody’s time.
Thus, the only parts that a stand-up should be composed of are sharing completed tasks and obstacles, and thinking how to overcome them. That’s about it. It is an update for better coordination, nothing else.
What Agile often is
Every stand-up I took part in drags on and on for double the allotted time some days. It pulls people into listening to other team members discussing their own tasks that don’t affect at all your own. Over time, this leads to disinterest in the meeting and people regularly zoning out. If I have nothing to contribute to the meeting, why am I being pulled in?
I occasionally ask to be spared this agony by asking the manager if I could skip the stand-up because I had no updates. Often the manager rejected my request because “there are important updates”. Guess what, they regularly turn up to be not important.
And don’t even get me started on managers forcing everybody to have their camera on. I could at least do some work while listening to another guy bantering about their task being too difficult or not comprehending what is asked of him but no, my dear manager thinks that if I have the camera off I don’t actually participate in the meeting.
Which is what I would, if I could. I would happily not waste 20 minutes listening to other people wondering how to do their job if possible, yes. Let me have my camera off so I can be actually productive (that includes doing chores at home, of course).
Speaking of which, how is it possibly productive in general for a manager to read a 500 word text while having a meeting with 4 other people who aren’t technical writers nor know much about the documentation? Don’t you have the chance to read it yourself before the meeting and let me know your observations later?
Why do we need to go through textual content by voice at all? While at the same time blocking multiple employees for the time needed to read and comment such content. It is madness.
And, in the end, why do we insist on having these meetings when WFH at all? Sometimes team members aren’t even on the same continent, and often not in the same time zone. Nobody is forcing them to actually stand up throughout the meeting, which would actually serve a purpose: keeping it short. It is not a “stand-up” if the participants are sprawled on their sofas while idly listening to the manager pushing his/her views on everybody else.
Even in the best stand-ups, when they were kept relatively short and team members focused on discussing only their accomplishments and roadblocks, the phrasing was more aimed at pleasing the manager rather than soliciting collaboration and insight. It was idle talking, scrambling to scapegoat others and not taking the blame for anything that may have been done wrongly.
Who cares other than managers about all this? Why isn’t it all a simple Teams message?
The issue: managers and accountability
Which leads me to what I believe is the actual problem here.
Managers need to justify their salary and time spent at work. A good manager makes everybody’s life better, doesn’t micromanage anybody, trusts workers, and helps them be the most productive they can be. The workers’ job is the justification of his/her salary and role, nothing else.
A bad manager cares more about not being scapegoated by higher ones, faking doing work, and overestimating their importance. Spoiler: you are not as vital to the job as you think. A bad manager is rarely humble. Often not very knowledgeable nor insightful. Bad managers love to get in the way of workers and tell them how to work, which sounds to me crazy: I am not going to tell the chef how to season, why would a manager tell office workers how to work?
Therefore, bad and mediocre managers have an issue: they have to show that they are necessary but at the same time they don’t want to be held responsible for the failures of the team, when they happen. And they usually will under them. Unsurprisingly.
Their solution is thus to prolong the stand-ups so they can attempt micromanaging everybody and have as many meetings as possible. Why meetings and not emails or messages?
Because meetings aren’t written and can’t be screenshotted. You as a worker have no way to prove the behaviour of a manager during a meeting unless it is recorded. And guess what? Most of the daily meetings aren’t. Clue.
The Agile methodology is thus the perfect excuse to have plenty of meetings, at the very least one per day, and justify the existence of these bad managers. They aren’t to be blamed for the meetings, it’s Agile, everybody implements it so it must be good. Plus, they can’t be held accountable for what happens during the unrecorded meetings. They’re basically free to waste everybody’s workday to justify their role.
If this is not the definition of a parasite, I don’t know what a parasite is.
To be frank, there are some good managers that keep meetings to a minimum, have no issue discussing via chat at length problems with team members and don’t spend 5 minutes talking about the weather. They are rare but do exist. Cherish them if you have the luck to have one.
I haven’t had this luck more than once or twice. Instead, I had managers who insisted on reporting the job done during the stand-up when all I had to report was that I was still working on the same documentation as yesterday. I guess they liked my voice, I don’t know.
I had managers deleting half the page I had written a few days earlier because “it seemed unimportant”. You are, you bloody idiot. I am a technical writer, leave writing to me. Managers that get in the way of workers and pretend to know their work better are the worst.
I had managers that considered themselves “Scrum master” and yet were regularly postponing the standups, canceling them at the last minute, not starting it but starting a different meeting altogether 10 minutes later. If you can’t organize your own workday, how are you supposed to organize everybody else’s?
Meetings are the perfect justification for bad managers, for their very existence. Agile is a comfortable excuse to have one every day, regardless of the actual needs of the job. Anything can be said in a meeting and no one can be held accountable for it, which is another perfect way for bad managers to hide their lack of competence and impose their views over workers.
Emails over meetings
So what’s the solution? Some sort of communication has to be had, regardless of Agile and bad managers. While I don’t claim to have THE solution, it is clear that lots of the meetings we have everyday at work are a waste of time and resources. Most can be just an email, but aren’t.
The reason is the reputedly superiority of meetings over messages and emails, and it lies in their synchronicity. With a meeting you can force every member of a team to sync, listen, and discuss a specific topic at a specific time.
Which is wonderful. Truly. Meetings can be extremely useful when used correctly.
The problem is that stand-ups are unnecessary in the form of meetings unless there are blockers that more than one of the team members should discuss about or there are important updates about the project that should be shared to everybody. 15 minutes for these are plenty. Meetings are not needed for simple updates about your own tasks, short questions, doubts, and anything that is not urgent or has an approaching deadline. Emails are just fine for these types of discussions.
Yeah, a meeting works as well but have you as a meetings fan considered its negatives? Let me remind them:
Meetings disrupt your focus way more than a message or email. Both the latter can be ignored or, if you can’t, can be dealt with in a matter of seconds. With a meeting you lose your focus for minutes and can’t even fake not having read a message, especially when camera on is a rule in your company.
If you were doing focused work before a meeting, goodbye to that.
Emails can be noisy and not get to the point, granted. But you can skim-read them. You can read them at your pace and ignore parts that don’t seem to add much value to you.
Meetings on the other hand force you to listen to people prattling for minutes and you can’t do much about it. You can do some work during meetings, and thank managers that allow you to have the camera off for this; but, can you focus as well while listening to your colleagues talking instead of your favourite music or silence? I guess not. You are forced to ingest also the noise and not only the value in meetings.
With emails you can take what is important for you and discard the rest. Aren’t they wonderful?
I am a technical writer. I write, mostly. My work relies around written content. A meeting is voice content. To translate what I heard to written content, I need a speech-to-text app or taking lots of notes and listening multiple times to the recording. It is part of my job so something that is naturally assumed of me.
How much better would though be to have the essential info of a meeting in textual form, ready to be copied and pasted where I want, read again anytime I want, elaborate about, tinkering with and so on? Especially with direct questions that have a short-medium long answer, an email is greatly superior to a meeting. Ask, wait for the answer, and copy it in your “knowledge base” or directly in the draft of the documentation. Simple, effortless. A meeting is impractical oftentimes for acquiring information from experts. It is useful when you are starting and have little to no idea of the topic, with barely any questions to ask. Then it is great to be able to hear an expert talking. But when you have a specific problem that you need to be clarified about, a concise email is king.
Waste of time
No, I am not thinking of the actual length of meetings (which is nearly always too long). I am talking about the time you waste while waiting for a meeting to start documenting.
Until the meeting a technical writer can do little and it is the task of the manager to make sure that the writer can do something else while waiting. Otherwise, wasted time.
Similarly after a meeting, if a new question arises or something that seemed clear before looks more complicated after, how do you clarify your doubts? With another meeting, in 24 hours or more? And what are you going to do with that piece of content until then? An email can be answered in a couple of hours and doesn’t require anybody to check the schedules and hope to have an empty spot that matches. Emails allow the documentation to move forward faster than meetings, with the added advantage that they require less time in general. Win-win.
Let me work as it is best for me, not for Agile
You get my point by now. Meetings can be useful but are largely over-used, badly used and exploited by bad managers to cover their inefficiencies. Meetings shouldn’t be hated by employees. Those who do are because they had enough of pointless, high noise to value ratio ones.
Agile isn’t a religion. If you treat it like one, you are limiting your work to the constraints and rules it brings with. Agile can be great at organizing everybody’s work. Can being the key word here. Agile isn’t a medicine with a 100% success rate. Is more like a natural remedy that has a 70% rate. If you fall in the right half, and is implemented well, Agile can make your work easier. But there’s no point to force it over those who are on the other half, those for whom Agile isn’t a good fit. Then Agile becomes an hindrance, an obstacle, a nuisance. Realizing this and being ready to get rid of it is the task of good managers.