[machinelearning]

IME standups are not even effective in unblocking most people.

Why would someone want to admit they're blocked by something in front of everyone? Someone else will inevitably proclaim that they have the solution, however simple it may be, and make the asker look stupid while elevating themselves.

Most people know who to ask to be unblocked or can ask their manager.

1:1s are the time to sync with regards to status on projects not in the middle of the day.

Weekly roundtable meetings are the time to sync up with the rest of the team and learn what everyone is working on.

The only purpose of standups is to slavedrive people into "productivity", which inevitably ends up with them thinking of how to hyperbolize whatever they're working on minutes before standup begins. Its useless.

[vvanders]

I really hope you aren't using 1:1s as status meetings, that's the worst possible use of your time[1].

As a developer I've found stand-ups to be useful to know what's going on within the team and if feature A with collide with feature B.

[1] https://randsinrepose.com/archives/the-update-the-vent-and-t...

[machinelearning]

I disagree with your reading of the article. It does not say that providing status updates in 1:1s are the "worst possible use of time" anywhere.

Quoted from the article: "The point of this discussion is not to solve my Disaster, the point is that we’re going to have a conversation where one of us is going to learn something more than just project status."

Status updates are a conducive part of 1:1s and its the perfect time to get unblocked as the quote above duly points out.

As for learning about whether "feature A will collide with feature B", weekly/biweekly roundtables are the perfect time to learn about such things. The weekly cadence allows people to find time to collaborate on the possible overlap.

Lastly, I don't think the article is even that good. It seems to make up for its lack of interesting-ness by feigning conviction and edginess. The central point of the article is highly unusual in that it lauds novelty over pragmatism.

A 1:1 should be an environment where all of what the article talks about CAN take place. But that doesn't mean it SHOULD during every meeting.

[nitely]

Does your team communicate outside of the stand-up?

I usually know what everyone is working on (because of ticket assignments, code reviews, some occasional side meeting, etc), as I usually work with teams of 5 (or less) people.

[philipov]

yeah, for a lot of people, being blocked isn't a bug, it's a feature.