Browse the book & resources

Chapter 12 / 20

12. Collaboration & Communication: Is the Context Usable?

Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.

Consider an illustrative ownership search. The result points to a team that reorganized last year; an assistant summarizes the page fluently. The answer is easier to obtain and still wrong. Fast retrieval cannot turn stale context into current responsibility.

Make decisions, owners, and operating instructions discoverable by the people who need them. Record where a customer requirement came from, which team accepts a handoff, and who can approve a rollback. A service catalog helps only if ownership is maintained when teams change. In Rippling's published account, ownership metadata improved on-call routing; it took a coordinated migration to cover the organization. That is a reminder that shared context has a maintenance cost, not proof that a knowledge base updates itself.

AI may help answer routine questions from approved documents, point to a decision record, or draft notes after a meeting. The alternative is to retire stale pages, require owners for critical documents, and settle decisions where people can find them. Sometimes a conversation is the only way to expose a disagreement that no summary could resolve. For any generated answer, provide the source and a route to correct it. In high-stakes situations, prefer a person or current runbook over a confident synthesis of uncertain context.

Onboarding is a good test of collaboration because a newcomer cannot rely on remembered shortcuts. Ask them, with consent, to identify the present owner, run the tests, and explain whom they would call during a bad release. The desk-researched onboarding investigation found examples of owner discovery but no published observation of one newcomer doing all three tasks unaided. That missing evidence is a reason to run a local exercise, not to declare the problem solved.

At the junction: Follow one repeated question from its first answer to its fourth asker. If the answer is hard to find, improve access; if it is wrong, improve ownership and upkeep; if people disagree, make the decision explicit. Only then ask whether AI retrieval reduces the remaining friction.

Sources cited in this chapter

  1. https://www.rippling.com/blog/code-ownership-at-rippling

Browse all references →