Designing for Adoption
5 likes•1,291 views
The document outlines Headshift's expertise in creating social solutions for various sectors and emphasizes their experience with Confluence as a user-centered design platform. It addresses barriers to adoption and suggests a combined top-down and bottom-up approach to implement successful solutions. Key strategies include setting clear expectations, engaging organizations throughout the process, and integrating design with ongoing support and training.
Designing for Adoption
- 1. Designing for Adoption | October 2009
- 2. About Headshift ‣ 7 years of experience in developing “smarter, simpler, social” solutions ‣ We work with professional and legal services, consumer products, media and publishing, health care, and government ‣ Headshift Australasia launched in mid-2008 ‣ Part of the global Dachis Group
- 3. Why we like working with Confluence ‣ More than a wiki Confluence is a flexible, social ‘platform’ at its core ‣ Enterprise technology fit No surprises for enterprise IT folks ‣ Development philosophy Suits our user-centred design approach
- 4. Barriers to Adoption 10% 80% 10%
- 10. Applying this to Confluence Iterative Design Design Brief Project Timeline Organisational engagement plan
- 11. Designing the Confluence Solution ‣ Investigation and specification ‣ Design brief, solution outline, wireframes ‣ Workshops, discussion, card sorting, content mapping and sketching
- 12. Organisational Engagement ‣ Why do IT implementations fail? ‣ What works? ‣ Top down and bottom up approach ‣ Set expectations and measures of success at the very beginning ‣ Integrate the design, communication, training, and on going support plan
- 13. Wrap Up ‣ Why use Confluence? ‣ Why use a user-centred design process with Confluence? ‣ The value of design + engagement for overcoming barriers to adoption