## Why this wiki Hi! I'm [[Who's Writing This|Vlad]]. I designed and ran growth programs inside large tech companies, working with a good number of startup founders and internal product teams across tens of M&As, joint ventures, and partnerships. Some bets scaled into new businesses, while others collapsed. In every case there was a reason why, and those reasons added up to a pattern. Naturally, when value from outside the core business tries to enter an organization, existing structures resist. They're fitted to optimize for the current business, not the new one. Organizations aren't built for systemic change. Yet given the lifecycle, every organization eventually has to evolve or die. Absorption as a concept exists across disciplines and methodologies. Yet I haven't found a practical, exhaustive answer for how to execute it well. The practice of absorbing opportunities is universal to any business, and understanding its principles is crucial before pouring in resources and expectations. This wiki is my attempt to document that system as it develops: to write down what I learned, test it against theory and against other companies' cases, and improve it in public. I believe that in the age of AI, understanding absorption is the deciding advantage. The world is about to test it harder than at any point in industrial history. At the pace of change expected through the 2030s, absorption becomes the terrain that decides corporate survival and startup outperformance. ## The main question **How do organizations identify, absorb, and extract value from emerging tech?** [[Absorption]] is a general capability. An organization can absorb any external resource: knowledge, talent, capital, business features and models, or entire companies. The focus here is technology, because technological change is the force that most reliably makes the current business insufficient and forces companies to look outside. Emerging technologies are where absorption is hardest, most valuable, and most often executed badly. I expect that solving the question for emerging tech yields guidance that generalizes to absorbing any kind of external value. ## The basic idea: Flow x Friction *terminology note: still maturing, not fixed* Returns from new opportunities depend on two variables. **Flow** governs where opportunities come from and what happens to them next: sourced, selected, structured, integrated, operated. **Friction** is a result of design decisions. It isn't simply resistance. It affects how smoothly opportunities access organizational resources and expand. Push friction defends the core, while pull acts as a magnet. Design's job, then, isn't to eliminate friction. It's to calibrate it, matching push or pull at each stage to what that opportunity can actually bear. The relationship is multiplicative: strong flow into badly-calibrated friction, in either direction, wastes what flow produced. Fixing only one element yields nothing, which is why copy-pasting a competitor's mechanics rarely works. This gives two parts of the playbook. **Mechanics** builds the flow. **Design** calibrates friction. ## How this wiki is organized **Playbook** is the practical core: what to do, why and how. * **Mechanics**: the operating process in five stages, source, select, structure, integrate, operate, each with its own rules. Each stage may be a project or a process. * **Design**: the organizational decisions that calibrate friction, including mandate, governance, access to resources, structural placement, people, and incentives. **Theory** is the intellectual foundation: what we know and how sure we are. * **Foundations**: the building blocks, concepts like absorptive capacity, transaction costs, ambidexterity, and complementary assets, explained in plain language. * **Frameworks**: how researchers and practitioners, myself included, have organized these elements, examined for where they support the playbook and where they contradict it. **Cases** are practical examples. Every case, whether from my own experience or from public records and interviews, is analyzed through the same lens: which stages of the process performed as designed, which design elements enabled or blocked the outcome, and what the resulting yield was, and why. Cases are how this playbook accumulates evidence instead of remaining a personal opinion. Please mind that this is a playbook, and it is useless without purpose and a real strategy behind it. Clear goal-setting to execute with this playbook is essential. ## Who this is for Different applications of the same lenses. **B2B founders:** if you sell to large corporations, this is how they actually decide. Understanding the absorption system from the inside is how you enter it and become irreplaceable to your largest customers. **Corporate operators:** CEOs, chief strategy officers, corporate development and partnership leaders, and anyone tasked with building or bringing a new growth layer inside an established company. **Product owners (internal):** the same system, used from within, is how you run a business inside the business: securing mandate, capital, and rails to grow like a venture with a corporate balance sheet behind you. **VC funds:** how to build an external integration layer across your portfolio, the value-add that actually drives IRR and attracts founders to your fund over others. Which absorption problems are common enough across portfolio companies to be worth solving once, for everyone. *A note on depth.* This wiki covers the system, not the specialties. There are excellent books on M&A, venture capital, strategy, innovation management, corporate finance, HR. What no specialist book covers is why a function, in isolation, produces no absorption when the surrounding system around it is missing. That system is the subject here. ## How this will grow This is an open working knowledge base. Pages will be revised as evidence and corrections come in. Where I am confident, I will say so. Where I am guessing, I will say that too. If you disagree with something, that is the point. Write to me. <!-- [[AI-Navigation]] -->