Introduction

This section captures the lessons learned by App Managed Services SRE teams and leadership through years of engagement across our client base, from application and platform managed services in critical national infrastructure, government, logistics, and hospitality, to the onboarding and transition of new services into SRE support.

These lessons are not abstract retrospectives. Each one reflects a real outcome, positive or negative, from a past project or engagement, and has been generalised into a principle, practice, or requirement that shapes how App Managed Services SRE operates today. Where a lesson resulted in a change to how we work, that change is documented here alongside the reasoning behind it, so the "why" isn't lost as teams and engagements change over time.

The purpose of this section is threefold:

• To prevent repeat mistakes. Where a past engagement surfaced a gap in transition readiness, tooling, communication, or scope the resulting principle exists so future projects don't rediscover the same problem the hard way.
• To codify what works. Not every lesson comes from something going wrong. Some capture practices that demonstrably improved delivery, stability, or client outcomes, and are worth repeating deliberately rather than by chance.
• To give context to our standards. Many of the requirements referenced elsewhere in this documentation in transition criteria, tooling standards, or engagement models originate from a lesson learned here. This section is the "why" behind those decisions.

These principles and practices are living guidance. As SRE takes on new engagements and engagement types evolve, this section should be revisited and extended, not treated as a fixed archive.