Dualwire composes the validated frameworks the industry already trusts — DORA, SPACE, DevEx, and the Flow Framework — and adds its own operations lens. Nothing here is invented; it's assembled to answer one question: how effective is your engineering system, end to end?
Deployment frequency, lead time, change failure rate, failed-deploy recovery, and reliability. Throughput leans DevEx; stability leans OpsEx. DORA tells you whether delivery outcomes are good.
Satisfaction, Performance, Activity, Communication, Efficiency. Its core lesson: never reduce productivity to one number captured one way. Every Dualwire driver is SPACE-tagged and pairs a survey signal with a system signal.
The product-side analog to DORA: flow time, throughput, flow efficiency, and WIP. It measures how work moves from idea to production — the spine of the Product lens.
Feedback loops, cognitive load, and flow state — the drivers behind developer productivity — plus tooling and satisfaction. This is the lens most tools stop at.
Dualwire's contribution: signal quality, operational complexity, interruption & toil, incident response, and on-call health — the SRE realities that DevEx-only tools miss.
Delivery flow, roadmap predictability, discovery & prioritization, and alignment — is the team building the right thing, and does the roadmap mean anything?
| DevEx driver | OpsEx analog |
|---|---|
| Feedback loops | Signal quality (alert precision, MTTD) |
| Cognitive load | Operational complexity (services owned, runbooks) |
| Flow state | Interruption & toil (manual, unplanned work) |
| Tooling & local dev | Incident response (MTTA/MTTR, postmortems) |
| Developer satisfaction | On-call health (pages, after-hours, error budget) |
Benchmarkable 0–100 scores — an index of indices — built transparently from the lenses.
driverScore = blend(surveyScore, systemScore, driver.perceptualShare)
lensScore(L) = weightedMean(driverScore for drivers in L) → DevEx, OpsEx, Product
EEI = w_dev · DevEx + w_ops · OpsEx (weights vary by team type)
PEI = lensScore(Product) (tracked beside EEI, not folded in)Product sits beside EEI as its own index, so opening up "are we building the right thing?" never muddies the engineering number. Lens weights adjust by team type — an SRE team weights OpsEx higher, a product squad weights DevEx higher — so one index compares different teams fairly. Reverse-scored items (e.g. "on-call is a source of burnout") are inverted so higher always means better.