COMPANY PLAYBOOK
HashiCorp
HashiCorp makes culture concrete through writing practices, meeting rules and measurable operating cadences rather than abstract values.
System principles
- Use writing as a tool for thinking and deciding.
- Pair every cadence with a source of truth and a review ritual.
- Distribute accountability and centralize visibility.
Tensions and trade-offs
- Writing creates inclusion and memory but can lengthen decisions and review load.
- Cadence creates accountability but can become metric and meeting ceremony.
PRACTICES
How HashiCorp builds its operating system
01
Decision making
Decide through written proposals
Documents such as PRDs and RFCs clarify thinking and preserve options and rejected paths.
- How it works
- A proposal is written first, reviewed by relevant people and preserved with its decision context.
- Why it is used
- Improves thinking quality and access to past decisions in a distributed team.
- Trade-off
- If every task becomes an RFC, speed and creative discovery suffer.
- Best fit
- High-cost, multi-stakeholder decisions.
02
Goals
Three-speed operating cadence
Company goals connect to annual, quarterly and weekly sources of truth and review rituals.
- How it works
- Annual and quarterly scorecards and weekly reporting packs are reviewed in defined rituals.
- Why it is used
- Connects long-term direction and short-term execution in one visible system.
- Trade-off
- A poor metric can scale behavior that looks good but is wrong.
- Best fit
- Organizations needing shared visibility across products or business units.
03
Meetings
Design meetings around purpose and output
Meeting type, participants and expected output are defined before the conversation begins.
- How it works
- Agenda and preparation are written, and facilitation matches the meeting purpose.
- Why it is used
- Uses synchronous time for shared thinking rather than information transfer.
- Trade-off
- Over-standardization can burden small, quick conversations.
- Best fit
- Global remote teams with high meeting costs.