{"id":2802,"date":"2022-09-22T17:46:00","date_gmt":"2022-09-22T21:46:00","guid":{"rendered":"https:\/\/beomniscient.com\/?p=2802"},"modified":"2023-04-14T09:46:38","modified_gmt":"2023-04-14T13:46:38","slug":"how-to-vs-how-we-content","status":"publish","type":"post","link":"https:\/\/beomniscient.com\/blog\/how-to-vs-how-we-content\/","title":{"rendered":"Field Notes #012: “How To” vs. “How We” Content"},"content":{"rendered":"\n

Here we go.<\/p>\n\n\n\n

The notion of “how we” vs. “how-to” content was born from a discussion with my business partners about how I believe B2B readers prefer “how we” content (inspired by unique, personal experience) over generic “how-to” content.<\/p>\n\n\n\n

But the two are not mutually exclusive. <\/strong>Ultimately, “how we” content makes for the best<\/em> “how-to” content.<\/p>\n\n\n\n

In my opinion, they should overlap: every thought piece should provide actionable takeaways, and every how-to article should feature a real-life anecdote. <\/p>\n\n\n\n

(We’re rolling out a requirement here at Omniscient that every piece of content features at least one expert quote or is infused with at least one SME story or experience. I’ll let y’all know how this program shakes out.)<\/p>\n\n\n\n

Now, a few folks I’ve shared this concept with have challenged the subjectivity of \u201chow we\u201d content.<\/p>\n\n\n\n

That’s the whole point\u2014subjectivity in content is how it wins<\/strong>. Subjectivity is context, and context is what creates trust and authority. Subjectivity infuses personality and authenticity into “how-to” content. Subjectivity builds and converts audiences<\/a>, not just answers queries.<\/p>\n\n\n\n

I started writing this “hybrid” style of content years before thought leadership was a thing. I remember receiving topic assignments at HubSpot (like sales leadership challenges<\/em><\/a> or inclusive sales training<\/em><\/a>) that I didn’t have any personal experience with. Sure, I could’ve read up on these topics, but my first thought was, “Aren’t people doing this very thing at HubSpot right now?” Talking to those practitioners and experts taught me much<\/em> more than I would’ve learned from combing competitor sites.<\/p>\n\n\n\n

Why feature HubSpot<\/em> experts over external experts? Both are knowledgable and credible, but by leveraging expertise tied to HubSpot, I built some brand affinity and authority in the process…a tactic that ultimately helped with gated asset downloads and demos.<\/p>\n\n\n\n

For topics that HubSpot folks didn’t<\/em> have experience with, I then turned to external experts\u2014which, in this case, would be “how they” content, I guess. My (master)piece on freelancing<\/em><\/a> is my favorite example of this tactic. I was an experienced freelancer myself but knew I’d barely scratched the surface of the profession. A survey of 80+ fellow freelancers helped make this the comprehensive guide it is. (Read more about this experience here<\/a>.)<\/p>\n\n\n\n

The idea here is that all too often, companies and publications give advice that’s not theirs to share (regurgitated SERPs, anyone?) simply because the keywords aligned like stars.<\/p>\n\n\n\n

Writing based on first-hand experience (whether yours, a colleague’s, or an external expert’s) yields better content. Full stop. <\/p>\n\n\n\n

I work in SEO; I understand its power. But just because you can rank for a term doesn’t always mean you should pursue it\u2014not without being able to tell a story, share an anecdote, or at least feature an expert.<\/p>\n\n\n\n

If you’re surfacing keywords to solve pain points for your audience, it’s better to do so in a way that builds trust, not simply answers a question. Hell, for quick info, readers can use Google’s SERP features.<\/p>\n\n\n\n

The best content strategy<\/a> exists at the intersection of SEO and storytelling. 101 content can and should almost always include POV.<\/p>\n\n\n\n

When your content is inspired by company, leadership, and product expertise and then<\/em> rooted in intent-driven keywords, you meet your audience where they are with information only you can share.<\/p>\n\n\n\n