Leading Under Pressure: Engineering Trust and Resilience
- Ken Nelson

- Oct 23, 2025
- 3 min read
Leadership under pressure isn’t about doing more, it’s about creating systems and trust strong enough to handle the strain.
In my years managing creative and technical teams, from VFX production floors to startup operations, I’ve learned that the real test of leadership isn’t how you handle chaos, it’s how well your team performs when you’re not in the room.
Strong leadership under pressure isn’t heroics; it’s preparation. The work you do before the crisis determines how your team performs during it.
That lesson came into sharp focus at Legend3D during one particularly demanding project.
In 2016, when another studio fell behind on Fantastic Beasts and Where to Find Them, our Toronto team was handed a last-minute emergency contract, some of the most complex shots in the film. To make things more complicated, I’d already booked time off to host friends visiting from out of the country.

When time and resources are tight, leaders often make one of two mistakes:
· Over-functioning: trying to do everything themselves, or
· Abdicating: stepping back and hoping their teams will figure it out.
If I’d over-functioned, I would’ve canceled my plans and stayed through the entire crunch period, signaling to my team that I didn’t trust them to manage without me. It might have resulted in a strong delivery, but it wouldn’t have built capability or confidence, and it likely would have led to burnout.
If I’d abdicated, I could’ve handed off the responsibility, wished them luck, and disappeared for four days. Without clear alignment, the message would’ve been obvious: if I wasn’t working, they didn’t need to either. Overtime would’ve stopped, progress would’ve stalled, and delivery would have failed.
Neither approach works because pressure doesn’t reward effort; it rewards clarity and trust built through structure. Effort alone under pressure usually leads to exhaustion, not excellence.
Despite the timing, producers insisted on assigning those shots to my team; I’d built a reputation for managing the work others couldn’t. The timeline was brutal: twelve to sixteen-hour days, seven days a week, for more than two weeks straight, and every one of my team members volunteered for the push.
Knowing I’d be away for four days in the middle of that crunch, I sat down with my team to plan, delegate, and distribute workload across more than a dozen artists, with several additional artists from other teams joining during overtime hours. Everyone knew their responsibilities, understood the dependencies, and trusted one another to deliver.
That’s when I learned one of the most valuable lessons in leadership: trust isn’t given; it’s engineered.
When my break arrived, I stepped away to enjoy some R&R, not because the pressure had eased, but because the system I’d built, and the people within it, were strong enough to function without me. While I was playing strategy board games with friends, my team was executing one of the hardest pushes of our careers, and they nailed it.

The takeaway? If your presence is the only thing keeping things on track, you haven’t built a team; you’ve built a dependency.
Effective leaders create systems that make themselves progressively less essential, not more.
Three Truths About Leadership Under Pressure
· Design for clarity before chaos: build systems that can operate without you.
· Trust is built in advance: don’t wait for pressure to test it.
· Delegate for growth, not relief: empowerment isn’t about offloading work; it’s about developing capability.
True leadership is rarely about holding things together. It’s about creating alignment, systems, and trust strong enough that your absence doesn’t derail progress; it proves it.



Comments