What makes an AI-native enterprise?

Define the changed work before judging the enterprise.

Define the changed work

Mayden proposes an AI-native enterprise as one that repeatedly converts AI capability into useful, accountable work across a defined organisational scope. This working definition concerns recurring decisions, workflows, responsibilities and learning. It is a research proposition, not an empirically validated classification.

Start with a resolved service request, reviewed clinical note, accepted production schedule or authorised maintenance decision. State what AI contributes and where the work finishes. A demonstration shows that an output can be produced under particular conditions. A changed operating model needs a repeatable relationship between output, people and result.

Counterexamples sharpen the definition. Buying licences establishes availability, not active use. A specialised model can be valuable without transforming an organisation. Restricting automation can reflect sound judgement; maximum autonomy is not the objective.

Test the mechanism and work boundary

AI research does not deliver one transferable enterprise effect. A customer-support study found gains differing by experience; writing experiments and a bounded consulting exercise study other work. They identify mechanisms and questions but cannot be averaged into an expected return for a Gulf enterprise. Generative AI at Work ↗; Experimental evidence on the productivity effects of generative artificial intelligence ↗; Navigating the Jagged Technological Frontier ↗.

Evidence complicating the positive story belongs in the same review. An early-2025 developer study found slower completion in its small selected setting despite perceived speed-up. A subsequent methods update describes selection and time-measurement problems in newer estimates. This warns about transfer and measurement; it is not a universal conclusion about developers. Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity ↗; We are Changing our Developer Productivity Experiment Design ↗.

Define eligible work, observation period, comparison and acceptance criterion before evaluating results. Include rejected outputs, checking, interruptions and the people absorbing change. A faster component can shift work elsewhere.

Keep three evidence ledgers

The practice ledger records workflow, scope, accountable role, permissions, frequency and coverage. The outcome ledger records quality, time, throughput, cost, service and adverse effects, together with the comparison supporting interpretation. The evidence ledger records respondent role, document or observation, date, locator, provenance, contradictions and review.

Connect the ledgers without collapsing them into one number. A documented disappointing result is scientifically valuable. A reported saving without a baseline may merit further study. Strong source access does not establish effectiveness; limited public disclosure does not establish a weak company.

Nine candidate themes organise the inquiry: AI in core work; workforce; ecosystem; interfaces and automation; decision lineage; experimentation; autonomy and operating model; organisational knowledge; governance. They are hypotheses about a useful composite, not interchangeable symptoms of a proven latent trait. Internal consistency alone would not validate them. Conventional Wisdom on Measurement: A Structural Equation Perspective ↗; Handbook on Constructing Composite Indicators: Methodology and User Guide ↗.

Build the benchmark around a useful decision

A private report should help executives decide what to improve, test, stop or verify. It should state scope, show disagreements and propose a bounded action with an owner and measure. It must remain useful even if research does not support a single headline score.

Development requires content review, bilingual cognitive work, feasibility testing, independent coding and empirical evaluation for declared purposes. Sample requirements follow the construct, comparisons and precision, not a convenient target. A 40–60-company feasibility plan is a capacity assumption, not validation power. Best Practices for Developing and Validating Scales for Health, Social, and Behavioral Research: A Primer ↗.

Public research describes source-backed examples and limits of a collection. A future participant study would examine permissioned evidence over a defined period. Their scales cannot be converted, and the public series cannot certify enterprise capability.

Leadership agenda

Executive sponsor: identify the recurring decision the assessment should improve.

Method lead: specify the construct and evidence needed for that use.

Operating team: retain outcomes, interventions and uncertainty alongside successes.

Scope and reading boundaries

The source corpus contains 80 purposefully selected entity records across eight sectors, ten per sector. Headquarters markets are Saudi Arabia, the UAE, Qatar, Kuwait and Bahrain; Oman is outside this edition. Groups, subsidiaries and specific operations have different scopes. This is not a representative sample. Source cutoff: 10 October 2026; publication edition: 11 October 2026.

Source extraction and challenge were AI-assisted, not independent human assurance or verification of current operations. Source visibility is not adoption prevalence. Unreported details are unresolved questions, not absent capabilities. Named examples imply neither participation, endorsement, confidential access nor a Mayden client relationship.