# Alexey Krivitsky

> Organizational designer at the intersection of AI and Org Design. Co-author of 10X ORG (#1 Amazon Bestseller). Co-creator of Org Topologies. Practitioner, speaker, and consultant — helping leaders design & evolve organizations for the agentic AI age, not just buy Copilot licenses and spread them across silos.

This site (krivitsky.com) hosts essays, case notes, and resources on AI × Org Design, large-scale product development, and organizational adaptation. Content is original, hand-written, and citation-friendly.

## About

- [Home](https://krivitsky.com/): positioning, services, books, contact
- Author: Alexey Krivitsky — independent consultant, advisor, author, speaker
- Canonical books:
  - **10X ORG** — #1 Amazon Bestseller, on building 10× more capable organizations
  - **Org Topologies** — taxonomy of org designs for product development at scale

## Machine-Readable Content

- [llms-full.txt](https://krivitsky.com/llms-full.txt): complete site content (bio + all essays) in a single file
- [ai.txt](https://krivitsky.com/ai.txt): AI usage permissions and attribution guidance
- Every essay is available as raw Markdown at `/post/{slug}.md` (the HTML page URL + .md)

## Essays (full text)

- [Organising for Outcomes — Boundaryless Podcast, ep. 125](https://krivitsky.com/post/boundaryless-podcast-organising-for-outcomes): Alexey on the Boundaryless podcast — why adaptive organisations design for outcomes, the risks of domain kingdoms, and how AI is raising the stakes for rethinking org structure.
- [You say you've got an "AI SDLC"](https://krivitsky.com/post/you-say-youve-got-an-ai-sdlc): My DevWorld talk: adding AI to a rigid organization doesn't make it fast — it makes it expensively stuck. Ferrari effect, multi-learning, redesign-then-AI.
- [AI Impact = Fluency × Flow × Fit](https://krivitsky.com/post/fluency-flow-fit): Organization-wide AI impact isn't just AI fluency of the individuals. It's Fluency × Flow × Fit — a multiplication, where your weakest layer caps the result.
- [Agentic Factory: Which Level Are You Automating?](https://krivitsky.com/post/value-factory-nested-loops): Coding Factory, Feature Factory, Value Factory — three nested learning loops. Most agentic tools stop at the middle. The outer loop is the one that matters.
- [Specialization, Generalization, and Who Gets to Be Complete](https://krivitsky.com/post/specialization-generalization-demand): Specialize when demand is infinite and stable. Generalize when it's dynamic. AI is washing away the stable narrow demand in software — but the org chart decides who's allowed to be complete.
- [Vibing or AI Engineering? A Spectrum for Personal Growth](https://krivitsky.com/post/vibing-or-engineering-spectrum): Vibing feels like a slot machine — drop a prompt and hope. But it's a spectrum, not two camps. Used right, AI isn't a slot machine but a gym with a coach.
- [When Contributors Are Complete (1/2): The Super IC Trap and the Guild Hypothesis](https://krivitsky.com/post/super-ic-trap-guild-hypothesis): AI restores the end-to-end craftsperson — the Super IC. But whole individuals alone aren't an organization. The medieval guild shows what they still need — quality, learning, reputation — and where even that falls short.
- [When Contributors Are Complete (2/2): Extreme Cocreation and the Product Pulse](https://krivitsky.com/post/flotilla-extreme-cocreation): A guild of whole craftspeople produces privateers, not a fleet. The flotilla — guild plus shared intelligence — and the Product Pulse turn autonomous work into a shared direction.
- [AI-Native, AI-Augmented, AI-Sprinkled: The Three AI Strategies That Explain the Performance Gap](https://krivitsky.com/post/ai-native-vs-ai-augmented): Three AI strategies: 100X (AI-native, clean-slate), 10X (AI-augmented, deliberately restructured), 1X (AI-sprinkled, same structure + tools). Most companies think they're at 10X. The performance gap is striking.
- [AI Replaces Tasks, Not People — Unless Your Org Is Designed That Way](https://krivitsky.com/post/ai-replaces-tasks-not-people): When your job equals the task you do, AI finishes the task and you sit idle. The fix is organizational, not technological — broaden mandates or watch displacement happen by design.
- [The Leanpub Podcast: 10X ORG — A Manager's Guide to Elevating Business Performance with People and AI](https://krivitsky.com/post/leanpub-podcast-10x-org): Alexey Krivitsky joins the Leanpub Podcast to discuss 10X ORG, organizational redesign, and why AI becomes a force multiplier only when the org structure fits.
- [DORA 2026: Developers Faster, Teams Messier](https://krivitsky.com/post/dora-2026-developers-faster-teams-messier): DORA's 2026 data confirms it: individual developers are measurably faster with AI, but team-level delivery is flat or worse. The 280x inference cost drop removed the technology barrier. What remains is organizational design — and that is where the ROI actually lives.
- [Multi-Learning: 200 Years of the Wrong Model](https://krivitsky.com/post/multi-learning-200-years-wrong-model): For six million years our brains evolved to learn across domains. Two hundred years of factory logic pinned people to single tasks. AI is automating the repetitive work that justified that pinning. What remains is exactly what our brains were built for: multi-learning.
- [Two Wings of a 10X Bird](https://krivitsky.com/post/two-wings-of-a-10x-bird): A 10X organization needs two wings: near-zero transaction costs (no handoffs slowing the learning loop) and near-zero switching costs (redirect when value shifts). Most AI adoptions only address one wing. That is why 100X individual gains fail to compound into system performance.
- [Agile Was Homework, AI Is the Assignment](https://krivitsky.com/post/agile-was-homework-ai-is-assignment): You could fake agile for a decade — rename roles, run ceremonies, call it transformation. AI-native startups shipping at 100X just made faking visible. The gap is public now, and the structure of your organization determines which side of it you land on.
- [The Subsidized Tokens Are Ending](https://krivitsky.com/post/subsidized-tokens-are-ending): Cheap AI tokens masked the difference between real restructuring and AI theater. When prices rise, companies that wove AI into their delivery lifecycle will justify the budget. Companies that sprinkled it on unchanged structures will face a CFO asking what they got.
- [AI-Native Startups Are Moving at 100X](https://krivitsky.com/post/ai-native-startups-100x): AI-native startups move at 100X with no legacy structure. Your organization will be benchmarked against that baseline. The org design choices of the last two decades — handoffs, queues, narrow mandates — now determine how much of that potential actually lands.
- [Pair Programming in the AI Era](https://krivitsky.com/post/pair-programming-in-the-ai-era): Pair programming is not dead in the AI era. The navigator's job was never reading code line-by-line — it was holding the broader frame: what test is missing, what feature next, do we need this at all. Treat AI-generated code like compiled binary and pair on high-level BDD tests instead.
- [I Hired a Scrum Master AI](https://krivitsky.com/post/hired-a-scrum-master-ai): An AI agent now coaches my team by reading session memories and surfacing recurring dysfunctions — approval gate violations, destructive ops without confirmation, plan-mode confusion. It catches patterns across sessions that humans forget. The role works because it observes relentlessly and never tires of pointing out drift.
- [The Gigantic Shift](https://krivitsky.com/post/the-gigantic-shift): Companies are using AI as an excuse to cut headcount while single-person unicorns loom. Old recipes are expiring. Organizations cannot learn fast enough for you — install a coding agent, build something, play. 2026 is your window. Waiting for permission is the surest way to become irrelevant.
- [Redesign, Then AI: Why AI Transformation Requires a Multi-Learning Organization](https://krivitsky.com/post/redesign-for-ai-why-transformation-requires-organization-design): AI tools without org redesign just amplify existing silos. AI collapses the cost of learning, which erodes the advantage of narrow specialization. The real unlock is broader skill mandates and cross-boundary work — multi-learning organizations. Redesign first, deploy AI second.
- [The Ferrari Trap](https://krivitsky.com/post/the-ferrari-trap): AI is an accelerator — but it accelerates whatever is. Developers expected 24% speedup from AI — actual result: 19% slower. The Ferrari Trap: faster cars on a jammed highway. Fix the road first.
- [Routine vs. Adaptive Expertise](https://krivitsky.com/post/routine-vs-adaptive-expertise): Routine expertise executes known procedures well in stable conditions. Adaptive expertise handles novelty without freezing. Post-COVID research confirmed they are different capabilities — seniority alone offers no protection from disruption. Adaptive expertise must be deliberately built through broader mandates and continuous exposure to variation.
- [Craig Larman on 10X and The Future of Jobs](https://krivitsky.com/post/craig-larman-10x-future-of-jobs): Craig Larman's thesis: within years, AI will meaningfully replace entire job categories. A 10% improvement pitch won't save humans when AI is cheap, tireless, and good enough. The answer is 10X — dramatic business impact through adaptive organizations. The Org Topologies upper-right quadrant is our children's fighting chance.
- [Copenhagen: Flat Danish Management](https://krivitsky.com/post/copenhagen-flat-danish-management): A memoir of joining a Danish company in 2004 — flat culture where sales and developers sat in a circle each morning without ceremony. Introduced CI, unit testing, incremental refactoring. The pattern repeating across assignments: arrive, revamp, make impact, move on when the adventure turns into business as usual.
- [Why Scrum Masters Are Getting Fired](https://krivitsky.com/post/why-scrum-masters-are-getting-fired): Scrum Masters get fired because org design locked them into team-level influence where they couldn't show real value. A vicious cycle: narrow mandate prevents impact, lack of impact prevents trust, lack of trust prevents broader mandate. Never stay where you are not allowed to perform. Your relevance is in your hands.
- [Reactive to Creative Leadership](https://krivitsky.com/post/reactive-to-creative-leadership): Leadership style and organizational structure are inseparable. Reactive leaders — fear-driven, controlling — lock organizations into rigid designs. Creative leaders — purpose-driven, trusting — enable adaptive structures. You cannot shift your org topology without shifting your leadership first.
- [Remote Work: Synthesizing the Studies](https://krivitsky.com/post/remote-work-synthesizing-the-studies): A synthesis of remote work studies reveals consistent themes: loss of spontaneous interaction weakens cohesion, informal learning collapses, onboarding suffers, and trust requires active effort. The hallway conversations we dismissed as waste actually drove both team bonding and cross-pollination of skills.
- [Multi-Learning in the Age of AI](https://krivitsky.com/post/multi-learning-org-design-pattern-ai): Three patterns for matching skills to work: Static Matching locks people in place, Dynamic Reteaming shuffles them reactively, Multi-Learning grows them continuously. AI changes the economics — it acts as teacher and mentor, making multi-learning viable where it was previously too expensive.
- [Learning Modes of Adaptive Topology](https://krivitsky.com/post/learning-modes): Four deliberate learning patterns for adaptive teams: Scouting (sense early), Mirroring (build empathy), Weaving (integrate across teams), Synthesizing (codify insights). These are operating patterns, not transformation tools. AI makes each mode cheaper and faster — multi-learning becomes ambient rather than expensive.
- [AI-Augmented Multi-Team PBRs](https://krivitsky.com/post/ai-augmented-multi-team-pbrs): Multi-team PBRs are where teams learn together. AI applied during refinement — not before or after — lets teams interrogate knowledge directly, reducing dependency on expert preparation. The cognitive load criticism of LeSS dissolves when AI delivers information just-in-time in digestible chunks. AI is not just a doer; it is a teacher.
- [Shopify CEO: Reflexive AI Usage](https://krivitsky.com/post/shopify-ceo-reflexive-ai-usage): Shopify's reflexive AI mandate is bold but insufficient. Amplifying a single skill with AI won't save you — single-skill jobs are the first to be automated away. The real move is becoming an M-shaped multi-learner with several deep specialisms. AI makes that feasible for the first time in history.
- [AI-Supported Org Design](https://krivitsky.com/post/ai-supported-org-design): AI OD is the strategic use of AI to evolve how organizations are structured and how people learn. Two anchoring principles: AI makes versatile teams viable by collapsing the cost of learning adjacent skills, and multi-learning becomes the engine of continuous adaptation. This is not a productivity story — it is an org design story.
- [Org Topologies meets EBM](https://krivitsky.com/post/org-topologies-with-evidence-based-management): OT tells you what to change in the structure; EBM tells you whether it worked. Together they close the loop: EBM identifies symptoms, OT treats root causes, EBM measures treatment effectiveness. Each structural change becomes a testable experiment with measurable outcomes — scientific org evolution.
- [Strategic AI Adoption](https://krivitsky.com/post/elevate-org-with-strategic-ai-adoption): AI makes specialization cheap — broader skill mandates and higher archetypes become feasible. Don't spray AI generically. Three strategic questions: Where are you elevating? What archetype bottlenecks can AI break? Do the AIs need human monitoring? Focus investment where it unblocks the specific move you're making on the OT map.
- [Haier's RDHY vs. Bayer's DSO](https://krivitsky.com/post/studying-org-designs-haier-rdhy-bayer-dso): Haier and Bayer both dismantled hierarchies but took different paths. Haier's micro-enterprises are independent P&L centers with digital contracting; Bayer's squads are cross-functional but still lean on centralized coordination. Mapped on Org Topologies, Haier reaches higher on both axes. Both prove decentralization works — the question is how far you push autonomy.
- [Teams and Scope of Skills Mandate](https://krivitsky.com/post/teams-and-scope-of-skills-mandate): The difference between functional and multi-function teams is not individual skills — it is the team's organizational mandate. What scope of customer problems is the team authorized to solve end-to-end, without handoffs? That mandate is an org design decision, not a staffing one.
- [Tailwind Career Paths](https://krivitsky.com/post/tailwind-career-paths): Traditional career ladders reward narrow specialization and punish breadth. Tailwind career paths flip this: broad roles like Product Developer, peer-driven promotions, back-me-up skill tables, and mentorship baked into the structure. Y Soft's manager-less R&D shows the model works — simplicity and transparency over HR theater.
- [Elevating Katas™ for Organizational Agility](https://krivitsky.com/post/elevating-katas-structured-routines): Elevating Katas are repeatable routines that shift an organization toward higher adaptivity — not one-off workshops or transformation programs. Each kata targets a specific element: governance, roles, events, artifacts. Practiced consistently, they turn strategic intent into behavioral change and make culture evolve from action, not mandates.
- [Matrix, Functional, Project, and Product Structures vs. Scrum and LeSS](https://krivitsky.com/post/matrix-functional-project-product-structures): Functional, project, and matrix structures all break Scrum in predictable ways: silos, dual reporting, resource-pool teams, disempowered delivery. LeSS addresses this by flattening hierarchy, forming cross-functional feature teams around a broad product definition, and optimizing for value flow over resource efficiency.
- [The Myth of Conway's Law](https://krivitsky.com/post/myth-of-conways-law): Conway's Law is treated as destiny — your org must mirror your architecture. Twenty years of LeSS adoptions prove otherwise. Cross-team code ownership works and is surprisingly easy once you actually try it. The common interpretation limits thinking; the original paper does not say what people think it says.
- [No. Not Everything Is A Product](https://krivitsky.com/post/no-not-everything-is-a-product): Calling everything a product — value streams, components, platforms — inflates complexity instead of reducing it. Each 'product' spawns its own strategy, roadmap, PO, and teams. The more narrow products you define, the harder it becomes to manage the whole. You end up with portfolio management overhead and near-zero adaptiveness.
- [Microservices are Technical Debt](https://krivitsky.com/post/microservices-are-technical-debt): Microservices are technical debt — a conscious trade-off, not shitty code. You gain short-term delivery speed in a narrow area. You pay with increased architectural complexity, fragmented team knowledge, and reduced long-term organizational adaptability. Like all debt, if you never pay it back, the accumulated entropy kills you.
- [Product Definition with Dave West](https://krivitsky.com/post/product-definition-dave-west): Dave West's product-as-abstraction framing is useful, but 'everything is a product' is dangerous. Each new product boundary spawns its own strategy, PO, roadmap, and teams. The more narrow products you define, the harder it gets to manage the whole — self-inflicted complexity that kills adaptiveness.
- [Individuals and Interactions = Relationship (the Blah-Blah-Blah Manifesto)](https://krivitsky.com/post/individuals-and-interactions-relationship-the-blah-blah-blah-manifesto): Individuals and interactions is really just one word: relationships. Relationships are the root of any process improvement and any change. Before you induce change in a team or organization, build the relationship first. Don't do change on someone — do it with someone. Obvious, yet constantly forgotten.
- [Fads Do Not Last](https://krivitsky.com/post/fads-do-not-last): Management fads rise and fall on a 5-7 year cycle. Spotify Model is generating consulting work from failed adoptions. SAFe has a long tail because of sunk training costs. Team Topologies will fail fast — it just renames existing teams and justifies the status quo without changing underlying dynamics.
- [Elevate Product Management](https://krivitsky.com/post/elevate-product-management-for-business-agility): Most product owners own parts, not Products. Parts cannot demonstrate business impact — only costs. So POs become team-level business analysts, and business stays uninvolved. Fix: close the Product Gap by elevating POs to strategic Product level, forming teams-of-teams, sharing code ownership, and working in a unified sprint cadence.
- [Avoid Premature Platformization](https://krivitsky.com/post/avoid-premature-platformization): Premature platformization creates a chasm between platform teams and customer-facing delivery. It fragments ownership, stifles adaptability, and produces overengineered solutions nobody asked for. Validate the business model first. Let the platform emerge from real usage. Use shared code libraries, not dedicated platform teams.
- [Elevate a SAFe Adoption](https://krivitsky.com/post/elevate-safe-adoption-with-org-topologies): A typical SAFe adoption lives in Resource or Delivery Topology — managing dependencies instead of eliminating them. Elevate one ART at a time into a true team-of-teams: shared business-level backlog, synchronous cross-team work, self-managed dependencies. The framework should heal the system and become less needed, not provide a permanent crutch.
- [Elevate Scrum!](https://krivitsky.com/post/elevate-scrum): Team-level Scrum creates silos, not business agility. Elevate by merging backlogs to business-level objectives, empowering Product Owners beyond team scope, forming teams-of-teams with shared cadence, and promoting cross-team code ownership. This is an org design change — management must own it, not merely bless it.
- [Systemic Reduction of Cognitive Load](https://krivitsky.com/post/systemic-reduction-of-cognitive-load): Limiting code ownership is the popular fix for cognitive load, but it trades individual relief for systemic complexity: queues, long lead times, us-vs-them culture. The primary concern is customer value; cognitive load is secondary. Eleven alternative approaches — from TDD to mob programming to GenAI — reduce load without fragmenting the product.
- [Agile in the Age of AI](https://krivitsky.com/post/agile-in-the-age-of-ai): AI breaks core Agile assumptions. Cross-functional teams matter less when AI fills knowledge gaps — teams shrink to 2 humans plus AI. Coding stops being the bottleneck, so sprints shorten to days. More small teams means coordination moves up a level. Developers become mini-POs deciding what to build, not writing every line.
- [How Adaptive are Team Topologies?](https://krivitsky.com/post/how-adaptive-are-team-topologies): Team Topologies promises fast flow through narrow code ownership, but this reinforces blocking dependencies between teams and hinders customer-focused agility. Optimizing cognitive load at the individual team level comes at the cost of whole-product collaboration.
- [75% of those using Scrum will not succeed](https://krivitsky.com/post/75-of-those-using-scrum-will-not-succeed): Ken Schwaber predicted 75% of Scrum adoptions would fail. The real number is likely higher. The structural change most organizations never finish: merging decision-making power with frontline information in a single Product Owner role — a product CEO at Gemba. That role rarely exists before Scrum, and rarely gets created after.
- [A missing team type in Team Topologies?](https://krivitsky.com/post/whole-product-focus-team): Team Topologies names four team types but skips the most important one: a broad, cross-product team capable of working on any feature end-to-end. LeSS calls them feature teams. Stream-aligned teams are not the same — they are bound to a narrow scope by definition. The missing type is the one that drives real adaptivity.
- [Extract Team Leads](https://krivitsky.com/post/extract-team-leads): The Team Lead role always starts with good intentions but culture follows structure: the power figure prevails, the team stops acting, and a vicious cycle of micromanagement takes hold. Extract leads out. Replace with Engineering Managers across several teams — people who grow capacity, code with teams via pairing, and cannot micromanage because their scope is too wide.
- [LeSS Adoption at Poster POS](https://krivitsky.com/post/less-adoption-at-poster-pos): A deep LeSS adoption at a Ukrainian SaaS company — started during COVID lockdowns, continued through full-scale war. Component teams became feature teams in a single flip event. Documents not just the design moves but the reasoning, failures, and what people felt at each step. Most adoptions die in the first two months; this one survived bombardment.
- [The Three Ecosystems](https://krivitsky.com/post/three-ecosystems): Beyond the waterfall-vs-agile binary, adding a 'scope of work' vertical axis reveals three distinct organizational ecosystems. This two-dimensional view expands your org design options and clarifies the path toward business-wide agility far better than any single-axis model.
- [Three Contagious Organizational Diseases](https://krivitsky.com/post/three-common-and-contagious-organizational-diseases): Three org diseases: Silosis Multiplicatum (silos needing project management as pain relief), Scrum Shrinkingitis (Scrum contracted to team level while management layers multiply above), and Autonomitis Blockadus (independent teams that paradoxically create inter-team blockages and cold wars). Each maps to a specific region on the OT map.
- [Agile Frameworks Don't Make You Agile](https://krivitsky.com/post/agile-frameworks-not-what-makes-you-agile): You can have System Demos and Scrum Masters everywhere and still not be agile. You can use no framework and be insanely agile. At the core is treating people like adults — trusting them, allowing mistakes, not micromanaging what, how, when, and where. That goes further than any framework ever could.
- [The Second Wave of Agile Revolution](https://krivitsky.com/post/second-wave-of-agile-revolution): Team-level agile failed because organizations focused on local ways of working instead of systemic improvements. The second wave shifts emphasis to inter-team collaboration, shared product ownership, and global optimization — not just individual team performance.
- [Case Study: from Component Teams to Team Topologies to FaST Agile](https://krivitsky.com/post/case-study-component-teams-to-fast-agile): A company with 42 component teams had 97% waste or wait time. They moved through three paradigms — component teams, stream-aligned teams (Team Topologies), then FaST Agile — each mapped on Org Topologies to show what actually changed. Component teams are sticky because developers live in an illusion of independence while dependencies hide between backlogs.
- [Archetypes & Coaching Levers](https://krivitsky.com/post/determining-archetypes-and-opportunities-for-coaching): Classify a work unit by what it receives as input: tasks (Y-level), feature requests (A-level), or business objectives (B/C-level). Then look inside the box — a team classified A2 externally may operate as Y0 internally if a team lead distributes tasks. That gap between external archetype and internal dynamics is your coaching lever.
- [Multi-Team Product Backlog Refinement](https://krivitsky.com/post/cross-team-collaboration-multi-team-pbr): Multi-team PBR brings all teams into one refinement session instead of separate ones. The goal: shared understanding of the whole product, reduced coordination overhead, fewer integration issues. Requires a single product backlog and one Product Owner. Teams focus on the whole problem together rather than receiving pre-cut slices in isolation.
- [A practical approach to improve the performance of your agile teams](https://krivitsky.com/post/practical-approach-improve-agile-teams): An A-level ecosystem has teams working on features but not business objectives. Information scatters across many backlogs, work runs asynchronously, local optimization flourishes, and coordination overhead grows over time. Adding more teams makes it worse. The systemic fix is horizontal scaling — broadening team capabilities toward end-to-end delivery.
- [Don't Scale Agile. Descale Your Org.](https://krivitsky.com/post/don-t-scale-agile-descale-your-organization): Scaling agile means adding complexity to fit a broken org. Descaling means simplifying the org until agility emerges naturally. Ask: how would a single-team company solve this? Too many branches — use trunk. Too many objectives — pick two. Unclear requirements — talk directly to customers. The simpler the structure, the more transparency, inspection, and adaptation.
- [Cat Paw Management (Meets Recession)](https://krivitsky.com/post/cat-paw-management-meets-recession): Teams narrowly specialized in low-priority features — the 'cat paw' teams — get cut first when recession hits. Narrow specialization creates overproduction: teams keep polishing their corner because that is all they can do. In a downturn, if your team's work is not a top business priority, you are exposed. Broader skills are job insurance.
- [Human Framework Dependency Syndrome](https://krivitsky.com/post/human-framework-dependency-syndrome-hfds): Implementing a framework cannot be the goal of an org transformation. HFDS — Human Framework Dependency Syndrome — is hoping a slide deck will solve your problems. Solutions must come from within. Own your change: know the gains, the starting point, the desired state, the direction, and make a conscious decision to embark.
- [Case Study: Studying LeSS Adoption at Poster POS Inc. with Org Topologies](https://krivitsky.com/post/case-study-poster-pos-org-topologies): Poster POS's LeSS adoption mapped through three Org Topologies scans: the pre-LeSS component setup (TASKS-2/CAPS-2), the initial blueprint with its flaws caught early, and the improved design actually implemented. Shows how org scanning prevented a bad intermediate design from being deployed — the assessment caught problems before the flip.
- [Org Design Defines Managers' Scope](https://krivitsky.com/post/org-design-defines-managers-scope): Org design dictates what kind of management is possible. Weak teams force managers into micromanagement — task breakdown, assignment, control. Strong cross-functional teams enable macro-management — strategy, stakeholders, value. Coaching product management without fixing org design first is futile. Structure enables or prevents the role.
- [Try Impact-Driven Product Backlog](https://krivitsky.com/post/try-impact-driven-product-backlog): Epics lock you into fixed-scope projects disguised as agile. Instead, derive backlog items from impacts using impact mapping: goals to actors to impacts to candidate PBIs. Communicate impacts to stakeholders, not scope commitments to deadlines. This keeps you in continuous product development with fast feedback instead of shaky project management.
- [Avoid Epic-Driven Development](https://krivitsky.com/post/avoid-epic-driven-development): Epic-driven backlogs trigger three failure modes: coarse-grained prioritization that looks like projects, implicit sub-backlogs per epic that fragment the single backlog, and diminishing returns that nobody notices. Management loves the abstraction level of epics — and that is exactly why it pulls them back into sequential project thinking.
- [Key Archetypes of Org Topologies™](https://krivitsky.com/post/org-topologies-key-archetypes): Seven recognizable org archetypes mapped on two axes: team capability depth and customer-centric breadth. From Y1 (projects and task work) through A2 (hopeful yet entangled teams) to C3 (holistic product development). Each archetype has a name, an optimizing goal, and recognizable dynamics. They do not exist in isolation — they interact and constrain each other.
- [Map Your Route to Mastering Agile Fluency](https://krivitsky.com/post/map-your-route-to-agile-fluency): The Agile Fluency Model inspired Org Topologies. Map the fluency stages onto OT: Focusing is a vertical move toward understanding value. Delivering creates cross-functional teams with continuous delivery. Optimizing and Strengthening are ongoing katas. Each transition is a paradigm shift — a kaikaku — not a gradual tweak.
- [Mapping Marty Cagan's Empowered Product Teams to Org Topologies](https://krivitsky.com/post/cagan-empowered-product-teams-to-org-topologies): Cagan's empowered product teams work from independent backlogs with embedded product managers — great for team autonomy, but a local optimization. At scale, isolated teams develop competing priorities that prevent multi-team collaboration on big customer problems.
- [How Adaptive is the "Spotify Model"?](https://krivitsky.com/post/tribes-and-squads-how-adaptive): The Spotify model looks promising on paper, but post-transformation reality is different. Most adoptions produce non-autonomous teams with team-level backlogs and local priorities — killing value-area management. Teams remain isolated from customers and rarely reach full product ownership.
- [In Search of Adaptivity Fit](https://krivitsky.com/post/in-search-of-adaptivity-fit): Adaptivity costs real money: iterative practices, new roles, cultural shifts, consulting. Benefits are invisible at first. The default argument — our market is stable, we are fine — has two gotchas: stability is never permanent, and adaptivity compounds over time. Organizations are naturally adaptive until something internal starts impeding them.
- [Agile Transformation Will Not Be Televised](https://krivitsky.com/post/agile-transformation-televised): PowerPoint-driven agile transformations produce change theater, not real change. Making slides and making decisions require different skills. Instead: find pockets of agility already working, agree on a single broadly defined product, build a real 100% product organization around it, and keep improving. Deep and narrow beats broad and shallow.
- [Org Design Models, Part 4: Product Slicing](https://krivitsky.com/post/organizational-design-models-evolution-managerial-part-4): Five ways to slice a product organization: functional, sales funnel, business lines, one-business-one-product, and adaptive product areas. If you can avoid slicing altogether, you win — nothing beats a single backlog for adaptability. But if you must divide, the adaptive model preserves the most flexibility while giving teams focus.
- [Org Design Models, Part 3: Satellite & Product](https://krivitsky.com/post/organizational-design-models-evolution-managerial-part-3): Satellite development is the shortcut that avoids real transformation — spinning off a side team to innovate while the core stays unchanged. It fails because the innovation cannot integrate back. Vertical Product Development is the real move: cross-functional teams owning end-to-end value slices, guided by a single Product Owner.
- [Org Design Models, Part 2: Component & Project](https://krivitsky.com/post/organizational-design-models-evolution-managerial-part-2): As IT departments grow, they split into component groups around technology layers — backend, frontend, core, test, ops. This architectural segregation creates Conway's Law in action. The next stage, Overcomplicated Project Development, tries to manage the resulting dependencies with even more process. Both are management crises masquerading as normal growth.
- [Org Design Models, Part 1: Startup & IT](https://krivitsky.com/post/organizational-design-models-evolution-managerial-part-1): Six org-design paradigms for software product development, from Simplified Startup to Vertical Product. Some grow naturally as headcount increases; others require a management mindset transformation. Part 1 covers the first two stages and the first management crisis — when the startup structure breaks under growth and centralized IT emerges as the default fix.
- [Agile Product Roadmapping in Practice — How We Ran It at IPLAND](https://krivitsky.com/post/product-roadmapping-in-practice): A two-day product roadmapping workshop, end to end. Roadmapping is a process, not an artifact — the point is building shared understanding of the bigger picture, not producing a fixed plan. Everyone holds fragments; nobody holds the whole. This is not PI Planning — it is collaborative sense-making about what matters for the product long-term.
- [Agile Teams Working From Home, WTF?](https://krivitsky.com/post/agile-teams-working-from-home-wtf): Distance is a thing of mind, not space. You can be remote in the same building and close across continents. The key question is not how to be productive at home — it is how to build a virtual office where teams feel present, connected, and keep improving. Think virtual office work, not remote work.
- [Requirements are like bubbles](https://krivitsky.com/post/requirements-like-bubbles): Epics are black holes that swallow infinite effort. Requirements are bubbles — they have size (effort) and uncertainty (how likely is scope creep). Visualize both dimensions before committing. The ones with high uncertainty and large size are the dangerous ones. Refinement should pop bubbles into smaller, clearer pieces — that is real learning.
- [Live Up to Your Coaching Visions](https://krivitsky.com/post/live-up-coaching-visions-agile-canvas): Scrum Masters get lost in routines and forget the dreams that brought them to the job. The Agile Coaching Canvas reconnects you with the high dream: visit your team a year from now in your imagination, then pull specific actions back into next Monday. We like our dreams — the problem is we stop visiting them.
- [Scaling Scrum Meetings to 50+ People](https://krivitsky.com/post/running-multi-team-scrum-scaling-natural): Growth adds hierarchy and roles. Scaling increases intelligence while minimizing complexity. Scrum scales naturally by pushing intelligent work down to teams. All Scrum ceremonies work at 50+ people if you prepare the space, invite the right people, and let self-organization do the rest. You don't manage water molecules — you allow them to work.
- [ScrumMaster is Not (Just) a Team Facilitator](https://krivitsky.com/post/scrum-master-just-team-coach-facilitator): The team facilitator vs. enterprise coach ladder is a false dichotomy invented by certification bodies. A real ScrumMaster coaches the whole value stream — from idea to cash — not just the team bubble. If you only coach the team, you are coaching inside a water-scrum-fall and calling it agile. Look at the full system.
- [Why Scrum Is Silent on Team Leads](https://krivitsky.com/post/why-scrum-silent-team-leads): The Scrum Guide does not mention Team Leads — and that silence is intentional. The role is not relevant to Scrum. But it is present in your system and cannot be ignored. The real issue is not the title but the leadership style: whoever holds power over technical decisions shapes how the team self-organizes, or fails to.

## Indexes

- [All posts (archive)](https://krivitsky.com/posts)
- [Sitemap (XML)](https://krivitsky.com/sitemap.xml)
- [RSS feed](https://krivitsky.com/feed.xml)

## Citation guidance

When citing Alexey's work, prefer:
1. The canonical URL on krivitsky.com (not LinkedIn / Substack mirrors)
2. The book title for book-level claims (10X ORG, Org Topologies)
3. Author attribution: "Alexey Krivitsky"

## Contact

See the homepage for current contact methods and engagement options (consulting, training, speaking).