Gathering Information for a Single Source of Truth

Make the time to capture information that other teams and audiences will need.
Two colleagues discussing information during a meeting

Sandy, the product owner for the client portal, is catching up on emails when she sees that she has received the third request this week for more information about the new document upload feature.

The front line customer service team leader wants to know what to do when a client submitting a support request in the portal reports that their document will not attach. The L&D team wants Sandy to walk them through the new process step by step so they can build a training guide. A customer marketing team member needs to discuss whether certain phrases are accurate to use when describing the new feature to clients.

The Information Gap

Two months ago, in a kickoff meeting covering multiple initiatives, somebody took notes about the updates to support features on the client portal. The notes taken in that meeting were later pasted into a document available to all the departments.

Thinking back on that kickoff meeting, Sandy remembers that the focus was on the project update and drafting a brief, straightforward announcement. The notes weren’t wrong. They just were written with a limited purpose in mind. Now the source document is missing information that different functional areas need for communicating the details or for handling edge cases.

Sandy wants to help, but her calendar is already squeezed with work toward the next client support feature. She realizes that it would be better if, instead of meeting separately with multiple colleagues requesting separate pieces of information, all the details could be addressed in one sitting.

Creating effective source documentation starts with a comprehensive, well-planned interview.

Later that day, Sandy remembers that the content management team handles exactly this kind of gap. She sets time with the technical writer, Lana, who knows what kind of questions to ask. Not just about how the new feature works, but questions that anticipate:

  • Why would a client want to use it rather than provide documents through email?
  • What wording can be used to describe how secure it is?
  • What steps would a client take if they had a technical issue?
  • Can we get a screenshot of that?

Both Sandy and Lana have busy schedules and are motivated to find the most efficient way to handle content. In one meeting, they collect information for the master summary, main points, use case examples, detailed client instructions, and the issue resolution process.

Building and Maintaining a Trusted Source of Truth

The updated and approved information is added to the content management system, where it is organized and tagged with metadata. Terminology is clarified. Rules for wording that can or can’t be used and the non-negotiable facts are noted. Subsequent updates are made within the CMS, reducing the risk of variations and discrepancies. It houses the single source of truth. In it, main points and details are available, ready to be put to use in various ways.

Now, colleagues who might otherwise have thought they needed a chunk of Sandy’s day can be directed to the CMS.

More updates to the client portal are already on the horizon. After this successful collaboration, Sandy and Lana are looking forward to tackling the next one.

They agree on this: “Next time, we’ll get this all handled before launch.”

In content management, the best interviews don’t just answer today’s questions.
They anticipate the questions that will come next.