-
Notifications
You must be signed in to change notification settings - Fork 14
Automated Map Analysis
This is a documentation for rules that are used for automatic map analysis.
A component is in a late transitional phase of evolution. A transition to utility is expected soon, therefore there may exists utility providers already, and your supplier may be interested in squeezing you as much as possible.
Formal requirements: 0.5 < positionX < 0.75, external.
A component is in the 'utility' phase of evolution, was created internally but never offered to anyone. Adopting industry standard may be a very good move.
Formal requirements: positionX > 0.75, internal, not a user need.
An internally developed component is approaching the 'utility' phase. It is high time to make a utility service out of it and disrupt the market if it has not been done already.
Formal requirements: 0.5 < positionX < 0.75, internal, not a user need.
An internally developed component that is a user need and is actively sold, is approaching the 'utility' phase. Inertia may trick you into thinking that you are ok, but there are huge chances that someone will deliver it as a utility product and you will be disrupted.
Formal requirements: 0.5 < positionX < 0.75, internal, a user need.
Any suggestion how to improve this documentation? Tell Wardley Maps