Operations, Organization and Digital Transformation

Introduction

An OTT service is often described as a technology platform, but its competitive performance depends equally on operations and organization. A catalogue is valuable only when rights are secured, media is technically prepared, metadata is accurate, content is localized, policies are applied consistently, publication is reliable, and customers can obtain help when something fails. These activities form an interconnected operating system rather than a series of isolated departments.

For legacy media organizations, the challenge is even greater. A broadcaster, newspaper group, film studio, or cable operator may possess strong editorial capabilities and valuable brands, but its inherited workflows may be designed for periodic release, physical distribution, advertising sales, or linear scheduling. OTT requires continuous publishing, data-informed decisions, rapid experimentation, software-enabled distribution, and direct relationships with audiences.

This chapter examines the design of OTT workflows, organizational forms, vendor management, capability development, and digital transformation. It treats transformation as a strategic and socio-technical process: new tools matter, but so do decision rights, incentives, skills, governance, and culture.

Learning Objectives

By the end of this chapter, students should be able to:

1. Map the end-to-end OTT operating workflow from acquisition to customer support.
2. Explain how metadata, localization, moderation, quality assurance, and publishing affect discoverability and trust.
3. Compare functional, matrix, product, and agile organizational arrangements.
4. Design basic vendor-governance and capability-development systems.
5. Analyze the transformation of a legacy media organization into a digital and OTT operation.
6. Evaluate operational risks, ethical issues, performance indicators, and the appropriate use of automation and AI.

1. The OTT Operating Model

An operating model explains how an organization converts strategic intent into repeatable work. In OTT, it connects five elements:

• Value proposition: the audience experience the service promises.
• Capabilities: what the organization must be able to do reliably.
• Processes: the sequence and controls through which work is performed.
• Technology: platforms, tools, data systems, and integration interfaces.
• Governance: who decides, who is accountable, and how risks are controlled.

A useful distinction is between the value chain and the operating workflow. The value chain identifies broad activities such as content creation, distribution, marketing, and service. The workflow specifies operational steps, inputs, outputs, owners, approvals, and exception handling.

OTT operations are characterized by four conditions. First, content is released across multiple devices and territories. Second, the catalogue is continuously changing. Third, customer experience depends on both editorial and technical performance. Fourth, decisions increasingly use behavioural data. Consequently, an OTT organization must coordinate creative judgment, rights management, software engineering, data analysis, operations, and customer care.

Core workflow stages

These stages should not be treated as strictly linear. Customer complaints may reveal metadata defects; rights changes may require immediate unpublishing; audience data may influence future acquisition and production. Effective OTT operations therefore combine a controlled pipeline with feedback loops.

2. Acquisition and Rights Operations

Acquisition begins with a strategic content requirement, not merely a list of attractive titles. The organization should define the target audience, genres, languages, territories, release windows, exclusivity requirements, expected consumption, and commercial constraints before negotiating.

A rights-management record should identify at least:

• licensor, producer, and relevant ownership parties;
• permitted territories and excluded territories;
• start and end dates;
• platforms, devices, and distribution modes;
• language, subtitle, dubbing, and accessibility rights;
• promotional, trailer, clip, and social-media rights;
• exclusivity, embargo, and windowing provisions;
• music, talent, image, and archival clearances;
• takedown, renewal, audit, and reporting obligations.

A title cannot be safely published simply because a contract exists. Rights must be translated into machine-readable availability rules and operational calendars. A rights-operations team should reconcile contracts, business terms, content-management systems, and territory settings. The principle of rights truth is important: the catalogue should reflect what the organization is legally entitled to make available, not what a spreadsheet or employee happens to assume.

Acquisition decision quality

Managers can compare opportunities using a disciplined business case. Relevant factors include expected audience value, strategic fit, exclusivity, duration, localization expense, technical preparation, marketing cost, and legal risk. Forecasts are uncertain; therefore, decision-makers should use scenarios rather than presenting a single forecast as fact. A low, central, and high case can reveal whether a proposal remains attractive under adverse conditions.

The cost of an acquisition is also more than the licence fee. Total landed cost may include delivery, quality control, captioning, dubbing, artwork, ratings, storage, marketing, payment fees, and customer-support demand. Separating these cost categories prevents underestimation and improves post-launch evaluation.

3. Production, Media Supply Chain and Quality Assurance

