Designing An Organizational Rule Set, IWODE Workshop, 12 December 2009
•
0 likes•426 views
Presentation at the International Workshop on Organizational Design and Engineering in Lisbon, 12 December 2009.
Recommended
More Related Content
Similar to Designing An Organizational Rule Set, IWODE Workshop, 12 December 2009
Similar to Designing An Organizational Rule Set, IWODE Workshop, 12 December 2009 (20)
More from Jeroen van Bree
More from Jeroen van Bree (11)
Recently uploaded
Recently uploaded (20)
Designing An Organizational Rule Set, IWODE Workshop, 12 December 2009
- 1. Designing an Organizational Rule SetJeroen van BreeMarinka CopierThijs Gaanderse
- 2. Some thoughts based on our discussions yesterday and today… 2
- 4. A focus on retrospective data may “prevent people from recognizing new ideas and seeing new ways to solve the problem” (Romme, 2003)
- 7. Abductive (or productive, conjectural) reasoningBrown, 2008; Cross, 2007; Fraser, 2007
- 8. 5
- 10. allowing more room for the autonomous “networker” and for learning.
- 11. Minimal structures as the “sweet spot”,
- 12. with a set of simple rules at its basis.6
- 13. Game design: second-order design 7
- 15. Envisioning the core mechanism
- 16. Building a (paper) prototype
- 17. Testing and adding rules
- 18. Playtesting8
- 20. Involving the stakeholders (players)
- 21. Including an evaluation of the design
- 22. Bringing designing to the material domain (of acting)9
- 24. aims to set up a separate Elective Care Centre (ECC),
- 25. which has to be competitive by being more patient focused.10
- 27. in which the intervention consisted of a number of workshops.
- 28. Third author joined team as external researcher,
- 29. primarily to record detailed observations.
- 30. In addition: interviews, recorded reflections.11
- 32. Based on the game design process, we developed a series of four workshops,
- 33. set up as “game design games”,
- 34. to achieve a game design lens and generate energy.12
- 36. grounded in competition, time pressure, scarcity of information and adherence to rules.
- 37. Progressive understanding of the system by participants.
- 38. Participants forced to work from a different perspective.
- 39. Delicate balance between game and content.
- 40. Value for organization lies in process, less in end product.13
- 42. because of the use of rules.
- 43. Involvement and open exchange of ideas between stakeholders achieved,
- 44. mainly caused by role-playing.
- 45. Evaluation of the design by means of playtesting is useful,
- 46. but needs to be extended and refined.
- 48. more attention to framework, improved prototyping and extended playtesting.
- 49. Focus on the evaluation of the implementation of the new design, and its effects.
- 50. Contrast this with the emergence in games, based on its “minimal structure”.15