Latest / Chief in Tech Deep Dive Shortcast / Chief in Tech S1E64 - Avery Anne Banta : Leading Organization Transformation

Transcript

Chief in Tech S1E64 - Avery Anne Banta : Leading Organization Transformation · Chief in Tech Deep Dive Shortcast

0:00
You know that feeling when you log into work
0:02
on, I don't know, a random Tuesday, and it feels
0:04
like the tectonic plates of your entire industry
0:07
have just shifted overnight? Oh, yeah, totally.
0:10
Everyone knows that feeling. Right. You get an
0:12
email about a sudden restructuring, or maybe
0:14
a massive pivot in strategy, or like a whole
0:17
new operating model that suddenly changes every
0:20
single KPI you've been working toward for the
0:22
last six months. Exactly. And I mean, that is...
0:25
basically the defining feature of the modern
0:27
corporate environment right now. Yeah, it really
0:29
is. That constant sort of lurching sensation
0:32
of instability. It isn't a temporary phase of
0:35
business anymore. It is the baseline operating
0:37
condition. And usually when we talk about navigating
0:40
this kind of corporate volatility, the conventional
0:43
advice leans very defensive. Very, yeah. Brace
0:46
for impact. Exactly. The literature tells you
0:48
to brace for impact, manage the fallout, and
0:51
just try to survive the transition without losing
0:53
your best people. But today's deep dive is looking
0:55
at a master class session titled Leading Organization
0:58
Transformation that takes a completely different
1:01
angle. A really fascinating angle, honestly.
1:04
It presents a blueprint for stopping the mere
1:07
management of change and instead actually using
1:09
that volatility to inspire and accelerate a team.
1:13
Which sounds impossible, but they map it out.
1:16
Okay, let's unpack this because the central premise
1:18
in these session notes establishes three specific
1:21
pillars for modern leadership purpose clarity
1:25
and empathy Yeah, those three core pillars right
1:29
and the stated goal of combining these three
1:31
is to create what the text calls Stability amid
1:34
transition, you know allowing leaders to communicate
1:37
with conviction and drive results Well, the phrase
1:40
stability amid transition is really where we
1:43
need to anchor this discussion Because honestly,
1:45
it sounds like a paradox. It really does. The
1:48
text is arguing that true stability doesn't come
1:51
from a static business model because, well, static
1:53
business models don't exist anymore. No, not
1:55
at all. So stability has to be generated internally
1:59
through the actual behavioral mechanics of the
2:01
leadership team itself. See, I have to push back
2:05
on the practical application of that. Creating
2:07
stability while everything is in transition sounds
2:11
ideal on a whiteboard sure It's like trying to
2:13
rebuild an airplane while you are flying it So
2:16
let's bring this into the day -to -day reality
2:18
of a director or a VP How does a leader actually
2:22
communicate with conviction when the ground is
2:24
constantly shifting underneath them? It's incredibly
2:26
tough Like, if a new competitor enters the market
2:29
or a supply chain collapses, how do you look
2:31
your team in the eye and say, I know exactly
2:34
where we are going when the strategic destination
2:36
just changed an hour ago? Well, you don't. You
2:39
don't. No. And that is a really common trap leaders
2:42
fall into. They confuse conviction with certainty.
2:46
Oh, that's an interesting distinction. Right.
2:48
You cannot offer certainty about the future state
2:51
of a volatile market. It's impossible. But you
2:53
can offer conviction in your method of navigating
2:56
it. Okay, I see. And this is exactly why the
2:59
framework elevates empathy from, you know, just
3:02
a peripheral soft skill to a central load -bearing
3:05
pillar of the strategy. Okay. Empathy is actually
3:08
the mechanism that regulates the team's cognitive
3:11
load during a crisis. Wait, walk me through the
3:14
actual mechanics of that. How does empathy regulate
3:16
cognitive load? Okay, so when an organization
3:19
announces a massive pivot, the natural human
3:22
response is a spike in anxiety. Oh, of course.
3:24
Everyone panics. Exactly. Employees immediately
3:27
wonder about their job security, their new reporting
3:30
lines, or if their skills are suddenly obsolete.
3:33
Right. Yeah. And when a team is trapped in that
3:36
state of neurological threat, their executive
3:38
functioning literally shuts down. They cannot
3:41
process complex tasks or execute on the new strategy.
3:45
Wow. So they are biologically incapable of adapting.
3:49
Exactly. So if a leader tries to force execution
3:52
without addressing the disruption, if they just
3:55
say ignore the noise, hit your targets, they
3:57
are fighting biology. That never works. No. So
4:03
calibrated empathy is the tool a leader uses
4:05
to acknowledge the reality of the turbulence.
4:08
By validating the friction and making the team
4:10
feel heard, the leader actually diffuses that
4:14
threat response. Okay, so the anxiety drops.
4:17
Right. The anxiety drops, the cognitive bandwidth
4:20
opens back up, and the team can actually focus
4:23
their energy on the work of the transition. So
4:25
empathy isn't just about being a nice person.
4:27
It's an operational requirement for keeping the
4:30
brain's prefrontal cortex online so the work
4:32
can actually get done. Yes, it is a purely strategic
4:36
asset. You provide psychological stability to
4:39
offset the operational instability. To understand
4:42
how you actually apply that level of calibrated
4:45
empathy at scale, You have to look at the kind
4:47
of leader who designs these systems. Absolutely.
4:50
The notes we are analyzing center on a specific
4:52
case study, a leader named Avery Bonta. And her
4:56
title at Globe Telecom gives a really good sense
4:58
of the operational territory we are dealing with
5:00
here. It's a huge scope. Yeah. She is the VP
5:04
and head of HR business partners, change management
5:06
and organization development. And that combination
5:09
of responsibilities means she isn't just dealing
5:12
with human resources in the traditional administrative
5:15
sense. Right, like payroll and benefits. Exactly.
5:18
Not just that. She is responsible for the architectural
5:21
alignment of how the company functions, how it
5:25
adapts to external pressure, and how its people
5:28
are actually deployed to meet those challenges.
5:30
Well, her bio highlights a foundational background
5:32
in both communication and business. And there
5:35
is a phrase in the text that attempts to bridge
5:37
her approach. It states, she brings a unique
5:40
blend of strategic foresight with empathy and
5:43
executional excellence. That's the key phrase
5:45
right there. But wait, we just established empathy
5:47
as a strategic tool for cognitive regulation.
5:50
But I really want to challenge the idea that
5:51
empathy and executional excellence can peacefully
5:54
coexist at the highest levels of corporate strategy.
5:57
Okay, why is that? Because traditionally, deep
5:59
empathy requires slowing down. It requires making
6:02
space for people to process, adapt, and voice
6:04
concerns. True. But executional excellence, on
6:07
the other hand, is usually defined by speed.
6:10
Ruthlessly hitting targets and cutting away anything
6:12
that introduces friction. Those seem fundamentally
6:14
at odds. What's fascinating here is that her
6:17
dual background in communication and business
6:19
is the exact synthesis required to resolve that
6:23
tension. Oh, really? Yeah. Because we are conditioned
6:26
to view execution and empathy as a zero -sum
6:29
game. Like, you have to pick one. But this framework
6:32
argues they are actually interdependent variables.
6:36
Let's look at the actual mechanism of what happens
6:38
when you separate them. Yeah, let's hear it.
6:40
So. If a leadership team optimizes entirely for
6:44
executional excellence and zero empathy, they
6:47
can easily force a team to hit their Q3 targets.
6:49
Sure, through sheer willpower. Right. They use
6:52
pressure, mandates, speed. But in doing so, they
6:55
accrue massive organizational debt. Oh, burnout.
6:59
Exactly. They burn out their top performers,
7:01
destroy psychological safety, and by Q4, retention
7:04
drops and execution falls off a cliff. The speed
7:08
was a total illusion. That happens all the time.
7:10
All the time. But conversely, if an organization
7:14
overindexes on empathy without business acumen,
7:18
you end up with endless processing sessions,
7:20
moving targets, and a very happy, well -adjusted
7:23
team that ultimately goes bankrupt. because they
7:26
failed to ship a product. Exactly. So her background
7:29
in communication allows her to deploy the empathy,
7:32
you know, listening, translating concerns, regulating
7:34
the anxiety. But the background in business dictates
7:37
the boundaries of that empathy. Yes, that is
7:40
perfectly stated. The business acumen ensures
7:43
that every empathetic intervention is ultimately
7:45
steering the team back toward driving business
7:48
impact. I like that. The empathy basically acts
7:51
as the lubricant for the engine of executional
7:54
excellence. It prevents the operational friction
7:56
from overheating and seizing the entire system.
8:00
But concepts like organizational debt and calibrated
8:02
empathy only truly matter if they can scale.
8:05
Right. Scaling is the hard part. The masterclass
8:08
notes detail a scenario where this approach was
8:10
tested at a massive enterprise -wide level at
8:13
Globe Telecom. She was tasked with designing
8:16
and launching reorganizations across three vastly
8:18
different areas. The commercial, technical, and
8:21
business support functions. Exactly. Attempting
8:25
to reimagine an operating model for just one
8:27
of those functions is highly complex, simply
8:30
because of all the dependencies involved. Oh,
8:32
absolutely. But attempting to execute that across
8:35
commercial, technical, and support functions
8:37
simultaneously, that is a monumental logistical
8:41
and cultural challenge. To put the sheer difficulty
8:44
of that into perspective for you listening, imagine
8:46
trying to conduct a massive symphony orchestra.
8:49
OK, I like this analogy. But the catch is every
8:52
single section is fundamentally wired to play
8:54
a totally different genre of music. Right. Your
8:57
commercial teams, sales, marketing, they are
9:00
the brass section. They play this fast -paced,
9:02
highly reactive, improvisational jazz because
9:04
they have to respond to market trends and customer
9:07
demands instantly. Makes sense. Your technical
9:09
teams, engineering, IT, they are the strings.
9:12
They are playing incredibly complex, precise
9:14
math rock where every single variable has to
9:17
be perfectly aligned or the entire system crashes.
9:19
Very true. And then your business support functions,
9:21
legal, finance, HR, they are the percussion,
9:24
holding down a steady, highly regulated classical
9:27
rhythm that keeps the entire enterprise compliant
9:30
and grounded. Right, the steady beat. The mandate
9:32
here wasn't just to make them play nicely together.
9:34
The mandate was to rewrite the sheet music and
9:36
fundamentally alter the operating model while
9:39
the concert was actively happening. And honestly,
9:41
the friction between those different sections
9:43
is exactly where most enterprise -wide reorganizations
9:47
fail. Because they don't speak the same language.
9:49
Exactly. You cannot walk up to the brass section
9:52
and the percussion section and hand them the
9:54
exact same set of technical instructions. They
9:57
don't value the same metrics. They don't operate
9:59
at the same speed, and they often view each other
10:02
as obstacles. The sales team just wants the product
10:04
to ship yesterday, and the engineering team won't
10:06
ship it until it's structurally flawless. Right.
10:09
They are essentially two completely different
10:12
cultures operating under one roof. Which requires
10:14
a unifying mechanism, I assume. It does. And
10:17
the notes state that her approach evolved building
10:20
teams equipped for the future by establishing
10:22
clarity and purpose. There's that word purpose
10:25
again. Yes. The shared purpose is really the
10:28
only thing that can bridge those cultural divides.
10:31
If the overarching purpose is clearly defined
10:33
and relentlessly communicated, the technical
10:36
side understands why speed is suddenly a priority.
10:39
And the commercial side understands why a structural
10:42
delay is necessary for long -term stability.
10:44
Exactly. The HR leader in this scenario essentially
10:48
acts as the chief translator, ensuring the overarching
10:51
strategy makes sense in the native language of
10:54
each specific department. Well, conducting that
10:56
kind of multi -genre orchestra requires a very
10:59
specific and honestly kind of counterintuitive
11:02
set of skills. It really does. When you look
11:04
at the credentials listed in her toolkit to actually
11:07
architect this level of change, the text notes
11:10
she is both a PMP, a project management professional,
11:13
and an Agilist. along with training from the
11:16
Project Management Institute, INSEAD, Kellogg,
11:19
and Ameritas. Right. And her defined sweet spot
11:22
is thriving at the exact intersection of strategy,
11:25
people, and change. But here's where it gets
11:28
really interesting. Oh, I know where you're going
11:30
with this. For those tracking the methodologies
11:32
here, holding both a PMP and an Agile certification
11:35
is a bit of a structural paradox. These are two
11:38
frameworks that are historically at war with
11:40
one another. Yeah, they represent completely
11:42
different philosophies of how work should actually
11:44
be accomplished. Right. I mean, you have the
11:46
waterfall structure of a traditional PMP. Massive
11:49
upfront planning, rigid sequential timelines,
11:53
heavy risk mitigation. You literally do not move
11:55
to phase two until phase one is signed in blood.
11:58
Very rigid. And then you have the iterative sprint
12:00
methodology of Agile, which is built entirely
12:03
on the premise that your initial plan is probably
12:05
wrong, so you need to move fast, pivot constantly,
12:08
and adapt to continuous feedback. Right. Agility.
12:11
Having credentials in both feels a bit like holding
12:14
a PhD in both strict classical architecture and
12:17
improvisational street art. How do those actually
12:19
combine in practice without just canceling each
12:22
other out? Well, the synthesis of those two frameworks
12:25
is actually the secret to executing the stability
12:28
amid transition mandate we discussed earlier.
12:30
Okay, how so? If a leader only uses traditional
12:34
waterfall project management, they will build
12:36
an incredibly detailed, highly stable five -year
12:39
roadmap. Which looks great in a boardroom. It
12:42
does, but the moment a new AI technology disrupts
12:44
their market in year two, that rigid plan completely
12:47
shatters, and the organization cannot pivot fast
12:50
enough to survive. But what if they only use
12:52
Agile? If they only use Agile at the enterprise
12:56
strategy level, they end up with endless frantic
12:58
pivoting. Just constant whiplash. Exactly. They
13:02
can adapt to every minor market fluctuation,
13:05
but they lack the structural foundation to actually
13:07
land a massive multi -year reorganization. They
13:10
become way too reactive. So how did Avery Banta
13:13
combine them? Her approach utilizes the macro
13:17
structure of the PMP framework to build the fences.
13:20
Build the fences, okay. Right. The traditional
13:23
project management methodology secures the multi
13:26
-million dollar budget, defines the absolute
13:28
regulatory requirements, and sets the non -negotiable
13:31
end dates. So that provides the psychological
13:34
and financial stability. Yes. But inside those
13:38
heavily guarded fences, the Agile methodology
13:40
is deployed. So he allows the individual teams
13:43
the flexibility to run iterative sprints, to
13:46
test new workflows, and to pivot on the micro
13:48
level when a process fails. Okay, I get it. So
13:52
the PMP framework determines what the ultimate
13:54
destination is and ensures the company has the
13:57
fuel to get there, while the Agile framework
13:59
empowers the teams to constantly recalculate
14:02
the route in real time as they encounter roadblocks.
14:04
Exactly that. It provides teams with the psychological
14:07
safety of a heavily structured, well -funded
14:10
plan. But it grants them the operational autonomy
14:13
to adapt when the reality on the ground inevitably
14:16
changes. It is the architectural embodiment of
14:19
strategy meeting people. That's a great way to
14:22
put it. It's a fascinating hybrid approach. But
14:25
systems and frameworks like PMP or Agile, no
14:28
matter how brilliantly integrated, only take
14:31
an organization so far. Right. At the end of
14:33
the day, you're dealing with people. Exactly.
14:35
Eventually, the massive reorganization ends.
14:38
The operating models are locked in, the new org
14:41
charts are published, and the external consultants
14:43
go home. we have to look at what happens to the
14:46
human beings left to actually run the new machine.
14:49
The source text makes a big point to emphasize
14:51
the long game here, well beyond just the operational
14:54
shifts. The human legacy of the transformation?
14:56
Yes, the legacy. Because the notes highlight
14:59
her 20 plus years as a dedicated mentor. 20 years
15:02
is a long time. It is, and her specific target
15:05
audience for this mentorship has been aspiring
15:07
project managers and emerging leaders. And the
15:10
text defines her core focus areas for these mentees,
15:13
not as technical proficiencies, but as building
15:16
capability, confidence, and a deep -seated belief
15:19
in their own potential. That really shifts the
15:21
focus. Yeah. And when you look at that timeline,
15:24
two decades, it tells a very specific story.
15:28
Twenty years means she was cultivating adaptability,
15:30
resilience, and confidence in emerging leaders
15:32
long before constant disruption became the default
15:35
setting of the corporate world today. If we connect
15:38
this to the bigger picture, it reveals a really
15:41
profound insight about what true organizational
15:43
transformation actually is. Let's hear it. Well,
15:46
a lot of executive boards treat transformation
15:48
as a software upgrade, like a finite project
15:51
with a clear start and end date. Right, you install
15:54
the update and you're done. Exactly. But this
15:57
text suggests that passing down capability and
16:00
confidence is actually the most effective way
16:02
to equip an organization for the future. Because
16:05
you can't plan for everything. No. You cannot
16:08
write a standard operating procedure for every
16:11
possible disruption your company might face over
16:12
the next decade. The variables in global business
16:15
are simply too complex, and they move way too
16:18
quickly. Right. You can't write a manual for
16:21
a market crash or a technological shift that
16:24
hasn't even been invented yet. Exactly. So instead
16:27
of trying to predict the exact nature of the
16:28
next disruption, you focus on the adaptive capacity
16:32
of your people. That makes total sense. You build
16:35
a generation of leaders who possess such a high
16:37
degree of capability and such a strong belief
16:40
in their own potential that they can absorb and
16:42
process whatever anomaly the market throws at
16:45
them. True organizational transformation isn't
16:49
an org chart change. It is a generational transfer
16:53
of adaptive belief. So by mentoring those emerging
16:57
leaders and focusing on their confidence rather
16:59
than just their tactical skills She is essentially
17:02
building the long -term immune system of the
17:04
organization. I take that a step further honestly
17:07
She is ensuring that the organization doesn't
17:10
just survive the next disruption But actually
17:13
has the internal leadership capacity to leverage
17:15
it to use the disruption to their advantage Yes,
17:19
when the next major shift happens leaders who
17:21
have been mentored in this methodology won't
17:24
freeze They will lean into the volatility because
17:27
they trust their own capability to navigate it.
17:30
That is the ultimate realization of the Sessions
17:32
mandate. To inspire people through change rather
17:35
than merely managing them through it. Absolutely.
17:39
Well, let's pull all of these threads together
17:41
and recap the blueprint we've decoded today.
17:43
The Masterclass Notes laid out a clear set of
17:46
directives for the modern era of business. Enable
17:48
your teams to navigate volatility. Equip your
17:51
leaders to manage transition with profound purpose.
17:53
and shift the culture from enduring change to
17:56
embracing it. And we saw how that actually works
17:58
in practice. Right. By analyzing the case study
18:01
of Avery Banta, we've seen the real world mechanisms
18:05
required to pull that off. It requires wielding
18:07
calibrated empathy to regulate a team's cognitive
18:10
load. Very important. It demands bridging the
18:13
gap between deep human understanding and ruthless
18:16
executional excellence to prevent organizational
18:18
debt. Synthesis. Yes, synthesizing the macro
18:22
stability of a traditional project management
18:24
framework with the micro flexibility of an agile
18:27
mindset. And most importantly, it requires dedicating
18:30
yourself to the long game. The mentoring. Exactly.
18:34
Mentoring the next generation so that the capability
18:37
to adapt outlives any single organizational restructure.
18:40
It's a really complete playbook. So what does
18:43
this all mean? How do we distill this enterprise
18:46
level strategy down into something actionable
18:48
for our own daily workflows? Well, the most immediate
18:51
application goes right back to the central paradox
18:53
we started with, creating stability amid transition.
18:58
Let's direct that inward. Okay, inward. If you
19:02
are listening to this right now, and you find
19:04
yourself in the middle of a highly volatile environment,
19:07
maybe your department is reorganizing, your budget
19:09
was just slashed, or your entire industry is
19:12
being rewritten by a new algorithm, what is the
19:15
very first thing you need to stabilize internally?
19:18
That's a great question. Right, because before
19:21
you can attempt to lead a team through the chaos
19:23
or successfully execute a new mandate, you have
19:26
to regulate your own cognitive load. You have
19:29
to put your own oxygen mask on first. Exactly.
19:33
What boundary, what daily habit, or what specific
19:36
mental framework do you need to lock into place
19:38
today to give yourself the baseline confidence
19:41
required to step into tomorrow's disruption?
19:44
That is a phenomenal question to sit with. Because
19:47
if you are going to navigate an environment where
19:49
the ground is constantly shifting, you just cannot
19:52
rely on external structures to keep you balanced.
19:54
No, you really can't. You have to find your own
19:57
center of gravity first before you can help anyone
19:59
else find theirs. Well, thank you so much for
20:02
coming along on this deep dive with us today.
20:04
Take that question with you. Apply it to whatever
20:06
volatility you are facing this week, and we will
20:09
catch you on the next one.