Research protocol. No respondents, dataset or empirical findings are claimed.

Research status

This is a proposed research protocol. Recruitment has not been reported, no respondent dataset is published and there are no findings, rankings or industry estimates. The protocol is available so prospective contributors and readers can inspect the intended questions before results exist.

Research questions

How do organizations define delegated authority? Which capabilities distinguish a bounded experiment from an operated business workflow? How do teams evaluate value after accounting for exceptions, rework and human oversight? Where do architecture and governance responsibilities meet?

Proposed methodology

Use a mixed-method design combining a structured organizational survey with consented interviews and artifact review. Define an eligible participant as someone with direct responsibility for an assessed workflow, platform or assurance function. Record role and scope rather than assuming one respondent speaks for the whole enterprise.

Pilot the questionnaire before recruitment. Publish the final instrument, recruitment channels, field dates, eligibility rules and exclusions before analyzing results. Any changes after data collection begins should appear in a dated protocol amendment.

Sample characteristics and limitations

A future report will disclose the number of eligible responses, completion and exclusion rules, organization size bands, industries, geographies and respondent roles. It will distinguish organization-level records from individual responses and explain how duplicates are handled.

A convenience sample must not be presented as representative of all enterprises. Small subgroups should be suppressed or combined to protect participants and avoid unstable comparisons. Publish uncertainty and missingness alongside any chart.

Analysis plan

Report descriptive distributions before constructing comparisons. Compare like assessment scopes and disclose differences in workflow type, consequence and deployment stage. Explore associations without claiming that a governance practice caused a business outcome.

Do not rank industries or geographies unless sample quality supports the comparison. The maturity model is a conceptual instrument; any use as a research measure requires reliability and validity work appropriate to the question.

Planned report structure

The eventual report will include an executive summary, methodology, sample description, findings, qualified comparisons, limitations, references and an accessible downloadable report. Tables will provide text equivalents for charts. A media kit will separate quotable findings from interpretation and provide the exact source location for each figure.

Participant protection

Collect only information needed for the research. Seek informed consent, avoid confidential operational details and document access, retention and deletion rules before recruitment. Named case material requires separate attribution permission. Anonymization must consider whether combinations of role, industry and architecture could identify a participant.

Citation

Krishnan, B. (2026). State of Enterprise Agentic Transformation: Research protocol. AgenticTransformation.ai. Cite this as a protocol, not as an empirical report. A DOI and downloadable findings report will be added only when those assets exist.

References

  1. NIST: AI Risk Management Framework ›
    Published 2023-01-26. Reviewed 2026-09-06. Voluntary framework for incorporating trustworthiness into AI design, development, use and evaluation. Framework publication date; landing page is maintained.
  2. Anthropic: Building effective agents ›
    Published 2024-12-19. Reviewed 2026-09-06. Distinguishes predefined workflows from model-directed agents; recommends increasing complexity only where justified. Vendor engineering perspective, not an independent benchmark.
  3. OWASP Gen AI Security Project: LLM06:2025 Excessive Agency ›
    Publication date not stated. Reviewed 2026-09-06. Excessive functionality, permissions and autonomy are identified as causes of excessive agency. Page belongs to the 2025 edition; exact publication day is not stated.

Balaji Krishnan

Author of AgenticTransformation. Senior Technical Architect specializing in enterprise AI, cloud CRM modernization, Financial Services Cloud, regulated-industry automation and accountable agentic systems.

About the author ›

Continue exploring

Strategy / v1.0

Enterprise Agentic Transformation Maturity Model

An evidence-led model for assessing whether an organization can delegate work to agents responsibly, operate it reliably, and realize measurable value.

By Balaji Krishnan · Sep 6, 2026 · 7 min read