<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>SelfService on Chido Dike</title>
    <link>https://blog.chido.me/tags/selfservice/</link>
    <description>Recent content in SelfService on Chido Dike</description>
    <image>
      <title>Chido Dike</title>
      <url>https://blog.chido.me/og-default.png</url>
      <link>https://blog.chido.me/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Nov 2026 09:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.chido.me/tags/selfservice/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Service That People Actually Use</title>
      <link>https://blog.chido.me/posts/self-service-people-use/</link>
      <pubDate>Mon, 16 Nov 2026 09:00:00 +0000</pubDate>
      <guid>https://blog.chido.me/posts/self-service-people-use/</guid>
      <description>&lt;p&gt;Every service desk I&amp;rsquo;ve worked with has a self-service portal. Very few have one that people choose over picking up the phone.&lt;/p&gt;
&lt;p&gt;The usual story goes like this. We build the portal, fill it with forms and knowledge articles, announce it, and watch adoption flatten at a number nobody wants to say out loud. Then someone says the users just need training. They don&amp;rsquo;t. The portal is telling us something.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
