10 Lessons for Leaders in an Age of Change

10 Lessons for Leaders in an Age of Change

The title of the original article overstates its case — most decades feel like an "age of revolution" to the people living through them — but the underlying question is real. The leaders shaped by the 1990s management playbook (stable industries, slow technology cycles, predictable five-year plans) are now running organisations where the assumptions underneath that playbook have stopped holding. AI is reshaping job categories on six-month cycles. Hybrid work has permanently altered what "team" means. The supply-chain certainties of 2018 are gone. Whatever you call the current period, the leadership operating system needs an upgrade.

The ten lessons below are drawn from the leaders we've watched navigate this stretch most effectively — across tech, manufacturing, non-profit and government. None of them are revolutionary in the literal sense; most are 20-year-old principles that have been undervalued and are now load-bearing. The change isn't that new leadership ideas have arrived. It's that the old ones that always mattered now matter more visibly and more urgently.

The lessons assume a working leader at the team or organisation level. They're not aimed at the global thought-leader audience; they're aimed at the person responsible for thirty to three hundred people through the next eighteen months.

1. Decide on a slower cadence than the news cycle, faster than the budget cycle

The mistake leaders make in turbulent periods is matching the speed of their decision-making to the speed of the noise. Every AI release, every regulatory shift, every layoff round at a competitor triggers a meeting, a memo, a re-strategy. The cost is whiplash for the team and the slow erosion of any coherent direction. The opposite mistake — keeping the annual budget cycle as the unit of strategic time — means you respond to a six-month shift twelve months late.

The functional cadence is quarterly: deep enough to actually re-evaluate, shallow enough that you're not re-strategising at a frequency that paralyses the team. Decide on the quarter; commit publicly to not re-litigating until the next one; let the team execute against a stable target for ninety days at a time.

2. Tell the truth about what you don't know

The leader who confidently extrapolates beyond their actual visibility loses credibility fast in a period when most extrapolations turn out wrong. The leader who says "I don't know how AI will reshape this category in 18 months; here's what we're tracking and here's how we'll re-decide in Q3" gains it. The cultural shift required is small but real: it's the willingness to be authoritative about your reasoning process while being humble about your conclusions.

This is hard because every previous decade rewarded confident-sounding forecasts. The current period penalises them, because the team can see through the forecast and judges the leader who pretends otherwise. Calibrated honesty about uncertainty isn't weakness — it's the version of confidence that teams in volatile conditions can actually build on.

3. Default to publishing your reasoning, not just your decisions

Teams in stable periods can follow decisions without understanding the reasoning. Teams in volatile periods cannot — they need to internalise the why, because the next decision will need to be made by someone closer to the problem, and they have to know how you think to make it the way you'd make it. The leaders who scale through this period are the ones who narrate the decision logic publicly, in writing, with the trade-offs explicit.

The practical version is a one-page memo per significant decision. Most leaders won't do this because it feels like over-explaining. The leaders who do it produce teams that can run autonomously in ways the non-narrators cannot. The memo is also a forcing function for the leader: if you can't write the reasoning clearly, you haven't finished the decision.

4. Treat AI as an operating change, not a product change

The most common leadership failure in 2025 and 2026 has been thinking about AI as a feature to ship rather than a change to how the organisation operates internally. The companies that have moved fastest aren't necessarily the ones with the best AI products; they're the ones whose internal workflows — engineering, support, research, recruiting, finance operations — have been rebuilt to assume AI in the loop. The leadership work is internal restructuring, not external positioning.

This requires comfort with the fact that some roles change shape, some compress, and some disappear. Avoiding the internal restructuring conversation doesn't make it less necessary; it just delays it past the point where competitors have already done it. The harder version of this lesson: leaders who have worked to understand AI's actual capabilities from the inside make better restructuring decisions than leaders who abstract over it entirely.

5. Trust the team enough to give up the illusion of control

The instinct in uncertain periods is to centralise — more approvals, more leader oversight, more meetings to "stay aligned." The instinct is wrong. Centralisation slows decisions exactly when speed matters most, and signals distrust to the team exactly when their judgment is the most valuable asset you have. The leaders who navigate this period well distribute authority deeper, not shallower.

The model that scales is L. David Marquet's "intent-based leadership" from Turn the Ship Around: team members declare intent ("I intend to ship X by Friday"), leaders approve or refine, and the locus of decision moves down. The leader's job becomes setting context, not approving outputs. This requires genuine trust, which requires genuine investment in developing the team's capability — which is why leadership development isn't optional overhead in volatile conditions.

6. Hire for adaptive capacity over current capability

The hiring criteria that worked in 2015 — deep expertise in a stable specialism — are partially obsolete. Specialisms are reshaping; the half-life of a current technical skill is shorter than it used to be. The hiring signal that's more durable is the candidate's track record of learning new things fast and reorganising their working model when conditions change. Two engineers who have re-skilled into a new domain and shipped credibly are worth more, in most contexts, than ten who have been doing the same thing well for a decade.

This shifts the interview structure: less about "what have you built" and more about "what have you had to unlearn, and how did you do it." Answers to that question reveal learning agility in ways that credential lists don't. The adaptive candidate will often be harder to evaluate on paper than the deep specialist — that difficulty is signal, not noise.

7. Make recovery a designed part of the operating rhythm

In stable periods, "burnout management" is an HR poster. In volatile periods, it's an operating priority — sustained high-pressure delivery without designed recovery breaks teams in 12 to 18 months. The leader's job is not exhortation about self-care; it's building the operating rhythm that actually allows recovery to happen. Real meeting-free blocks. Real vacation that doesn't shift the workload to colleagues. Real shutdown rituals at the end of intense pushes.