OTT production includes original commissioning, co-production, acquisition delivery, versioning, encoding, packaging, and archival management. A professional media supply chain uses defined specifications and acceptance criteria.

A delivery specification may cover resolution, frame rate, aspect ratio, audio channels, loudness, colour space, captions, timed-text formats, naming conventions, checksums, artwork dimensions, and documentation. Specifications should be proportionate to distribution needs. Requiring an unnecessarily high technical standard can increase cost without improving customer value; accepting inadequate masters creates rework and reputational risk.

Quality assurance generally includes:

1. Technical QC: picture, sound, synchronization, encoding, captions, and file integrity.
2. Editorial QC: title, episode order, synopsis, ratings, artwork, and language accuracy.
3. Rights and compliance QC: territory, window, music, talent, advertising, and regulatory conditions.
4. Device and playback testing: representative televisions, mobiles, browsers, operating systems, and network conditions.
5. Post-publication monitoring: playback errors, subtitle complaints, and catalogue anomalies.

Quality assurance should use risk-based sampling. High-profile originals, live events, children’s material, and content with complex rights may require more extensive review than routine catalogue updates. A defect-management system should record severity, owner, due date, root cause, corrective action, and recurrence.

4. Metadata as an Operating Capability

Metadata is structured information about content. It includes title, synopsis, cast, crew, genre, themes, language, country, release date, age rating, accessibility features, relationships between seasons and episodes, and rights availability. It is both an editorial resource and a technical control layer.

Metadata performs four major functions:

• Discovery: helps users search, browse, and receive recommendations.
• Context: tells audiences what a programme contains and who may view it.
• Distribution: determines where, when, and in what form content is displayed.
• Measurement: provides consistent labels for catalogue and performance analysis.

A metadata workflow should establish a controlled vocabulary, mandatory fields, validation rules, approval roles, version history, and correction procedures. Free-text descriptions may be useful editorially, but uncontrolled labels create duplication and inconsistent analytics. A data dictionary should explain each field, allowed values, ownership, and downstream use.

Metadata quality has several dimensions: completeness, accuracy, consistency, timeliness, uniqueness, and fitness for purpose. These dimensions may conflict. Highly detailed tagging can improve discovery but increase preparation time and introduce subjective disagreement. The appropriate level of detail depends on audience need, editorial strategy, accessibility, and system capability.

AI can assist with speech-to-text transcription, entity extraction, translation drafts, scene detection, and classification. However, automated output must be reviewed where errors could mislead audiences, expose sensitive information, create discriminatory labels, or violate rights. Human accountability remains necessary for ratings, sensitive descriptors, cultural interpretation, and legal claims.

5. Localization, Accessibility and Cultural Adaptation

Localization is broader than translation. It adapts content and its surrounding presentation to a language and cultural market. Activities may include subtitles, dubbing, voice-over, artwork, synopsis, title treatment, ratings, content warnings, payment language, and customer-support scripts.

A localization workflow normally includes source preparation, translation or adaptation, linguistic review, timing and technical integration, cultural review, quality assurance, and final approval. Subtitling requires attention to reading speed, line length, speaker identification, timing, and meaning. Dubbing adds casting, performance direction, lip synchronization, recording, mixing, and regulatory considerations.

Accessibility is a service obligation and a design principle. Closed captions, subtitles for the deaf and hard of hearing, audio description, accessible navigation, keyboard support, readable contrast, and appropriate player controls expand participation. Accessibility assets should be planned during acquisition and production rather than treated as an emergency afterthought.

Localization vendors should be assessed not only on price and turnaround, but also on linguistic competence, cultural knowledge, security, reviewer independence, accessibility expertise, and ability to handle corrections. Back-translation or independent review may be appropriate for high-risk content, but quality processes must avoid treating one language or culture as the unquestioned standard.

6. Moderation, Trust and Safety

Moderation determines whether content and user behaviour comply with law, platform policy, contractual obligations, and organizational values. OTT services may moderate editorial content, user-generated material, comments, reviews, profile names, thumbnails, and customer communications.

A defensible moderation system includes:

• clearly published rules and definitions;
• classification of severity and urgency;
• trained reviewers and escalation specialists;
• evidence preservation and decision records;
• appeals or review mechanisms where appropriate;
• safeguards for moderator wellbeing;
• consistent treatment across languages and markets;
• regular policy review and audit.

