Abstract
In policy practice, the concept of chain computerization is often applied. Development of chain computerization often proceeds 'under architecture'. The role of architecture is however contested: it can foster collaboration in chains, but also lead to polarization.
For this reason, research into how architectures are developed is relevant. The question is how architecture development can contribute to collaboration in chains. Our research shows that architectures have to be associated with variety on several important aspects. This is demonstrated in this article. Both the content and the form of an architecture varies across cases. Also, development projects vary, with regard to nature, strategy, and organization of decision making. We explain this variety by looking at the choices that underlie architectures, and at how stakeholders make those choices. It appears that stakeholders' frames play an important role in these choices. We show that stakeholders value the role of trust, and for this reason they sometimes choose not to come to agreements on subjects; it explains both content and form of architectures. This article is based on my recent thesis (Oosterbaan, 2012).
On these grounds, the conclusion is drawn that an architecture not only functions as an agenda for the development of ICT, but also for the development of collaboration. The concept of 'architecture' can play a strategic role with regard to chain-computerization if this function is taken seriously by both architects and public managers.
Original language | English |
---|---|
Article number | 1 |
Pages (from-to) | 1-10 |
Number of pages | 10 |
Journal | Journal of Chain-Computerisation |
Volume | 4 |
Issue number | 1 |
Publication status | Published - 2013 |
Research programs
- ESSB PA
- EUR ESSB 25