What does the team need to grow and mature on a yearly level?
Technical practices have made continuous deployment to production a norm. The engineering team focus more on customer product metrics than on Engineering constraints. Experimentation techniques are embedded for both technical de-risking and customer behaviour hypotheses. The team enjoys a diversity of Engineering talent and experience.

Continuous Deployment 🔗

Formally decoupling deployment from (Customer) release activity. Building on continuous Integration, all successful builds are automatically promoted and deployed to production. The team is likely practicing Trunk-based development (TBD) or non-blocking pull requests where Engineers work on a single branch as much as possible to encourage continuous integration. Pushing changes directly to trunk or main is made safe with mature TDD and quality engineering practices. Changes are implemented with the intention that it will be deployed directly to production.

💎 Benefit: Maximum throughput of changes while verifiably maintaining quality of changes. Very fast feedback loops. High throughput of small lower-risk changes.

📶 Signal(s): High degree of release controls (e.g. feature flags, experiments) ensure it's safe to deploy partially implemented features. High maturity alerting, quality of service, and incident management to detect and revert problem changes.

Product Metrics 🔗

The team effectively captures and analyzes product performance metrics, enabling data-driven decision-making and continuous product improvement.

💎 Benefit: The team can independently form and test a new hypothesis using standard user event capture, aggregation and visualization tools.

📶 Signal(s): User events and flows are well-documented and accessible to all teams. Event processing filters activity from automated testing.

Experimentation 🔗

The discipline of experimentation to support hypothesis-driven development and technical risk management (e.g. migrations, performance optimisations, new features). The team conducts controlled experiments, A/B tests, and user research to validate assumptions, gather feedback, and inform decision-making.

💎 Benefit: Actively promotes a culture of experimentation to support both hypothesis-driven development and technical risk management.

📶 Signal(s): The team can run multiple experiments in parallel. Significant system changes can be safely tested in production.

Career Growth 🔗

My product team provides ample opportunities for career growth and professional development. There is a mix of junior and senior talent on the team. Everyday pairing and coaching on specialised areas avoid key person dependencies. The team and company encourage continuous learning, supports skill enhancement, and provides access to training resources and mentorship programs. Regular performance evaluations and constructive feedback help identify areas for improvement and define career paths.

💎 Benefit: Everyday pairing and coaching on specialised areas avoid key person dependencies. Regular performance evaluations and constructive feedback help identify areas for improvement and define career paths.

📶 Signal(s): There is a mix of junior and senior talent on the team. My team provides ample opportunities for career growth and professional development.