Principles for enabling deep secondary design

User-based redesign after implementation has been studied in many contexts gone by many different names, such as appropriation of technology, malleable design and secondary design. The phenomenon of redesigning content has mainly revolved around technologies such as Facebook, Twitter, or Wikipedia or portal-based technology with configuration abilities, with very little focus on technologies where users can change both functionality, content and the level of technology complexity. We coin this type of secondary design deep secondary design. In this paper, we investigate how to enable deep secondary design by analyzing two cases where secondary designers fundamentally change functionality, content and technology complexity level. The first case redesigns a decision model for agile development in an insurance company; the second creates a contingency model for choosing project management tools and techniques in a hospital. Our analysis of the two cases leads to the identification of four principles of design implementation that primary designers can apply to enable secondary design and four corresponding design implementation principles that secondary designers themselves need to apply.