In this session, you’ll learn about the challenges and victories as we worked to build a unified product content practice at an enterprise software company. We took a help documentation team, and from there grew the content practice to influence, drive, and unify content throughout the entire product ecosystem. Many times, it can be hard to know where to start. We’ll share the steps we took and the lessons learned as we reimagined our content practice.
In this session, attendee’s will learn:
Creating a product content style guide
Connecting content through the product ecosystem
Refining your product creation process
Influencing and content decisions across the organization
Working in an agile environment with few resources
6. Content is a crucial part of your product. Content strategists
have become an important part of web-focused UX teams – so
why are so many product companies still missing out?
7.
8. How might we build a
unified product
content strategy?
22. Before After
Mostly worked on help articles
Outdated help site
Reactive to product changes
Work thrown over the wall
Largely unknown to to product teams
Basic editorial guidelines
23. Before After
Mostly worked on help articles Content across the product ecosystem
Outdated help site Updated help site
Reactive to product changes Active in product development
Work thrown over the wall Work collaboratively with designers
Largely unknown to to product teams Relied on by product teams
Basic editorial guidelines Robust content guidelines and principles
31. Find people
● Find designers, product managers, developers, and become friends
● Work to understand their pains and challenges
● Learn about what they are trying to solve
● Ask how you can help
32. Join them
● Show up at design critiques and product reviews
● Learn design and product language
● Find ways to help or add value
● Ask questions
37. At some point, everything's gonna go
south on you and you're going to say, this
is it. This is how I end. Now you can either
accept that, or you can get to work. That's
all it is.
You just begin. You do the math. You
solve one problem and you solve the
next one, and then the next.
And If you solve enough problems, you get
to come home.
Image courtesy of: https://the-martian.fandom.com/wiki/The_Martian/Film
38. Before
Mostly worked on help articles
Outdated help site
Reactive to product changes
Work thrown over the wall
Largely unknown to to product teams
Basic editorial guidelines
39. Don’t break big things
into big plans.
Break big things into small
things with small plans
Jeff Patton
49. 49
For products made of
words and pixels,
words are at least 50
percent of the ship.
Elizabeth McGuane
https://blog.intercom.com/how-words-build-a-product/
50. Where are words?
● tooltips
● confirmation messages
● error messages
● labels
● buttons
● empty states
● feature names
● confirmation screens
● transactional emails
● in-app user assistance
● release notes
● … and on and on.
59. A typical project, before
Product Manager
UX Designer
Developer
Content
~~-
-- [ ] ~~-
-- [ ]
60. A typical project, after
Product Manager
UX Designer
Developer
UX Writer
~~-
-- [ ]
61. 1. Consider words early and often
2. Have a conversation, then write
3. Focus on verbs and nouns
4. Make every word earn its place
5. Throw away work
6. Prototype and test words
Designing with Words
Low Fidelity
Medium Fidelity
High Fidelity
64. Tell people
● Find designers, product managers, developers, and talk to them
● Show people your work and challenges
● Tell people what you’re doing
● Ask for help
71. Our current challenges
● Our team is the same size it was when we started
● We have more content to create and manage
● Empower and educate others
● The struggle is real
72. Start small, and then don’t stop
Show, do, tell
Create frameworks as you go
Find and join people
74. Resources
1. How the words you use build your product - Elizabeth McGuane
2. Words and the design process - Biz Sanford
3. Writing thoughtful product content at scale - Biz Sanford
4. How to design words - John Saito
5. 10 things UX writers hate to hear - John Saito
6. Why your design team should hire a writer - John Saito
7. Bring out your inner UX writer - Rachael Mullins
8. Software Complexity: The Art of Naming - Alexandre Oliveira
9. Revenge of nerdview - Ryan Bigge
10. Hide all text JS