↓Skip to main content
Zeitgeist — a spike by Chris Gathercole
  1. Topics/
  2. Team & Org Use of Claude/

Initial Gather — 11 June 2026

Anthropic’s Internal Playbook — 80% of Production Code Now Claude-Authored #

  • How Anthropic teams use Claude Code (Anthropic, 2026-06) — Anthropic published its internal usage report profiling 10 teams across engineering and non-engineering functions. Key metrics: Security Engineering 3× faster incident diagnosis (15 min → 5 min); Inference Team 80% reduction in documentation research time; Data Infrastructure saved 20 minutes per production outage via screenshot-to-diagnosis. More than 80% of the code merged into Anthropic’s production codebase in May was authored by Claude, not humans. Non-engineering patterns cluster into four: bulk document processing, ad hoc data analysis, workflow automation, and small internal tooling. Legal built phone tree systems; Marketing generated hundreds of ad variations in minutes; Data Scientists built complex visualisations without knowing JavaScript. Anthropic’s framing: “agentic coding isn’t just accelerating traditional development — it’s dissolving the boundary between technical and non-technical work.”
  • Anthropic says 80% of its new production code is now authored by Claude (VentureBeat, 2026-06) — VentureBeat’s enterprise angle on the same data: what Anthropic’s internal adoption curve means for enterprises trying to replicate it. The gap between Anthropic’s 80% and the average enterprise (where AI assists in writing 61% of code but 81% report production failures) frames the central enterprise challenge as governance and measurement, not access.
  • How Claude Code is built (Pragmatic Engineer, 2026) — Gergely Orosz’s inside look at how the Claude Code team itself operates: 90% of Claude Code’s own code is written by Claude; engineers run ~5 PRs per day; PR output per engineer increased 67% while the team doubled. The Claude Code team as a case study of what “AI-native engineering” looks like in practice — not gradual adoption but a full restructuring of the development loop around AI.

Team-Level Friction Patterns — Martin Fowler’s Five-Pattern Framework #

  • Patterns for Reducing Friction in AI-Assisted Development (MartinFowler.com, 2026-02) — Martin Fowler’s five-pattern framework for team-level AI-assisted development, published February 2026. The five patterns: Knowledge Priming (share curated project context before requesting code, functioning as manual RAG), Design-First Collaboration (progress through capability/component/interaction/contract levels before implementation), Encoding Team Standards (treat AI instructions as versioned, reviewed, shared artefacts), Context Anchoring (maintain a living doc capturing decisions and constraints across sessions), Feedback Flywheel (systematically capture effective prompts to improve the other four patterns). Critical scope note: the patterns yield returns primarily for non-trivial work spanning multiple sessions or involving team coordination — simple one-off tasks don’t justify the overhead. Encoding Team Standards is the pattern most directly relevant to CLAUDE.md authoring: it reframes CLAUDE.md from personal config to team-maintained knowledge artefact.

Enterprise Governance Gap — Production Failures at Scale #

  • The 2026 State of Code Abundance Report (CloudBees, 2026-05) — CloudBees surveyed 200+ enterprise technology leaders. Key finding: 81% report an increase in production issues tied to AI-generated code, despite organisations self-scoring 83.6/100 on AI readiness. AI now writes or assists in 61% of the average enterprise codebase, yet most organisations lack governance infrastructure to manage it. “Code Abundance” — code generated faster than it can be tested, governed, and attributed — is the coined term for the structural problem. Traditional developer metrics (PRs/week, LOC, commits) are actively misleading in 2026 because AI-assisted workflows inflate volume without proportionally increasing value. The 5-dimension measurement framework: adoption, AI code share, complexity-adjusted velocity, code quality, and ROI — measuring adoption alone is measuring the wrong thing.

