Chapter

Splitting teams by purpose scatters each discipline. Put four designers on four teams, one each, and every team has the roles it needs while every designer is alone.

Three things go missing at once. With no place to agree on interface rules, one product ends up with four different button shapes. There's nobody on the team to teach a newly hired designer, and the team lead can't judge design work, so there's no basis for evaluation either. Ask in review why this team's screens look different and the answer is that they decided it that way, with no standard anywhere to argue against it.

A chapter regathers the scattered people by discipline and creates that place. Teams decide what to build; chapters decide the standards for how. Nobody moves desks, and no team loses a member.

A person belongs to a team and to a chapter at the same time, receiving different things from each.

1. Group by discipline. All designers form the design chapter, all backend engineers the backend chapter. Five to fifteen people is typical, and past that it splits. Scoping a chapter inside a tribe — the unit that groups related squads — is also common.
2. Appoint a chapter lead who sets the discipline's standards and owns hiring, growth, and evaluation. The lead also does hands-on work on a team, which keeps those judgments close to practice.
3. Meet on a cadence. Every two weeks, share the calls made on each team and decide which ones become shared rules. This is where four button shapes become one.
4. Split the reporting lines. What gets built this cycle comes from the squad; what gets learned and how performance is judged comes from the chapter. One person now talks to two people about different things, so unless who decides what is written down in advance, the two decisions collide.

"This isn't for the team to decide. The design chapter should set the standard."

A judgment that the rule applies to the whole discipline, not one team.

"I'll raise it at the chapter meeting next week."

Saying they'll align with others in the same discipline first.

"Talk to the chapter lead about growth, and to me about this quarter's work."

Confirming which reporting line owns what.

At Pagedeck the design chapter formed when headcount reached forty-five. Before that Noa reviewed screens for three teams alone, and each team had settled into its own rules. Once there were four designers, they started meeting every two weeks, and over six months the scattered rules for buttons and inputs merged into one set, which the fifth designer inherited on their first day instead of inventing.