Read the Room Without a Meeting
The move in short
Connector — Every Friday afternoon the founder copies all team members' end-of-week Slack status messages into Claude with a standing prompt that returns a synthesised pulse note — recurring themes, anyone flagging a blocker or a morale dip, and one suggested conversation to have on Monday — replacing the hour she used to spend re-reading individual posts.
The Company
Brynteg Studio builds software products for other companies — the kind of work where a client comes to them with a problem and leaves with something their team can actually ship. They're 22 people, fully remote, spread across Wales and a few other parts of the UK. The founder, Sioned, set up the studio in 2019 and has never had a Cardiff office to wander around. Everyone works from home, everyone communicates in Slack, and the whole thing runs without the informal check-ins you'd get just by walking past someone's desk.
The Pain
Every Friday, Sioned asks the team to post a short end-of-week note in Slack — what they got done, how they're feeling, anything blocking them. Twelve to fifteen people usually post something. She reads the first few on Friday afternoon, then gets pulled into something else. By Monday morning she's forgotten most of it, or she reads the thread properly then, which takes the better part of an hour. Either way, she's usually reacting to things she should have spotted days earlier. Last month, one of the senior developers had mentioned in his Friday post that he was struggling with a client handoff. Sioned missed it. He'd moved on by the time they spoke, but it had quietly eaten into the following week's work. She's not ignoring the thread on purpose. She just can't process fifteen separate posts and come away with a clear picture of how the team actually is.
The Move
On Friday afternoon, once the last few posts are in, Sioned copies the whole thread into Claude. She pastes in a standing prompt she wrote once and saved in a document: it asks Claude to pull out any recurring themes across the posts, flag anyone who sounds like they're hitting a wall or having a rough week, and suggest one specific conversation worth having on Monday. Claude returns a few short paragraphs. It takes her about four minutes to read. She gets a cleaner picture of the team's week than she'd get from reading every post herself, and Monday morning she goes into her first call already knowing who she wants to check in with and roughly why.
The blind spot
The Friday Slack thread already exists, so it feels like the system is working. Sioned's not avoiding the information — it's there, she just hasn't read it properly. It doesn't feel like a problem that needs fixing; it feels like a reading backlog. So nothing changes.
The pattern
The same move works in a few other places:
- A COO who gets weekly project update emails from six team leads and skims them looking for anything urgent, usually missing things that aren't obviously flagged
- A founder who asks the team to fill in a short Friday form in Notion and then doesn't have time to read through all the responses before the weekend
- A head of client services who reviews call notes from four account managers each week and needs to know quickly if any client relationship is starting to look shaky