1. Knowledge Integration – Balancing Between Anarchy and Despotism Joakim Lilliesköld The Royal Institute of Technology joakiml@ics.kth.se Lars Taxén Linköping University lars.taxen@telia.com

2. The core issue in Knowledge Integration [Knowledge integration] depends upon the extent of commonality in […] specialized knowledge. There is something of a paradox in this. The benefit of knowledge integration is in meshing the different specialized knowledge of individuals - if two people have identical knowledge there is no gain from integration - yet, if the individuals have entirely separate knowledge bases, then integration cannot occur beyond the most primitive level. (Grant, 1996:116) NoneFull Low High Commonality Knowledge Integration

3. Market & SalesIn Service SupportSupply & ImplementationResearch & Development Customers, TendersProductOrdersInstalled Base Customer needs 3G system The organization as Activity Domains Driven by the object of work Context in which individual actions are meaningful Shapes the worldview (ideology) of actors Has a fractal constitution – domains within domains Transformative and coordinative actions Coordinative mechanisms – activity modalities

4. Dimensions of coordination – activity modalities Contextualization –Activities take place in social fabrics Spatialization –In order to act, humans need to orient themselves spatially Temporalization –Actions are carried out in a certain order Stabilization –Rules, norms, etc., signify valid and meaningful actions Transition –Humans cooperate across social fabrics Applies to each Activity Domain

5. The ABB case

6. NoneFull Low High Commonality penetration Anarchy No authority over Activity Domains Despotism Complete sovereignty over Activity Domains Release 1.0, 1.5 Release 2.0 Knowledge Integration Knowledge Integration in the ABB case

7. Differences between Release 2.0 and previous projects Commonality enforcement Status reports in power point Configuration change board Coordination meetings Dependency diagram Commonality withdrawal Allowing different project models Abandon central budget control Central and local steering groups Release 1.0, 1.5

8. Conclusions Knowledge Integration from an alternative perspective –Integration of Activity Domains –Balancing between Anarchy and Despotism Analyzed global ABB projects –2 failed, 1 successful Findings –Successful project – move towards optimum Knowledge Integration –Less invasive commonality, more autonomy for Activity Domains –Small set of simple, mandatory and common obligations Activity Domain Theory a viable framework for Knowledge Integration inquiries

9. Re-conceptualizing Knowledge Integration [Knowledge integration] depends upon the extent of commonality in […] specialized knowledge. There is something of a paradox in this. The benefit of knowledge integration is in meshing the different activity domains - if two domains have identical knowledge there is no gain from integration - yet, if the activity domains have entirely separate knowledge bases, then integration cannot occur beyond the most primitive level. (adapted after Grant, 1996:116)