How we work
This page describes our default working agreements. Engineering standards live in Engineering; infrastructure runbooks live in Run & Support → Infrastructure.
Defaults
Section titled “Defaults”- Concept-perfect over pixel-perfect — model the right thing before polishing the interface.
- Fast, functional outcomes over slow perfectionism — deliver usable increments, then iterate.
- Strong defaults, minimal exceptions — exceptions become tomorrow’s legacy.
- Business-first technology — technology serves the business; it is not the goal.
- Integrate early, test often — feedback loops beat confidence.
Collaboration
Section titled “Collaboration”- Prefer written context over implicit knowledge: assumptions, constraints, and acceptance criteria.
- Ask “what changes next?” early — it influences the model and the interfaces.
- When something is unclear, slow down and clarify; rework is always more expensive later.
Ownership
Section titled “Ownership”- Autonomy is expected: make decisions within your scope and communicate intent.
- Manage dependencies explicitly: who is blocked, what is needed, and when.
- Escalate early when risk increases (scope, timeline, security, or operability).
Documentation
Section titled “Documentation”- Keep documentation close to the truth: update docs when you change the system.
- Prefer linking over duplicating: one canonical page and cross-links.
- Write down decisions that affect future work (trade-offs, constraints, chosen defaults).