We try to avoid change when by definition; change is what we’re here to manage. Why not make it a skill?
Learn why managing change is a skill like any other. It is a career differentiator. And it’s easy as can be.
This presentation was given at Information Development World on May 16, 2017
Don’t miss our upcoming event, Information Development World: Creating Machine-Ready Content to be held on November 28-30, 2017.
http://www.informationdevelopmentworld.com
5. 5
Ch-Ch-Ch-Changes
1985
§ Hardcopy text + line art
§ Well-defined process
§ Using WYSIWYG (then GML) software
§ Book paradigm (TOC, PTOC, LOF, LOT,
Index, …) with headers/footers
§ Took a long time
§ Using standard fonts
§ Physical specs
§ Output measured in shelf-feet
§ Change agent = ourselves
2017
§ HTML online text + line art / video / photos /
animations AND in-product guidance
§ Well-defined process
§ Using XML software + CMS + graphics + sound
§ Topic paradigm with metadata and hypertext
links and loading optimization and tracking
§ Who has time?!
§ We have fonts?!
§ Device awareness
§ Output measured in completeness
§ Change agent = everyone
15. 15
Managing Change
Establish a Corporate Culture of Transparency
VP
Leadership
Employees
VP
Leadership
Employees
VP
Leadership
Employees
Your org Customer Support Dev Eng
Who we are
Our problems
What we’re doing
18. 18
Organizations are People
§ Rumours are deadly to organizations
§ Poorly informed people (employees,
coworkers, other organizations) make
things up or ascribe motivations / points of
view
§ When people are informed, they don’t
gossip or mong rumours
§ Communications transparency is the
antirumour and builds trust and thus a
stronger organization.
22. 22
Easy Example:
We now need to perform first-article proofs
Change = insert a step after content dev but before print
• What process are we replacing or improving?
• What content needs first-article proofs?
• What’s in-scope for a proof? What’s not?
• Who submits? Who inspects? Who arbitrates?
• How long should a proof take?
• What’s the time frame to correct problems?
• How many times can something be submitted?
• What feedback loops are there?
23. 23
Moderate Example:
Our content should conform to a standard BOM
Change = Create a standard then deliver content consistently
• What groups are affected?
• Should there be an analysis? Do we
need standards?
• Do changes affect any other groups or
products?
• Are the changes by vote? Are they
optional? What are the consequences
of not implementing?
• Do we need a proof of concept?
• How do we know when we’re done?
• What org goals does this support?
• What’s the schedule?
• How does this fit with what product
managers want?
• Does this affect our SEO strategy?
• Does this affect our Style Guide?
• Does this apply to all content ever
created? Or just the most recent?
• Do we need new metadata?
• Who wanted us to do this?
• Does this take precedence over my
product schedule?
24. 24
Complex Example:
Improve Content Quality
Change = Measure and improve content quality
• What quality measures does
Development use? Marketing?
Support? The company? The
industry? Competitors?
• Which ones are most
important?
• Who gets a vote?
• What are the big levers?
• Should we do an assessment?
Internal or external or both?
• How do we know when we’re
done?
• What’s the schedule?
• Do we all do the same
thing?
• How do we decide?
• Who tracks separate
actions?
• Are we staffed to do
everything?
• Do we have the right skill
sets?
• How do we assess what we
want to do?
• Who are all the
stakeholders?
• What changes are occurring
the rest of the company?
• Who else cares about our
content quality? Sales?
Customers? Support?
• What do we expect to
happen as a result of our
actions?
• Who took my cheese?
• Do these pants make me
look fat?