Designing for Adoption

Designing for Adoption | October 2009

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

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

Barriers to Adoption 10% 80% 10%

Applying this to Conﬂuence Iterative Design Design Brief Project Timeline Organisational engagement plan

Designing the Conﬂuence Solution ‣ Investigation and speciﬁcation ‣ Design brief, solution outline, wireframes ‣ Workshops, discussion, card sorting, content mapping and sketching

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

Wrap Up ‣ Why use Conﬂuence? ‣ Why use a user-centred design process with Conﬂuence? ‣ The value of design + engagement for overcoming barriers to adoption

Designing for Adoption

by Anne Bartlett-Bragg on Oct 22, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

3 Embeds 8

Statistics

Designing for Adoption — Presentation Transcript

http://annebb.posterous.com	4
http://digitaldialogues.blogs.com	2
http://www.slideshare.net	2