Eurobank - What happens when you point Problem Framing at the inside of an organization

The innovation blind spot most banks share

Most financial services innovation conversations start in the same place: the customer. How do we improve the customer experience? How do we make products more compelling? How do we compete with fintechs on the front end?

These are important questions. But they have a habit of consuming all the available attention, leaving a different category of challenge largely unexamined: the internal conditions that determine whether any innovation actually lands.

A bank can design an exceptional customer journey and still fail to deliver it, because the teams responsible for delivery are working in processes that create friction at every step. It can invest in digital transformation and watch adoption stall, because the people meant to carry it forward are disengaged and nobody has properly diagnosed why. It can generate good ideas in workshops and lose them to organizational inertia, because the problems blocking implementation were never clearly defined.

The questions that live on the inside of an institution — about culture, engagement, process, and the conditions that enable or prevent good work — are often treated as too complex, too political, or too uncomfortable to subject to the same structured rigor applied to product problems. They stay vague. They get managed rather than solved.

That's the blind spot Problem Framing is particularly well suited to address.

What Eurobank wanted to work on

In 2019, Design Sprint Academy ran a Problem Framing Training for Eurobank teams in Athens. Eurobank is one of Greece's four systemic banks — a large, established financial institution operating in a sector defined by regulatory complexity, hierarchical decision-making, and the particular kind of organizational inertia that accumulates in institutions built for stability rather than speed.

The distinctive feature of this engagement was its focus. Rather than applying Problem Framing to customer-facing product challenges — the typical starting point for innovation work in banking — the training deliberately turned the lens inward. The teams worked on internal challenges: the dynamics inside the organization that either enable or obstruct the work.

Two challenge areas anchored the day.

The first was engagement: how to make banking more engaging as a working environment, not just as a customer proposition. Banks face a structural tension here. The culture that makes an institution reliable — careful, process-driven, risk-aware — can also make it feel slow, rigid, and unrewarding for the people who work inside it. The gap between what makes a bank trustworthy and what makes it a place people want to come to every day is a real and underexamined problem.

The second was people: how to effectively manage demotivated staff. This is a challenge most large organizations know exists and few address with the same rigor they apply to operational or product problems. Demotivation is typically diagnosed at the symptom level — low scores on an engagement survey, high turnover in specific teams, visible disengagement in meetings — without the underlying causes being clearly identified. When the causes aren't clear, the responses tend to be generic: a new initiative, a communication campaign, a revised incentive structure. These may reduce the visible symptom without touching the actual problem.

The choice to work on these challenges, rather than customer-facing innovation questions, was itself a form of problem reframing.

What the training produced

A one-day Problem Framing Training doesn't solve organizational challenges. That's not what it's designed to do, and it's important to be precise about what it does instead.

What it produces is clarity: a more accurate understanding of what the challenge actually is, which problems within it are worth prioritizing, and what a well-defined intervention would need to address. That clarity is the prerequisite for any effective response. Without it, organizations invest in solutions to problems they haven't properly described.

For the Eurobank teams, the day produced three specific shifts.

From general to specific. Challenges like "banking isn't engaging enough" or "staff are demotivated" are not actionable in their general form. They describe a condition, not a problem with a defined cause and a testable intervention. Problem Framing gave the teams a structured process for disaggregating those general conditions into their component parts — identifying which specific aspects, in which contexts, for which people, were most significant. By the end of the day, the teams were working with problems that had enough specificity to be addressed.

From symptoms to causes. The presenting version of most internal organizational challenges is a symptom. Demotivation is what shows up in observable behavior. The causes — unclear expectations, lack of autonomy, misalignment between stated values and daily experience, insufficient recognition, structural barriers to doing good work — are upstream, and they require deliberate investigation to surface. Problem Framing created the process for that investigation: asking what's driving the symptom before deciding what to do about it.

