A product team that stopped losing decisions

A 40-person product organization · Software

The shape of the problem

Three squads, one platform team, and a support function that needs to know what shipped. The failure mode is familiar: a decision gets made in a thread, the thread scrolls away, and four months later nobody can reconstruct why the schema looks like that.

How it is set up

• One space per squad, plus a shared space for cross-team work.
• An announcement channel per squad for anything the rest of the company should read without replying into.
• Threads for every decision, so the main transcript stays scannable.
• Guest roles for the two contractors, scoped to the channels they work in and unable to start direct messages across the company.

What the audit log is for

Not compliance theatre. When a channel’s permissions change or someone’s role is raised, there is a row saying who did it and when. It answers the question that otherwise takes a week of asking around.