Your SlideShare is downloading. ×
Designing for Adoption
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Designing for Adoption

1,771
views

Published on

Headshift webinar for Atlassian TV - 23 October, 2009 …

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

Published in: Technology, Business

0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,771
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
5
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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