process-engineering

Identify bottlenecks and plan data-driven process improvements.

Plan release with versioning, deployment, and rollback strategy.

Design and document comprehensive development workflow.

Design branching strategies (git flow, trunk-based development, etc.) that support parallel work while maintaining stability. Use when establishing version control discipline or managing deployment complexity.

Design change control processes that prevent production surprises while avoiding process paralysis. Use when coordinating multiple team changes or managing infrastructure modifications.

Define criteria for work to enter development (DoR) to ensure engineering time is spent on well-understood, achievable work. Use when standardizing requirements or reducing rework.

Design development workflows that balance speed, quality, and safety. Use when establishing team processes or improving delivery efficiency.

Design incident response procedures that prioritize quick resolution and learning over blame. Use when establishing on-call practices or improving incident response effectiveness.

Design fair on-call schedules that distribute burden, prevent burnout, and maintain coverage. Use when establishing on-call practices or scaling incident response.

Systematically identify and implement process improvements that increase team velocity and reduce friction. Use in retrospectives or when noticing repeated friction points.

Design repeatable release processes that minimize risk and manual overhead. Use when shipping to production, managing versioning, or coordinating multi-team releases.