If you do not know where to start, pick what hurts today and get recommended Execution Kits and Templates matched to your symptom.
Search by symptom title, signals, or DORA metric (LT, DF, MTTR, CFR).
Environment inconsistencies cause bugs that only appear in production.
Too many people have too much access; no audit trail.
Too many alerts, most are noise, real issues get missed.
Breaking changes and version conflicts plague integrations.
No one has a clear picture of how systems connect.
Evidence collection is manual and late; controls are bolted on.
Fear of change leads to infrequent, risky releases.
Build and test times discourage frequent integration.
Unexpected bills; no visibility into what's driving costs.
Collecting audit evidence requires manual work before reviews.
Schema changes are risky and require downtime.
Known vulnerabilities in dependencies are not addressed.
Releases wait in queue because only certain people can deploy.
Releases are high-stress, manual, and hard to roll back.
Backups exist but recovery has never been tested.
Docs exist but don't reflect reality; developers don't trust them.
Manual, repetitive work consumes engineering time.
E2E tests are slow, flaky, and hard to maintain.
Dev, staging, and prod are all different; surprises in prod.
Work takes 3x longer than estimated, planning is unreliable.
Old flags accumulate, nobody knows what's active.
Unreliable tests are ignored, defeating their purpose.
Can't tell if things are working until users complain.
Work passes through multiple teams, each adding delay.
Success depends on individual heroes, not sustainable systems.
Emergency fixes skip CI/CD, creating technical debt and risk.
Reliability issues recur; the same failure modes repeat.
Work gets stuck in queues; integration and testing happen late.
Critical system with no documentation or original authors.
If one person leaves, critical knowledge is lost.
Dashboards exist but don't drive decisions.
Too many services; hard to debug across boundaries.
Large codebase makes changes risky and slow.
Low test coverage means changes feel risky.
Same problems persist; no learning from mistakes.
No agreed-upon reliability targets; everything is equally important.
On-call rotation is exhausting and unsustainable.
New team members need months to become productive.
Incident reviews happen but follow-up items are never completed.
Pull requests sit unreviewed for days or get rubber-stamped.
Old bugs keep coming back; fixes break other things.
Coordinating releases across teams is painful and error-prone.
Rollback procedures exist but are never practiced.
Capacity planning and scaling require human intervention.
Credentials, API keys, or tokens found in repositories.
Security reviews happen late, blocking releases.
Dev, Ops, Security don't collaborate; us vs. them mentality.
Each server is uniquely configured; replacement is risky.
Accumulated shortcuts making every change harder.
Manual testing or QA handoffs slow down delivery.
Engineers spend more time in meetings than coding.
Teams juggle many items, nothing gets finished.
Too many disconnected tools creating friction.
Critical knowledge exists only in people's heads, not documented.
Everything is "high priority," so nothing is.
Nobody knows who owns what, causing delays and finger-pointing.