WEBVTT
00:00:00.080 --> 00:00:01.600
Welcome to today's deep dive.
00:00:01.760 --> 00:00:05.599
Um, we are unpacking a really fascinating exclusive interview today.
00:00:05.839 --> 00:00:07.280
Yeah, it's a wildly interesting one.
00:00:07.599 --> 00:00:08.000
It really is.
00:00:08.080 --> 00:00:12.160
It's from the September 2025 issue of the IBSI FinTech Journal.
00:00:12.320 --> 00:00:21.519
And the whole piece focuses on Chris Walters, who uh he took over as CEO of the financial technology giant Finastra back in January of 2025.
00:00:21.839 --> 00:00:22.160
Right.
00:00:22.559 --> 00:00:30.559
So the mission for our analysis today, for you listening, is to basically deconstruct what I'd call a masterclass in modern corporate strategy.
00:00:30.800 --> 00:00:39.119
We're looking at how a massive, you know, entrenched global company actually learns to stop doing absolutely everything just so they can do the right things better.
00:00:39.439 --> 00:00:40.159
Which is rare, right.
00:00:40.320 --> 00:00:44.479
Because I mean, the tech industry has been utterly addicted to addition for the last, what, two decades.
00:00:44.799 --> 00:00:45.359
Oh, at least yeah.
00:00:45.679 --> 00:00:51.280
Growth is almost exclusively defined by adding more features or acquiring more companies, expanding into new verticals.
00:00:51.520 --> 00:00:53.439
Subtraction is just it's treated like a failure.
00:00:53.520 --> 00:00:53.679
Trevor Burrus, Jr.
00:00:53.840 --> 00:00:54.479
Like you're retreating.
00:00:54.799 --> 00:00:55.119
Exactly.
00:00:55.359 --> 00:00:59.200
But this source material it outlines a radical departure from that mindset.
00:00:59.359 --> 00:01:03.520
It actually shows an enterprise actively utilizing subtraction as a growth engine.
00:01:04.079 --> 00:01:08.799
And I think you see the consequences of that uh that addiction everywhere.
00:01:09.040 --> 00:01:10.719
I mean, think about the software you use every single day.
00:01:10.799 --> 00:01:11.359
Aaron Powell Oh, for sure.
00:01:11.599 --> 00:01:15.359
Maybe it's your primary work platform or I don't know, just your email client.
00:01:15.680 --> 00:01:19.920
Over the years, it has accumulated 50 features you literally never touch.
00:01:20.079 --> 00:01:21.680
Aaron Powell Just sitting there taking up space.
00:01:21.760 --> 00:01:22.079
Aaron Powell Right.
00:01:22.319 --> 00:01:34.400
You just want to execute a core task, but you are forced to navigate like three submenus, dismiss some annoying AI assistant, and ignore a dashboard that looks like a space shuttle control panel.
00:01:34.719 --> 00:01:35.200
Yeah, exactly.
00:01:35.519 --> 00:01:37.760
That is feature creep on a personal scale.
00:01:38.000 --> 00:01:46.719
But now multiply that frustration by a factor of about 10 million, because that is the reality for a multinational bank trying to modernize its infrastructure.
00:01:46.879 --> 00:01:49.599
They are just drowning in enterprise level complexity.
00:01:49.680 --> 00:01:53.840
Aaron Powell Which naturally brings us to how Walter spent the first half of 2025.
00:01:54.079 --> 00:01:57.439
Because he bypassed that traditional, you know, new CEO Victory Lab.
00:01:57.840 --> 00:01:58.719
The usual PR tour.
00:01:59.040 --> 00:01:59.920
Yeah, the PR tour.
00:02:00.079 --> 00:02:08.800
Instead, he spent six months on this grueling global tour across North America, Europe, Asia, the Middle East, just sitting directly with customers.
00:02:09.039 --> 00:02:13.439
And those conversations highlighted a, well, a universal paradox.
00:02:13.840 --> 00:02:14.240
Which is what?
00:02:14.560 --> 00:02:27.759
Basically, these institutions are under immense pressure to adopt cutting-edge innovation, but they're simultaneously crippled by the burden of maintaining absolute security, not to mention navigating increasingly dense regulatory environments.
00:02:27.840 --> 00:02:28.000
Trevor Burrus, Jr.
00:02:28.159 --> 00:02:28.319
Right.
00:02:28.400 --> 00:02:32.000
Because every financial institution on earth desperately wants modernization.
00:02:32.560 --> 00:02:39.599
But enterprise tech companies fundamentally struggle to deliver it without accidentally, you know, dumping more complexity into the client's ecosystem.
00:02:39.680 --> 00:02:40.159
Aaron Powell Exactly.
00:02:40.319 --> 00:02:40.479
Trevor Burrus, Jr.
00:02:40.560 --> 00:02:47.520
So Walter's listening tour, it actually reads less like a standard corporate meet and greet and more like a global intervention.
00:02:47.599 --> 00:02:48.800
Trevor Burrus That's a great way to put it.
00:02:48.879 --> 00:02:51.759
Trevor Burrus The core demand from these customers wasn't for more features.
00:02:51.840 --> 00:02:53.520
It was a plea for simplicity.
00:02:53.680 --> 00:03:01.439
They want speed, easier integration, and uh a strategic ally rather than just another software vendor hawking licenses.
00:03:01.520 --> 00:03:07.599
Aaron Powell And that term, strategic ally, it carries very specific operational weight in this context.
00:03:07.680 --> 00:03:11.360
Aaron Powell So Well, a vendor simply sells you a tool and walks away, right?
00:03:11.520 --> 00:03:15.360
They leave your IT department to figure out how it fits into your existing tech stack.
00:03:15.840 --> 00:03:22.159
But a strategic ally actually aligns their own product development roadmaps with your long-term survival.
00:03:22.639 --> 00:03:22.800
Okay.
00:03:23.360 --> 00:03:35.759
And the universal feedback Walters got was that Finastra's products were powerful, but the sheer gravity of the company's sprawling portfolio was just it was making them too difficult to implement and scale quickly.
00:03:36.159 --> 00:03:47.280
Okay, let's apply some critical friction to this narrative, though, because I mean selling the market on terms like customer-led and strategic partner is basically the oldest play in the enterprise software playbook.
00:03:47.520 --> 00:03:48.000
Oh, absolutely.
00:03:48.319 --> 00:03:48.479
Right?
00:03:48.639 --> 00:03:59.039
A new CEO goes on a listening tour, they issue a press release filled with synergistic buzzwords, maybe initiate a minor rebrand, and then operations just continue exactly as they did before.
00:03:59.280 --> 00:04:05.439
Claiming to prioritize customer simplicity over corporate empire building is super easy to say in a journal interview.
00:04:05.759 --> 00:04:10.879
Yeah, and the skepticism is totally warranted given the industry's history of empty pivots.
00:04:11.039 --> 00:04:18.079
But the validation for Walter's claims here lies strictly in the timeline and the severity of the action they actually took.
00:04:18.319 --> 00:04:18.560
Okay.
00:04:18.800 --> 00:04:21.040
So the listening tour concluded in the spring.
00:04:21.199 --> 00:04:27.439
And in May of 2025, Finashra didn't just launch a marketing campaign promising simpler software.
00:04:27.680 --> 00:04:30.399
They executed a massive corporate divestiture.
00:04:30.720 --> 00:04:31.680
Wait, they sold something off?
00:04:31.920 --> 00:04:32.399
Yes.
00:04:32.639 --> 00:04:38.079
They sold off their treasury and capital markets business known as TCM to the private equity firm Apex.
00:04:38.480 --> 00:04:38.639
Wow.
00:04:38.720 --> 00:04:38.879
Okay.
00:04:39.040 --> 00:04:44.399
But selling a massive division like TCM usually signals one of two things in the corporate world, right?
00:04:44.639 --> 00:04:52.319
Either the division is bleeding money and dragging down the quarterly earnings, or the parent company is desperate for a quick cash injection to cover debt.
00:04:52.720 --> 00:04:54.000
Right, the usual suspects.
00:04:54.319 --> 00:04:59.759
Yeah, the PR spin is always about like streamlining, but the reality is frequently just financial engineering.
00:04:59.920 --> 00:05:04.240
So exactly what was the structural motivation here if we assume it wasn't just a fire sale?
00:05:04.639 --> 00:05:09.680
Well, the financials of the TCM division disrupt that whole fire sale narrative entirely.
00:05:09.920 --> 00:05:17.680
Walters is highly transparent in the IBSI piece that TCM was a remarkably strong, profitable, and healthy business unit.
00:05:18.160 --> 00:05:18.639
Wait, really?
00:05:18.720 --> 00:05:20.319
So they weren't dumping a bad asset?
00:05:20.560 --> 00:05:21.040
Not at all.
00:05:21.199 --> 00:05:23.920
Apex wasn't buying a distressed asset to gut it.
00:05:24.000 --> 00:05:26.240
They bought a thriving division to scale it.
00:05:26.399 --> 00:05:32.000
For FENASTRA, the sale was entirely about eliminating operational and mental fragmentation.
00:05:32.240 --> 00:05:35.279
Walters described the move with a very specific phrase.
00:05:35.439 --> 00:05:38.160
He called it being bold in service of focus.
00:05:38.560 --> 00:05:39.839
Bold in service of focus.
00:05:40.000 --> 00:05:40.240
Okay.
00:05:40.399 --> 00:05:48.480
I mean, maintaining a division like TCM means splitting your engineering resources, dividing your regulatory compliance teams, fracturing executive attention.
00:05:48.720 --> 00:05:48.959
Exactly.
00:05:49.120 --> 00:05:51.839
It's like, okay, think of it like managing a massive orchard.
00:05:52.319 --> 00:05:54.959
You have this beautiful, heavy, fruit-bearing branch.
00:05:55.120 --> 00:06:02.720
It's perfectly healthy and generating a great yield, but it is drawing massive amounts of water and soil nutrients away from the central root system of the tree.
00:06:02.959 --> 00:06:04.079
That's a perfect analogy.
00:06:04.480 --> 00:06:04.879
Right.
00:06:05.040 --> 00:06:15.680
If you make the painful decision to prune that branch, the root system suddenly reroutes all that biological infrastructure into the main trunk, which makes it highly resilient to storms.
00:06:16.079 --> 00:06:18.480
And that's exactly what pruning the TCM branch did.
00:06:18.639 --> 00:06:27.360
It allowed Finastra to forcefully redirect capital and honestly, more importantly, engineering bandwidth into their absolute core leadership areas.
00:06:27.439 --> 00:06:28.720
Aaron Powell Which are what, specifically?
00:06:29.040 --> 00:06:31.199
Lending, payments, and core banking.
00:06:31.519 --> 00:06:35.519
These three pillars represent the central nervous system of global finance.
00:06:35.759 --> 00:06:40.399
Institutions simply cannot afford latency or integration failures in these domains.
00:06:40.560 --> 00:06:40.800
Right.
00:06:41.040 --> 00:06:51.040
So by shedding the lucrative distraction of TCM, Finastra basically manufactured the internal capacity required to completely redefine how those core products actually function.
00:06:51.120 --> 00:06:55.920
Aaron Powell And untangling a major division also forces a company to reckon with its own friction points, right?
00:06:56.160 --> 00:07:02.560
Because if the overarching mandate is to be a simpler strategic ally, well, fixing the software is only half the battle.
00:07:02.639 --> 00:07:02.800
Trevor Burrus, Jr.
00:07:02.879 --> 00:07:03.199
Oh, yeah.
00:07:03.360 --> 00:07:06.720
The relationship itself is usually bogged down in legacy bureaucracy.
00:07:06.800 --> 00:07:07.439
Aaron Powell Exactly.
00:07:07.600 --> 00:07:15.279
I mean, a multi-year enterprise tech contract can languish in legal review for six to eight months before a single line of code is ever deployed.
00:07:15.600 --> 00:07:17.439
And Walters recognizes that.
00:07:17.680 --> 00:07:21.199
Administrative friction is just as damaging as technical friction.
00:07:21.360 --> 00:07:26.959
So this sharpened strategy includes a mandate to fundamentally overhaul how the company does business.
00:07:27.279 --> 00:07:28.399
Meaning what, practically?
00:07:28.720 --> 00:07:34.240
It means instituting simplified contracting models and dramatically accelerating implementation times.
00:07:34.480 --> 00:07:44.480
The objective is to drastically shrink the window between the moment a client signs a contract and the moment they actually experience tangible, measurable value in their daily operations.
00:07:44.560 --> 00:07:50.720
Aaron Powell But I mean, accelerated implementation only matters if the technology being deployed is actually built for the future.
00:07:50.879 --> 00:07:57.360
And you can't talk about a three to five year innovation horizon in 2025 without slamming into the reality of AI.
00:07:57.680 --> 00:07:58.319
Oh, of course not.
00:07:58.639 --> 00:08:02.800
The source material notes extraordinary customer interest in artificial intelligence.
00:08:02.959 --> 00:08:13.439
But the trap here is that legacy tech companies notoriously just they slap a thin layer of generative AI over a 20-year-old database just to market the product as AI enabled.
00:08:13.600 --> 00:08:13.759
Trevor Burrus, Jr.
00:08:13.839 --> 00:08:14.000
Right.
00:08:14.160 --> 00:08:18.639
Superficial AI layering is a massive risk when you're modernizing legacy systems.
00:08:18.800 --> 00:08:25.120
But Finastra's approach, as detailed in the interview, is deliberately pragmatic to avoid exactly that trap.
00:08:25.519 --> 00:08:25.600
Okay.
00:08:25.680 --> 00:08:26.560
How are they doing it differently?
00:08:26.879 --> 00:08:28.480
They're running a dual-track strategy.
00:08:28.639 --> 00:08:33.600
So they deploy AI internally first and then embed it into customer products.
00:08:33.679 --> 00:08:34.559
Aaron Powell Internally first.
00:08:34.960 --> 00:08:35.039
Yeah.
00:08:35.279 --> 00:08:39.039
Internally, the primary targets were actually the software engineers.
00:08:39.279 --> 00:08:46.399
AI tools were introduced to automate routine coding tasks, run initial bug checks, manage all that boilerplate development.
00:08:46.559 --> 00:08:46.720
Trevor Burrus, Jr.
00:08:46.799 --> 00:08:47.679
Oh, I love that.
00:08:47.919 --> 00:08:52.639
Using AI to clear out routine coding work creates this fascinating ripple effect.
00:08:52.799 --> 00:09:01.200
Because if your developers aren't wasting hours writing boilerplate code, you suddenly free up your most expensive senior talent to tackle deep architectural debt.
00:09:01.519 --> 00:09:01.840
Exactly.
00:09:02.080 --> 00:09:07.600
The underlying structural mess that causes enterprise software to feel bloated and slow can finally be dismantled.
00:09:07.679 --> 00:09:16.080
Once that internal efficiency is proven, then the transition to customer-facing AI becomes about actual utility rather than just, you know, marketing flash.
00:09:16.480 --> 00:09:23.759
And the external customer-facing AI applications are strictly bound to that overarching theme we talked about: simplicity.
00:09:24.080 --> 00:09:31.840
Finastra is utilizing embedded AI to automate incredibly time-consuming repetitive steps within their clients' daily workflows.
00:09:32.240 --> 00:09:33.440
Make the boring stuff disappear.
00:09:33.840 --> 00:09:34.159
Right.
00:09:34.399 --> 00:09:38.799
And it's also powering more intuitive, instantly accessible support systems.
00:09:39.039 --> 00:09:43.840
But the critical boundary Walters draws here involves the concept of responsible AI.
00:09:44.159 --> 00:09:45.120
Responsible in what sense?
00:09:51.840 --> 00:09:55.600
The AI's outputs must be entirely transparent, explainable, and fair.
00:09:55.919 --> 00:09:56.879
That makes total sense.
00:09:57.039 --> 00:10:04.639
And that insistence on functional, explainable technology over flaffy buzzwords really seems to be reshaping their entire software philosophy.
00:10:04.879 --> 00:10:09.440
The interview highlights a major pivot in how Finastra approaches the concept of open finance.
00:10:09.759 --> 00:10:11.039
Yeah, that was a huge point.
00:10:11.440 --> 00:10:15.759
Because for years, open finance was just this collection of technical specifications, right?
00:10:15.919 --> 00:10:21.519
Companies boasted about being cloud native and API enabled as if those architectural choices were the ultimate goal.
00:10:21.919 --> 00:10:25.600
And Walters completely redefines open finance in this interview.
00:10:25.840 --> 00:10:29.600
He shifts it from a technical architecture to a set of practical outcomes.
00:10:30.000 --> 00:10:30.879
Okay, so what does it mean now?
00:10:31.200 --> 00:10:41.600
FNASTRA remains committed to building open by design systems, sure, with robust APIs and cloud infrastructure, but those technical realities are no longer the focal point.
00:10:41.840 --> 00:10:50.399
Because the bank executive evaluating the software does not care about the elegance of the API if the system still requires a 12-month deployment cycle.
00:10:50.799 --> 00:10:51.840
Right, they just want it to work.
00:10:52.159 --> 00:10:52.720
Exactly.
00:10:52.960 --> 00:11:01.120
Walters emphasizes that open finance now simply means delivering speed, absolute reliability, and faster time to value for the customer.
00:11:01.440 --> 00:11:07.679
And moving the conversation from the underlying engine to the actual destination changes the entire sales dynamic.
00:11:07.840 --> 00:11:15.840
Because if your primary metric of success is how easily a client can use your tool, you inevitably uncover markets that were previously locked out by complexity.
00:11:16.080 --> 00:11:17.279
Yeah, it opens up a whole new world.
00:11:17.600 --> 00:11:22.159
Finastra built its empire serving massive Tier 1 global banks.
00:11:22.399 --> 00:11:31.440
But the interview reveals a strategic push into underserved segments, specifically mid-sized institutions and organizations operating in emerging markets.
00:11:31.759 --> 00:11:32.000
Right.
00:11:32.159 --> 00:11:42.080
Because a regional credit union or a mid-sized private credit firm, they face the exact same regulatory gauntlet and shifting consumer expectations as a massive global bank.
00:11:42.399 --> 00:11:44.240
Just with way fewer resources.
00:11:44.639 --> 00:11:45.120
Precisely.
00:11:45.279 --> 00:11:48.559
They have a fraction of the IT personnel and budget to manage it.
00:11:48.799 --> 00:11:56.960
This market expansion actually relies heavily on a startling admission Walters makes regarding Finastra's flagship product, which is called Low NIQ.
00:11:57.200 --> 00:11:57.840
What does he admit?
00:11:58.080 --> 00:12:06.879
He candidly acknowledges that for rapid growth segments like private credit, low NIQ is actually too feature-rich and fundamentally more complex than what those institutions require.
00:12:07.200 --> 00:12:07.759
Oh wow.
00:12:08.000 --> 00:12:14.080
A CEO publicly admitting their flagship product is too complex for a target market is a rare moment of corporate humility.
00:12:14.399 --> 00:12:14.639
Very rare.
00:12:14.879 --> 00:12:18.960
Think of Low IQ like a massive, top-of-the-line Swiss Army knife.
00:12:19.039 --> 00:12:23.279
It's got a magnifying glass, a fish scaler, pliers, a saw blade.
00:12:23.519 --> 00:12:28.799
And that is brilliant if you are a tier one bank trying to survive in the wilderness of global finance.
00:12:29.120 --> 00:12:29.919
You need all those tools.
00:12:30.240 --> 00:12:30.399
Right.
00:12:30.639 --> 00:12:37.200
But a mid-sized private credit firm just needs a razor-sharp, highly reliable main blade to open a box.
00:12:37.360 --> 00:12:41.840
Handing them the massive multi-tool just guarantees they will cut themselves trying to figure out how to open it.
00:12:42.080 --> 00:12:46.879
And forcing a monolithic system onto a mid-market client just results in implementation failure.
00:12:47.039 --> 00:12:52.480
So to capture these underserved segments, Finasra has to fundamentally alter the architecture of their offerings.
00:12:52.799 --> 00:12:53.600
So they have to break it down.
00:12:53.919 --> 00:12:54.320
Exactly.
00:12:54.559 --> 00:12:57.840
The solution lies in scalable modular platforms.
00:12:58.080 --> 00:13:05.279
Functionally, this requires containerizing the legacy software, breaking the massive monolith down into discrete microservices.
00:13:06.159 --> 00:13:16.480
This allows a regional institution to purchase and integrate only the specific modules they actually need without inheriting the processing bloat or, you know, the massive price tag of the entire enterprise system.
00:13:16.879 --> 00:13:22.159
But breaking down monolithic software into modular components cannot be done in a vacuum.
00:13:22.320 --> 00:13:26.960
A modular approach necessitates a robust ecosystem to plug those modules into.
00:13:27.200 --> 00:13:27.360
Right.
00:13:27.440 --> 00:13:28.159
You need partners.
00:13:28.480 --> 00:13:35.519
And the interview outlines an aggressive expansion of Finastra's partner network categorized into three distinct layers.
00:13:36.159 --> 00:13:42.240
First, they are integrating with nimble fintechs, who provide highly specialized complementary capabilities.
00:13:42.559 --> 00:13:43.200
That's layer one.
00:13:43.440 --> 00:13:53.120
Then second, they are leaning heavily on system integrators to manage the actual deployment, ensuring that the installation of these modular platforms is as frictionless as possible.
00:13:53.440 --> 00:13:58.480
And then the third crucial layer of that partnership strategy involves deepening ties with hyperscalers.
00:13:58.799 --> 00:13:59.840
To provide the cloud space.
00:14:00.080 --> 00:14:00.399
Exactly.
00:14:00.559 --> 00:14:06.960
To provide the vast cloud infrastructure necessary to run these modular platforms globally with zero latency.
00:14:07.200 --> 00:14:11.759
Walters frames this entire ecosystem approach as just a necessary evolution.
00:14:12.080 --> 00:14:13.440
The walled garden is dead.
00:14:13.679 --> 00:14:14.320
It is.
00:14:14.559 --> 00:14:23.840
The era of the walled garden, where a tech giant attempts to build, sell, and implement every single piece of the technology stack themselves is over.
00:14:24.240 --> 00:14:33.759
Embracing partnerships creates better outcomes for the client, it expands market reach for the integrators, and it extracts maximum value from Finastra's core code.
00:14:34.080 --> 00:14:40.720
So looking ahead to the five-year vision laid out in the journal, the ultimate destination of this strategy really comes into sharp focus.
00:14:40.879 --> 00:14:52.480
A company that actively divests a highly profitable division to protect its core engineering resources, redefines innovation as practical simplicity, and breaks its own monolithic products into accessible modules.
00:14:52.639 --> 00:14:54.559
They're building a very specific type of culture.
00:14:54.879 --> 00:14:55.279
They are.
00:14:55.440 --> 00:14:58.960
Walters envisions a distinctly leaner, sharper organization.
00:14:59.279 --> 00:15:04.799
And the defining metric of this future state is encapsulated in his mandate to value impact over activity.
00:15:05.120 --> 00:15:05.519
Yes.
00:15:05.840 --> 00:15:09.360
Because in the tech sector, activity is incredibly easy to generate.
00:15:09.679 --> 00:15:10.320
Oh, tell me about it.
00:15:10.559 --> 00:15:19.279
You can push out minor software updates every week, hold endless cross-departmental alignment meetings, layer new features onto legacy databases, and it looks super productive on a quarterly report.
00:15:19.519 --> 00:15:20.320
Right, you look busy.
00:15:20.720 --> 00:15:30.799
But impact, however, is solely measured by the client's ability to execute their core business faster, safer, and cheaper because your software got out of their way.
00:15:31.120 --> 00:15:36.480
The Finastra narrative we've explored today is truly a masterclass in the mechanics of focus.
00:15:36.720 --> 00:15:41.759
It proves that true modernization isn't about accumulating more capabilities.
00:15:41.919 --> 00:15:47.600
It is about relentlessly stripping away distractions until only the absolute core value remains.
00:15:48.000 --> 00:15:54.960
And having the discipline to stop doing perfectly good things so that you can dedicate your entire operational capacity to doing great things.
00:15:55.200 --> 00:15:58.159
I mean, that is arguably the rarest trait in corporate leadership today.
00:15:58.240 --> 00:15:58.960
Aaron Powell It really is.
00:15:59.120 --> 00:16:02.240
And you know, that principle scales down perfectly to the individual level too.
00:16:02.720 --> 00:16:02.960
Absolutely.
00:16:03.360 --> 00:16:13.440
Whether you are leading a multinational enterprise, managing a regional team, or simply trying to optimize your own daily workflows, we are all fighting a constant battle against creeping complexity.
00:16:13.840 --> 00:16:15.279
We all have our own feature creep.
00:16:15.679 --> 00:16:16.159
We do.
00:16:16.320 --> 00:16:22.720
We all maintain habits, projects, or workflows that are technically productive but inherently lack true impact.
00:16:22.960 --> 00:16:27.200
They are those heavy, fruit-bearing branches pulling energy away from the trunk.
00:16:27.679 --> 00:16:31.919
Which leaves us with the final thought to mull over long after this deep dive ends.
00:16:32.240 --> 00:16:38.639
Finestra intentionally severed a highly profitable, perfectly healthy division to achieve ultimate focus.
00:16:38.960 --> 00:16:50.080
So if you were forced to completely cut out or sell off one productive or profitable component of your own professional life right now to become radically better at your core mission, what would you choose to lose?
00:00:00.080 --> 00:00:01.600
Welcome to today's deep dive.
00:00:01.760 --> 00:00:05.599
Um, we are unpacking a really fascinating exclusive interview today.
00:00:05.839 --> 00:00:07.280
Yeah, it's a wildly interesting one.
00:00:07.599 --> 00:00:08.000
It really is.
00:00:08.080 --> 00:00:12.160
It's from the September 2025 issue of the IBSI FinTech Journal.
00:00:12.320 --> 00:00:21.519
And the whole piece focuses on Chris Walters, who uh he took over as CEO of the financial technology giant Finastra back in January of 2025.
00:00:21.839 --> 00:00:22.160
Right.
00:00:22.559 --> 00:00:30.559
So the mission for our analysis today, for you listening, is to basically deconstruct what I'd call a masterclass in modern corporate strategy.
00:00:30.800 --> 00:00:39.119
We're looking at how a massive, you know, entrenched global company actually learns to stop doing absolutely everything just so they can do the right things better.
00:00:39.439 --> 00:00:40.159
Which is rare, right.
00:00:40.320 --> 00:00:44.479
Because I mean, the tech industry has been utterly addicted to addition for the last, what, two decades.
00:00:44.799 --> 00:00:45.359
Oh, at least yeah.
00:00:45.679 --> 00:00:51.280
Growth is almost exclusively defined by adding more features or acquiring more companies, expanding into new verticals.
00:00:51.520 --> 00:00:53.439
Subtraction is just it's treated like a failure.
00:00:53.520 --> 00:00:53.679
Trevor Burrus, Jr.
00:00:53.840 --> 00:00:54.479
Like you're retreating.
00:00:54.799 --> 00:00:55.119
Exactly.
00:00:55.359 --> 00:00:59.200
But this source material it outlines a radical departure from that mindset.
00:00:59.359 --> 00:01:03.520
It actually shows an enterprise actively utilizing subtraction as a growth engine.
00:01:04.079 --> 00:01:08.799
And I think you see the consequences of that uh that addiction everywhere.
00:01:09.040 --> 00:01:10.719
I mean, think about the software you use every single day.
00:01:10.799 --> 00:01:11.359
Aaron Powell Oh, for sure.
00:01:11.599 --> 00:01:15.359
Maybe it's your primary work platform or I don't know, just your email client.
00:01:15.680 --> 00:01:19.920
Over the years, it has accumulated 50 features you literally never touch.
00:01:20.079 --> 00:01:21.680
Aaron Powell Just sitting there taking up space.
00:01:21.760 --> 00:01:22.079
Aaron Powell Right.
00:01:22.319 --> 00:01:34.400
You just want to execute a core task, but you are forced to navigate like three submenus, dismiss some annoying AI assistant, and ignore a dashboard that looks like a space shuttle control panel.
00:01:34.719 --> 00:01:35.200
Yeah, exactly.
00:01:35.519 --> 00:01:37.760
That is feature creep on a personal scale.
00:01:38.000 --> 00:01:46.719
But now multiply that frustration by a factor of about 10 million, because that is the reality for a multinational bank trying to modernize its infrastructure.
00:01:46.879 --> 00:01:49.599
They are just drowning in enterprise level complexity.
00:01:49.680 --> 00:01:53.840
Aaron Powell Which naturally brings us to how Walter spent the first half of 2025.
00:01:54.079 --> 00:01:57.439
Because he bypassed that traditional, you know, new CEO Victory Lab.
00:01:57.840 --> 00:01:58.719
The usual PR tour.
00:01:59.040 --> 00:01:59.920
Yeah, the PR tour.
00:02:00.079 --> 00:02:08.800
Instead, he spent six months on this grueling global tour across North America, Europe, Asia, the Middle East, just sitting directly with customers.
00:02:09.039 --> 00:02:13.439
And those conversations highlighted a, well, a universal paradox.
00:02:13.840 --> 00:02:14.240
Which is what?
00:02:14.560 --> 00:02:27.759
Basically, these institutions are under immense pressure to adopt cutting-edge innovation, but they're simultaneously crippled by the burden of maintaining absolute security, not to mention navigating increasingly dense regulatory environments.
00:02:27.840 --> 00:02:28.000
Trevor Burrus, Jr.
00:02:28.159 --> 00:02:28.319
Right.
00:02:28.400 --> 00:02:32.000
Because every financial institution on earth desperately wants modernization.
00:02:32.560 --> 00:02:39.599
But enterprise tech companies fundamentally struggle to deliver it without accidentally, you know, dumping more complexity into the client's ecosystem.
00:02:39.680 --> 00:02:40.159
Aaron Powell Exactly.
00:02:40.319 --> 00:02:40.479
Trevor Burrus, Jr.
00:02:40.560 --> 00:02:47.520
So Walter's listening tour, it actually reads less like a standard corporate meet and greet and more like a global intervention.
00:02:47.599 --> 00:02:48.800
Trevor Burrus That's a great way to put it.
00:02:48.879 --> 00:02:51.759
Trevor Burrus The core demand from these customers wasn't for more features.
00:02:51.840 --> 00:02:53.520
It was a plea for simplicity.
00:02:53.680 --> 00:03:01.439
They want speed, easier integration, and uh a strategic ally rather than just another software vendor hawking licenses.
00:03:01.520 --> 00:03:07.599
Aaron Powell And that term, strategic ally, it carries very specific operational weight in this context.
00:03:07.680 --> 00:03:11.360
Aaron Powell So Well, a vendor simply sells you a tool and walks away, right?
00:03:11.520 --> 00:03:15.360
They leave your IT department to figure out how it fits into your existing tech stack.
00:03:15.840 --> 00:03:22.159
But a strategic ally actually aligns their own product development roadmaps with your long-term survival.
00:03:22.639 --> 00:03:22.800
Okay.
00:03:23.360 --> 00:03:35.759
And the universal feedback Walters got was that Finastra's products were powerful, but the sheer gravity of the company's sprawling portfolio was just it was making them too difficult to implement and scale quickly.
00:03:36.159 --> 00:03:47.280
Okay, let's apply some critical friction to this narrative, though, because I mean selling the market on terms like customer-led and strategic partner is basically the oldest play in the enterprise software playbook.
00:03:47.520 --> 00:03:48.000
Oh, absolutely.
00:03:48.319 --> 00:03:48.479
Right?
00:03:48.639 --> 00:03:59.039
A new CEO goes on a listening tour, they issue a press release filled with synergistic buzzwords, maybe initiate a minor rebrand, and then operations just continue exactly as they did before.
00:03:59.280 --> 00:04:05.439
Claiming to prioritize customer simplicity over corporate empire building is super easy to say in a journal interview.
00:04:05.759 --> 00:04:10.879
Yeah, and the skepticism is totally warranted given the industry's history of empty pivots.
00:04:11.039 --> 00:04:18.079
But the validation for Walter's claims here lies strictly in the timeline and the severity of the action they actually took.
00:04:18.319 --> 00:04:18.560
Okay.
00:04:18.800 --> 00:04:21.040
So the listening tour concluded in the spring.
00:04:21.199 --> 00:04:27.439
And in May of 2025, Finashra didn't just launch a marketing campaign promising simpler software.
00:04:27.680 --> 00:04:30.399
They executed a massive corporate divestiture.
00:04:30.720 --> 00:04:31.680
Wait, they sold something off?
00:04:31.920 --> 00:04:32.399
Yes.
00:04:32.639 --> 00:04:38.079
They sold off their treasury and capital markets business known as TCM to the private equity firm Apex.
00:04:38.480 --> 00:04:38.639
Wow.
00:04:38.720 --> 00:04:38.879
Okay.
00:04:39.040 --> 00:04:44.399
But selling a massive division like TCM usually signals one of two things in the corporate world, right?
00:04:44.639 --> 00:04:52.319
Either the division is bleeding money and dragging down the quarterly earnings, or the parent company is desperate for a quick cash injection to cover debt.
00:04:52.720 --> 00:04:54.000
Right, the usual suspects.
00:04:54.319 --> 00:04:59.759
Yeah, the PR spin is always about like streamlining, but the reality is frequently just financial engineering.
00:04:59.920 --> 00:05:04.240
So exactly what was the structural motivation here if we assume it wasn't just a fire sale?
00:05:04.639 --> 00:05:09.680
Well, the financials of the TCM division disrupt that whole fire sale narrative entirely.
00:05:09.920 --> 00:05:17.680
Walters is highly transparent in the IBSI piece that TCM was a remarkably strong, profitable, and healthy business unit.
00:05:18.160 --> 00:05:18.639
Wait, really?
00:05:18.720 --> 00:05:20.319
So they weren't dumping a bad asset?
00:05:20.560 --> 00:05:21.040
Not at all.
00:05:21.199 --> 00:05:23.920
Apex wasn't buying a distressed asset to gut it.
00:05:24.000 --> 00:05:26.240
They bought a thriving division to scale it.
00:05:26.399 --> 00:05:32.000
For FENASTRA, the sale was entirely about eliminating operational and mental fragmentation.
00:05:32.240 --> 00:05:35.279
Walters described the move with a very specific phrase.
00:05:35.439 --> 00:05:38.160
He called it being bold in service of focus.
00:05:38.560 --> 00:05:39.839
Bold in service of focus.
00:05:40.000 --> 00:05:40.240
Okay.
00:05:40.399 --> 00:05:48.480
I mean, maintaining a division like TCM means splitting your engineering resources, dividing your regulatory compliance teams, fracturing executive attention.
00:05:48.720 --> 00:05:48.959
Exactly.
00:05:49.120 --> 00:05:51.839
It's like, okay, think of it like managing a massive orchard.
00:05:52.319 --> 00:05:54.959
You have this beautiful, heavy, fruit-bearing branch.
00:05:55.120 --> 00:06:02.720
It's perfectly healthy and generating a great yield, but it is drawing massive amounts of water and soil nutrients away from the central root system of the tree.
00:06:02.959 --> 00:06:04.079
That's a perfect analogy.
00:06:04.480 --> 00:06:04.879
Right.
00:06:05.040 --> 00:06:15.680
If you make the painful decision to prune that branch, the root system suddenly reroutes all that biological infrastructure into the main trunk, which makes it highly resilient to storms.
00:06:16.079 --> 00:06:18.480
And that's exactly what pruning the TCM branch did.
00:06:18.639 --> 00:06:27.360
It allowed Finastra to forcefully redirect capital and honestly, more importantly, engineering bandwidth into their absolute core leadership areas.
00:06:27.439 --> 00:06:28.720
Aaron Powell Which are what, specifically?
00:06:29.040 --> 00:06:31.199
Lending, payments, and core banking.
00:06:31.519 --> 00:06:35.519
These three pillars represent the central nervous system of global finance.
00:06:35.759 --> 00:06:40.399
Institutions simply cannot afford latency or integration failures in these domains.
00:06:40.560 --> 00:06:40.800
Right.
00:06:41.040 --> 00:06:51.040
So by shedding the lucrative distraction of TCM, Finastra basically manufactured the internal capacity required to completely redefine how those core products actually function.
00:06:51.120 --> 00:06:55.920
Aaron Powell And untangling a major division also forces a company to reckon with its own friction points, right?
00:06:56.160 --> 00:07:02.560
Because if the overarching mandate is to be a simpler strategic ally, well, fixing the software is only half the battle.
00:07:02.639 --> 00:07:02.800
Trevor Burrus, Jr.
00:07:02.879 --> 00:07:03.199
Oh, yeah.
00:07:03.360 --> 00:07:06.720
The relationship itself is usually bogged down in legacy bureaucracy.
00:07:06.800 --> 00:07:07.439
Aaron Powell Exactly.
00:07:07.600 --> 00:07:15.279
I mean, a multi-year enterprise tech contract can languish in legal review for six to eight months before a single line of code is ever deployed.
00:07:15.600 --> 00:07:17.439
And Walters recognizes that.
00:07:17.680 --> 00:07:21.199
Administrative friction is just as damaging as technical friction.
00:07:21.360 --> 00:07:26.959
So this sharpened strategy includes a mandate to fundamentally overhaul how the company does business.
00:07:27.279 --> 00:07:28.399
Meaning what, practically?
00:07:28.720 --> 00:07:34.240
It means instituting simplified contracting models and dramatically accelerating implementation times.
00:07:34.480 --> 00:07:44.480
The objective is to drastically shrink the window between the moment a client signs a contract and the moment they actually experience tangible, measurable value in their daily operations.
00:07:44.560 --> 00:07:50.720
Aaron Powell But I mean, accelerated implementation only matters if the technology being deployed is actually built for the future.
00:07:50.879 --> 00:07:57.360
And you can't talk about a three to five year innovation horizon in 2025 without slamming into the reality of AI.
00:07:57.680 --> 00:07:58.319
Oh, of course not.
00:07:58.639 --> 00:08:02.800
The source material notes extraordinary customer interest in artificial intelligence.
00:08:02.959 --> 00:08:13.439
But the trap here is that legacy tech companies notoriously just they slap a thin layer of generative AI over a 20-year-old database just to market the product as AI enabled.
00:08:13.600 --> 00:08:13.759
Trevor Burrus, Jr.
00:08:13.839 --> 00:08:14.000
Right.
00:08:14.160 --> 00:08:18.639
Superficial AI layering is a massive risk when you're modernizing legacy systems.
00:08:18.800 --> 00:08:25.120
But Finastra's approach, as detailed in the interview, is deliberately pragmatic to avoid exactly that trap.
00:08:25.519 --> 00:08:25.600
Okay.
00:08:25.680 --> 00:08:26.560
How are they doing it differently?
00:08:26.879 --> 00:08:28.480
They're running a dual-track strategy.
00:08:28.639 --> 00:08:33.600
So they deploy AI internally first and then embed it into customer products.
00:08:33.679 --> 00:08:34.559
Aaron Powell Internally first.
00:08:34.960 --> 00:08:35.039
Yeah.
00:08:35.279 --> 00:08:39.039
Internally, the primary targets were actually the software engineers.
00:08:39.279 --> 00:08:46.399
AI tools were introduced to automate routine coding tasks, run initial bug checks, manage all that boilerplate development.
00:08:46.559 --> 00:08:46.720
Trevor Burrus, Jr.
00:08:46.799 --> 00:08:47.679
Oh, I love that.
00:08:47.919 --> 00:08:52.639
Using AI to clear out routine coding work creates this fascinating ripple effect.
00:08:52.799 --> 00:09:01.200
Because if your developers aren't wasting hours writing boilerplate code, you suddenly free up your most expensive senior talent to tackle deep architectural debt.
00:09:01.519 --> 00:09:01.840
Exactly.
00:09:02.080 --> 00:09:07.600
The underlying structural mess that causes enterprise software to feel bloated and slow can finally be dismantled.
00:09:07.679 --> 00:09:16.080
Once that internal efficiency is proven, then the transition to customer-facing AI becomes about actual utility rather than just, you know, marketing flash.
00:09:16.480 --> 00:09:23.759
And the external customer-facing AI applications are strictly bound to that overarching theme we talked about: simplicity.
00:09:24.080 --> 00:09:31.840
Finastra is utilizing embedded AI to automate incredibly time-consuming repetitive steps within their clients' daily workflows.
00:09:32.240 --> 00:09:33.440
Make the boring stuff disappear.
00:09:33.840 --> 00:09:34.159
Right.
00:09:34.399 --> 00:09:38.799
And it's also powering more intuitive, instantly accessible support systems.
00:09:39.039 --> 00:09:43.840
But the critical boundary Walters draws here involves the concept of responsible AI.
00:09:44.159 --> 00:09:45.120
Responsible in what sense?
00:09:51.840 --> 00:09:55.600
The AI's outputs must be entirely transparent, explainable, and fair.
00:09:55.919 --> 00:09:56.879
That makes total sense.
00:09:57.039 --> 00:10:04.639
And that insistence on functional, explainable technology over flaffy buzzwords really seems to be reshaping their entire software philosophy.
00:10:04.879 --> 00:10:09.440
The interview highlights a major pivot in how Finastra approaches the concept of open finance.
00:10:09.759 --> 00:10:11.039
Yeah, that was a huge point.
00:10:11.440 --> 00:10:15.759
Because for years, open finance was just this collection of technical specifications, right?
00:10:15.919 --> 00:10:21.519
Companies boasted about being cloud native and API enabled as if those architectural choices were the ultimate goal.
00:10:21.919 --> 00:10:25.600
And Walters completely redefines open finance in this interview.
00:10:25.840 --> 00:10:29.600
He shifts it from a technical architecture to a set of practical outcomes.
00:10:30.000 --> 00:10:30.879
Okay, so what does it mean now?
00:10:31.200 --> 00:10:41.600
FNASTRA remains committed to building open by design systems, sure, with robust APIs and cloud infrastructure, but those technical realities are no longer the focal point.
00:10:41.840 --> 00:10:50.399
Because the bank executive evaluating the software does not care about the elegance of the API if the system still requires a 12-month deployment cycle.
00:10:50.799 --> 00:10:51.840
Right, they just want it to work.
00:10:52.159 --> 00:10:52.720
Exactly.
00:10:52.960 --> 00:11:01.120
Walters emphasizes that open finance now simply means delivering speed, absolute reliability, and faster time to value for the customer.
00:11:01.440 --> 00:11:07.679
And moving the conversation from the underlying engine to the actual destination changes the entire sales dynamic.
00:11:07.840 --> 00:11:15.840
Because if your primary metric of success is how easily a client can use your tool, you inevitably uncover markets that were previously locked out by complexity.
00:11:16.080 --> 00:11:17.279
Yeah, it opens up a whole new world.
00:11:17.600 --> 00:11:22.159
Finastra built its empire serving massive Tier 1 global banks.
00:11:22.399 --> 00:11:31.440
But the interview reveals a strategic push into underserved segments, specifically mid-sized institutions and organizations operating in emerging markets.
00:11:31.759 --> 00:11:32.000
Right.
00:11:32.159 --> 00:11:42.080
Because a regional credit union or a mid-sized private credit firm, they face the exact same regulatory gauntlet and shifting consumer expectations as a massive global bank.
00:11:42.399 --> 00:11:44.240
Just with way fewer resources.
00:11:44.639 --> 00:11:45.120
Precisely.
00:11:45.279 --> 00:11:48.559
They have a fraction of the IT personnel and budget to manage it.
00:11:48.799 --> 00:11:56.960
This market expansion actually relies heavily on a startling admission Walters makes regarding Finastra's flagship product, which is called Low NIQ.
00:11:57.200 --> 00:11:57.840
What does he admit?
00:11:58.080 --> 00:12:06.879
He candidly acknowledges that for rapid growth segments like private credit, low NIQ is actually too feature-rich and fundamentally more complex than what those institutions require.
00:12:07.200 --> 00:12:07.759
Oh wow.
00:12:08.000 --> 00:12:14.080
A CEO publicly admitting their flagship product is too complex for a target market is a rare moment of corporate humility.
00:12:14.399 --> 00:12:14.639
Very rare.
00:12:14.879 --> 00:12:18.960
Think of Low IQ like a massive, top-of-the-line Swiss Army knife.
00:12:19.039 --> 00:12:23.279
It's got a magnifying glass, a fish scaler, pliers, a saw blade.
00:12:23.519 --> 00:12:28.799
And that is brilliant if you are a tier one bank trying to survive in the wilderness of global finance.
00:12:29.120 --> 00:12:29.919
You need all those tools.
00:12:30.240 --> 00:12:30.399
Right.
00:12:30.639 --> 00:12:37.200
But a mid-sized private credit firm just needs a razor-sharp, highly reliable main blade to open a box.
00:12:37.360 --> 00:12:41.840
Handing them the massive multi-tool just guarantees they will cut themselves trying to figure out how to open it.
00:12:42.080 --> 00:12:46.879
And forcing a monolithic system onto a mid-market client just results in implementation failure.
00:12:47.039 --> 00:12:52.480
So to capture these underserved segments, Finasra has to fundamentally alter the architecture of their offerings.
00:12:52.799 --> 00:12:53.600
So they have to break it down.
00:12:53.919 --> 00:12:54.320
Exactly.
00:12:54.559 --> 00:12:57.840
The solution lies in scalable modular platforms.
00:12:58.080 --> 00:13:05.279
Functionally, this requires containerizing the legacy software, breaking the massive monolith down into discrete microservices.
00:13:06.159 --> 00:13:16.480
This allows a regional institution to purchase and integrate only the specific modules they actually need without inheriting the processing bloat or, you know, the massive price tag of the entire enterprise system.
00:13:16.879 --> 00:13:22.159
But breaking down monolithic software into modular components cannot be done in a vacuum.
00:13:22.320 --> 00:13:26.960
A modular approach necessitates a robust ecosystem to plug those modules into.
00:13:27.200 --> 00:13:27.360
Right.
00:13:27.440 --> 00:13:28.159
You need partners.
00:13:28.480 --> 00:13:35.519
And the interview outlines an aggressive expansion of Finastra's partner network categorized into three distinct layers.
00:13:36.159 --> 00:13:42.240
First, they are integrating with nimble fintechs, who provide highly specialized complementary capabilities.
00:13:42.559 --> 00:13:43.200
That's layer one.
00:13:43.440 --> 00:13:53.120
Then second, they are leaning heavily on system integrators to manage the actual deployment, ensuring that the installation of these modular platforms is as frictionless as possible.
00:13:53.440 --> 00:13:58.480
And then the third crucial layer of that partnership strategy involves deepening ties with hyperscalers.
00:13:58.799 --> 00:13:59.840
To provide the cloud space.
00:14:00.080 --> 00:14:00.399
Exactly.
00:14:00.559 --> 00:14:06.960
To provide the vast cloud infrastructure necessary to run these modular platforms globally with zero latency.
00:14:07.200 --> 00:14:11.759
Walters frames this entire ecosystem approach as just a necessary evolution.
00:14:12.080 --> 00:14:13.440
The walled garden is dead.
00:14:13.679 --> 00:14:14.320
It is.
00:14:14.559 --> 00:14:23.840
The era of the walled garden, where a tech giant attempts to build, sell, and implement every single piece of the technology stack themselves is over.
00:14:24.240 --> 00:14:33.759
Embracing partnerships creates better outcomes for the client, it expands market reach for the integrators, and it extracts maximum value from Finastra's core code.
00:14:34.080 --> 00:14:40.720
So looking ahead to the five-year vision laid out in the journal, the ultimate destination of this strategy really comes into sharp focus.
00:14:40.879 --> 00:14:52.480
A company that actively divests a highly profitable division to protect its core engineering resources, redefines innovation as practical simplicity, and breaks its own monolithic products into accessible modules.
00:14:52.639 --> 00:14:54.559
They're building a very specific type of culture.
00:14:54.879 --> 00:14:55.279
They are.
00:14:55.440 --> 00:14:58.960
Walters envisions a distinctly leaner, sharper organization.
00:14:59.279 --> 00:15:04.799
And the defining metric of this future state is encapsulated in his mandate to value impact over activity.
00:15:05.120 --> 00:15:05.519
Yes.
00:15:05.840 --> 00:15:09.360
Because in the tech sector, activity is incredibly easy to generate.
00:15:09.679 --> 00:15:10.320
Oh, tell me about it.
00:15:10.559 --> 00:15:19.279
You can push out minor software updates every week, hold endless cross-departmental alignment meetings, layer new features onto legacy databases, and it looks super productive on a quarterly report.
00:15:19.519 --> 00:15:20.320
Right, you look busy.
00:15:20.720 --> 00:15:30.799
But impact, however, is solely measured by the client's ability to execute their core business faster, safer, and cheaper because your software got out of their way.
00:15:31.120 --> 00:15:36.480
The Finastra narrative we've explored today is truly a masterclass in the mechanics of focus.
00:15:36.720 --> 00:15:41.759
It proves that true modernization isn't about accumulating more capabilities.
00:15:41.919 --> 00:15:47.600
It is about relentlessly stripping away distractions until only the absolute core value remains.
00:15:48.000 --> 00:15:54.960
And having the discipline to stop doing perfectly good things so that you can dedicate your entire operational capacity to doing great things.
00:15:55.200 --> 00:15:58.159
I mean, that is arguably the rarest trait in corporate leadership today.
00:15:58.240 --> 00:15:58.960
Aaron Powell It really is.
00:15:59.120 --> 00:16:02.240
And you know, that principle scales down perfectly to the individual level too.
00:16:02.720 --> 00:16:02.960
Absolutely.
00:16:03.360 --> 00:16:13.440
Whether you are leading a multinational enterprise, managing a regional team, or simply trying to optimize your own daily workflows, we are all fighting a constant battle against creeping complexity.
00:16:13.840 --> 00:16:15.279
We all have our own feature creep.
00:16:15.679 --> 00:16:16.159
We do.
00:16:16.320 --> 00:16:22.720
We all maintain habits, projects, or workflows that are technically productive but inherently lack true impact.
00:16:22.960 --> 00:16:27.200
They are those heavy, fruit-bearing branches pulling energy away from the trunk.
00:16:27.679 --> 00:16:31.919
Which leaves us with the final thought to mull over long after this deep dive ends.
00:16:32.240 --> 00:16:38.639
Finestra intentionally severed a highly profitable, perfectly healthy division to achieve ultimate focus.
00:16:38.960 --> 00:16:50.080
So if you were forced to completely cut out or sell off one productive or profitable component of your own professional life right now to become radically better at your core mission, what would you choose to lose?
