// Topics / Teams

Teams

    The Review Queue Is Your Real Agent Limit Plan agent rollouts like capacity: risk-weighted review demand against effective reviewer-hours. Past the constraint, seats buy inventory, not throughput. ai operations teams Agent Scale Has a Company-Size Gap Large firms report scaling AI agents; smaller ones sit flat. A small company needs one workflow with an owner, gate, boundary, spend cap, and off switch. ai strategy operations The Handoff Tax 80% report personal AI gains while EBIT impact stays flat. The handoff tax: task time down, throughput flat, queues rising at one nameable transition. leadership operations ai Don't Book the Cut Before the Work Disappears Expected AI headcount cuts outran reported ones last year. Let forecasts drive scenarios; book a saving only once the work has observably gone. leadership teams ai The Rung Contract Competency matrices describe skills. Apprenticeship needs a contract per rung: permission, evidence, reviewer, a promotion rule two managers apply alike. leadership teams ai The Junior Developer Cliff Is a Leadership Problem AI eats the work juniors learned on. Rebuild apprenticeship around verification and ownership, or starve your senior bench. leadership ai teams The Diffusion Gap: Why Pilots Don't Become Capability Most AI pilots pass the trial and then die. Closing the gap takes ownership, cadence, and incentives. Write exit criteria as operating changes. ai operations leadership Unsupervised Producing the work can be handed to a machine. Answering for it cannot. What an organization values when machines do most of the making, what people are for, and four things to try this week. opinion ai strategy Leading Senior Engineers in the AI Era: Autonomy, Standards, and Accountability Leading senior engineers on AI features: a written definition of done with an owned eval, a named failure mode, a rollback drill, and a paging threshold. leadership ai teams The Anti-Fragile AI Organization A warm LLM fallback is a standing cost that needs an owner. Price portability per feature, and turn each vendor shock into a capability you keep. teams ai reliability The New Talent Stack: Product, Platform, and Applied AI Must Work as One System AI organizations create leverage when product, platform, and applied AI are designed as one operating system instead of three kingdoms. teams ai platform-engineering The Post-Prototype AI Org: Operating Models That Survive Year Two Canon post — Year-two AI failure usually comes from org-design mismatch, not model-quality mismatch. The handoffs are where the system slows down. ai teams leadership The Operating Cadence: Turning AI Leadership Interfaces Into Predictable Output Canon post — Leadership interfaces decay without rhythm. A weekly metrics review, monthly outcome review, and quarterly architecture audit keep AI ownership real. leadership ai operations Designing the AI Leadership Bench: Roles, Interfaces, and Failure Boundaries Canon post — Scaling AI needs a leadership bench: named owners for product, platform, applied AI, and governance, with failure handoffs rehearsed before incidents. leadership teams ai Hiring for AI Teams: The Operator Profile That Scales The AI hires that scale are operators who handle ambiguity, systems tradeoffs, and verification pressure. Four traits and four interview questions. hiring ai leadership Technical Leadership in the AI Era: Throughput Over Trends Technical leadership in 2026: anchor decisions in throughput, verification, and operability instead of chasing the latest agent framework. leadership ai teams Stop Building Internal AI Tools No One Uses Internal AI tools die quietly when teams optimize for launch over workflow fit, output trust, and post-launch ownership. One tool failed, one stuck. productivity ai leadership Why Most AI Platform Teams Become the New Bottleneck Canon post — AI platform teams become bottlenecks when they centralize decisions instead of capabilities. The warning signs, the metrics that expose it, and the fix. platform-engineering ai teams Build the System the Model Cannot Break Canon post — A manifesto for AI-native organizations: twelve tenets across strategy, architecture, economics, and people, and the one test that matters in year two. opinion ai strategy The CTO Communication Protocol for AI Programs Canon post — AI programs fail when engineers, executives, and investors hear different definitions of success. A communication cadence that keeps one true story. leadership ai executive AI Team Structures 2026: Central, Embedded, and Hybrid Models Central, embedded, or hybrid AI team? How to decide where AI ownership lives, with roles, tradeoffs, platform-to-product ratios, and scaling rules. teams ai architecture AI and Team Productivity: Shared Infrastructure Wins Individual AI speedups are a distraction. The real gains come from treating AI as team infrastructure, embedded in docs, decisions, and onboarding. productivity ai teams Building AI Teams: Ownership and Evaluation Beat Hiring Most AI team failures come from unclear ownership and weak evaluation, not missing talent. Team structures that work, who to hire, and the operating loop. ai teams hiring Restructuring Engineering Orgs After Layoffs Most post-layoff reorgs redraw boxes instead of fixing ownership gaps. What worked in 2023: explicit owners, killing work, and direct communication. leadership teams Leading Engineering Teams Through Uncertainty Early 2023 layoffs and budget cuts brought startup-style uncertainty to every engineering team. What helps: weekly updates, explicit stops, firm standards. leadership teams startups Resilient Engineering Teams Are Boring Teams The engineering teams that got through 2022 best had the least drama: no heroics, no single points of failure, sane on-call, and bad news raised early. teams leadership reliability Tech Layoffs 2022: What I Saw From the Inside What I saw during the 2022 tech layoff wave, and what helps engineering teams survive contraction without burning out. leadership teams hiring Engineering Documentation: Owners, Doc Types, Docs as Code Engineering docs get ignored because nobody can find them, trust them, or tell what they are for. Owners, separate doc types, and docs as code fix it. engineering developer-experience teams Engineering Onboarding: Ship a Real PR by Day Three Most engineering onboarding wastes the first week on access requests and context overload. The fix is simple: ship a real PR by day three. hiring leadership teams SRE Team Structures: Stop Renaming Your Ops Team Centralized, embedded, or platform SRE: how each model fails, the engagement tiers and entry criteria I use, and why renaming ops to SRE changes nothing. reliability teams leadership Most 'Technical Debt' Is Just Decisions You Disagree With Now Most 'technical debt' is code that aged, not debt. How to spot real debt by its costs (incidents, delivery, security, hiring) and get fixes funded. technical-debt leadership architecture Remote Work for Engineering Teams: Benefits and Dangers Years of running distributed engineering teams: what remote work gives you, where it hurts (isolation, blurred boundaries, eroding trust), and what works. remote-work leadership teams Hybrid Work for Engineering Teams Is Harder Than Full Remote Hybrid engineering teams drift into a two-tier system unless you run them remote-first: written decisions, async defaults, outcome-based reviews. remote-work teams leadership Distributed Engineering Teams: What Works Six Months In Remote-first since before COVID, I watched everyone else scramble. What works for distributed engineering teams six months in, and what still doesn't. remote-work teams engineering Remote Overnight: The First Two Weeks for Engineering Teams COVID sent engineering teams home overnight. What matters in the first two weeks: working access, decent hardware, three enforced norms, and new hires. remote-work engineering teams Engineering Onboarding: First PR on Day One Most engineering onboarding is a polite abandonment ritual. What I've learned across startups about getting new engineers shipping fast. hiring engineering teams Scaling Engineering Teams: What Breaks at 10, 25, and 50 How engineering teams change as they grow: what breaks at each size, explicit ownership, written decisions, and process that follows pain. engineering leadership teams Code Reviews: Fixing Rubber Stamps and Nitpick Wars Most code reviews are theater. How we fixed ours at a fintech startup: review for risk, label comments, small PRs with a template, and same-day turnaround. engineering teams Building a Platform Team: Lessons from Our First Year Standing up a small platform team at a fintech startup: tight scope, infrastructure run as a product, paved roads over mandates, and what I'd change. platform-engineering teams engineering Async-First Engineering Teams: Cutting Decision Latency How our fintech team cut meetings and decision latency across time zones: written decisions, response-time rules, and calls only when they earn it. remote-work leadership teams Code Review Quality: Stop Counting Reviews, Start Reading Most code reviews are rubber stamps. What made ours useful at a fintech startup: read the change, skip style nits, label comments, small PRs, automation. engineering testing teams Security Champions: Startup Security Without a Security Team No budget for a security team? Turn one motivated engineer per team into a security champion. How we run it at an eight-engineer fintech startup. security startups engineering Building a Startup Engineering Team: Lessons from 2016 What growing an engineering team at a mobility startup in 2016 taught me about hiring, trust, and the habits that actually matter. teams engineering leadership Building a Security-First Engineering Culture Security culture is habits leadership enforces: no secrets in code, a security question on every PR, least privilege, patch deadlines, and champions. security engineering teams Building a DevOps Culture from Scratch Hiring a DevOps engineer won't end the dev vs ops fight. Put developers on the pager, pilot with one team, and fix incentives before tools. devops teams engineering