Guild

Dividing teams by product scatters the people who do the same kind of work. Put one designer into each squad — the small team that owns a feature end to end — and the designers across the company stop having any reason to meet.

A chapter solves half of that. It groups the same discipline, but only inside a tribe, the larger grouping that holds several related squads. Interests that run across tribes still have nowhere to sit.

That happened at Pagedeck. Three squads were fixing accessibility problems without knowing about each other. The same mistake got made three times, and the third fix — Noa's — took a different approach from the first two, so the behavior ended up differing from screen to screen.

A guild creates the missing place. It doesn't touch the org chart; it lets whoever cares raise a hand and show up.

Voluntary membership is the whole point of this unit. Joining and leaving are the member's decision, and reporting lines stay exactly as they were.

Which means four things have to be settled for it to run at all.

1. One topic. Keep the scope narrow — accessibility, test automation, writing. Something as broad as frontend is already a chapter's job.
2. One organizer. Without someone booking the date and keeping notes, the second meeting never happens.
3. A cadence and a length. Start small, like thirty minutes every other week. Attendance isn't required, so a heavy commitment simply means nobody comes.
4. Somewhere to leave things. Write what came out of the meeting somewhere anyone can read it. People who missed it have to be able to catch up, or they don't come next time.

What it produces is practice rather than decisions. An accessibility guild doesn't issue instructions; it produces a checklist to attach to design reviews, and each squad decides whether to use it.

Whether it lasts comes down to two things: whether the topic touches real work, and whether the company treats the time as work. Miss either and attendance drops to the organizer alone within about three months.

"The accessibility guild has a checklist for this. Let's use it."

Practice scattered across teams has been gathered in one place.

"This isn't for the guild to discuss — the chapter has to decide it."

Anything enforceable belongs where the authority is.

"Thirty minutes every other week I can make. Weekly I can't."

Voluntary participation only survives below a certain cost.

Noa opened Pagedeck's accessibility guild after the episode above. Five people from three squads met for thirty minutes every other week, and four months produced two documents: an eight-line checklist attached to design reviews, and the order in which to verify a screen with a screen reader. Mia counting that time as work is why it lasted.