e OpenDEX

Working draft · version 0.1 · working draft

OpenDEX

An open, interoperable specification for measuring DEX.

OpenDEX provides a common way to define and exchange Digital Employee Experience (DEX) measurements. It covers terminology, metric definitions and a machine-readable data schema. The specification is in development.

Scope

What OpenDEX is — and isn't

Scope and purpose of the specification.

OpenDEX is not a DEX product, vendor ranking or consulting framework. It does not replace existing DEX platforms. It defines how measurements can be described and exchanged.

A standard that only one vendor controls isn't a standard anyone should trust.

From the original OpenDEX proposal

Positioning

Two different problems, easily confused

DEX operating models and measurement specifications address different needs. OpenDEX focuses on the data: how measurements are defined, represented and exchanged.

The operating question
How should an organization run a DEX program?
The OpenDEX question
How should DEX measurements be described and exchanged?
Operating output
A discipline — roles, cadence, escalation
OpenDEX output
A machine-readable language for the data underneath it
Nearest analogy
An ITIL-style operating model
OpenDEX's analogy
OpenTelemetry, FOCUS, CloudEvents

An operating model describes how a DEX practice works. OpenDEX describes the measurements it uses.

Architecture

Four pillars, held deliberately narrow

The specification covers four areas.

i.

Taxonomy. What things count as DEX in the first place — a shared vocabulary across device, application, network, collaboration, security and sentiment.

ii.

Metric definitions. What each measurement precisely means: unit, start event, end event, exclusions, aggregation, sampling.

iii.

Data schema. How a measurement is represented on the wire, so it moves between systems without a hand-written translation layer.

device.login_time — example record
{
  "metric": "device.login_time",
  "value": 14.2,
  "unit": "seconds",
  "timestamp": "2026-09-01T09:14:02Z",
  "device": "anon-device-id",
  "os": "Windows 11"
}
iv.

Interoperability. Can two unrelated DEX platforms produce data a third system can consume without custom mapping? That's the real test.

Taxonomy v0.1

A first, deliberately small taxonomy

The initial taxonomy is expected to cover approximately 30–50 metrics across six categories. The list will be reviewed and revised as the specification develops.

Device · boot, login, CPU/memory pressure, disk health, uptime Application · launch time, crash rate, freeze, response time Network · latency, packet loss, DNS, Wi-Fi quality, VPN Collaboration · call quality, audio/video, meeting connectivity Security · AV/EDR status, firewall, encryption, patch state Sentiment · IT satisfaction, ease of resolution, friction

OpenDEX does not currently define a universal score. The specification describes individual measurements; it does not prescribe how organizations should combine or weight them.

Charter v0.1

Nine working principles

  1. Vendor neutral.
    No platform gets a deciding vote by default.
  2. Open specification.
    Published, versioned and changed in the open.
  3. Practitioner driven.
    Written by people who run DEX programs, not only people who sell tools for them.
  4. No vendor ranking.
    OpenDEX describes measurements. It never scores or ranks products.
  5. No mandatory scoring formula.
    It says what to measure, not how every organization must weight it.
  6. Interoperability over differentiation.
    The goal is comparable data, not a distinctive methodology.
  7. Transparent governance.
    Decisions and disagreements get recorded, not smoothed over.
  8. Evidence over opinion.
    Claims about what DEX should measure get tested, not just asserted.
  9. Privacy by design.
    No raw employee data, no identifiers, aggregation thresholds from day one.

Year one

Four movements, September 2026 – August 2027

The first-year plan is organized into four stages. Dates and deliverables are targets and may change as the work progresses.

September – November 2026

One — Foundation

Publish the OpenDEX Charter v0.1 and an initial governance draft. Stand up the specification repository. Draft the first taxonomy. Begin a biweekly Working Note documenting open questions in public.

December 2026 – February 2027

Two — Community

Recruit five to ten Founding Contributors. Open four working groups. Run the first OpenDEX Roundtable and publish what came out of it.

March – May 2027

Three — Validation

Ship a small reference collector. Run an interoperability challenge across independent and synthetic data sources. Launch a small benchmark pilot and publish distributions, never company-level scores.

June – August 2027

Four — Institutionalization

Publish OpenDEX v0.9 with taxonomy, schema, reference implementation and governance in place. Form a Technical Council with no single-company majority. Release OpenDEX v1.0.

Target: OpenDEX 1.0, by the end of August 2027.

Get involved

Who this is for, starting now

Participation is open to practitioners, engineers, researchers and others with relevant experience. The initial focus is on substantive review and contributions to the specification.

Practitioner participation

Practitioners can help review metric definitions, contribute use cases, take part in interviews and working groups, and identify gaps in the draft. Roles and responsibilities will be defined through the project's governance process.

SIG 1Measurement — what should be measured, and why.

SIG 2Schema — how a measurement gets represented.

SIG 3Benchmarking — how organizations can be compared safely.

SIG 4Practitioner Experience — what DEX means operationally, day to day.

Working Notes will document open questions, proposals and decisions as the specification develops.

Governance & IP

Governance and intellectual property

OpenDEX is intended to be developed as a shared, community-governed specification. Participation does not confer equity or ownership of the initiative.

Open participation

Individuals and organizations may contribute under the project's published policies.

No equity

Contributions do not provide shares, financial returns or governance rights by payment.

Independent governance

The intended model is neutral stewardship and community-led decision-making.

The specification is intended to be a shared resource. Its governance will be documented openly, with participation available across organizations and interest groups. The project will publish its formal governance, contribution and licensing policies as they are adopted.

Contributing as an individual or organization

Contributors may participate in their own capacity or on behalf of an organization, provided they have the necessary authority to submit their work. Contributions do not transfer ownership of an employer's intellectual property. Contributors are responsible for confirming that they are permitted to make any required rights grants.

Who owns a contribution?
Ownership and permitted use will be governed by the project's adopted contribution terms and specification license. No exclusive ownership claim is created merely by participating.
Who stewards the OpenDEX name?
The stewardship arrangements will be set out in the project's governance documents. The long-term objective is neutral stewardship under a structure accountable to the community.
Can an employer contribute?
Yes. Organizations may contribute directly or authorize an employee to contribute on their behalf, subject to the applicable policies and agreements.
Is participation an investment?
No. OpenDEX is not an equity or investment scheme. Participation does not provide a financial return or ownership stake.

Contribution and licensing framework

The project is reviewing established approaches to open specification governance and contribution management. These include the Community Specification framework and the Developer Certificate of Origin. No framework or legal instrument should be treated as adopted until the project's own policies are published.

These references are provided for background. OpenDEX's formal governance and intellectual property policies remain under development. This page is not legal advice.

Source

Specification repository

The repository will be the public source for specification drafts, examples and project governance documents.

In preparation

The repository is planned to contain the taxonomy, schema, examples, reference implementation and governance documents. Publication details will be added when the repository is available.

specification/ · examples/ · reference-implementation/ · governance/ · CONTRIBUTING.md · GOVERNANCE.md

Repository link to be added.

Join

Contribute to OpenDEX

We welcome practitioners, engineers, researchers and organizations interested in developing an open DEX measurement specification.

To express interest, share your area of experience and how you would like to contribute. You may also suggest a metric, use case or issue for the working groups to consider.