One way to look at Interweave Thinking and the Interweave Practice is from a New Product Development point of view. Seeing Interweaving as a new product development Pivot away from Enterprise Architecture offers important insights.
Enterprise Architecture (EA) is an approach with strong roots and traditions coming from business information systems, IS/IT and engineering domains. In recent years the sellers of the approach(s) tries to expand its reach to fields outside IS/IT and engineering. But, reports of pushback from customers are frequent and appear to come more often.
What do with all those customers that tries the products and return them? One way is to sell, sell harder. This approach together with rebranding is what many do, although the product features are almost the same as before. The pushback’s are no surprising since it is easy to see why the engineered approach meets resistance. The traditional EA is comprehensive and built around creating and use “dead” artifact’s (machines, things, IS/IT) ,while an organisation, company, enterprise are socio-economical. A software application does not say NO, but people say NO and do much more than any enterprise architects can and want to model.
This is how you can view Interweaving, a Pivot and an approach that follow customers need. Interweaving aims at Unlocking, Realising, & Optimising The Value Of Togetherness.
The following sections each outline a topic where Interweaving Pivot from the tradition of Enterprise Architecture.
Interweaving - a complementary, supplementary and agile practice
From the Starting Point to the “Right Size”
Note: The exist a number of mis-interpretations of the start with what you need and not more approach. If you want to build a (new) truck then you should not start by building a bicycle and then try to scale and grow. Start with what you need. Maybe you aim for a minimal viable truck product, with extensibility options?!
Interweaver - the complementary and supplementary Integrator, Facilitator, Mediator Role