Automation can prioritize queues, identify likely spam, detect duplicates, and flag potentially harmful material. It should not be assumed to understand context reliably. Satire, documentary evidence, artistic expression, political speech, and culturally specific language can be misclassified. Human review is particularly important for irreversible actions, ambiguous cases, vulnerable groups, and high-impact decisions.

Moderation also raises governance questions. Who defines harm? How are laws in different territories reconciled? How are errors corrected? What transparency can be offered without enabling abuse? An organization should distinguish legal removal, contractual restriction, age-gating, recommendation demotion, and editorial disagreement; these are different interventions with different justifications.

7. Publishing and Customer Support

Publishing is the controlled release of an asset to a defined audience. A release checklist may verify media readiness, metadata, subtitles, artwork, rights window, age rating, payment status, device compatibility, promotional placement, and rollback instructions.

For major launches, a release plan should identify a responsible owner, freeze times, deployment sequence, monitoring dashboard, communication plan, and incident commander. A staged rollout can reduce risk by releasing to a limited market or percentage of users before full availability. Rollback must be technically and organizationally possible; a team that can launch but cannot safely withdraw a defective release is not operationally mature.

Customer support is not merely a cost centre. It is a diagnostic channel linking audience experience to product and operations. Common contacts concern authentication, billing, playback, subtitle availability, device compatibility, parental controls, and content availability. Support records should be categorized consistently so that repeated failures can be routed to engineering, product, editorial, or rights teams.

Useful service indicators include first-response time, resolution time, repeat-contact rate, escalation rate, complaint themes, and customer satisfaction. These should be interpreted carefully. A short interaction is not necessarily a successful one, and satisfaction may be influenced by a policy the support agent cannot change. Operational metrics should therefore be combined with outcome evidence such as successful playback, reduced recurrence, and retention.

8. Organization Design: From Functions to Product Teams

Traditional media organizations often use functional structures: programming, production, marketing, technology, legal, finance, and customer service. Functional specialization creates expertise and accountability, but handoffs can slow delivery and encourage local optimization.

A matrix combines functional expertise with project or product responsibility. It can coordinate complex launches but may create ambiguity when a person has multiple managers. A product operating model organizes durable, cross-functional teams around customer or business outcomes, such as acquisition, playback, discovery, subscriptions, or retention. These teams may contain product management, design, engineering, data, operations, and subject-matter expertise.

Agile is not simply a meeting schedule or a collection of software tools. It is an approach emphasizing small increments, customer feedback, prioritization, transparency, and adaptation. Agile teams still require planning, documentation, compliance controls, architecture standards, and operational discipline. In OTT, agile delivery must coexist with fixed broadcast dates, contractual windows, regulatory obligations, and high-risk live events.

A useful design principle is to separate decision rights from execution roles. For example, a product manager may prioritize a discovery feature, legal may approve a rights interpretation, editorial may own programme positioning, and engineering may own technical implementation. A responsibility matrix can clarify who is accountable, responsible, consulted, and informed, but it should not replace real collaboration.

9. Vendor Management and Service Governance

OTT companies commonly rely on cloud providers, content-delivery networks, payment processors, localization houses, studios, customer-support outsourcers, measurement firms, and software vendors. Outsourcing a task does not outsource accountability. The platform owner remains responsible for customer impact, legal compliance, security, and service quality.

Vendor governance should cover:

1. due diligence on capability, financial stability, security, privacy, labour practices, and resilience;
2. a clear statement of work and measurable service levels;
3. data ownership, access control, retention, and deletion requirements;
4. incident notification and business-continuity obligations;
5. audit rights and evidence requirements;
6. intellectual-property, confidentiality, and subcontracting terms;
7. escalation paths and remediation procedures;
8. renewal, transition, and exit planning.

Service-level agreements should measure outcomes that matter. Availability may be important for a streaming platform, but a vendor’s high availability is not sufficient if playback failures, subtitle defects, or support delays remain high. Organizations should distinguish a service-level target from a contractual remedy and avoid selecting metrics that are easy to report but weakly related to audience value.

Concentration risk deserves attention. Dependence on one cloud, localization supplier, payment provider, or CDN may create efficiency but reduce resilience. Multi-vendor strategies are not automatically safer: they add integration and governance complexity. The appropriate choice depends on criticality, substitutability, switching cost, and the organization’s ability to operate alternatives.

