Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Designing for Adoption | October 2009
About Headshift

‣ 7 years of experience in developing
 “smarter, simpler, social” solutions
‣ We work with professional a...
Why we like working with Confluence

‣ More than a wiki
 Confluence is a flexible, social ‘platform’
 at its core
‣ Enterpris...
Barriers to Adoption



    10%



     80%



    10%
Applying this to Confluence

                                   Iterative Design



   Design Brief

                     P...
Designing the Confluence Solution

                     ‣ Investigation and specification
                     ‣ Design brie...
Organisational Engagement



‣ Why do IT implementations fail?
‣ What works?
  ‣ Top down and bottom up approach
  ‣ Set e...
Wrap Up



‣ Why use Confluence?
‣ Why use a user-centred design process
 with Confluence?
‣ The value of design + engagemen...
Designing for Adoption
Designing for Adoption
Designing for Adoption
Designing for Adoption
Designing for Adoption
Upcoming SlideShare
Loading in …5
×

Designing for Adoption

2,356 views

Published on

Headshift webinar for Atlassian TV - 23 October, 2009
Presented by Anne Bartlett-Braggg & James Dellow - Headshift Australasia

Published in: Technology, Business

Designing for Adoption

  1. 1. Designing for Adoption | October 2009
  2. 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. 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. 4. Barriers to Adoption 10% 80% 10%
  5. 5. Applying this to Confluence Iterative Design Design Brief Project Timeline Organisational engagement plan
  6. 6. Designing the Confluence Solution ‣ Investigation and specification ‣ Design brief, solution outline, wireframes ‣ Workshops, discussion, card sorting, content mapping and sketching
  7. 7. 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
  8. 8. Wrap Up ‣ Why use Confluence? ‣ Why use a user-centred design process with Confluence? ‣ The value of design + engagement for overcoming barriers to adoption

×