This post is part of a worldwide flashbook or flashblog, where many contributors simultaneously publish on the topic of "My top tip for building a service catalogue".
Both service catalogue and service request catalogue matter - the order in which you address them and the relative priority you give them depends on the circumstances. Don't fall for the hype around service request catalogue right now. Click to tweet this.
A menu is not a service catalogue. Please can we desist with this awful analogy. It makes people think automated service requests is an "actionable service catalogue". It's not. It's an actionable request catalogue.
Not only has ITIL V3.1 2011 not fixed the problems with business-vs-technical services, they have gone the wrong way and reinforced the problem. I will fight to the death to say there is no such thing as internal supporting "services", because I care about ITSM.
Why are so many sample Business Service Catalogues so hideously boring? - dull and analytical. They should be written by marketing people: they should be brochures. Bright and colourful, creating a positive impression, selling the benefits.
If your service catalogue says you provide application "hosting", your IT department is committing organisational suicide. You need to be an Information Service Provider.