L5: Role & Script Theory

--- [0:00] Recap & Learning Outcomes --- Good morning. Last class we unpacked the elements of risk in services — why customers feel uncertain, what types of risk they experience, and how service firms can reduce perceived risk through branding, information, guarantees, and standardisation. We used Dudhsagar treks as our anchor. Today we're doing something that I personally find one of the most intellectually interesting topics in this course: Role and Script Theory. This is borrowed from sociology and social psychology, and it does a remarkable job of explaining why service interactions work when they work — and why they feel so uncomfortable when something goes wrong. Today's anchor idea: every service encounter is a performance, and both customer and service provider are playing scripted roles. When the script breaks down, the experience breaks down. --- [5:00] Core Concepts: Role Theory and Script Theory --- Let's start with role theory. The concept comes from Erving Goffman, a sociologist who wrote about social life as a kind of theatrical performance. In his framework, all of us play different roles in different social contexts — we behave differently at home, at work, in a temple, in a mall, at a cricket match. Each context has a set of expected behaviours associated with it. In services marketing, we apply this to the service encounter. Both the service provider and the customer have roles to play. The service provider's role is shaped by training, organisational culture, and customer expectations. The customer's role is shaped by their prior experiences, cultural norms, and the cues they receive from the service environment. When both parties perform their roles competently and consistently, the service encounter is smooth. When either party steps outside their expected role — whether intentionally or by mistake — discomfort, confusion, or conflict arises. Now, script theory extends this idea. A script is a cognitive structure — a mental map that tells us the expected sequence of events in a given situation. We all have scripts for common service encounters. Think about your script for visiting a doctor. You arrive and give your name at reception. You sit in the waiting area. You're called. You go in, the doctor is at their desk. They ask what's wrong. You explain. They examine you. They prescribe or advise. You leave and collect medication. Every step is scripted. You know what's coming next, and so does the doctor. Now imagine the doctor stands up and gives you a hug when you walk in. Scripted — violation. You'd be startled, confused, maybe alarmed. Even though a hug is a perfectly warm gesture in many social contexts, it's outside the service script for a medical consultation. The script violation creates discomfort. --- [20:00] Deep Dive: Script Theory at a Bank Branch in Panaji --- Let me walk you through a really concrete example from right here in Goa. Imagine a customer walks into a bank branch in Panaji — let's say an SBI or a Goa-based cooperative bank — to open a new account. What's the customer's script? I walk in, I find the relevant counter, I take a number if needed, I speak to a bank officer, I submit my KYC documents, I sign some forms, I receive my account details. Clean, sequential, predictable. Now, what are some common script violations that happen in Indian bank branches? Script violation one: The counter has no sign indicating what it handles. The customer doesn't know where to go. First step of the script fails. Frustration begins immediately. Script violation two: The bank officer asks for a document the customer didn't bring because it wasn't listed anywhere. The customer's script assumed they had everything needed. Now the script is broken — they have to leave, get the document, come back. Temporal risk, frustration, possible embarrassment. Script violation three: The officer leaves the counter in the middle of processing to attend to something else without explanation. The customer's script expects continuous, dedicated attention during the transaction. The abandonment feels like a role violation — the officer has stepped out of their "dedicated service provider" role. Now here's a powerful managerial insight: script violations are often the root cause of customer complaints. When a customer complains that the service was "confusing," "unprofessional," or "disorganised," what they're usually describing is a series of script violations — moments when the encounter didn't match their mental model of how it should have gone. And as managers, what's the solution? Script design. Deliberately think through every step of your service process, anticipate where scripts might break, and either: one, adjust the process to prevent the violation; two, adjust customer expectations in advance so their script includes the non-standard element; or three, train staff to communicate the deviation before it happens. Let me give you an example. If your bank requires an obscure document that customers commonly don't bring, put it on your website, your printed pamphlet, and a sign at the entrance. Now the customer's script includes bringing that document. No violation. --- [35:00] Case / Field Connection --- This connects beautifully to something we see in Indian retail banking. Banks that are doing customer experience well are essentially doing sophisticated script management. HDFC Bank's branch redesign initiatives, Kotak Mahindra's digital-first approach — what they're doing is simplifying and clarifying the service script for customers, reducing the number of potential violation points. And here's an interesting dimension to add: cultural scripts. In Goa, we have a beautifully multicultural service environment. Goan tourists include domestic visitors from Maharashtra, Karnataka, Gujarat, Delhi, and increasingly large numbers of international tourists from Russia, UK, Germany, Israel. Each customer group brings a different cultural script for service interactions. The typical Russian tourist's script for beach service is quite different from the typical Mumbaikar's script, which is quite different from a German tourist's script. The Russian customer might be comfortable with very minimal service interaction. The Mumbaikar might expect quick, efficient attention. The German tourist might have a very detailed script about transparency of pricing and process. Goan service providers who understand this — who can flexibly adapt their service performance to match the cultural scripts of different customer segments — are the ones who get five-star reviews across the board. Those who apply one fixed script to every customer type will inevitably create violations for segments whose scripts differ. So let me ask you all: have you ever been in a service situation — as a customer or as a worker — where you could feel that the script was breaking down? What happened? How did either party try to repair it? --- [45:00] Class Activity --- Let's do an activity. Working in pairs, I want you to write out the full script for one of the following service encounters: checking into a domestic flight at Dabolim Airport, or ordering a meal at a sit-down restaurant in Goa. Write every step — what the customer does, what the service provider does, in sequence. Then identify three places where the script could plausibly break down. And for each, write one sentence on how the service provider could either prevent the violation or recover from it. Ten minutes. Go. Okay, let's hear from the airport group first. Interesting — you've noted the check-in script has at least eight distinct steps, and the most common violation points are at baggage check (unexpected rules about weight), security (items customers didn't know were prohibited), and gate changes (the script includes going to the right gate, but changes break it). Excellent observation. And the solutions? Better communication upfront — clear baggage rules, prominent prohibited items list, proactive gate-change announcements. All of this is script management. Restaurant group — yes, the most interesting point you raised is when the item a customer orders is not available. That's a script violation — the customer's script includes "I order, I receive." The recovery script is critical: how the waiter communicates the unavailability, whether they suggest an alternative, whether they apologise with warmth — all of this determines whether the violation becomes a complaint or is absorbed gracefully. --- [55:00] MCQ Recap & Assignment Brief --- Today's anchor: every service encounter is a performance. Both parties play roles. When the script breaks down — at a bank branch in Panaji, at a hotel, at a clinic — the experience breaks down. But that script breakdown is also an opportunity, if you have a recovery script ready. Assignment: observe one complete service encounter — physically, in person. Write a script analysis. What was the expected script? Where did it deviate? How did the service provider respond to deviations? One to two pages. Due next class. Next time: Flowcharting Service Usage — we get technical and map service processes as blueprints. It's an incredibly practical tool for service design and improvement. See you then.