How do we keep quality consistent across teams
Cadence, membership, and the line between what a guild decides and what stays with the team.
The standard objection to cross-functional teams is that they produce inconsistent work. The standard fix, keeping all the designers or all the engineers together in a functional group, creates more problems than it solves.
Specialists held in a hive feel and behave like outsiders rather than team members, and it creates a handoff, with teams waiting on artifacts before the next stage can start. That is a bottleneck, and the lost revenue from slower releases across every product team outweighs whatever the inconsistency cost.
A guild gets the consistency without breaking the teams apart. Teams stay cross-functional in their daily work, and the same function from different teams meets regularly, outside that work, to coordinate and share what has emerged from it.
What you get
- A five-item charter to fill in with the guild rather than for it
- A decision-boundary table, the guild decides versus the team decides
- The test for whether you have rebuilt the hive with a nicer name
- The failure mode to watch for at the six-month mark
Where should we send it?
One email with the worksheet. You can unsubscribe from anything else in one click.
On its way
Check your inbox. If it has not landed in a minute or two, look in promotions or spam, and add sam@startuppatterns.com to your contacts so the rest arrive.
Adapted from the Delivery chapter of The Mindful Product Company by Sam McAfee.