How They Do ItBETA

COMPANY PLAYBOOK

thoughtbot

thoughtbot builds quality product delivery through paired work, explicit working agreements, and regular sharing rhythms rather than individual heroics.
Operating system
  1. Scope agreement
  2. paired delivery
  3. daily alignment
  4. visible result
  5. weekly learning.

System principles

  • Start pairing with an intentional working agreement.
  • Use synchronous time for alignment and joint problem solving.
  • Adapt processes to the product and team needs.

Tensions and trade-offs

  • Pairing creates quality and shared context but assigns two people to one task.
  • Cadences create visibility but can become unnecessary ceremony.

PRACTICES

How thoughtbot builds its operating system

01
Collaboration

Working agreement before pairing

Pairs discuss scope, duration, location/environment, and pairing style before beginning.

How it works
Two people explicitly agree whether they will work until a ticket is done or for a timebox, and choose a style such as ping-pong.
Why it is used
Makes the purpose and mode of participation in pairing explicit.
Trade-off
Setup discussion can feel disproportionate for small urgent fixes.
Best fit
Teams doing complex delivery work that benefits from shared learning.
Open original source ↗
02
Collaboration

Think aloud while pairing

Partners share their thinking, keep one another involved, and check in regularly while working.

How it works
Conversation continues, alternatives are questioned, and both participants stay active.
Why it is used
Makes tacit technical reasoning shareable and reviewable.
Trade-off
It can add cognitive load for tasks requiring deep individual focus.
Best fit
When knowledge diffusion and immediate peer feedback are valuable.
Open original source ↗
03
Learning

Weekly discussion of successes, failures, and plans

The operations guide calls for a weekly meeting to discuss successes, failures, and future plans.

How it works
The team looks back weekly and makes its next intentions visible together.
Why it is used
Connects learning from delivery to a regular feedback loop.
Trade-off
It can turn into repetitive status reporting if not connected to action.
Best fit
Teams coordinating several clients or workstreams.
Open original source ↗
04
Collaboration

Deliberate pair-programming setup

Pairs agree goal, environment and pairing style before work, switch roles while working, then share outcomes and ask for feedback.

How it works
The guide specifies before/during/after pairing rituals, including ping-pong or time-based switching.
Why it is used
It turns pairing into joint learning and review rather than co-presence.
Trade-off
Two people on one task can cost more in the short term.
Best fit
Complex work where shared context and rapid feedback outweigh individual throughput.
Open original source ↗
05
Meetings

Inclusive meeting facilitation

Meetings use practices such as starting and ending on time, making space for others, allowing silence, crediting origins and using clear language.

How it works
Concrete prompts (“step up, step back,” Shine Theory, clarify what you hear) govern participation.
Why it is used
It makes contributions from quieter or underrepresented participants more likely to be heard.
Trade-off
Facilitation discipline slows some discussions.
Best fit
Diverse teams where meeting participation is uneven.
Open original source ↗
06
Learning

Investment time

Time outside client work is invested in individual learning, company improvement and community contribution.

How it works
The operations guide names activities from learning and handbook improvements to tooling, hiring and open source.
Why it is used
It protects continuous improvement from billable-work crowd-out.
Trade-off
It reduces immediately billable capacity.
Best fit
Professional-services organizations that deliberately fund capability building.
Open original source ↗
07
Performance

Sustainable pace

Productivity is kept even over time to achieve a higher long-term pace, recognizing that tired and demoralized teams produce less.

How it works
The guide explicitly treats sustainable, rather than perpetually extended, pace as the operating target.
Why it is used
It protects long-run delivery capacity.
Trade-off
It can constrain response to genuine short-term emergencies.
Best fit
Knowledge work with recurring demand and a need to retain expertise.
Open original source ↗

Primary sources

Working togetherCompany-published playbook practice guide
Source details
Company publication: YesAccessed: 2026-09-05Visible update: Copyright 2026 visible; individual-page update not displayedLicence: No reuse licence displayed; treat page prose as copyrighted/all rights reserved.Archive: Public HTML URL; eligible for an external web snapshot (no snapshot is claimed).
PlaybookCompany-published playbook
Source details
Company publication: YesAccessed: 2026-09-05Visible update: Copyright 2026 visible; individual-page update not displayedLicence: No reuse licence displayed; treat page prose as copyrighted/all rights reserved.Archive: Public HTML URL; eligible for an external web snapshot (no snapshot is claimed).
OperationsCompany-published playbook operations guide
Source details
Company publication: YesAccessed: 2026-09-05Visible update: Copyright 2026 visible; individual-page update not displayedLicence: No reuse licence displayed; treat page prose as copyrighted/all rights reserved.Archive: Public HTML URL; eligible for an external web snapshot (no snapshot is claimed).
TimeCompany-published playbook operations guide
Source details
Company publication: YesAccessed: 2026-09-05Visible update: Copyright 2026 visible; individual-page update not displayedLicence: No licence stated in the reviewed source.Archive: Public HTML URL; eligible for an external web snapshot (no snapshot is claimed).