HP Inc.

Role: Content Writer

Project Focus: Technical Writing, Copywriting, Content Management, Marketing Operations

Background

I led a content writing and management project, standardizing, documenting, and developing a shared content database for 401(k) plan FAQs.

The problem

HP Inc. didn't have a single source of truth for their review, answering, or managing 401(k) investment questions from stakeholders. This caused internal teams at HP to spend valuable time searching for investment information and points of contact every time an investment question arose. 

The lack of structure, organization, and documentation caused delays in response time, inconsistent responses, inconsistent copy and voice across communications, and an increasing amounts of content and knowledge trapped on individual hard drives.

The idea: Bring structure, process, and documentation to cross-departmental investment information and content through a centralized database. This would enable shared access across teams, allowing them to collaborate, edit, update, and distribute accurate and consistent investment information to stakeholders, saving time and reducing error rates.

The challenge.

Content development and management for investment information was shared by three teams and owned by no one; fixing it became a game of hot potato.

Accurate investment content required a CMS

HP Inc. had three core teams coordinating and delivering investment information to stakeholders: HR, Treasury Ops, and Treasury Investments.

All teams held different pieces of investment information with no one solely responsible for managing the process.

The flow of information between teams wasn’t defined, nor was there a formal process outlining the management and handoff of investment questions and content.

Research

To solve our content development and management problem, I wanted to understand our content and the systems we used to for investment questions, source information, and sharing out responses. I conducted an audit, reviewing our investment content as well as the systems used to manage and deliver investment information amongst teams. 

I conducted a listening tour to understand HR and Treasury team staff experiences to elucidate how they worked through investment inquiries from stakeholders. This helped to codify areas of friction amongst staff or within the process.

Content and systems audit

As part of my audit, I outlined questions that guided my review.

  • What (if any) is the current process between HR, Treasury Ops, and Treasury Investments?

  • Who are the people involved? What do they do?

  • Is content being created on a schedule? Is content stored in any one place? If yes, what format is the content, what is the platform being used, and who has access?

  • [Is there / What is] the process for updating content?

  • Are certain investment questions raised more often than others?

  • What information would help our plan members?

  • What regulations, market situations, or internal guidelines might impact the information we release?

Key insights

Audits and interviews revealed there wasn’t a strict protocol for answering questions. HR would most often reach out to Treasury teams if and when a stakeholder had an investment question. A variety of staff were involved at varying points, without a single threaded leader managing.  

Stakeholders had access to the company’s annual 401(k) investment prospectus via the corporate website and HR intranet, but these documents were only updated annually and could have outdated information.

All other investment information was either pushed out quarterly via the 401(k) plan’s administrator, or was contained internally amongst HR and Treasury teams.

Neither a shared network drive nor a content management system was used to aggregate, update, and share information across teams for managing stakeholder inquiries.  

Listening tour

By listening to staff share their experiences, I was able to fill in knowledge gaps and answer questions unanswered during my content and systems audit. The interviews and audit data formed a starting place for designing a human-centered solution for creating, handling, and managing our investment content.

Key insights

After speaking with staff across all three teams, I found people were concerned about their workloads and giving incorrect information.

Investment staff held specialist investment knowledge, but didn’t have bandwidth to write bespoke answers to investment questions. 

HR staff didn't know who to contact on either Treasury Operations or Treasury Investments to answer stakeholder questions. This caused inefficient email chains as those emails often didn’t land in the correct staff members inbox, resulting in multiple outreaches or forwarded messages until the email landed in the right person’s hands or someone was willing to take on the work.

Furthermore, there wasn’t a project lead amongst HR or Treasury who owned investment questions. HR staff didn't feel qualified to answer stakeholder questions, Investment staff believed it was an HR issue, and Operations staff referred back to the Investment team to handle investment-level questions. 

The company held a fiduciary responsibility to all 401(k) plan members; how well staff communicated the company’s investment choices and policies could impact HP’s litigation risk. HR and Treasury staff were keenly aware of this risk and needed a sustainable solution.

The solution

In order to better manage distributed investment content and mitigate fiduciary duty concerns, I recommended a shared database for information storage and management, a master database of all investment FAQs, and a comprehensive and documented workflow outlining how to handle and managing investment information from creation to distribution.

This solution would manage and direct investment content for staff. Helping them to use, share, iterate content and unwind buried, institutional knowledge lost through staffing changes.

My approach

I chose to leverage existing and underutilized technology resources at HP Inc. to manage our investment information. Microsoft SharePoint was available and could be rapidly customized and deployed across all teams. From my audit and interview data, I created a process, documented the workflow, and collected investment FAQs to post to the site database.

Content management

Using Microsoft SharePoint, I created a consolidated site for our investment content accessible to HR and Treasury teams. The site held all supporting investment data for communications used across internal and external documents, including quarterly investment reports and reviews, compliance policies, and investment questions.

Process workflow

I documented the location of the SharePoint site, types of documents included, and how to save and use various document types for investment communications. I also wrote a process for answering incoming investment questions from stakeholders, including points of contact across teams, and a defined owner of the investment FAQs moving forward.

Investment FAQ database

I aggregated all investment questions HP Inc. had received as well as every answer we had distributed to plan members or stakeholders. Based on staff interviews, I also wrote new FAQs for other important investment topics that hadn’t been asked, but were likely topics. I focused on topics relating to fiduciary duty and issues raised in recent corporate 401(k) litigation. All content was uploaded into our shared database accessible to all.

My solution aimed to close information gaps, provide staff with clearly defined content management practices, and guide them to answers quickly, without detracting from their job responsibilities.


Investment FAQs

In writing investment FAQs, I followed HP Inc.’s brand standards.

As a 401(k) Plan Sponsor, HP Inc. was a fiduciary to its plan members and stakeholders, all information had to be reported accurately and therefore took on a formal tone given the serious subject matter.

Final thoughts

Limited reach

Putting order to a chaotic system was a fulfilling endeavor, but in analyzing how our teams were working together, I found even more opportunities to collaborate on content and build out strategic plans to leverage our knowledge for the benefit of stakeholders. However at the time, our team had limited scope to pursue additional content projects.

Thinking broadly

Putting stakeholders first, I was able to empathize with the types of information they might need in addition to simply having questions answered. I was able to go from a reactive position to a more proactive one, which can provide even greater outcomes when conceptualizing content creation and management.