From individual to shared understanding. One of the most consistent findings across Problem Framing sessions in large organizations is that different people in the same team hold meaningfully different mental models of the problem they're working on. A manager's understanding of why staff are demotivated may diverge significantly from what team members experience. A leadership team's diagnosis of an engagement problem may be anchored in the parts of the organization they see, rather than the full picture.

Problem Framing surfaces those divergences explicitly. The process of working toward a shared problem statement reveals where understanding is genuinely aligned and where it isn't — which is valuable regardless of whether the eventual problem statement is acted on, because the divergences themselves are often part of the problem.

For the Eurobank participants, the experience of seeing their challenge reframed in real time — watching a vague, overwhelming difficulty become a specific, describable problem with identifiable causes — was the most impactful part of the day.

Why internal challenges are harder to frame than external ones

Product and customer-facing problems have a natural structure that makes them easier to work with. There's usually a defined user group, a describable experience, and some form of feedback signal — data, testing, research — that can be used to evaluate whether a proposed solution is moving in the right direction.

Internal organizational challenges are harder to frame for several reasons.

The problem and the problem-holders are the same people. When a team is working on an internal culture or engagement challenge, the people doing the framing are also inside the system being examined. This creates proximity bias: people tend to see the challenge through the lens of their own experience and position, which may be accurate for their context but unrepresentative of the whole. Problem Framing creates structured distance — a process for examining the challenge more systematically rather than relying on individual perception.

The stakes feel more personal. In banking especially, where hierarchy is real and careers are long, naming internal problems explicitly can feel risky. Saying "the problem is how performance is managed" or "the problem is that the decision-making process creates learned helplessness" is a different kind of statement than naming a product gap. Problem Framing's structured approach — building toward a shared problem statement rather than attributing blame — creates the conditions for those conversations to happen productively.

The causes are often structural, not individual. Most engagement and culture problems in large organizations aren't caused by bad individuals. They're caused by structural conditions: incentive systems, process design, communication flows, and the organizational arrangements that determine what behavior is rewarded and what gets ignored. Diagnosing at the structural level requires a process that can surface systemic patterns rather than getting stuck at the level of individual behavior. That's precisely what Problem Framing is designed to do.

What this means for financial services teams

Banking is one of the more structurally challenging environments for this kind of work. The regulatory environment creates a legitimate need for process and control that can make any change conversation feel threatening. The hierarchy is real and shapes what can be said in what rooms. The culture of stability that makes banks trustworthy can coexist uneasily with the diagnostic honesty required to surface and name internal dysfunction.

None of that makes Problem Framing less valuable in banking. It may make it more valuable, precisely because the barriers to naming internal problems clearly are higher — which means the costs of not naming them compound for longer.

For L&D leads, HR directors, and transformation leaders in financial services, the Eurobank case points to something specific: the same structured problem definition that works for product and innovation challenges works equally well for people and culture challenges. The method doesn't change. What changes is the subject matter — and with it, the willingness to examine what's really driving the conditions the organization is working in.

Problem Framing Training equips teams to have those conversations with structure and without blame. That's valuable anywhere. In a sector as structurally resistant to self-examination as banking, it's particularly so.

What a one-day Problem Framing Training actually produces

It's worth being direct about scope, because the value of the training is sometimes undersold when framed too modestly and oversold when framed too ambitiously.

A one-day Problem Framing Training does not solve an organization's culture or engagement challenges. No single training session does. What it produces is the prerequisite for solving them: a clearer, more specific, more shared understanding of what the actual problem is.

That output is more valuable than it sounds. Most large organizations spend significant resources on responses to problems that haven't been precisely defined. The response may be technically competent — well-designed, well-executed, well-resourced — and still fail to move the needle, because it's addressing a symptom rather than a cause, or a cause that is real but not the most important one.

Problem Framing doesn't prevent that failure. It creates the conditions for avoiding it: a shared problem statement, specific enough to generate testable interventions, agreed by the stakeholders who will need to act on it.

For Eurobank's teams in Athens, that shift — from facing a complex, interconnected set of organizational difficulties to working with a clearer set of defined problems — was the output of the day. Where they took it from there was their work to do.