A. You don’t take on any new tasks before the meeting. You’re already too distracted by the meeting to start anything new. So now you’re sitting there killing time for an hour until the meeting starts. You were doodling in a notepad, missed the start of the meeting, and joined 5 minutes late.
B. You were working on something and didn’t realise it was meeting time. Someone messages you 5 minutes after the meeting started, reminding you to join. You’ve completely forgotten what the meeting is about and it takes you a further 5 minutes to get your bearings.
You made me realize the office provided cues and support. If others were collecting their desk, even if for another meeting, it was clear we were 5 to 10 from the half hour. Also, you grabbed your friends on the way. You hustled earlier to get a good seat. You planned breaks, walks, etc to time around you getting back at a certain time. Comparatively, WFH is an unstructured ADHD hell sometimes.
My meetings don't even last 5 mins. I have an alarm 5 minutes before the meeting so I can't forget about it. If I miss it, someone messages me 30 seconds in. Then at 10:05 we all start working.
The time after the meeting is spent not wanting to engage in tasks you can’t accomplish before end of day, and watching the clock knowing the meeting screwed up the day.
For software engineers, problem is management thought you could just hire a ton of people to solve the problem. Then the people who could actually solve the problem are stuck in meetings all day explaining it to people who can’t even understand the problem you keep explaining to them. Fun times.
(In simple terms, as the number of people increases, the communications overheads also increase, generally faster, so if you have more people a greater proportion of time is wasted, hence work done doesn't increase proportionally to the number of people. Or if you just want to inform management that more people won't simply mean the work gets done much faster just give the example of "If takes 9 months for a woman to make a child, it doesn't mean you can get 9 women and make a child in one month")
Or if you just want to inform management that more people won’t simply mean the work gets done much faster just give the example of “If takes 9 months for a woman to make a child, it doesn’t mean you can get 9 women and make a child in one month”
Management: "I don't have time for theoretical discussions. Marketing says this releases in two weeks and you better get it done. Do you need more resources?"
The people that don't understand the problem usually are management, and I have to spend an exhausting time each day explaining to them why the problem exists and why it takes so long to fix it. I once was honestly telling them their meetings were a big part of the delays. Which then obviously led to more meetings on "how we can better communicate so we can have less meetings and more productive time". I wish I was joking.
Meetings are rarely productive for anyone, neurotypical or not, once it gets bigger than like five people and/or hierarchy enters the room imo. Then it morphs into politics and showmanship.
Best meeting I’ve ever had was with two engineers. We were all on time, had prepared well, and lasted seven minutes because there were zero pleasantries, got right into breaking down the subject, and the answer was frank and forthright.
I have about 3 meetings a week because I keep only the productive ones. I refuse to attend bullshit meetings.
My graph would look like the first one except after the meeting there's a huge burst of activity because now everyone is more informed about what needs to be done and how to do it.
To be fair, my work has a culture of ridigly policing meetings to keep them on topic, no chitchat, no rambling, anyone who starts that tends to get called out immediately.
I had a former workplace like that, it was beautiful 🥹
We had a hot seat meeting where each department representative wasn’t even in the room until their individual staggered start time kicked in. One out, one in, cycling through each department until the meeting was over. They get to go back to their work and not be ‘meat’ in the room for fifteen minutes or more, we got focused reports from each as they filed in and out.
Sometimes I miss working for Germans, but “alles in Ordnung” cuts both ways - good luck breaking through the bureaucracy reporting chain and getting quick results
I typically have 8-10 meetings a day. I try to either have 60-90 min in the morning and/or 60-90 at the end of the day for focus time... Unfortunately the end of day sometimes gets nuked because I am fried from all of the meetings
Stand up / syncs / recruiter meetings / follow ups - they are usually only 15 minutes, so you can churn em out. They are easier to do than a daily email
My old job I used to have a lot of days where I'd have meetings every half hour or often consecutively. It was impossible to actually get anything big done because I'd just always be organizing notes from the last one or prepping for the next one. I between it was all I could do to put out fires. It was insane.
I have found that if the meeting is actually quick (sub 20 minutes) rebounding is not as difficult. When the "quick meeting" turns into a check in + "do we have time to talk about..." + any other number of meandering paths a meeting can travel down, I'll have a hard time getting back into task mode.
Something that helps me is to take a walk right after those meetings. Helps me reset when I get back to my desk.
This is why you make your own work better, improve the team’s work, and position yourself as a candidate for team lead by insisting that meeting timeboxes are enforced.
Even if it breaks productivity by cutting things off the first few times, it will train everyone to get to the point, which will make everything better after the first few breakages.
This isn't adhd it is the legit flow from after a bullshit meeting. Then by the time you get ramped back up again it's the next meeting.
My only gripe to the chart is there should be some flat lining down near the bottom on the productivity side as a buffer pre and post. You spend time doing nothing wondering why you need to attend during pre-meeting time then during post-meeting time, doing nothing thinking about how you weren't necessary at that meeting. Then you begin the accel ramping.
Yup. and some meetings you people ask you a question so you legit need some time to think about what information you should look up before the meeting. Even if 95% of the time nobody asks you anything, you gotta take some time to think about the topic the meeting is on and whether there might be a question for you so you have the answer for that 5% of the time. But 100% of the time you have to stop and consider what the meeting is about beforehand for the 5% of the time there's an actual question.
Also when I know I have a meeting coming up, I don't want to get in too deep on something that takes a lot of focus.
I'm lucky to not have many meetings in my current dev job, but I get the same effect from having a dozen people a day asking for "quick" fixes for various bugs that are conveniently always more urgent than whatever big task I'm in the middle of.
The bug fixes themselves can have massive cognitive overhead. I’ve spent hours thinking about a problem to make a very small change. It takes focus to fix complex problems correctly.
Do you not have a bug tracker or ticketing system of some sort to manage these things coming your way?
Incredibly few people at my work get much more than dismissive small talk from just walking up or from sending me a message expecting me to re-prioritize everything else for their special pet problem.
My manager sets my priorities, any changes to that need to come from him. They can take it up with him if they don't like it or disagree.
I don't respond to IMs or emails not from my boss or from my own team except when I've hit a mental road block and need to think about something else to refresh.
And I don't actually work on any of those requests until there's a ticket in. If someone comes to me asking why my main job duty isn't done, I'm sure as hell going to have a paper trail documenting who fucked up the timeline. No ticket, no work.
That also puts some weight on anyone else able to pick up tickets for your team to do it, so it's not always falling to you because you're not jaded enough to say no.
My previous job didn't have a ticket tracker for my team. It was my first real job, so I didn't realize how far we were straying from best practices. If I had some more experience, I would have pushed hard for ticket tracking. I was constantly disorganized, and my manager blamed me for not keeping track of everything. He was probably in his 50's, he should have known better.
Hahaha I wish. There isn't any real "management" to speak of where I'm at, and it's a flat structure, meaning literally anyone can send me work and I'm just expected to do it. Right now I'm working the weekend to finish a task that someone else couldn't do and it fell to me. There's a ticketing system, but it's only really half-used (of course, I myself turn these tasks into tickets, but that's about it).
Trying to slowly change all this over time, because I love my job outside of this lack of management, but I also don't hold any delusions about that.
Jesus fuck I would hate to work with you. At my job there's a lot of teams working on a lot of projects with very tight deadlines, and if every request had to be routed through managers it would take 10x as long. When we ask people from other teams directly for help, "I'm sorry I'm too busy right now" is a perfectly acceptable response because we've all been there. We don't need our managers to act like playground referees.
We're all intelligent and capable workers and we get paid well to take initiative and solve things without running to mommy.
I recall going to a time management seminar.
The speaker said, "When the average interrupted during a task, even momentarily, the time it takes the person to get back on task is between 20-60 minutes, and can take longer"
This is great, also if you haven’t read it, you should read Makers Schedule, Managers Schedule by Paul Graham, it really helped me describe this concept to all of the managers I have had hah.
Well, damn, I've never seen that put so clearly before. I literally have been trying to schedule myself like a manager using half-day increments like a maker.
Right? It minorities blew my mind when I read it the first time and keeping that in mind has made my life so much easier overall, and definitely made it easier to describe to managers over the years.
Yup. Thankfully management at my old job understood this, we had one quick 10 minute catchup about 30 minutes into the day every day and that was it.
If a project required several meeting, they were all done as close together as possible over as few days as possible, leaving as many free full days as reasonably could be achieved. It worked really well
There are many many important meetings to have and to get done. The worst meeting you can have is a status-update call where you mark off items on a checklist. This can be done by automation and status-tracker boards.
No the worst meeting is when the entire team — CEO, CTO, sales, engineering — spend all of Friday (every Friday) divvying up the tabs in a big excel spreadsheet, going and re-going through workflow checklists.
I knew they had no automated tests when I joined. I was promised, when I joined, that I’d be allowed to spend at least 25% of my time building an automated test suite for our app.
But we never had time to allow me to do that. So instead of spending 25% of my time developing an automated suite, which would steadily reduce the following until it was zero, we spent 20% of the entire company’s time doing human rspec tests.
One time the CTO asked me “Why wasn’t this caught in testing?” and I said “Because we don’t do any testing”
Huh. In theory, at least. In IT I've really only seen the status/blamestorm sessions. If I suggest that meetings aren't a good use of time, it's from that bias.
Yeah, I have to wrap up what I'm working on so that I can be available for the "quick meeting" which usually means I'm doing nothing for 15-20 minutes as I can't get started on anything else. If I'm caught not doing well, I get in trouble for the productivity, so I have to pretend.
When the 5-10 minute meeting runs closer to 45, I'm out an hour I could have been working.
Not the end of the world, but when we have these at least once, if not twice a day...
Two meetings a day sounds like luxury to me! I don't have ADHD but meetings still absolutely kill my productivity. The switching penalty for technical tasks is much higher than non-technical people realise.
Avoid morning meetings like the plague. The first four hours of a work day are golden and should be reserved for creativity and nothing else. The agile process was instituted at our workplace and that startup meeting is an absolute menace. I'll tell you how the day is going in the afternoon but right now I have to work.
This is why I can't work in an office. The last one I worked in, people kept waking up to chat "for a sec", when it took at least 10 minutes regardless of the inquiry.
Just as I'm starting to get myself back into my workflow.... "Hey, you got a sec?"
Sure, looks like I'm not going to get anything fucking done today, so why the fuck not. The only people I'm disappointing is the employer. I can have a chat. It's fine. Not like this will negatively affect my ongoing employment.
The shitty part to those workplaces is that chitchat often helps your employment more than actually doing work. Likeable people get promoted, effective workers stay where they're at.
That's a terrible workplace culture, but it's fairly common.
I will say that the support I got from co-workers when I was no longer working there. I got a number of messages about how disappointed they were about losing me from the team, etc.
None of that helped me find new employment, nor did it help me move up while I was there, but I was well liked.