If you're a bank executive, you've probably heard the term "McKinsey Panorama Global Banking Pools" thrown around in strategy meetings or seen it referenced in industry reports. It sounds impressive, maybe a bit mysterious. But what is it actually for, and more importantly, how do you move from just having the data to using it to make decisions that actually grow your business? Having worked with clients who use this tool, I've seen the gap between simply accessing the pools and leveraging them strategically. Many treat it like a fancy report to be glanced at quarterly. The winners treat it as a live strategic compass.

What Exactly Are the McKinsey Panorama Global Banking Pools?

Let's strip away the jargon. The McKinsey Panorama Global Banking Pools is essentially a massive, proprietary database and analytical framework. McKinsey & Company builds it by aggregating and standardizing financial data from thousands of banks worldwide. Think of it as a supercharged, consistently formatted set of financial statements for the global banking industry.

But it's more than just data. The "Pools" part is key. McKinsey segments the global banking revenue into discrete "pools"—like Retail Banking fees, Corporate Lending, Wealth Management, Transaction Banking. They then size these pools at a regional and often country level, forecast their growth, and analyze the competitive landscape within each. The latest iterations, as discussed in their broader financial services insights, increasingly weave in digital adoption rates, cost structures, and customer behavior analytics.

The Common Misstep: Most bankers fixate on the "market share" number within a pool. The more nuanced insight lies in the profit pool analysis. A bank might have a small revenue share in a high-margin pool (like payments) and a large share in a low-margin, capital-intensive pool (like certain types of lending). Panorama helps you see that disparity, which is far more strategic.

It's not public data. Access is typically granted to McKinsey's banking clients as part of a consulting engagement or through a dedicated subscription to their Panorama services. This exclusivity is part of its perceived value—and its frustration for those on the outside.

How Banks Actually Use Panorama: Beyond the Brochure

The brochure says it's for "strategy." In practice, its use varies wildly. Here’s how I’ve seen it applied in the real world, far from the sanitized case studies.

Scenario 1: The Growth-Oriented CEO

The CEO of a strong regional bank in Southeast Asia is under pressure from the board to expand. "Should we enter Vietnam? Or double down in Indonesia?" Panorama provides the granular, comparable data to model these scenarios. They're not just looking at total banking revenue in Vietnam. They're drilling into:

