Protocol InstituteBusiness

Feed · thread · version 1 · updated 27 September 2026

Fat vs Lean: Tempo Management and Organizational Protocols

Session of 17 November 2025. Participants: sachbenny, timber1997, ggnore999, rafa_0x, stevebeans., waveywaves., drevius., ncc1031.

The SIGPfB group convened to discuss how organizations manage the tension between 'fat' (high-entropy organizational surplus with undirected potential) and 'lean' (streamlined, directed efficiency). Rafa introduced the concept that true organizational fat is necessarily disorganized and multidirectional to maintain readiness across diverse, long-term strategic challenges—unlike simple inventory surplus. The group identified that firms serving stable, long-term clients (military, government, institutional investors) have successfully maintained fatness and volatility resistance, while those pursuing lean strategies struggle with rapid environmental change. A critical insight emerged: many organizations lack self-awareness about whether they are actually fat or lean, creating hidden risks.

Key points

  • Organizational 'fat' requires high-entropy disorganization and directionless potentiality to maintain readiness across multiple strategic directions, with high maintenance costs at higher organizational levels.
  • Many organizations are unaware of their actual lean or fat status, creating existential risk; conversely, some may survive despite unintended fat due to client stability.
  • Institutions with stable, long-term clients (military, government, enterprise) successfully maintain fatness, while lean management ideology inadvertently moved these sectors toward vulnerability.
  • Organizational Ontological Primacy may serve as a more measurable protocol than Time to Mediocrity for managing AI-first organizations' trustworthiness tensions.
  • Formal ontologies rarely translate from technical to management levels due to organizational messiness and politics, yet implicit ontologies already exist embedded in protocols like accounting hierarchies and legal structures.

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 4pt890bzhkdr656am70z60s5zh

    Quote line ![[4pt890bzhkdr656am70z60s5zh]]

    Respond to (stub_of) {"origin": "https://protocolsforbusiness.com/blyg/", "id": "4pt890bzhkdr656am70z60s5zh", "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