This is the third post in our DRIVE Deep Dive series. We've covered Delivery and Reliability so far; this post takes on Initiatives. For the complete model, download the full DRIVE framework.
In this video, Becka gives a guided tour of Cortex, the Engineering Operations Platform that runs mission control for your AI software factory. Learn how to centralize visibility, clarify ownership, and automate standards across your entire software ecosystem.
Most engineering metrics track individual output. DRIVE measures the health of the system as a whole. In this Feature Friday, Director of Customer Education and Delivery Taylor Schmidt walks through Cortex's DRIVE scorecard and dashboard, a framework covering five pillars: delivery, reliability, initiatives, vigilance, and efficiency.
You can hit every DORA target and still be losing ground. Deploy frequency up, lead time down, change failure rate and MTTR both healthy, but underneath it could be hiding an organization slowly getting worse at turning work into reliable software. New services shipping without clear owners, an attack surface widening faster than anyone is tracking, on-call rotations quietly filling up, a migration that was supposed to close last quarter still limping along.
This is the second post in our DRIVE Deep Dive series. Over the coming weeks we're examining each pillar of the DRIVE framework in turn, and mapping DRIVE against the frameworks engineering leaders already run on, including DORA and SPACE. For the complete model, download the full DRIVE framework. Our last post covered Delivery. Up next: Initiatives. --- AI has removed the last real constraint on producing code, and organizations are shipping more of it than ever.
This is the first post in our DRIVE Deep Dive series. Over the coming month we'll examine each pillar of the DRIVE framework in turn, and map DRIVE against the frameworks engineering leaders already run on, including DORA and SPACE. For the complete model, download the full DRIVE framework.
Stop guessing whether your repos meet your branch policies. Start knowing. In this Feature Friday, Senior Engineering Manager Gabriel walks through Cortex's new native support for GitHub branch rule sets and how to use them in scorecards to enforce consistent policies across all your repos. What you'll see: Questions? Reach out to your CSM or drop a comment below.
Incident response is a context problem. The first minutes of any incident are spent reconstructing what the affected service is, what it depends on, and who owns it. That reconstruction happens during the worst possible window. The Cortex catalog already holds this data: services, teams, domains, and the relationships between them, maintained by the engineers who run those systems.
Ask a software engineer what they do and the answer, for years, has been some version of "I write code." That assumption is unwinding fast. AI agents can now write code, review pull requests, run tests, and ship to production, and they're taking on a fast-growing share of that work. As agents absorb more of the execution, the human role shifts.