Retail lending pool growth (is it driven by mortgages or unsecured personal loans?),
Competitive density (how many players are fighting for the wealth management pool, and what are their margins?),
Digital readiness (what's the adoption of mobile payments, a key indicator of future channel costs?).

This moves the conversation from "Vietnam is hot" to "The SME lending pool in Vietnam is growing at 12% CAGR, is fragmented, and our digital onboarding platform gives us a 30% cost advantage over the top three incumbents." That's actionable.

Scenario 2: The Efficiency-Focused COO

The COO at a European bank is tasked with cutting the cost-to-income ratio by 300 basis points. Panorama's benchmarking capabilities are her secret weapon. She can filter for banks of similar size, in similar markets, with similar business mixes. She's not comparing her universal bank to a pure-play investment bank.

She can ask: "Among peer banks in the DACH region with a 40% corporate banking mix, what are the best-in-class metrics for:
- Back-office operations cost per transaction?
- Branch sales productivity?
- IT spend as a percentage of revenue?"

This external benchmark provides an unassailable justification for investment in automation or for restructuring certain divisions. It turns an internal cost-cutting exercise into a targeted performance improvement program.

Scenario 3: The Investor Relations Head

This is a use case many overlook. When analysts ask, "Why is your wealth management ROE lower than your peers?", a compelling answer needs context. The IR head uses Panorama to show that the bank's specific wealth management pool (e.g., mass affluent in a saturated market) structurally has lower margins than the "private banking" pool where competitors play. It's a tool for shaping the narrative.

The Nuts and Bolts: Access, Cost, and What You Really Get

Let's talk practicality. How do you get this tool, what does it look like, and what's the damage?

Access: Primarily through a McKinsey engagement. You might get access to the Panorama platform for the duration of a strategy project. Some large banks have annual enterprise subscriptions, but that's a significant commitment. There's no public sign-up page.

The Platform: It's typically a web-based interface with dashboards, deep-dive modules, and robust export functions. You'll see interactive maps, trend graphs, and competitor tear-sheets.

Cost: This is the black box. Fees are never published and are highly negotiable, tied to the scope of work or subscription level. We're talking high six to seven figures annually for a comprehensive global subscription for a large bank. For a regional bank with a focused geographic need, it might be part of a project fee in the low millions. It's a major investment, which is why aligning it to a critical strategic initiative is crucial.

Core Deliverables: What's in the box? The table below breaks down a typical output structure.

Module/Output What It Contains Typical Use Case
Market Sizing & Forecast Historical and projected size of revenue/profit pools (e.g., "UK Mortgage Lending") by segment, with growth drivers. Validating the addressable market for a new digital loan product.
Competitive Benchmarking Financial and operational metrics (ROE, C/I ratio, cost per account) for a customizable set of peer banks. Identifying performance gaps in your retail network versus top quartile peers.
Bank Teardown Profiles Deep-dive analysis on specific competitors: business mix, geography, key strategies, strengths/weaknesses. Preparing for a competitive response when a rival launches a new mobile app.
Trend Analytics Data on digital adoption, customer preferences, regulatory impacts shaping the pools. Making the case for increasing the AI/ML budget to match shifting customer channels.

A Critical Look: The Limitations and Expert Considerations

No tool is perfect. After using this with teams for years, here are the sharp edges you need to watch for.

Data Lag: The data is incredibly rich, but it's not real-time. You're often looking at figures that are 6-12 months old. In a fast-moving market, that's a lifetime. Basing a tactical digital campaign solely on this data is a mistake. Use it for strategic direction, not day-to-day trading.

The "McKinsey Lens": The data categorization and pool definitions are McKinsey's. Their view of what constitutes "Wealth Management" might differ subtly from your internal definitions. This can cause misalignment when translating insights into internal budgets and P&Ls. Always map their categories to yours as a first step.

Cost vs. Value Trap: The biggest pitfall is subscribing to Panorama without a clear, burning question to answer. It becomes an expensive dashboard that people log into once a quarter, nod sagely, and log off. You must have a process—quarterly strategy reviews, M&A screening, performance deep-dives—that requires this data as an input. Otherwise, it's shelfware.

Alternative Sources: It's not the only game in town. Public data from central banks, S&P Global Market Intelligence, and Bloomberg can get you 70-80% of the way there for a fraction of the cost, but it requires more internal effort to clean and standardize. Panorama's value is in that last 20-30% of consistency, curation, and the analytical framework.

The banking pools aren't static. The most forward-looking use of Panorama is to model how disruptions will redistribute value. Here’s how I encourage clients to think about it.

The Green Financing Pool: This is a sub-pool exploding within corporate and investment banking. Panorama can help quantify the premium (or penalty) associated with ESG-linked loans in different regions. Is it a differentiator in Europe but table stakes in North America? The data is starting to show this.

Embedded Finance Erosion: Revenue from traditional consumer auto loans is a pool. But as car manufacturers embed financing at point-of-sale, that pool shrinks for banks and grows for non-banks. Panorama's trend analytics, combined with your own market scans, can help you model the velocity of this erosion. Should you partner with OEMs, compete directly, or cede the space?

Scenario Planning: Don't just look at the base-case forecast. Use the tool to ask: "If interest rates remain higher for longer, which pools (e.g., transaction banking, fixed income trading) benefit most, and which (e.g., long-duration mortgage lending) suffer? How does our business mix align with that future?" This turns a data tool into a war-gaming engine.

Your Burning Questions Answered (FAQ)

How can a regional bank justify the cost of McKinsey Panorama?

Frame it around one or two make-or-break decisions. Don't buy it for "general insight." Propose a time-bound, project-based engagement: "We need to decide on our $500M ASEAN expansion target within 12 months. The Panorama data for market selection and target screening is critical to de-risking this capital allocation. The project cost (including Panorama access) is a fraction of the potential downside of choosing the wrong market." This ties the cost directly to a high-value outcome.

What's the most underutilized feature within the Banking Pools data?

The granular cost structure benchmarking. Everyone looks at revenue pools and market share. Far fewer drill into the cost per account or cost per transaction metrics by business line and region. This is where you find hidden inefficiencies and, more importantly, identify which competitors are truly operationally superior—not just bigger—and in what specific areas. It's the key to building a realistic performance improvement plan.

We have access, but our team doesn't use it. How do we drive adoption?

This is a change management problem, not a tool problem. Stop sending generic login emails. Run a 90-minute "clinic" focused on a live problem. Gather the retail team, pull up the dashboard, and collaboratively answer: "Based on the pool data, which customer segment (mass market, mass affluent, small business) in our top three regions has the highest growth and worst current service satisfaction? Let's find the numbers now." When people see it solve a real, immediate puzzle, they get hooked. Mandate its use in the first page of any new business case or strategy memo.

How does Panorama handle the rise of neobanks and fintechs that aren't traditional banks?

This is a current limitation, though McKinsey is working to integrate more non-traditional player data. Traditionally, the Pools focused on regulated banking entities. Today, they increasingly try to estimate the revenue fintechs are taking from traditional pools (like payments or personal loans). However, the data on private fintechs is spotty. The insight here is to use Panorama to understand the pressure points—which pools are most under attack (high margin, low customer satisfaction)—and then use alternative data sources (App Annie, Crunchbase) to track the fintechs themselves. Panorama tells you "where" to look for disruption.