The leaders who model this set the team's actual norm. Telling people to rest while messaging at 11pm sets the opposite norm, regardless of what the wellness documents say. The operating cadence the team observes in the leader is the operating cadence the team adopts. That cuts both ways: protecting your own recovery time is, in this sense, a leadership act rather than a personal preference.

8. Be explicit about what you're not doing

Strategy in a stable period is mostly about what to pursue. Strategy in a volatile period is mostly about what to stop pursuing, because the opportunity surface is expanding faster than the team can chase. The discipline of saying "we're not doing X" — and naming it, repeatedly, until the team stops drifting back to it — is the leader's most underused tool.

The companies that have done well through this period have visible "not-doing" lists, often longer than their priority lists. The companies that are struggling have aspirational priority lists with no corresponding rejection list, and the team is shipping nothing well because it's shipping everything poorly. Writing down what you've decided not to pursue, and revisiting that list at the same cadence as your priority list, is a small practice with large effects on focus.

9. Treat communication as a leadership product, not an overhead task

In a period when the team is anxious about the future, the leader who under-communicates is interpreted as withholding. The communication frequency that felt sufficient in 2018 — quarterly all-hands, occasional memo — is now under-served by half or more. The leaders who do this well treat written, weekly, honest updates as a deliverable they'd never miss. Tone matters: authentic uncertainty beats forced optimism beats radio silence, in that order.

The format matters less than the consistency. A Slack note every Friday afternoon, a short recorded video via Loom (now part of Atlassian's product ecosystem but still widely used), a memo, a town hall — pick the format you'll actually maintain and maintain it. Teams in volatile conditions don't need leadership to be inspiring so much as they need it to be consistent. Predictability in communication is itself a form of stability.

10. Pay attention to the second-order effects of every decision

The first-order effect of a decision — what it's intended to do — is what gets debated in the room. The second-order effects — what it signals to the team about the leader's values, what behaviour it implicitly endorses, what precedent it sets for the next analogous decision — are what actually compound over time. The leader who promotes the wrong person sends a signal about what the company actually rewards that takes years to reverse, regardless of the official rationale offered at the time.

The discipline is to ask, before every meaningful decision: "what is this decision teaching the team about how we operate?" Often the answer changes the decision. This is not slow or indulgent — it's the minimum viable strategic thinking that separates leaders who compound organisational trust from those who erode it steadily while believing they're managing normally.

The honest framing

Calling the current period an "age of revolution" is the kind of language that makes leadership writing feel important. The more useful framing is that this period rewards the operating disciplines that always mattered — clarity, trust, decentralisation, honest communication, designed recovery — and penalises the ones that used to be tolerable, like centralised control, vague strategy, and performed confidence. The leaders who treat the moment as a forcing function for the basics are the ones who come out of it intact.

The change generation isn't characterised by entirely new principles. It's characterised by an environment that no longer forgives the absence of the old ones. Leaders who internalised these basics ten years ago are at an advantage now not because they predicted this period, but because they had the operating muscle ready when the period arrived.

For the deeper reading on the foundational principles above, the 12 tips to develop great leadership skills covers the actionable side. The 38 motivational quotes on leadership distils some of these ideas into the shorter form that travels well in team channels. For the harder edge of what these lessons actually cost in operating reality, the scary truths of being an entrepreneur is the companion piece.

Frequently asked questions

How often should leaders update their strategy in an uncertain environment?

Quarterly is the most functional cadence for most organisations — deep enough to genuinely re-evaluate based on new information, shallow enough not to paralyse teams with constant redirection. More frequent re-strategy (matching the news cycle) creates whiplash and erodes any coherent direction. Annual cycles leave you responding 12 months late to 6-month shifts. Commit publicly to not relitigating the strategy until the next quarterly review, and hold that commitment.

How should leaders communicate during sustained periods of uncertainty?

With higher frequency and more honesty about what you don't know. Authentic uncertainty — naming what you're tracking, how you'll decide, by when — builds more trust than performed optimism that teams can usually see through. Weekly written updates at a fixed cadence provide the consistency that functions as stability when external conditions are not. Radio silence is the worst option: a leader who under-communicates in anxious conditions is interpreted as withholding.

What does 'intent-based leadership' mean in practice?

Team members declare their intended action ('I intend to ship X by Friday'), leaders approve or refine, and decision authority sits with the person closest to the work rather than at the top. L. David Marquet developed this approach in the US Navy; it's described in Turn the Ship Around. In volatile conditions, centralised approval slows decisions to the speed of the bottleneck. Intent-based leadership allows the team to move fast while preserving strategic alignment — the leader sets context, not every output.

Should leaders get personally involved in AI adoption in their organisations?

Yes, and the involvement should focus on internal operations first. The organisations that have adapted most effectively in 2025–2026 are those that rebuilt internal workflows — engineering, support, recruiting, finance — to assume AI in the loop, not just those with AI products. The leadership work is internal restructuring: deciding which roles change shape and building team capacity to work effectively with AI tools. Positioning AI as an external story while leaving internal workflows unchanged is the most common avoidance pattern.

Why is designing recovery time into the operating rhythm a leadership responsibility?

Because the operating cadence the team observes in the leader is the actual norm, not the stated policy. A leader who exhorts rest while messaging at 11pm sets the opposite norm from what they're advocating. Sustained high-pressure delivery without designed recovery breaks teams in 12–18 months — it's an operating risk, not a wellness preference. Building in real meeting-free blocks, real shutdown rituals after intense pushes, and real vacation that doesn't shift load to colleagues is the leader's structural responsibility.

Comments (0)

Leave a Comment