{"id":28,"date":"2026-01-08T10:20:45","date_gmt":"2026-01-08T07:20:45","guid":{"rendered":"https:\/\/ruck.nz\/?p=28"},"modified":"2026-01-08T10:31:31","modified_gmt":"2026-01-08T07:31:31","slug":"2-3","status":"publish","type":"post","link":"https:\/\/ruck.nz\/?p=28","title":{"rendered":"2.3."},"content":{"rendered":"\n

Now let\u2019s look at the concept of products and services in ITIL.<\/p>\n\n\n\n

In ITIL, a product is a configuration of an organisation\u2019s resources designed to offer value to a consumer.<\/p>\n\n\n\n

Products are used by service providers to deliver services.<\/p>\n\n\n\n

A service is enabled by one or more products.<\/p>\n\n\n\n

Customers do not usually consume products directly.<\/p>\n\n\n\n

Instead, they consume services that are enabled by those products.<\/p>\n\n\n\n

A service offering is a description of one or more services, designed to meet the needs of a specific consumer or group of consumers.<\/p>\n\n\n\n

Service offerings describe what the service does, how it is delivered, and what value it provides.<\/p>\n\n\n\n

Understanding the relationship between products, services, and service offerings is important for effective service management.<\/p>\n\n\n\n

\n\n\n\n

2. How this applies to TakeCars<\/strong> (car-rental marketplace)<\/h2>\n\n\n\n

This distinction is crucial<\/strong> for understanding why marketplaces scale\u2014or fail.<\/p>\n\n\n\n

a) Cars are products; mobility is the service<\/h3>\n\n\n\n

From an ITIL perspective:<\/p>\n\n\n\n

    \n
  • Products<\/strong> in TakeCars:\n
      \n
    • Vehicles<\/li>\n\n\n\n
    • Booking system<\/li>\n\n\n\n
    • Payment infrastructure<\/li>\n\n\n\n
    • Support tools<\/li>\n\n\n\n
    • Supplier contracts<\/li>\n<\/ul>\n<\/li>\n\n\n\n
    • Service<\/strong>:\n
        \n
      • Reliable, low-friction temporary mobility<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

        Customers do not<\/strong> want a \u201c2019 Corolla Hybrid\u201d.
        They want transport that works<\/strong>.<\/p>\n\n\n\n

        Confusing products with services leads to feature bloat and poor prioritisation.<\/p>\n\n\n\n

        \n\n\n\n

        b) Service offerings explain pricing tiers<\/h3>\n\n\n\n

        Service offerings in TakeCars could be explicitly framed as:<\/p>\n\n\n\n

          \n
        • \u201cBudget city rental\u201d<\/li>\n\n\n\n
        • \u201cFamily road-trip ready\u201d<\/li>\n\n\n\n
        • \u201cBusiness-ready pickup\u201d<\/li>\n\n\n\n
        • \u201cLong-term monthly rental\u201d<\/li>\n<\/ul>\n\n\n\n

          Each offering:<\/p>\n\n\n\n

            \n
          • Uses the same underlying products<\/li>\n\n\n\n
          • Packages value differently<\/li>\n\n\n\n
          • Targets a different perception of value<\/li>\n<\/ul>\n\n\n\n

            This explains why identical cars can justify different pricing and rules.<\/p>\n\n\n\n

            \n\n\n\n

            c) Why TakeCars should design offerings, not listings<\/h3>\n\n\n\n

            Listings describe products<\/strong>.
            Offerings describe outcomes<\/strong>.<\/p>\n\n\n\n

            ITIL logic suggests TakeCars should shift emphasis from:<\/p>\n\n\n\n

              \n
            • Specs, years, engine size<\/li>\n<\/ul>\n\n\n\n

              Toward:<\/p>\n\n\n\n

                \n
              • Use cases<\/li>\n\n\n\n
              • Risk removal<\/li>\n\n\n\n
              • Predictability<\/li>\n\n\n\n
              • Support guarantees<\/li>\n<\/ul>\n\n\n\n

                That is where margin and trust live.<\/p>\n\n\n\n

                \n\n\n\n

                3. Key ideas to read right before the exam<\/strong> (high-yield)<\/h2>\n\n\n\n

                This topic appears frequently as definition-matching<\/strong> questions.<\/p>\n\n\n\n

                Core definitions (recognise instantly)<\/h3>\n\n\n\n
                  \n
                • Product<\/strong>A configuration of an organisation\u2019s resources designed to offer value to a consumer.<\/li>\n\n\n\n
                • Service<\/strong>Enabled by one or more products to facilitate outcomes.<\/li>\n\n\n\n
                • Service offering<\/strong>A description of one or more services designed to meet specific consumer needs.<\/li>\n<\/ul>\n\n\n\n
                  \n\n\n\n

                  Exam trap to avoid<\/h3>\n\n\n\n

                  Wrong answers often:<\/p>\n\n\n\n

                    \n
                  • Say customers consume products<\/li>\n\n\n\n
                  • Blur products and services<\/li>\n\n\n\n
                  • Ignore service offerings entirely<\/li>\n<\/ul>\n\n\n\n

                    Correct answers:<\/p>\n\n\n\n

                      \n
                    • Separate products from services<\/li>\n\n\n\n
                    • Emphasise consumer-facing descriptions<\/li>\n\n\n\n
                    • Focus on value and outcomes<\/li>\n<\/ul>\n\n\n\n
                      \n\n\n\n

                      Fast exam shortcut<\/h3>\n\n\n\n

                      If the question asks:<\/p>\n\n\n\n

                        \n
                      • \u201cWhat does the customer consume?\u201d \u2192 Service<\/strong><\/li>\n\n\n\n
                      • \u201cWhat enables the service?\u201d \u2192 Product<\/strong><\/li>\n\n\n\n
                      • \u201cWhat describes the service to customers?\u201d \u2192 Service offering<\/strong><\/li>\n<\/ul>\n\n\n\n
                        \n\n\n\n

                        One-line exam anchor<\/h3>\n\n\n\n
                        \n

                        Customers consume services, not products.<\/p>\n<\/blockquote>\n\n\n\n

                        Repeat this if you hesitate during the exam.<\/p>\n\n\n\n

                        \n\n\n\n

                        Ready for the next file<\/h2>\n\n\n\n

                        Upload the next SRT when ready.
                        We will continue with the same three-layer structure.<\/p>\n\n\n\n

                        You are now firmly inside the core conceptual engine<\/strong> of ITIL 4 \u2014 this is where most exam points are earned.<\/p>\n","protected":false},"excerpt":{"rendered":"

                        Now let\u2019s look at the concept of products and services in ITIL. In ITIL, a product is a configuration of an organisation\u2019s resources designed to offer value to a consumer. Products are used by service providers to deliver services. A service is enabled by one or more products. Customers do not usually consume products directly. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-28","post","type-post","status-publish","format-standard","hentry","category-1"],"_links":{"self":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/28","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=28"}],"version-history":[{"count":2,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/28\/revisions"}],"predecessor-version":[{"id":36,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/28\/revisions\/36"}],"wp:attachment":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=28"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=28"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=28"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}