Claude Cowork — AI Desktop Agent for Team Project Automation #

  • Use Claude Cowork on Team and Enterprise plans (Anthropic Support, 2026) — Claude Cowork is a new Anthropic product in research preview for Pro, Team, and Enterprise plans. It’s an AI desktop agent that connects to project management tools (Teamwork.com, Microsoft Teams, others via MCP) to read, analyse, and act on live project data — turning Claude from a generic chatbot into a coworker that understands current projects, tasks, and timelines. Critical current limitation: Cowork Projects are local to your computer. Colleagues cannot access your projects or outputs. The four-product Anthropic stack now reads: Claude AI (thinking), Claude Code (building), Claude Cowork (automating), Claude Team (collaborating). The local-only constraint makes Cowork an individual productivity tool in research preview, not yet a team coordination layer — but the trajectory toward shared project state is evident.

Team Plan Democratisation — Claude Code Now Universal #

  • Use Claude Code with your Team or Enterprise plan (Anthropic Support, 2026) — As of January 2026, Claude Code is included with every standard Team plan seat at no extra cost (minimum 5 users). Previously, organisations limited premium Claude Code seats to senior engineers or specific roles. The democratisation removes a structural barrier to team-wide adoption but creates the governance challenge: when every engineer has Claude Code, coordination on shared CLAUDE.md conventions, prompt libraries, and coding standards becomes a team responsibility. GitHub issue #14467 tracks the unimplemented feature request for org-wide shared CLAUDE.md (similar to .github community health files), suggesting the tooling for team-level config sharing is still ahead of the adoption curve.
  • Claude-Specific Expertise Martin Fowler’s “Encoding Team Standards” directly maps to CLAUDE.md authoring practice — team-maintained vs. individual config is an unresolved question.
  • Vibe Coding Approaches The five friction-reduction patterns apply at team scale to any AI coding workflow, not just Claude.
  • Applications of Vibe Coding The 80% Anthropic production code figure and the CloudBees “code abundance” governance gap are two sides of the same enterprise adoption story.
  • Claude Integrations Claude Cowork’s MCP-based project tool connections (Teamwork.com, Microsoft Teams) are integration stories as much as team workflow stories.

Meta-observations #

  • Emerging theme: The central team-level tension is not access but governance — adoption is easy, coordination and measurement are hard.
  • Emerging pattern: Anthropic’s own teams are the clearest case study for what AI-native engineering looks like at scale; the 80% production code figure is a landmark that will anchor future enterprise comparisons.
  • Keyword suggestion: Add "CLAUDE.md" team conventions and "claude cowork" workflow to search keywords.
  • Author to watch: Gergely Orosz is covering the Claude Code team’s internal practices with direct access — high signal.
  • Gap: No coverage yet on measurement tooling for AI-assisted team workflows (beyond the CloudBees governance framing). Worth tracking.

Synthesis #

The inaugural gather for this topic arrives at a moment of structural transition: the access problem is solved (Claude Code is now universal on Team plans, Cowork is in research preview) but the coordination problem is just beginning. Anthropic’s own 80% production code figure is simultaneously a success story and a warning — it was achieved by a highly cohesive, AI-native team with deep internal alignment, not by rolling out a tool to a conventional engineering organisation.

The CloudBees data makes the gap explicit: 61% of enterprise code is AI-assisted, yet 81% of enterprise leaders report production failures from that code. The missing layer is not capability but institutional practice — shared standards, measurement frameworks, and governance infrastructure that most organisations haven’t built yet. Martin Fowler’s five-pattern framework names the pieces (Knowledge Priming, Encoding Team Standards, Context Anchoring, Feedback Flywheel, Design-First Collaboration), but all five require team-level discipline to sustain, not just individual adoption.

Claude Cowork is the most interesting leading indicator: it promises to connect Claude to live project state (the “coworker that understands your projects” framing), but its current local-only limitation means it’s still an individual tool. When Cowork gains shared-project state — the logical next step — the team coordination layer will exist natively in the Anthropic product stack. The unimplemented org-wide CLAUDE.md feature request (GitHub issue #14467) is the same gap expressed at the configuration layer. Both point to the same structural need: a shared context layer that makes team-wide Claude adoption coherent rather than a set of independent individual workflows.