I took a “Service Management” course at business school. I’ll be looking back on the learnings from all six sessions in a series. This is the first installment.
When I first heard “Service Management,” I honestly assumed it would be a course about hospitality — how to serve guests at hotels and restaurants. As someone who had spent her entire career in IT infrastructure, it felt like a world away from my own.
That assumption was shattered in the very first lecture. “Service exists within every business.” That was the starting point of this course.
Why Would an IT Manager Study “Service Management”?
I work as a delivery manager at an IT vendor. My job is delivering system design, implementation, and operations to clients.
This work is, in fact, a service in its purest form. Clients can’t verify the quality of a system before they “buy” it. Project outcomes vary depending on team members’ skills and condition. A delivered system can’t be inventoried. All of these correspond to the characteristics of services.
Yet in the IT industry, the perspective of “how do we manage our work as a service?” rarely comes up. We have project management methodologies and technical discussions, but there’s been little opportunity to learn a systematic framework for service business management. ITIL exists as a service management framework, but its focus is primarily on process standardization — a somewhat different conversation from how to leverage the fundamental nature of services in business strategy.
That’s precisely why I chose this course. And it turned out to be the right call.
Breaking Free from the “Product Mindset”
The lecture opened with G. Lynn Shostack’s concept of “Breaking Free from Product Marketing.” In her 1977 paper, Shostack argued that applying product (tangible goods) marketing methods to services is fundamentally flawed.
Traditional marketing theory assumes mass-produced goods from a factory. The 4Ps (Product, Price, Place, Promotion) are essentially a framework for selling physical things. But services have no physical form, can’t be stored as inventory, and their quality isn’t consistent. Applying the logic of goods directly to services leads to a fundamental misunderstanding.
This critique hit close to home for someone in the IT industry. We constantly use terms like “deliverables” and “artifacts.” But in reality, the bulk of an IT project’s value lies in the process itself — dialogue with the client, translating requirements, coordinating between teams. Deliverables are merely the crystallization of that process, not the whole picture. Rather than viewing services as an extension of products, we need to think about them using service-specific logic. This shift in perspective was the foundation of this course.
The “Four Characteristics” of Services
The first thing to understand when studying Service Management is the four characteristics that services possess. These are also abbreviated as “IHIP.”
1. Intangibility
Services can’t be seen or touched before purchase. You can’t taste a restaurant meal before ordering, and you won’t know the quality of consulting until you’ve engaged the firm. Insurance provides no tangible value until an incident occurs, and you can’t tell if an educational service suits you until you’ve actually taken the course.
This is precisely why service providers must find ways to communicate benefits in advance. Reviews, case studies, free trials — these are all means of overcoming the barrier of intangibility. When luxury hotels fill their websites with beautiful photos, or consulting firms publish case studies, they’re attempting to “make the invisible visible.”
Intangibility has another tricky dimension: since customers can’t evaluate quality beforehand, “trust” becomes the deciding factor in service selection. That’s why track records, reputation, and branding matter even more than they do for physical goods. When choosing a doctor, you can’t see their technical skill directly, so you rely on credentials, experience, and reviews.
2. Inseparability (Simultaneity)
Services are “produced” and “consumed” simultaneously. A haircut at a salon is consumed the moment it’s performed. Unlike manufacturing, you can’t produce it in advance and deliver it later. A doctor’s examination, a teacher’s lesson, a lawyer’s advice — all are provided and consumed on the spot.
This means that service facilities need to be located close to customers, and that the quality of frontline staff directly determines the success or failure of the service. This requires a fundamentally different management approach from factory quality control.
Inseparability also means that the customer becomes a “co-producer” of the service. How well you communicate your preferences at a hair salon affects the outcome. If you can’t accurately describe your symptoms at a hospital, the correct diagnosis becomes harder to reach. Service quality depends not only on the provider but also on the degree of customer participation. This concept of “co-production” maps directly onto requirements definition in the IT industry — it resonated deeply with me.
3. Variability (Heterogeneity)
The content of a service changes depending on who provides it, when, and where. Even the same staff member at the same establishment may deliver differently on a Monday morning versus a Friday evening. A veteran nurse inspires different levels of confidence than a newcomer, and the same instructor’s class quality can fluctuate based on their condition or the audience’s engagement.
The flip side is that customization comes naturally to services. While uniform quality control is difficult, the ability to tailor the experience to each individual customer can be a genuine strength. A bartender who remembers a regular’s favorite drink, a doctor who adjusts their explanation style to match a patient’s personality — these approaches of “turning variability into a weapon” create service differentiation.
At the same time, efforts to control variability are necessary. Manuals, training, technology adoption — the fact that fast-food chains achieve uniform quality worldwide is the result of aggressively suppressing variability through standardization. Where to strike the balance between standardization and personalization is a fundamental question in service design.
4. Perishability
Services can’t be inventoried. A hotel’s empty room can’t be carried over to the next day. An airplane’s empty seat vanishes the moment it takes off. A stylist sitting idle during a slow period can never reclaim that time. Concert seats, taxi idle time — all perish the moment they go unused.
That’s why managing the balance between supply and demand is the lifeline of service businesses. Staff are deployed to match peak times, and promotions stimulate demand during slow periods. Airlines’ yield management (adjusting seat pricing in real-time based on demand), restaurant happy hours, hotel early-bird discounts — these are all supply-demand adjustment mechanisms designed to cope with perishability.
Perishability poses another critical question: should you design capacity for peak demand or for average demand? Design for peak, and resources sit idle during off-peak times. Design for average, and service falls short during peak times. This supply-demand calibration is where service businesses demonstrate their strategic prowess.
The Four Characteristics Are Both Challenges and Opportunities
Reading this far, services might seem disadvantaged compared to manufacturing. Quality fluctuates, inventory is impossible, you can’t demonstrate the product in advance…
But what the lecture emphasized was this: “Turning these challenges into opportunities is the art of service management.”
Because of intangibility, you can differentiate through the design of the experience itself. Because of inseparability, you can create moments of delight at customer touchpoints. Because of variability, personalized attention becomes a competitive weapon. Because of perishability, companies that excel at demand management gain an overwhelming advantage.
Whether you view the four characteristics as “constraints” or “sources of differentiation” — that difference in perspective separates good service management from great. For example, eliminating variability entirely and perfecting manual-based operations is one strategy. Conversely, maximizing variability to sell a “you can only get this here” personal experience is another. There is no single right answer; it needs to be tailored to your company’s positioning.
Applying This to IT Work
What I learned mapped directly onto my own work.
Intangibility: Clients place orders before seeing the finished system. That’s why proposals and prototypes are needed to “communicate the benefits” — this is precisely a response to intangibility. In a past project, we invested heavily in preparing prototype demos during the proposal phase, making the completed vision as concrete as possible. That alone dramatically reduced the client’s anxiety and helped us win the contract. Conversely, even a technically flawless proposal fails to move a client if it doesn’t convey “what they’ll get.” To overcome intangibility, I’ve found it extremely effective to include abundant screenshots and flow diagrams in proposals, visualizing “what the finished product will look like.”
Inseparability: System development progresses through collaborative work with the client. Requirements definition meetings, test witnessing — production and consumption happen simultaneously. That’s why the quality of team members at customer touchpoints directly determines project success. On one project, we assigned an engineer with strong technical skills but weak communication abilities to a client-facing role. The result was frequent misalignments in requirements understanding. The essence of inseparability is that “value is determined on the spot” — customer-facing positions require people who combine both technical ability and communication skills.
Variability: Even using the same framework, quality differs depending on which engineer handles the work. You can never eliminate the human factor entirely. That’s precisely why balancing standardization with individual discretion matters. On my team, we standardize processes like code reviews and design reviews to mitigate variability risk, while leaving room for individual engineers to exercise judgment in technology selection. Lock things down too tightly and creativity dies. Allow too much freedom and quality becomes inconsistent. This balancing act is the very essence of service management.
Perishability: Project team members’ availability can’t be “inventoried.” Unallocated time is gone forever. The importance of resource management is precisely a perishability problem. If bench time (time unassigned to projects) drags on, only costs accrue for the company. Conversely, if all team members are running at 100% utilization, the ability to respond to sudden project changes or new engagements is lost. Keeping utilization around 85-90% is the typical balance, and this is itself a strategy for dealing with perishability.
In the IT industry, our eyes tend to focus on technology and processes. But when I reexamined our work through the lens of the four service characteristics, management priorities suddenly became clearer. And above all, the shift in mindset — “we’re not building things; we’re delivering services” — felt like it could reshape everyday decision-making.
Recommended Reading for This Session
To deepen your understanding of the four characteristics of services and Shostack’s “Breaking Free from Product Marketing,” the following book is an excellent resource.
“Mastering Service Is Mastering Business” (サービスを制するものはビジネスを制する) by Hidehiko Yamaguchi, GLOBIS Graduate School of Management, Toyo Keizai — A comprehensive guide to the fundamental frameworks of Service Management. This book aligns well with the course content at GLOBIS, covering everything from the four characteristics of services to the Service Profit Chain and service design, presented in an accessible way for practitioners. It works equally well as preparation or review for the course, and as a foundation-builder for managers working in service businesses.
Coming Up Next
The first lecture covered another major theme: Customer Satisfaction (CS) Management. How much difference does “satisfaction” versus “delight” make in repeat rates? What are the three barriers to implementing CS management? I’ll cover that in the next installment.