This might not scale well to larger teams, but we simply write a short message in a dedicated channel each day. It contains a short status and a few bullet points to plan the next day.
Slack makes this conventient because you can write a top level message and then use the reply feature to add more details.
Anyway, I’ve come to really dislike async comms. If something is being communicated to you over async, it’s something not important enough that you can ignore it, in many cases indefinitely. Meetings are still the best way to keep everyone in sync and it’s a structural strategy to keep everyone accountable for making progress at their jobs.
What? Instead you are punishing everyone to sit on a meeting, hearing two people discuss something that could have been a dm. I get that some people prefer meetings but to me every meeting with more than 3 people is a massive waste of time
Sync is even worse at scale. I had the pleasure of attending standups in a 20-person team. It was a nightmare where I said two sentences and then wasted the next two hours of my life listening to things I either know or are unrelevant to me.
>you’re punishing everyone with having to back-read
Great, because skipping three pages of unimportant conversation is faster than skipping 30 minutes of banter between two extrovert UI developers as a backend specialist.
>structural strategy to keep everyone accountable
Sounds exactly like something mid level managers say to themselves. Structural synergy? Keeping people accountable? I just want to work, damnit.
Why is your team 20 people if the majority don’t do anything you’re remotely close to? Someone should have split the team or at least the standup.
Why doesn’t your lead enforce a time limit and script?
It can happen the other way round as well. My team is small but only I ever stick to the script. Every one else talks in detail for 2-3 minutes. Their updates could have been 20sec.
You wouldn’t be complaining if someone actually did something about it.
Again the problem is that no one is interested in processes to make things better or more efficient and then people blame the process.
The process might have plenty of short comings, but we’ll never know.
All of that can happen just fine in a real-time team chat as well - and give people the chance to provide actual context and links, and also check back at the actual discussion later.
In practice, this is harder because people don't speak up unless prodded. And on Slack, I spend a lot of time and effort prodding people for that update, whereas a stand-up takes 15 minutes, tops.
Not attending stand-up is a lot more visible than silently ignoring an async update request on Slack.
If a second "please respond, I need the answer now" Slack message is not enough, you have bigger problems
I’ve got ~90 years on this planet at best. I’m not interested in wasting 1/5th of my working career in meetings, listening to people I don’t even know, telling me personal details about their lives I will not retain for more than 5 seconds. To me, it’s genuinely insulting to my time to waste it with these pointless fake displays of familiarity instead of getting to the work at hand and ending the meeting early.
Don't even be sure they're real; there are increasingly people who outsource their work to bots these days.
When we treat visible presence as a proxy for being "real," we exclude people who can't - or shouldn't have to - mimic neurotypical behaviour just to belong.
Then the meeting is pointless. But not all projects allow for that.
Perhaps, for efficiency, they could ask everyone simultaneously in parallel, or at least roughly around the same time?
To maximize creativity and opportunity, perhaps we could then figure out some way to share each person's status update with every other person on the team?
You still don't need a meeting for that if everyone actually does it.
This is a nice way of saying that some people just won't tell you what they're up to async, you have to wring information out of them synchronously. They're just bad at communicating.
On a well functioning team I can rely on people just reporting status themselves when something relevant happens and reaching out for help. But some people just don't do that, especially people from other teams, departments, etc.
Like, you explicitly ask them in an IM and they don't tell you?
Not telling you on their own, I can understand. If the former happens though, you have bigger problems, that asking on a real-life meeting wont solve.
A team meeting should not be the go-to solution for "Bob is bad at communicating"!
> But some people just don't do that, especially people from other teams
Hope this helps.
If you're the manager, YOUR job is to figure out how to get the information from the people who owe you a report, not weaponize my presence at a meeting to ferret out people you can't manage to reach.
But honestly the condescending tone of this whole exchange tells me everything I need it to about why you struggle to get information out of people.
You're reading things into what I'm saying that aren't there.
My job is to defend my direct reports from having their time wasted and clear blockers for them. Sometimes, yeah, this means meeting with people to ferret them out.
I'm not weaponizing anyone's presence at a meeting except mine.
If you need to babysit bunch of juniors thats fine, but it should be clear from one's role in team/project that this needs to be a continuous effort (at least till they grok how to step up, but it takes years if at all for some).
It will tell you how much time you spent working on tickets, and how long to spent working on the perfect reply for hacker news.
Much easier said then done. Especially if this really goes towards technological unemployment.
Instead they'll just wait until the next meeting and basically ask you to give a tl;dr or 'context'. I wasn't sure if it was a case of just having poor literacy or just some bullshit power play on their part.
In the most egregious cases I started to get petty and just read my message aloud, verbatim, while they had it open on the screenshare. Not as if their time is automatically more valuable than mine.
This is a real thing but it should only be temporary. If your culture is good and amendable to this sort of thing, then the IC should learn fairly quickly that they need to ask for help.
This behavior in ICs is, believe it or not, trained. I'm sure they've worked somewhere before or with a different manager in the past who would get annoyed at them asking for help. So they've tuned their behavior to that.
That's not entirely it. Some people just won't say something unless put in a setting where they are explicity asked for it. I've had meetings where I ask for a status, and someone says they are stuck on X, and they've been stuck on X for two days.
And I'll ask why they didn't just ask for help. They weren't comfortable asking for help. They were only ok stating the problem when asked specifically for status.
So it also creates that environment were some people are more likely to share.