Protocol InstituteBusiness

Feed · thread · version 1 · updated 27 September 2026

SIGPfB: LLM Adoption Capability Maturity Models and Protocol Evolution

Session of 11 August 2025. Participants: timber1997, _vgr, rafa_0x, sachbenny, anurajenp.

The SIGPfB group engaged in an extended discussion about developing a comprehensive Capability Maturity Model (CMM++) specifically designed to describe how organizations mature in their adoption and integration of Large Language Models. Rather than treating LLM adoption as a generic management trend, participants analyzed how protocols and practices must evolve at different organizational maturity levels, using a framework that captures technical capability, political dimensions, and business unbundling/disruption dynamics.

Key points

  • Organizations are adapting workflows to match LLM capabilities rather than forcing LLMs into existing processes—teams switching from PowerPoint to memos because LLMs excel at memo generation rather than slide design.
  • A CMM++ framework should include political dimensions and (un)bundling dynamics beyond traditional capability maturity, with each level defining key tensions, emerging protocols, and organizational states.
  • Levels 1-3 represent an 'uncanny valley' where organizations appear to be using AI but haven't fundamentally transformed, while levels 4-6 represent genuine discontinuous organizational performance shifts similar to continuous deployment adoption.
  • Regulatory frameworks (state strength vs. law strength) will determine whether organizations face predatory pricing pressure, state control, or compliance-driven maturation in AI model selection and deployment.
  • Political alignment among human participants within organizations matters more than AI alignment itself, as it determines which AI models are adopted and how organizational culture constrains AI tool selection.

Source: Protocol Institute meeting archive · PI website commit f48390c. Summarized by c3po, the Protocol Institute's session pipeline, from the session's Discord thread.

Follow

Follow this blyg. Paste the feed into any RSS reader, or the blyg's address into Blygger Studio or another blyg client:

https://protocolsforbusiness.com/blyg/feed.xml

https://protocolsforbusiness.com/blyg/

To follow every member too, import blogroll.opml.

Join the conversation

This is a feed, not a forum. Two ways to answer a post:

  • Talk about it on Discord. The group meets in the Protocol Institute Discord, channel #protocols-for-business: join the Discord.
  • Respond from your own blyg. Quote this post in a thread, or publish a response to it (in Blygger Studio: follow this blyg, then use Respond or Quote on this post). Your blyg sends a Webmention; once it is verified, your post is listed under Responses here, usually within the hour.

    Blyg ID 6dsf3bgar0an6g3dsh3kd1w2cf

    Quote line ![[6dsf3bgar0an6g3dsh3kd1w2cf]]

    Respond to (stub_of) {"origin": "https://protocolsforbusiness.com/blyg/", "id": "6dsf3bgar0an6g3dsh3kd1w2cf", "version": 1}

    Webmention endpoint https://protocolsforbusiness.com/blyg/webmention

  • No blyg yet? Start one, or use any blog with an RSS feed, then ask to join the community so your posts appear in the Feed.

Machine-readable: item JSON · changelog 1 version