Alden DeSoto
2y ago
Bringing products and ideas to life with compelling content
Tech writers and content designers: Want to demonstrate impact? The HEART framework can help.
Many writers and UXers struggle with communicating the impact of their work. Showing impact takes time, but if you articulate a strategy and a North Star, your leadership will actively support you.
First, shoot for AT LEAST ONE of the following outcomes:
1. Increase adoption, engagement, and retention
2. Reduce support costs
3. Build user trust
This maps pretty well to the HEART framework, developed at Google, which breaks down product success into 5 areas:
Happiness
Engagement
Adoption
Retention
Task Success
Let's look at each one.
Happiness:
User trust is key. Do you proactively explain product changes to users? Do you listen to customers and teach them how to be successful, or does your content simply document product features? Monitor Product CSat and Net Promoter Score. Don’t rely on knowledge base CSat; it measures how happy users are with the content, not your product.
Engagement:
Create online courses and certifications to build a passionate base of power users. More tactically, lead with examples in knowledge base articles. Measure effectiveness with Average Session Length, Conversion Rate, and similar metrics.
Adoption:
Speak to users in their language, not your product jargon. If your content assumes that new users know your product terminology, you’ll have a hard time driving adoption. Use a metric that measures initial opt-ins, e.g. N of Accounts Created.
Retention:
As users become more sophisticated, does your content grow with them, addressing use cases they hadn’t considered? A common metric is Churn Rate, but use whatever metric captures the nuances of your product.
Task Success:
When users can’t complete tasks, they request support. This is expensive. A high Escalation Rate suggests that your knowledge base is not doing its job. Also look at Avg Time to Resolution because customers often request support even when the knowledge base has the information they need. In these cases, the support rep can simply reply with an article link and quickly close out the ticket. A high Escalation Rate with a low Average Time to Resolution suggests that the content might be fine, but needs to be more discoverable.
Of course, credit for these metrics has to be shared with the rest of the product team. But HEART gives you a strategy and North Star that will make sense to leadership and your cross functional teams.