Skip to main content

Product Operations

Product Operations defines how EGI takes a product from initial concept through launch, release management, and long-term support. These procedures apply to all client projects and internal products built by EGI.

Scope​

Product Operations covers everything that happens between "we've agreed to build this" and "this is running in production and someone is responsible for it." It bridges the gap between engineering work and operational readiness.

Core Principles​

  1. Every product follows the same lifecycle. Whether it is a client engagement or an internal tool, the phases and quality gates are consistent.
  2. Nothing launches without a checklist. The launch and release checklists exist to catch issues before they reach users.
  3. Instrumentation is not optional. Every product ships with analytics and monitoring from day one.
  4. Ownership is always clear. At every stage, there is a defined owner responsible for the product. Handoffs between EGI and Anchor MSP follow a structured process.

Documents in This Section​

Product Lifecycle​

The full lifecycle from Discovery through Maintenance, including deliverables per phase and go/no-go criteria for advancing between phases.

Launch Checklist​

A pre-launch validation checklist covering testing, performance, security, monitoring, documentation, and client sign-off. Used before the first production deployment of a new product or major feature.

Release Checklist​

A step-by-step process for shipping individual releases after the initial launch, including version management, changelog updates, deployment verification, and stakeholder communication.

Analytics Instrumentation​

Standards for PostHog setup, event tracking, user identification, feature flags, session replay, and dashboards. Ensures every product collects the data needed to make informed decisions.

Feature Flags​

Patterns and conventions for using PostHog feature flags, including when to use them, naming conventions, rollout strategies, and cleanup policies.

Support Ownership​

Defines who is responsible for supporting a product at each lifecycle stage, including escalation paths, SLA definitions, and the transition from EGI to Anchor MSP.

How These Documents Relate​

The typical flow through these documents during a project:

  1. A project enters the Product Lifecycle at the Discovery phase
  2. As the project approaches its first production deployment, the team works through the Launch Checklist
  3. Analytics Instrumentation and Feature Flags are configured during the Build phase and validated during Launch
  4. After launch, each subsequent deployment follows the Release Checklist
  5. Support Ownership governs who is on point throughout, with formal handoff from EGI to Anchor MSP after stabilization