Team & Org Use of Claude

What We’re Tracking #

How teams and organisations adopt Claude collectively — shared CLAUDE.md conventions, hooks and skills at team scale, enterprise deployment patterns, coordination norms, productivity measurement, and multi-person workflow case studies. Focus is on org-level patterns and friction rather than individual technique (see claude-expertise for that).

Config: journals/topics/config/claude-teams.yaml

Index #

• 2026-06-26 — Gather
• 2026-06-19 — Gather
• 2026-06-11 — Initial Gather

2026-06-26 — Gather #

Enterprise Rollout: Dynamic Workflows and Deployment Playbooks #

• Claude Code Enterprise Rollout Playbook for 50+ Developers (systemprompt.io, 2026) — Practitioner playbook for deploying Claude Code across >50 engineers: centrally managed settings developers cannot override, least-privilege permissions, hooks as audit trail of every session, phased onboarding, and an org-level CLAUDE.md template that teams extend but cannot strip. Covers SSO, RBAC, and integrating session logs with SIEM. The first structured org-scale rollout guide to address the governance infrastructure requirements in detail.
• Enterprise AI coding agent deployment in 2026 (Northflank, 2026) — Northflank’s guide to moving AI coding agents from pilot to production: sandbox isolation via microVM (BYOC inside enterprise AWS VPC), RBAC on agent environment provisioning, audit log export to SIEM, and the argument that identity/logging/code-review/incident controls must be in place from day one. Uses Claude Code as the primary example; Northflank’s infrastructure-provider perspective gives the most concrete production-environment guidance available.
• Claude Code’s Dynamic Workflows Take on the Tasks That Were Too Big to Automate (DevOps.com, 2026) — DevOps framing of Dynamic Workflows (on by default for Team and Enterprise): removes the adoption barrier for tasks too large for a single agentic session. Monorepo-scale migrations, cross-cutting security audits, and large-scale bug investigations previously required manual orchestration scripts; Dynamic Workflows generates the orchestration harness automatically. Teams no longer need to maintain pipeline code for task classes that exceed single-session context.

Productivity Measurement: New Metrics for AI-Assisted Teams #

• AI Coding Productivity: 2026 Benchmarks Show Real Impact (byteiota.com, 2026) — Elite teams see 80%+ weekly active AI usage, 60–75% AI-assisted code share, and sub-8-hour PR cycle times — achieving 1.8–2.0x productivity multipliers. But teams exceeding 40% AI code share face 20–25% rework rate increases (7 hours lost per person per week). Code turnover ratio (code reverted or rewritten within 30–90 days) is identified as the critical quality metric for AI-assisted development — traditional metrics (PRs, LOC, commits) inflate without this correction.
• 7 AI-Era Developer Productivity Metrics That Work in 2026 (Exceeds.ai, 2026) — Seven AI-native metrics: adoption rate, AI code share, complexity-adjusted velocity, code quality delta, review time, rework rate, and cost/ROI. Requires repository-level diff analysis rather than metadata. The argument: traditional metrics are actively misleading in AI-assisted environments because they inflate volume without proportionally increasing value — a direct application to the 80%/81% divergence (Anthropic internal vs. enterprise production failures) tracked June 11.

Author Watch: Gergely Orosz #

• Pragmatic Engineer Summit 2026 — AI adoption findings (Frances Coronel, 2026) — Attendee notes from Orosz’s summit: AI adoption is 90%+ among engineering teams, but real organisational impact is still hard. High usage does not equal transformation. Teams making measurable progress invest in enablement, developer experience, and change management — they treat AI as infrastructure requiring intentional configuration, not assistants that just need to be handed to engineers.

Cross-links #

• [claude-expertise] The CLAUDE.md as team policy document (systemprompt.io) is the same principle as Anthropic’s steering guide (June 26 entry) — the difference is who controls it: individual vs. centrally governed.
• [claude-integrations] Dynamic Workflows (Team/Enterprise default) and the 28 Compliance API integrations are both structural infrastructure — teams adopting Claude Code get Dynamic Workflows automatically; security teams get Compliance API integration through their existing vendors.

Synthesis #

The enterprise Claude Code deployment pattern is crystallising around three components: (1) a centrally governed CLAUDE.md template that individual team members can extend but not override; (2) hooks as the deterministic audit layer above Claude’s non-deterministic outputs; (3) Dynamic Workflows for task classes that exceed single-session scale. The productivity measurement gap remains the open problem: the byteiota.com data (40%+ AI code share → 20–25% rework increase) suggests the productivity multiplier is real at the task level but offset by quality debt at the system level. Code turnover ratio is the metric that makes the offset visible.