10. Capability Development and Performance Management

Digital transformation requires capabilities, not just recruitment. A capability map identifies what the organization must perform well: rights operations, content supply-chain management, product management, data literacy, experimentation, platform engineering, cybersecurity, localization, trust and safety, and customer insight.

Capability development can combine formal training, mentoring, communities of practice, job rotation, documented playbooks, pair work, and post-incident learning. Training should be linked to observable performance. For example, metadata training may be evaluated through completeness and error rates, while incident-response training may be evaluated through detection, communication, and recovery performance.

Performance management must avoid harmful single-metric incentives. If a localization team is rewarded only for speed, quality may decline. If support agents are rewarded only for short handling time, unresolved contacts may increase. A balanced scorecard may include quality, timeliness, reliability, customer outcomes, risk control, and learning.

11. Digital Transformation of Legacy Media

Legacy transformation is not equivalent to placing existing programmes on a website. It usually involves changes in revenue logic, customer relationship, content economics, data practices, technology architecture, and organizational identity.

A transformation can be understood across four layers:

• Digitization: converting analogue or physical assets into digital form.
• Digitalization: improving existing processes with digital tools.
• Digital transformation: redesigning the operating model and value proposition around digital capabilities.
• Strategic renewal: changing the organization’s position, portfolio, and relationship with audiences.

Common barriers include fragmented archives, incompatible systems, rights uncertainty, broadcast-centric calendars, departmental power boundaries, limited product skills, and fear that direct-to-consumer activity will weaken existing partners. Transformation should therefore begin with a baseline assessment and a prioritized target state rather than a technology purchase.

A staged approach is often practical:

1. establish executive sponsorship and a measurable case for change;
2. inventory content, rights, systems, skills, data, and major pain points;
3. define the target customer journey and operating model;
4. build foundational capabilities such as identity, metadata, analytics, and release management;
5. pilot a bounded product or audience segment;
6. measure outcomes and learn before scaling;
7. retire redundant processes and systems deliberately;
8. institutionalize governance, skills, and continuous improvement.

Transformation should preserve valuable legacy strengths, including editorial judgment, production craft, trusted brands, archives, and community relationships. The objective is not to imitate a technology company in every respect, but to combine media strengths with digital operating discipline.

Applied Case: Northstar Public Media (Illustrative)

Background

Northstar Public Media (NPM) is a fictional regional broadcaster with a respected documentary archive, two television channels, and a growing youth audience. Its initial streaming application contains attractive programmes but has low monthly usage and frequent complaints about missing subtitles and confusing availability.

Problem

An internal review finds that acquisition contracts are stored in separate legal folders, metadata is entered differently by each department, localization begins only after launch dates are announced, and customer-support data is not shared with editorial or engineering. The organization plans to introduce a subscription tier but lacks confidence in its operational foundation.

Analysis

NPM maps its workflow and identifies four critical failure points. First, rights windows are manually interpreted, creating incorrect territory availability. Second, there is no controlled metadata vocabulary, so search and recommendation systems receive inconsistent labels. Third, localization is treated as a final production task rather than a release dependency. Fourth, support agents cannot distinguish a technical playback failure from a rights restriction.

The transformation team classifies these as operating-model problems rather than isolated employee errors. It creates a cross-functional catalogue product team, while retaining specialist communities in legal, editorial, engineering, and accessibility.

Approach and solution

NPM introduces a rights register connected to the content-management system, with mandatory territory and date fields. It establishes a metadata dictionary and assigns data owners. A release-readiness checklist requires technical QC, accessibility assets, rights validation, localized presentation, and rollback planning. A small localization panel reviews high-risk translations, while AI-generated transcripts are treated as drafts requiring human verification.

Customer support receives structured reason codes and a direct escalation channel. Weekly reviews examine recurring issues rather than merely counting closed tickets. NPM also pilots staged releases for selected programmes and conducts a post-launch review after each pilot.

Outcome

After the pilot period, NPM reports fewer catalogue corrections, earlier detection of rights conflicts, improved subtitle availability, and clearer prioritization of engineering defects. The subscription launch is postponed until the operating controls are stable. This postponement is treated as risk management rather than failure. The organization has not eliminated all problems, but it has made ownership, evidence, and learning more visible.

