Leading Through Tough Times
I've had the unusual experience of leading through three significant economic downturns across three different professional contexts. The lessons that have held across all three are fewer than you'd expect — and more specific than most leadership guidance on this topic tends to be.
Culture is a structural decision, not a morale initiative
In difficult periods, the instinct is to reach for visible gestures — team events, motivational messaging, signs of normalcy. These have limited shelf life. What actually stabilizes a team is the intentional design of how they work together day to day.
If your team operates at the edge of organizational change, build a culture of active learning — make sense-making a shared practice rather than an individual burden. If silos are forming, address them through structural intervention: consistent meeting discipline, written pre-reads and agendas, multiple formats for contribution so that participation isn't limited to whoever speaks loudest in a room.
Culture built with intention during hard times outlasts the crisis. Culture built around events doesn't.
Communication is the work
In tough times, information tends to contract. Less gets written down. More gets decided in small rooms. The resulting speculation costs more in productivity and morale than the information itself would have.
The counter-move is deliberate forward communication — sharing context before people ask for it, documenting decisions, reducing the conditions under which rumors fill the gap. This consistently feels like swimming against the current. It is also consistently worth it.
Pair this with clear expectations and honest feedback. Recognition during hard periods doesn't require lowering the bar — it requires acknowledging that staying focused and functional under pressure is itself a form of high performance, not a baseline to be taken for granted.
Accountability requires showing your work
If you are asking your team to go the extra mile, they need to see that you are doing the same — in ways specific to your actual contribution, not generic effort signals.
When something doesn't land as planned, say so. Name what happened, what you learned, what changes as a result. This is not vulnerability as performance. It's the organizational practice of making work legible — so that individuals, teams, and initiatives can be understood accurately, common problems can be identified and solved, and the gap between what leadership sees and what the team experiences stays narrow.
The more work is visible, the less confusion costs you. In a resource-constrained environment, that's not a soft benefit. It's a structural one.