Q: 7
A service provider is implementing a new self-service portal for users to request access to IT services.
The portal will be made available to 5000 users across 50 sites.
Which is the BEST guidance for producing guidelines for users of the self-service portal?
Options
Discussion
C imo, guidelines should be straightforward for end users, not overloaded with details.
I think C is best for a new portal with so many users. If this was just an upgrade or if users already knew the old system, then D could be more useful to highlight the changes, but here you need clarity first. Agree?
C . Official guide always highlights user-centric and simple communication, especially at this scale. If you check some practice exam feedback, most suggest keeping it concise for higher adoption. Open to counterpoints if anyone has seen another approach in real ITIL examples.
C . Had something like this in a mock. With 5000 users, you want concise, simple instructions so everyone actually reads them, and making the exception contacts clear cuts down on confusion. Detailed docs (A) just get ignored. Anyone think otherwise?
Option C, Simple guidelines plus clear escalation for exceptions just makes sense with that many users, not totally sure but seems right.
C, Had something like this in a mock, always picked simple user guidelines for a fresh rollout.
Why not D? Feels like that’s only helpful if users already know the old process and just need changes.
A tbh
C is what I'd pick. Keeping the guidelines simple helps more users get started without confusion, and pointing out who to contact for exceptions is practical for the rollout size. Pretty sure that's what ITIL would recommend for value delivery. Disagree?
Think it should be A for this situation.
Be respectful. No spam.