COMPANY PLAYBOOK
Warp
Warp collects its working principles in a living public document, organizing around solving user problems and learning by using its own product.
System principles
- Keep principles as a living document.
- Begin coding work by trying the tool.
- Record both success and failure as feedback.
Tensions and trade-offs
- Using one’s own product gives fast insight but employee experience may not represent customers.
- A tool-first discipline increases learning but can delay urgent work.
PRACTICES
How Warp builds its operating system
01
AI-assisted work
Start each coding task with a Warp prompt
A coding task is first attempted with a prompt in Warp.
- How it works
- A successful result is shared; on failure, feedback is first provided about what did not work.
- Why it is used
- Makes the product’s success in real work systematically visible.
- Trade-off
- Starting every task from the same entry point can add friction where it does not fit.
- Best fit
- Product teams seeking to test their own tool in daily workflows.
02
Learning
Record failure after ten minutes
If prompting appears unproductive after ten minutes, failure information is sent to the relevant feedback channel.
- How it works
- The person shares context such as the prompt and conversation ID to help the team learn and potentially create an evaluation.
- Why it is used
- Produces concrete, repeatable failure signals about tool behavior.
- Trade-off
- Reporting overhead can make users document every experiment.
- Best fit
- Fast-learning AI product teams with a feedback channel and clear ownership.
03
Knowledge sharing
Share what works and what does not
Success is shared in the #warped-it channel; if another AI tool works better, people are asked to report what worked there too.
- How it works
- Good examples and comparisons with competing tools do not remain private individual knowledge.
- Why it is used
- Creates reusable examples of good use and signals of product gaps.
- Trade-off
- Channel noise or tool advocacy can obscure the real problem.
- Best fit
- Teams that connect experience-sharing to a product-improvement loop.
04
Product
Coding-mandate dogfooding
Every coding task starts with Warp, putting the product in the team’s own development workflow.
- How it works
- The coding mandate makes internal use the prescribed entry point to development work.
- Why it is used
- It creates direct exposure to product friction.
- Trade-off
- A mandatory tool can be costly or poorly suited in edge workflows.
- Best fit
- Product companies whose staff are genuine target users.
05
Product
Gamechanger–showstopper prioritization
Work is split between high-impact novel features and parity gaps that block use; everything else is treated as a distraction.
- How it works
- The team deliberately balances gamechangers and showstoppers and considers impact relative to effort.
- Why it is used
- It prevents novelty from crowding out basic usability, and vice versa.
- Trade-off
- The categories require judgement and can underweight enabling maintenance work.
- Best fit
- Products needing both differentiation and credible workflow coverage.
06
Product
Risk-specific discovery
Product risk is tested with users and technical risk with a prototype.
- How it works
- Before dismissing work as too large or small, the team actively assesses risk using face-to-face user conversations where possible and prototypes for feasibility.
- Why it is used
- It separates desirability from buildability evidence.
- Trade-off
- Interviews and prototypes add upfront time.
- Best fit
- Uncertain product bets with reversible discovery work.
Primary sources
Source details
Company publication: YesAccessed: 2026-09-05Visible update: Living document; per-page update not displayedLicence: No reuse licence displayed; treat page prose as copyrighted/all rights reserved.Archive: Public Notion URL is capturable, though mutable; preserve URL and content in any external snapshot (no snapshot is claimed).
Source details
Company publication: YesAccessed: 2026-09-05Visible update: Not displayedLicence: No reuse licence displayed; treat page prose as copyrighted/all rights reserved.Archive: Public Notion URL is capturable, though mutable; preserve URL and content in any external snapshot (no snapshot is claimed).
Source details
Company publication: YesAccessed: 2026-09-05Visible update: Not displayedLicence: No reuse licence displayed; treat page prose as copyrighted/all rights reserved.Archive: Public Notion URL is capturable, though mutable; preserve URL and content in any external snapshot (no snapshot is claimed).