Engineering Operating Principles¶
Purpose¶
As the platform and customer base grow, the cost of ad-hoc decisions, unplanned interruptions, and last-minute changes increases significantly. These operating principles exist to ensure that engineering work is delivered in a way that is reliable, predictable, and sustainable, while supporting the broader business goals.
The intent of these principles is to:
- Reduce production risk
- Improve delivery predictability
- Protect focus time for complex work
- Ensure stability during peak revenue periods
- Create a sustainable operating pace for the team
These principles are not about limiting output - they are about optimising how work gets done so the right work is prioritised and delivered effectively.
Core Principles¶
1. Production Stability Is a Business Priority¶
Changes to production systems carry real business risk. All engineering work should consider the impact on system stability, customer experience, and revenue - especially during high-traffic or peak trading periods.
2. Urgency Is Defined, Not Assumed¶
Not all work is urgent, and urgency should be clearly defined rather than implied.
Clear escalation paths and prioritisation help ensure genuinely critical issues are addressed quickly, without creating unnecessary disruption or burnout.
3. Deep Work Requires Protected Focus Time¶
Complex engineering tasks require uninterrupted focus.
Reducing unnecessary interruptions improves quality, reduces rework, and speeds up overall delivery.
4. Sustainable Pace Beats Heroics¶
Consistently delivering at a sustainable pace is more effective than relying on after-hours work, last-minute changes, or reactive "firefighting."
Long-term velocity is prioritised over short-term wins.
5. Peak Revenue Periods Require Reduced Change Risk¶
During high-impact business periods (e.g. October–December), engineering activity should prioritise stability and risk reduction. Large or high-risk changes should be planned outside these windows wherever possible.
6. Work Should Be Visible and Documented¶
Decisions, priorities, and tasks should be captured in shared systems rather than relying on private messages or tribal knowledge. This improves alignment, accountability, and continuity across the team.
7. Processes Should Reduce Cognitive Load¶
Processes exist to make work easier, not harder.
Clear guidelines for communication, task intake, and releases help the team focus on execution rather than constant context-switching.
How These Principles Are Applied¶
These principles guide:
- Communication and escalation practices
- Task intake and prioritisation
- Release and deployment decisions
- After-hours and on-call expectations
- Planning around peak business periods
Supporting SOPs define how these principles are applied in day-to-day work.
Review & Iteration¶
These principles are living guidelines.
They will be reviewed periodically and refined as the platform, team, and business continue to evolve.