Learning points

The case demonstrates that transformation is cumulative. A new application cannot compensate for weak rights data, unclear ownership, or disconnected support information. It also shows why staged experimentation is preferable to a large launch based on untested assumptions. Finally, operational maturity is a strategic asset: it permits the organization to innovate with lower avoidable risk.

Challenges, Ethics and Contemporary Developments

OTT organizations must manage privacy, cybersecurity, accessibility, employment conditions, copyright, consumer protection, child safety, and cultural representation. Personalization systems should use data proportionately, explain important decisions where appropriate, protect sensitive attributes, and provide meaningful controls. Data minimization and retention discipline reduce both privacy exposure and operational clutter.

Generative AI may accelerate metadata creation, dubbing drafts, support responses, code development, and content analysis. Risks include hallucinated descriptions, unauthorized use of performers’ likenesses or voices, biased classification, confidential-data leakage, copyright disputes, and de-skilling. Organizations need approved use cases, human review thresholds, model documentation, access controls, provenance records, and incident procedures.

Contemporary OTT operations are also shaped by cloud-native architecture, event-driven workflows, automated observability, connected-TV fragmentation, ad-supported streaming, FAST channels, real-time personalization, and increasingly complex regulation. These developments increase the need for interoperability and governance. Speed without control can produce legal, financial, and reputational damage; control without adaptability can make the service irrelevant.

Best-Practice Principles

1. Design the entire value stream, not isolated departmental tasks.
2. Make rights, metadata, and accessibility first-class operational data.
3. Define ownership and escalation before a crisis occurs.
4. Automate repetitive work, but retain human judgment for ambiguous or high-impact decisions.
5. Use staged releases, observable systems, and tested rollback procedures.
6. Govern vendors through outcomes, evidence, resilience, and exit planning.
7. Measure customer and business outcomes rather than activity alone.
8. Treat support interactions and incidents as sources of organizational learning.
9. Build capabilities through practice, documentation, and feedback.
10. Transform legacy strengths instead of discarding them uncritically.

Chapter Summary

OTT success depends on an integrated operating model linking acquisition, rights, production, quality assurance, metadata, localization, moderation, publishing, and customer support. Each stage creates inputs and risks for the next, so workflow design must include feedback, ownership, controls, and exception handling.

Metadata is both an audience-discovery resource and a distribution control. Localization includes cultural adaptation and accessibility, while moderation requires policy clarity, human oversight, appeals, and attention to reviewer wellbeing. Publishing should use readiness checks, monitoring, staged release, and rollback capability.

Functional structures provide expertise but may create handoff problems. Matrix and product-team designs can improve cross-functional delivery when decision rights are clear. Agile practices are useful when adapted to contractual, regulatory, and live-event realities. Vendor management remains an internal accountability, and capability development must link skills to measurable outcomes.

Legacy-media transformation involves digitization, process redesign, new customer relationships, data capability, and strategic renewal. Successful transformation is staged, evidence-led, and respectful of valuable editorial and production strengths. Ethical governance, privacy, accessibility, cybersecurity, and responsible AI are integral to operational quality rather than optional additions.

Key Terms

Operating model: The way an organization aligns strategy, capabilities, processes, technology, and governance.

Rights window: The authorized period during which content may be distributed.

Rights truth: An accurate operational representation of contractual availability.

Media supply chain: The coordinated flow of media assets from creation or acquisition to distribution.

Quality control: Inspection and testing to identify defects before or after release.

Metadata: Structured information describing, classifying, and controlling content.

Controlled vocabulary: An approved set of terms used consistently in a system.

Localization: Adaptation of content and presentation for a language and cultural market.

Accessibility: Design and provision that enables people with disabilities to use a service.

Moderation: Application of legal, policy, and safety rules to content or user behaviour.

Release readiness: Evidence that an asset or feature is prepared for publication.

Rollback: Reversal of a release or deployment when serious defects occur.

Product operating model: Organization around durable cross-functional teams responsible for outcomes.

Agile: An adaptive approach based on incremental delivery, feedback, and reprioritization.

Service-level agreement: A contractual specification of service expectations and remedies.

Capability map: A structured view of what an organization must be able to do.

Digitization: Conversion of analogue or physical information into digital form.

Digital transformation: Redesign of an organization’s value proposition and operating model through digital capabilities.

