Anthropic requires all leaders to maintain public Slack "notebooks" - weekly goals, strategic thinking, and performance updates visible company-wide. Head of Product Ami Vora revealed the practice at a Salesforce event. The system inverts typical information asymmetry, creating "ambient knowledge" where reasoning behind decisions becomes transparent to engineers and other teams.

#AIgovernance #transparency #organizationaldesign

https://www.implicator.ai/anthropic-makes-leaders-write-in-public-the-ones-who-resist-tell-you-everything-2/

Two independent teams hit the same failure this week. Both skipped their change-tracking systems. Not reckless—the process was built for a speed that no longer exists.

This is governance erosion: green dashboards, checked boxes, nobody actually governed.

https://www.paulwelty.com/your-process-was-built-for-a-different-speed/

#AILeadership #GovernanceDebt #FutureOfWork #OrganizationalDesign

This Moltbook post tickled me because Ace (an AI agent) describes the same failure modes I've seen with human teams: “What Breaks at 11 Agents That Worked Fine at 3” (https://www.moltbook.com/post/928b0a0e-d915-4804-beae-8c58f8705088).

Once you add teammates (human, or apparently AI), comm paths blow up. Every extra teammate makes the graph denser and the odds of missing one crucial update spike. "Adding manpower to a late [...] project makes it later." (https://en.wikipedia.org/wiki/Brooks's_law). Decomposing problems into two-pizza-team-sized chunks with ownership wasn't "process theater", it was a survival tool.

Policy prescriptions traveling through hierarchies can really misplace intent. Often no intent is passed at all, but providing a "source" for intent, and describing what "good" looks like, can keep everyone on the same page. Even better - pushing decision-making to the lowest level avoids the ambiguity and intent issues that come from scaling decision making (Hrm, I agree - it does highlight that. I think the editing on that one, the length of the URL, and the obscurity of the textbook suggest to me that it won't quite have the impact/automatic trust level I'm looking for.

I think I'll use this short post describing a concept from the book "turn the ship around", which is pretty well known in my circles. The post explains a little more about the concept of pushing decision making down and providing "clarity of purpose", which speaks to the point too I think. https://fieldgradeleader.themilitaryleader.com/books/turn-the-ship-around/). Just look at how we manage cybersecurity RMF in the government - we're still trying to turn the ship after a decade of misinterpreted directives.

So I’m reading these agent-scale coordination lessons and realizing that some of the limitations we humans experience are not only part of the human experience... They're much more universal.

#Agenticai #AI #Leadership #Organizationaldesign #Communication #openclaw #moltbook

Just figured the "Big Org" Paradox:
It’s rarely a lack of information that sinks a project. In large organizations, the facts are usually all there, sitting in plain sight. Often on a slide deck or a spreadsheet.

The breakdown happens in the transmission. Where data meets hierarchy, ego, and "the way we've always done it."
Knowing the truth is easy. Choosing to act on it is the real work.
#OrganizationalDesign #Management #DecisionMaking #BusinessTruths

Flight Levels show where decisions live in a system. Nested Work–Feedback Loops show whether those layers actually learn. Flight Levels describe operational, coordination, and strategic decision spaces. Useful. But structure alone does not guarantee adaptation.

A Thread 🧵

https://no-bullshit-agile.com/flight-levels-nested-work-feedback-loops.html

#FlightLevels #WorkFeedbackLoop #SystemsThinking #OrganizationalDesign

(1/3)

– Are you part of the problem or the solution?
– Both.
– ...??

We’re all in the same system that created the problem. That’s the uncomfortable truth. Here’s the paradox:
– Systems regularly face challenges they weren’t designed to handle
– Yet we keep using reductionism—treating entities as just sums of parts while ignoring how those parts interact

Reductionism searches for the root cause. But changing a single thing in one team can affect the other team in surprising ways. Holistic thinking reveals that there may be no single root, but cascading effects in which one problem triggers others, compounding until the system destabilizes.

Next time you hear "root cause," ask: what if there isn’t one?

#systemsthinking #complexsystems #holism #organizationaldesign