Ecosystem / keystone organization model
Casts the firm as a keystone that invests in shared assets and standards to keep a partner ecosystem healthy, choosing that stance deliberately over a dominator strategy, but never asks which ecosystem tasks an agent should hold.
Marco Iansiti and Roy Levien, 2004
The origin of the framework, as the directory records it. The mark grades the origin, not this page.
Umbrex, Ecosystem / keystone organization model
The directory entry this score was read from. Umbrex is a consultancy network; its summary is the reference, not a primary source.
Scored against the twelve cells, it loads four: Structure, Authority, Coordination, and Strategy. The other eight it leaves to you. None of Composition, Evidence, or Mastery is among them, which is the usual result in this directory: the questions an agent in the loop raises first are the ones the literature answers least.
This is not a summary of the framework. Umbrex has one; the link under Sources goes there.
What is the smallest unit that can own a customer outcome end to end?
Which decisions may an agent make alone, and who is able to stop it?
What synchronizes the work when there is no room and half the team is not a person?
Where on the evolution curve does each capability sit, and does that dictate build, buy, or let go?