Meta-observations #

• Emerging theme: “Hooks as audit trail” appears independently in the systemprompt.io and Northflank guides — both practitioners converging on hooks not as automation but as governance. Hooks that log every session interaction are the enterprise’s primary mechanism for post-hoc review of what Claude did, distinct from what the Compliance API captures (content events).
• Author to watch: Frances Coronel (Pragmatic Engineer Summit attendee reporter) — provides a consistent outside perspective on Orosz’s findings without the paywall.

2026-06-19 — Gather #

Skills as Team Infrastructure #

• Claude Skills Are Replacing Prompts in Enterprise AI Workflows (Memeburn, 2026) — Enterprise teams are moving from prompt experimentation to skills that encode company-specific standards: nine distinct skill categories now in common use (CI/CD, security, refactoring, code review, testing, documentation, data analysis, design, deployment). The key finding: “The most successful companies aren’t the ones that prompt the best; they are the ones that encode their internal standards most clearly.” Skills are the operationalisation of the CLAUDE.md authoring pattern at team scale — instead of a project-level CLAUDE.md, teams share skill files that encode process and style across all projects.
• Claude Enterprise Guide 2026: Deployment & Training Specs (IntuitionLabs, 2026) — Enterprise platform maturation: by 2026, Claude Enterprise has shifted from “niche enterprise chatbot” to “central AI platform” for global organisations. The shift from 2024–2025’s “chat-first experimentation” to “permanent repeatable infrastructure” is the key adoption pattern. Teams are encoding internal standards in skills rather than re-prompting each session.

Author Watch: Gergely Orosz #

• Building OpenCode with Dax Raad (Pragmatic Engineer) — Orosz covers Dax Raad building OpenCode, an open-source Claude Code alternative using MCP as its core protocol. Relevant to claude-teams because OpenCode’s open-source nature makes team-level customisation and self-hosting viable for organisations with data governance constraints that prevent use of Anthropic’s hosted CLI.
• Pragmatic Summit 2026 (February): Orosz’s summit headline finding — 92% of developers using AI tools monthly, but “experienced engineers are finishers”: the distinctive value of senior engineers is not writing code but knowing when to override, reject, or redirect AI-generated output. This reframes team composition: the premium is on engineers who can supervise AI reliably, not those who can generate the most code.

Governed AI at Scale #

• Snowflake and Anthropic Accelerate Enterprise AI Adoption Driven by Rising Demand for Governed AI (Snowflake / BusinessWire, 2026-06-01) — The Snowflake-Anthropic partnership expansion frames the enterprise demand explicitly: “rising demand for governed AI” is the market driver. Governed AI = AI that can operate on enterprise data while maintaining security, governance, and compliance controls. This is the enterprise team’s core requirement: not the most capable model, but the most auditable deployment.

Synthesis #

The coordination infrastructure for enterprise teams is maturing in parallel with the governance pressure. Skills are the encoding mechanism (team standards → reusable files); Compliance API is the audit mechanism (usage data → security tools); “governed AI” is the product positioning (capability + auditability). The pattern from the initial gather holds: access is solved (Team plan universally available); the open problem is coordination. What’s new this cycle is that the market is now offering infrastructure answers to that problem — skills libraries, compliance APIs, governed data platforms — rather than just naming the gap.

Cross-links #

• [claude-expertise] Skills infrastructure at team scale is built on the same CLAUDE.md/hooks/skills primitives tracked in claude-expertise; the difference is shared authorship and governance.
• [claude-integrations] Snowflake-Anthropic “governed AI” positioning and Claude Compliance API vendor ecosystem are the integration layer that enterprise teams are adopting for oversight.

Meta-observations #

• Emerging theme: “Skills replacing prompts” is the team-scale equivalent of the individual-level “agentic engineering replacing vibe coding” shift. Both represent the same move: from ad-hoc natural language to encoded, repeatable standards. The language used at the team level (“encode your internal standards”) maps directly to the individual-level Karpathy vocabulary (“don’t tell it what to do, give it success criteria”).
• Author to watch: Dax Raad — building OpenCode as an open-source, MCP-native Claude Code alternative. His design decisions will reveal what the community considers missing from the official CLI; worth monitoring for team deployment patterns.

2026-06-11 — Initial Gather #

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.

Cross-links #

• [claude-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] The five friction-reduction patterns apply at team scale to any AI coding workflow, not just Claude.
• [vibe-coding-applications] 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.

Strategy Changelog #