Omnichannel Orchestration Team (OOT)

Background Image

Overview

Why do we need Omnichannel?

Customer experience expectations are changing faster than ever before. Customers expect every business they engage with to deliver great customer experiences. It is crucial for BD to strengthen Omnichannel capabilities to deliver truly inspiring customer experiences and to differentiate BD in a highly competitive environment.

What is needed to enable Omnichannel?

To enable true Omnichannel, teams need to operate with speed, be responsive and relevant in each customer interaction over the lifetime of the customer journey. One way to deliver that is through a strong team that adheres to agile principles of working. We call that an omnichannel orchestration team, or OOT for short.

Omnichannel Orchestration Team (OOT)

An OOT is a cross-functional, agile team responsible for defining the marketing strategy and executing test-and-learn campaigns.

OOT’s leverage proven agile strategies like Scrum to guide new management practices and ways of working to respond to rapidly changing customer needs.

  • Time-saving and repeatable processes

    Repeatable processes that are quick to implement and scale

  • Internal data-driven results

    Emergence of data-driven campaigns that refine the understanding of the customer via “test and learn”

  • Empowered decision-making to react to data

    Efficiency-driven processes and ceremonies driven by a connected team with internal capability built for campaigns

  • Reducing risk through customer-centricity and iteration

    Iterative campaign roll out reduces downside risk

  • Customer-centric, persona-driven, qualified leads

    Higher volume and better converting leads driven by personas shared across BUs

The Approach

The approach to setting up and scaling OOTs begins by establishing an OOT for one BU and one BD product, and then scaling across the BU

Single BD Product (e.g., MedBank)
Single BD Product (e.g., MedBank)
  • OOT team delivers “test and learn” campaigns to decrease campaign risk
  • Iterative campaigns drive deeper customer understanding and more prudent spending
  • New ways of working are learned and tested within individual use cases
  • Further synergies (communication, resource allocation) can be achieved by expanding model across BU
See Medbank example
Single BU (e.g., MMS)
Single BU (e.g., MMS)
  • Creation of common customer views across BU to help enable better coordination across teams, and true Omnichannel experiences
  • Ability for cross-functional understanding to enable shared customer lists and cross-selling
  • Ability to achieve 30% gains in marketing efficiency driven by increased cross-functional team coordination and output
Agile across the organization
Agile across the organization
  • There is clear standardization of processes and roles allowing more interoperability
  • Teams share a common customer definition and single source of truth data source
  • True Omnichannel is delivered to the prospective customer

Steps to Implement


            

Use case Use case
Use case
Setup Setup
Setup
Governance Governance
Governance
Tools Tools
Tools

How:

Decide on an appropriate use case for agile i.e., new campaign standup, segment or product

Why:

An opportunity to scale agile is best used when there are new opportunities to do so

How:

Identify your product owner, scrum master, and additional roles listed on the previous slide

Why:

Determining roles early allows team members to research roles and responsibilities associated

How:

Determine the type of governance you’d like to use for the project and the agile cadence you will follow

Why:

Governance ensures transparency, minimizes wasted work and empowers the team

How:

Establish your ways of working as a team including tools and processes referenced in this guide

Why:

Tools are essential to the functioning of Agile, your Jira board will become a single source of truth

How-to Guide for Scaling Agile