<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mike Hales on Medium]]></title>
        <description><![CDATA[Stories by Mike Hales on Medium]]></description>
        <link>https://medium.com/@michaelhales?source=rss-a143cd7629fc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6yMkn2aoff8Vh9XVsKNDsA.jpeg</url>
            <title>Stories by Mike Hales on Medium</title>
            <link>https://medium.com/@michaelhales?source=rss-a143cd7629fc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:48:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@michaelhales/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[At the foot of the cliff: A place for everything]]></title>
            <link>https://medium.com/@michaelhales/at-the-foot-of-the-cliff-a-place-for-everything-08b8ae07cc98?source=rss-a143cd7629fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/08b8ae07cc98</guid>
            <category><![CDATA[content-curation]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[content-management]]></category>
            <category><![CDATA[content]]></category>
            <dc:creator><![CDATA[Mike Hales]]></dc:creator>
            <pubDate>Sat, 15 Mar 2025 09:33:50 GMT</pubDate>
            <atom:updated>2025-03-15T09:33:50.317Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*eyZiEF9_8X81kg3ZhXtmFA@2x.jpeg" /></figure><p>More often than not, I compare creating and managing help content to gardening. The simple reason being that it requires a consistency of small effort to get good results.</p><p>Of course, there’s great effort in the creation – understanding who it is for, being consistent in style, being brief as possible without losing meaning – but the mechanics of content maintenance are too often overlooked.</p><p>Content is created, published and then forgotten.</p><p>Of course, occasionally – with great fanfare – great chunks are transplanted but without any real attention to detail or review. And, left in its new location to fester.</p><p>Happily for me, my slight obsessive and compulsive nature comes to my aid as I take great pleasure in auditing all content and structure, creating a unique ID for each piece, categorising its function – article, navigation page or functional tool, adding notes as to whether that content contains time-sensitive language or data such as a statement based in time or prices, and also whether it has elements that need to be reviewed – images and videos for example.</p><p>Additionally, each piece of content will be assigned a review date based on a sliding scale of whether it’s timeless, like terms and conditions that only need to be checked annually, or something that talks about a product or service that changes regularly, like add-on services, listings or an offer.</p><p>Then, each piece of content needs to be tagged, in connection to the wider business language so that it relates to the service, product and area it supports. That way, when a change to a service or suite of products happens, I can easily pull all related content and check to see if anything needs revision or removal.</p><p>Of all of this meta data attached to the content, the review date is the key.</p><p>I mentioned the ‘set and forget’ that often happens, which in turn leads to a reactive management when you only get prompted to look at something when it’s spotted as being broken, out of date or simply wrong. Of course, the unseen malaise is that your users or readers lose trust in that content – why believe something that talks about something that happened a year or two ago, or references something long gone – product or event and so on. And, worse still, those within your business will have their suspicions about Help content confirmed, that it’s the lowest rung on the ladder and if you, as the responsible person don’t care, why should they!</p><p>By using date prompts and the follow up to the product owners, you’ll address all these issues in one simple step. Your content is cared for, the facts checked regularly and the product people can have faith that you’ll ensure that your side of their information structure is being well maintained. It also forms part of the long game of showing the value of the help content. Heck, you can even show off and put a review date for your users to be reassured by.</p><p>I’ve used spreadsheets to manage all this – not great and who likes coding in Excel? Content management systems are often focused on the production or publishing rather than the admin – it’s not as sexy let’s admit it. And, knowledge systems, a natural home, are often so specific to themselves that integration into other systems, analytics and using AI to pick out the red flags are not thought about and available.</p><p>I’m starting to see a few products appearing that address the admin of content and more importantly allow you to establish relationships between content sets – public and internal for example. But, so far, I’ve stuck to hacking a solution using JIRA.</p><p>All of my work requests come in through JIRA. So, I manually, boring as heck, created an archive of all the content pieces, using the editable description field to capture the what (URL, who and info notes), content tags as “Labels” and of course the due date as the review point. So, each piece of content is a “story” in JIRA:</p><ul><li>linked to the URL for that content</li><li>has a description of what, where and who</li><li>labelled as what it is – so at a click I can see all related content tagged as such</li><li>has a review date that can generate a regular to do list of content to get reviewed by the who for that content</li><li>and is linked to the work done to that content – a transparent history of changes, updates and who did them.</li></ul><p>Very labour intensive but it works.</p><p>So, the outcome is a semi-automated process of what needs looking at, when and by who. Happily, 90% of the time, there’s little or no update required but the owner is happy to have checked it and to know that; the content gets a nice refreshed on this date label for readers to be reassured by; the content gets a reset review date based on what it’s about and how important it is strategically, where it is and what is in it – prices, images or video, and the weeds in the garden are gone, the overgrowth trimmed back and hopefully everything’s looking pretty good!</p><p>I’m sure there are better ways or tools that could be used, so let know what you do, how and with what. I’m always looking to learn and improve so do share!</p><p>Hopefully this is useful for someone like me out there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=08b8ae07cc98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[At the foot of the cliff: The value of help]]></title>
            <link>https://medium.com/@michaelhales/at-the-foot-of-the-cliff-the-value-of-help-6b6cc2f5cddc?source=rss-a143cd7629fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b6cc2f5cddc</guid>
            <category><![CDATA[business-value]]></category>
            <category><![CDATA[content-value]]></category>
            <category><![CDATA[support-system]]></category>
            <category><![CDATA[help]]></category>
            <dc:creator><![CDATA[Mike Hales]]></dc:creator>
            <pubDate>Sat, 08 Mar 2025 12:41:54 GMT</pubDate>
            <atom:updated>2025-03-08T12:41:54.049Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*REwUqqn1B5IN-k3h5jLpSQ.png" /></figure><p>The political position of Help content — last on the list and often an afterthought — is a simple result of the perceived value of that content. Often, it’s valued by qualitative metrics such as customer feedback or even NPS but for businesses it’s always about the bottom line — calls saved, costs out.</p><p>As an area of content I’ve managed, that has been the key for me, that £ value. Having that information to hand, repeating it as often as possible and ensuring your team has it as part of their KPIs brings a clear vision to work required and importantly gets you some chips at the top table. The qualitative metrics are important to me as flags or indicators. This article, topic or section is not working for customers, why? But the everyday duty of ensuring your work is valued and supported and your team is well resourced will come down to that value.</p><p>So job one on joining in a help content management role for me has been discovering what are the call drivers, what’s the average, or averages, cost of those calls and are the journeys from help to phone being measured and how? Most common is Digital Call Rate (DCR), essentially tracking has a customer visited the help content and then called the business — the detail of were the visit and call for the same thing is still missing but that’s true for First Contact Resolution as well.</p><p>After that, it’s a relatively simple calculation as you seek the elevator pitch summary. Visits X DCR will give you the relative impact value of that content; visits x avg call value will give you the size of the value pie; so after that it’s a simple breakdown. Your area gets 100 visits per year, 20% then go onto call and an average call cost is £5 the your Help content value is £400 and your target is to reduce the £100 slipping through.</p><p>The underlying premise is that if you took that help content away then your business would be getting £500 worth of calls, migrate that into hundreds of thousands of calls a year and that value figure will get grab anyone’s attention and there’s your elevator pitch when your director asks “why do I care about help content?”, your answer is that value figure.</p><p>Is it rock solid statistical analysis? That’s not the point, it’s about headlines, elevator pitch, instant answer to what’s the value of this thing. Of course, you have to work with your analytics team to ensure that the statistical foundation is solid, especially if you’re trying to claim benefits as part of the service budget!</p><p>Once you have that number, and currently mine is in the £millions, then you’ve got your chips at the table, you’ve got your director’s attention, your squad have something to show in performance reviews and then it’s onto the hard work of improving that number!</p><p>That’s where that impact value I mentioned before comes into play — what areas rank highest? What areas are above the average for the body of content as a whole? Mix that with the strategic priorities for your business, the product release schedule and you’ve got your priority ranking of work readymade for you.</p><p>Those qualitative metrics should be high on your radar but how often have you impressed anyone with an NPS or DCSAT shift of 1%? Sure, it’s important as a supporting metric but what’s it worth?</p><p>Let me know how you present the value of your help content — I would love to know.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b6cc2f5cddc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[At the foot of the cliff]]></title>
            <link>https://medium.com/@michaelhales/at-the-foot-of-the-cliff-870bd4222b16?source=rss-a143cd7629fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/870bd4222b16</guid>
            <category><![CDATA[content]]></category>
            <category><![CDATA[help]]></category>
            <category><![CDATA[content-creation]]></category>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[content-writing]]></category>
            <dc:creator><![CDATA[Mike Hales]]></dc:creator>
            <pubDate>Sun, 02 Mar 2025 08:52:33 GMT</pubDate>
            <atom:updated>2025-03-02T08:58:08.866Z</atom:updated>
            <content:encoded><![CDATA[<p>Having worked in digital content for more years than I care to contemplate, I want to share my views on the creation, management and strategy for Help content as a separate genre of content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kyRZPXgbWgEPnoQJZcbDhQ.png" /></figure><p>I’m going to break it down into a series of chapters covering the inception, creation and administration of content to provide self-service support for the readers and value for the business or owner.</p><p>Why ‘at the foot of the cliff’? Well, more often than not help content and services are treated like an ambulance at the foot of the cliff, expected to somehow rescue the user when earlier intervention might be so much easier and better for all involved.</p><p><strong>On inception</strong></p><p>One of my greatest frustrations at work is that Help content is often the last item on a product creation list, is poorly regarded by the business, or is simply dismissed as &quot;FAQs.”</p><p>Many times, I’m handed Frequently Asked Questions (FAQs) for a new product, which confuses and amazes me. How can these be frequently asked when a product has not even yet been released? The answer is that a product team will draw from their imagination to create answers for questions they believe will be asked, and that’s perfectly valid but let’s call it what it is, draft support content for a product that can be used for public consumption but will need to be validated, reviewed and updated on the basis of actual questions asked by customers.</p><p>Being the last item on a production creation list, this is the most frequent thing I see. Here, I completely agree with the basic tenants of content design (or good writing, as I prefer to call it). Ideally, those charged with creating help content should be engaged as early as possible so they can understand the end-users needs and who those end-users are, and then layer on the brand style and ensure the information is presented with as much clarity and simplicity as possible.</p><p>Sadly, this is often not the case (see FAQs as mentioned), which I find confusing as when the Help content team are involved early, they make life easier for the product team by fulfilling their role and removing that task from the shoulders of the product team, ensuring the end-user is front and centre, and aligning the help content to the product’s context.</p><p><strong>On creation and administration</strong></p><p>Assuming the help content team is engaged early, the next phase is a combination of creation and management of the help content. As a product owner, this is where I should be earning my corn. I work to a model where every piece of content has these attributes:</p><ul><li>A unique ID, could be the URL but ideally a separate piece of meta data. This provides the opportunity to link public-facing content with internal content i.e. that used by agents as well as other public content — public product pages, community posts. This is where the product owner can have automated processes that pop up content reviews when needed, helping to ensure consistency, accuracy, and instill internal faith in the content. Especially if help is functioning more as a platform, serving not only internal and public consumers but also other services such as generative AI or NLP chatbots.</li><li>An owner, not the writer but instead someone who is the expert and can validate the facts, not the style — that’s the Help writer’s role.</li><li>A review date — when does this content need to be checked/reviewed? This is often selected from somewhere on a sliding scale from a fixed date (i.e. competition info or terms &amp; conditions) through to a date based on an understanding of the life of the content. By which I mean, if it’s a product that rarely changes, such as a piece of hardware, then 6 months might suffice. Whereas, if it’s a fast-moving or evolving product, then 1–3 months might be better. With each review, the fact-checker and the help writer can co-ordinate and review that date so that the same piece doesn’t come around for review more often than is really needed.</li></ul><p>As mentioned at the start, I’ll go into more detail on each phase in future chapters, covering each in more detail and outline opportunities where dedicated tools are needed — content admin. And, of course, I welcome any and all feedback and questions.</p><p>See you next time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=870bd4222b16" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>