IT self-service portal -
implementation and adoption strategy

The self-service portal is live - but nobody uses it. Employees email the help desk instead of clicking "reset password" in the portal. The fix is a deliberate adoption strategy, not just turning the portal on and waiting. In this article I break down a 5-phase plan that helps durably increase portal adoption.

5-phase self-service portal adoption strategy

Phase 1 (Weeks 1-2): Preparing the portal

• Knowledge base content must be complete - prepare articles for the most common matters (password reset, hardware request, new employee onboarding)
• The portal must be fast and easy - a few clicks to submit a request
• Search must work - type "laptop" and articles about ordering a laptop should appear
• Mobile-friendly - employees may be on a phone

Phase 2 (Weeks 3-4): Awareness campaign

• Email to everyone: "The portal is open. Instead of emailing - use the portal. Faster and more transparent."
• Posters in the office: "Need help? Log in to the portal [link]"
• A 2-minute video: "How to change your password in the portal" - share it on Slack/Teams
• Lunch event: the IT team is present in the office to show how the portal works

Phase 3 (Weeks 5-8): Folding the portal into the workflow

• When an employee emails helpdesk@..., send an auto-reply: "Please submit your request via the portal [link]. It will be handled faster."
• The IT team does not handle requests by email - only via the portal. That forces adoption.
• Email notifications from the portal: "Your request SR-1234 is ready, please log in"

Phase 4 (Weeks 9-12): Gamification and incentives

• Leaderboard: "This department used 45 self-service requests - a record!" - monthly report by email
• Contest: "Every employee who submits 5 requests via the portal enters a draw for a coffee laptop accessory"
• Recognition: "Top users" called out on Slack - "Pawel submitted 20 self-service requests - saved the help desk 10 hours of work!"

Phase 5 (Months 4-6): Continuation and optimization

• Track adoption metrics - monthly reports (% self-service vs email)
• A/B test: try different FAQ questions, see which articles people read
• Update the knowledge base based on feedback ("we are missing an article about X")
• Communicate progress: show the team how the share of tickets handled through the portal is growing compared with previous months

Best practices for high adoption

• Mobile first: some employees use the portal on a phone - it must work well on mobile devices
• Search front and center: many users prefer searching to browsing categories - the search field should be clearly visible on the home page
• Fast approvals: long waits for approval discourage portal use
• Transparency: the employee must see the request status - "Pending approval", "In progress", "Ready"
• Feedback loop: after closing a request, run a survey ("Was the portal easy to use?") and optimize based on feedback

Adoption metrics

KPI #1: Self-service adoption rate - the share of tickets submitted through the portal. Set the target individually and monitor the trend - it should be growing.

KPI #2: Portal page views over time - how often employees use the portal. Expected direction: upward trend.

KPI #3: Time spent on the portal - a short time to handle a matter signals that the portal is easy to use.

KPI #4: Reduction in help desk tickets - whether the number of tickets reaching the help desk is going down. Measure this by comparing periods before and after the rollout.