Presentation by Andrea Ames (@aames) from CMS/DITA North America 2017 (#cmsconference): https://cm-strategies.com/2017-cms-conference/agenda-day-3-2/ames/
Before you DITA, know your users, their goals, and the content that they need. Then design an experience that delivers the right content at the right time, and leverage the capabilities of DITA to implement that experience. Easy to say…not always easy to do. Enter Design Thinking! The Design Thinking approach provides a collaborative framework for thinking about a problem space and gives you the methods to take action. And it’s FUN!
This presentation describes the basics of the Design Thinking problem-solving framework, how to apply it to a content challenge, and how it can be used to generate ideas and requirements.
2. About
Andrea
Technical communicator since 1983
Areas of expertise:
Content experience design: strategy, architecture, and
interaction design
Architecture, design, and development of product-
embedded assistance
Information and product usability
User-centered process for content development and
experience design
Senior Technical Staff Member and chief content strategist
for Integrated Content (IC) Center of Excellence (CoE),
IBM Digital Business Group
University of CA Extension program chair and instructor
STC Fellow, past president, former member of Board of
Directors
ACM Distinguished Engineer
@aames 2
5. Wikipedia
says…
Design thinking is a
methodology not exclusive
(sic) for designers, that
helps people understand
and develop creative ways
to solve an (sic) specific
issue, generally business
oriented.
@aames 5
7. What
@aames 7
As-is experience
Empathy map
As-is scenario map
Brainstorm
Prioritize
To-be experience
To-be scenario map
Low-fi prototype
Requirements
Roadmapping
User test
Stanford’s process depiction
Some of the methods you can use – the ones I’ve found
to be most useful
14. As-is
scenario
map
Visual representation of user workflow
Makes explicit the team’s knowledge
Exposes gaps and what needs further
research
Identify pain points and biggest
opportunities for improvement
Input to requirements
Consider…
“extra” steps
points of inefficiency (doing)
pain points (feeling)
points of confusion (thinking)
@aames 14
22. To-be
scenario
map
Visual representation of user workflow
Makes explicit the team’s knowledge
Exposes gaps and what needs further
research
Identify pain points and biggest
opportunities for improvement
Input to requirements
Consider…
“extra” steps
points of inefficiency (doing)
pain points (feeling)
points of confusion (thinking)
@aames 22
24. Story-
boarding
Create a seamless, comic-
book like story
Beginning, middle, end
Focus on the user
NOT on screens
Be ready to tell your story
to someone else
@aames 24
26. Design
first!
Tech doesn’t solve
problems, people (you!) do
You need a fast, agile,
effective problem-solving
approach
DesignThinking IS that
approach…for any kind of
problem.
@aames 26