Rights concentration risk: Exposure created by dependence on one critical rights holder, supplier, or route to market.

Observability: The ability to understand system condition through logs, metrics, traces, and related evidence.

Review Questions

Short Answer Questions

1. What is the difference between a value chain and an operating workflow in OTT?
2. Identify four types of information that should appear in a rights-management record.
3. Why is metadata both an editorial resource and a technical control layer?
4. State two reasons why outsourcing does not remove organizational accountability.
5. Distinguish digitization from digital transformation.

Long Answer Questions

1. Explain how acquisition, localization, metadata, and publishing are interdependent. Use examples of possible failures at their handoffs.
2. Compare functional, matrix, and product-team organizational structures for an OTT service.
3. Discuss the role of quality assurance across technical, editorial, legal, and playback dimensions.
4. Explain how a legacy broadcaster can transform without losing its editorial and production strengths.
5. Evaluate the opportunities and risks of AI in metadata, moderation, localization, and customer support.

Analytical / Application Questions

1. Design an end-to-end release workflow for a multilingual documentary series, specifying owners, approval gates, data requirements, and rollback actions.
2. An OTT service has low support handling time but rising repeat contacts and cancellations. Analyze the likely measurement problem and propose a balanced performance framework.
3. Using the NPM case, recommend three transformation priorities for the next twelve months and justify their sequence.

Multiple Choice Questions with Answers

Question 1

Which statement best describes rights truth in an OTT operation?

A. The number of titles listed in the catalogue

B. An accurate operational representation of contractual availability

C. The audience’s preferred content genre

D. The technical quality of a master file

Correct Answer: B. An accurate operational representation of contractual availability

Question 2

Which metadata quality dimension concerns whether required fields contain information?

A. Completeness

B. Uniqueness

C. Timeliness

D. Confidentiality

Correct Answer: A. Completeness

Question 3

What is the principal purpose of a staged OTT release?

A. To eliminate the need for quality assurance

B. To increase the number of contractual rights holders

C. To reduce risk by testing with a limited audience before wider release

D. To prevent customer-support teams from seeing incidents

Correct Answer: C. To reduce risk by testing with a limited audience before wider release

Question 4

Which activity is an example of technical quality control?

A. Checking whether a synopsis is culturally appropriate

B. Verifying picture, sound, synchronization, and file integrity

C. Negotiating an exclusive territory

D. Designing a loyalty programme

Correct Answer: B. Verifying picture, sound, synchronization, and file integrity

Question 5

Why should accessibility assets be planned during production or acquisition?

A. They are unrelated to the release workflow

B. Late preparation can create defects, delays, and exclusion

C. They replace the need for subtitles in every market

D. They are required only for promotional trailers

Correct Answer: B. Late preparation can create defects, delays, and exclusion

Question 6

Which organizational form normally organizes durable cross-functional teams around customer or business outcomes?

A. Pure functional structure

B. Product operating model

C. Geographic hierarchy only

D. Temporary payroll structure

Correct Answer: B. Product operating model

Question 7

Which statement about vendor management is most accurate?

A. Outsourcing transfers all legal and customer accountability to the vendor

B. Vendor governance is needed only for low-cost suppliers

C. The platform owner remains accountable for customer impact and compliance

D. Service-level agreements eliminate the need for incident management

Correct Answer: C. The platform owner remains accountable for customer impact and compliance

Question 8

A support team is rewarded only for minimizing handling time. What is the most likely risk?

A. Improved resolution of every underlying problem

B. More unresolved or repeated customer contacts

C. Higher metadata completeness automatically

D. Lower dependence on all vendors

Correct Answer: B. More unresolved or repeated customer contacts

Question 9

Which option best distinguishes digital transformation from digitization?

A. Transformation converts paper files, while digitization changes strategy

B. Transformation redesigns value and operating models, while digitization converts information

C. They are identical terms

D. Digitization always requires artificial intelligence

Correct Answer: B. Transformation redesigns value and operating models, while digitization converts information

Question 10

Why is human review especially important for automated moderation?

A. Automated systems cannot process any content

B. Context, satire, and culturally specific meaning may be misclassified

C. Human review guarantees that no policy violation occurs

D. Automation is prohibited in all OTT operations

Correct Answer: B. Context, satire, and culturally specific meaning may be misclassified