Executive Brief
How to win without disruption
Mandates stall. Communities compound. The senior director who wins routes capability through the network, not through the org chart.
Inertia defeats mandates. Networks defeat inertia.
Top-down change initiatives collide with the standing organization and lose. Durable transformation moves laterally — through self-organizing networks of practitioners who already share a problem and want a way out.
Example: A directive lands in every inbox on Monday. By Friday, the calendars look identical to the week before. Meanwhile, a working group two layers down has quietly changed how three teams write code.
Align the individual's career and the organization's outcome will follow.
A community of practice that rewards the practitioner — visibility, promotion, mastery — turns personal motivation into collective capability. Without that alignment, the community is a meeting; with it, the community is a flywheel.
Example: Picture an engineer choosing between two extra hours of work this week. One hour earns nothing visible. The other writes her name onto a shared playbook the whole org will use. The flywheel is built on which hour she picks.
Invest in emergent capability, not in mandated change. The first compounds. The second decays.
From the Executive Brief
InnerSource turns tacit knowledge into compounding capital.
Tacit knowledge that lives in heads and chat threads decays the moment the practitioner moves teams. A shared repository — read, forked, contributed to across the org — converts private insight into a durable asset that anyone can stand on.
Example: Two teams solve the same problem in parallel. One writes the answer into a repo the whole company can clone. The other writes it into a thread that disappears below the fold by next quarter. Only one of those answers is still doing work a year later.
Removing toil is the cleanest path to capacity.
Toil is the repetitive, manual, interrupt-driven work that fills calendars without producing anything new. Every hour reclaimed from toil is an hour returned to delivery — and the return shows up in throughput before it shows up in headcount.
Example: An engineering team measures the share of the week spent on the same recurring chores. They cut that share in half. Nothing else about the team changes — the schedule, the staffing, the roadmap — and the next quarter ships materially more work.
Two routes to the same outcome. One arrives.
Push from the top
A directive sets the destination. Compliance is the metric. The org chart is the delivery mechanism, and the standing organization absorbs the impact.
Consequence: motion without compounding. The next mandate has to start over.
Compound from the network
Practitioners self-organize around a real problem. Career incentive aligns with shared outcome. The repository, not the directive, carries the lesson forward.
Consequence: each cycle leaves more capability behind than it consumed.
Fund the community. Reward the contributor. Measure the toil.
A senior director who waits for the mandate inherits the inertia that came with it. The director who funds the community of practice this quarter — and ties career advancement to its output — is the one whose org is still compounding when the next reorg lands on everyone else.