Skip to content
HN On Hacker News ↗

DRIVE | Cortex

▲ 11 points • 10 comments • by gsdatta • 4mo ago • HN discussion ↗

Pangram verdict · v3.3

We believe that this document is fully human-written

5 %

AI likelihood · overall

Human
100% human-written 0% AI-generated
SEGMENTS · HUMAN 2 of 2
SEGMENTS · AI 0 of 2
WORD COUNT 657
PEAK AI % 5% · §1
Analyzed
Jul 9
backend: pangram/v3.3
Segments scanned
2 windows
avg 329 words each
Distribution
100 / 0%
human / AI fraction
Verdict
Human
Pangram v3.3

Article text · 657 words · 2 segments analyzed

Human AI-generated
§1 Human · 5%

Operational Excellence for AI-accelerated engineering.AUTHORED BYGanesh DattaCo-Founder & CTO at CortexDRIVE is a framework for measuring engineering organizational health in the age of AI.It assesses organizational effectiveness across five pillars—Delivery, Reliability, Initiatives, Vigilance, and Efficiency—and the recurring review that turns those measurements into action.Why DRIVE, why nowSoftware engineering is having its industrial revolution. We've gone from writing code by hand to building software factories. The controls and frameworks that govern the accelerated output have not caught up, while the gap continues to widen as AI takes on more of the work.The engineer’s job is changingAs agents automate more of the SDLC, engineering work increasingly shifts to designing and operating the systems that produce software. The organization's hardest questions shift with them, into the operational layer.Velocity is outpacing the controlsAI accelerates output, but the controls layer hasn’t kept pace. Without a counterweight, that pressure compounds. The missing layer is organizational backpressure: the brakes and signals that hold the system stable.Organizational health needs its own frameworkOther engineering frameworks measure developer and team productivity. Whether the organization can sustainably turn customer needs into reliable software is a different question, at a different altitude.What DRIVE measuresDRIVE measures whether an organization is sustainably turning customer needs into reliable software. DeliveryPillar 01“Are we shipping fast and is it sustainable?”AI has eliminated the constraint on writing code, but every other bottleneck in the SDLC remains, and improving anything other than the binding constraint yields no real gain. This pillar measures both the structural and human capacity to sustain high performance.CRITICAL METRICSDeploy frequency.Lead time for changes.On-call pager volume.ReliabilityPillar 02“Are we delivering on our promises to customers?”AI makes it easier to write automated tests that give you a false sense of confidence. The reliability pillar is grounded in reality through the customer’s experience and expectations.CRITICAL METRICSFunctional SLO status (binary pass/fail).Sev0 and Sev1 incident count.InitiativesPillar 03“Are our org-wide engineering investments making progress?”With AI drastically changing how engineering teams operate, org-wide engineering-driven initiatives are becoming more critical than ever to take full advantage of the benefits AI has to offer.

§2 Human · 4%

CRITICAL METRICSTier 1 initiative milestone completion rate.OpEx action item completion rate.VigilancePillar 04“Are we actively defending our systems and managing our acceptable risk?”AI code generation is introducing vulnerabilities and expanding attack surfaces faster than ever, making systemic security risk harder to ignore. DRIVE tracks the security posture of your engineering organization so you can stay ahead of what matters most to your customers.CRITICAL METRICSOpen Critical and High fixable CVEs.Assets below the minimum compliance and security bar.Orphaned assets.EfficiencyPillar 05“Are we allocating resources to the right problems?”As teams adopt agentic workflows and ship AI-enabled products, token spend is climbing fast, reshaping how resources in dollars and engineering time are allocated. DRIVE tracks how capacity is split between innovation and maintenance.CRITICAL METRICSCloud spend versus budget.Internal AI and LLM token costs.Percentage of capacity spent on innovation.The OpEx reviewThe Operational Excellence review is the recurring leadership ritual that treats the engineering organization as a complex system, measures it against DRIVE, and reallocates time, people, and money to close the gaps.The practice has roots in manufacturing, where Operational Excellence emerged as a discipline for treating an entire factory as one observable, continuously improving unit.Many leading engineering organizations already run their own versions.A weekly operational review that reaches the most senior engineering leadership.Facilitator-led reviews that shape resource decisions. API reliability sits above 99.999%.Blameless production meetings that feed capacity planning.The review takes a different shape as an organization grows, from a single global review at smaller companies to separate local and org-wide reviews at enterprise scale.Startup / mid-marketOne global reviewWeeklyEnterpriseLocal team reviewWeekly or biweeklyOrg-wide reviewWeekly or biweeklyRead the full framework to see a breakdown of each meeting format: attendees, agenda, and more.Find your fastest sustainable speedSee how your organization measures up across the DRIVE pillars and get personalized recommendations.Powered byDRIVE is a framework that any engineering org can adopt.Cortex makes operating against it actually feasible at scale.Scorecards for the metrics that matterPurpose-built workflowsTrack initiatives and vigilance gaps