The Shadow Under the Car
Within my first few weeks at Fin Design & Effects, my lead, Stuart White, asked me to render the shadow underneath a Toyota Kluger.
On paper it sounded simple enough. In reality, it meant rendering the shadow separately, so it could later be projected back into the environment — avoiding expensive raytraced shadows throughout the whole scene. Today you'd probably never bother with a trick like this. Back then, computers were slower, render time was precious, and most of those words may as well have been another language.
I sat there for the next thirty minutes trying to figure it out. Moved nodes around. Changed settings. Rendered things that didn't work. Read what little documentation I could find. Every few minutes I'd convince myself I understood it, only to realise I didn't.
Eventually I admitted something to myself: I didn't actually understand what Stuart was asking me to do.
I looked across the room and said something like, "Hey Stu... I've been looking at this for about half an hour and I still don't understand what you want me to do. I think I'm stuck."
He didn't sigh. He didn't make me feel stupid. He just walked me through what we were actually trying to achieve. Within five minutes I understood the objective. About an hour later, I'd finished the task.
That moment stayed with me for the rest of my career.
Ask First, But Try First
Asking questions isn't a sign of weakness. Pretending you understand is.
There's an important distinction, though. I don't think the answer is to ask someone else to solve every problem the moment you hit it — you owe it to yourself to try first. Spend some time thinking. Experiment. Make progress. Reach the actual edge of your own understanding.
Then ask.
When you've genuinely tried, your questions become far more valuable. You're no longer asking someone to do your work for you — you're asking them to help you bridge the gap between what you know and what you don't. That's a very different conversation, and it's one people are usually glad to have.
The Other Side of the Desk
Years later, when I found myself leading teams, I saw the other side of this.
The people who asked questions rarely worried me. The people who didn't were the ones I kept an eye on. You could almost always tell — someone would nod through a conversation, say they understood everything, then quietly disappear for the rest of the day. More often than not they'd spent hours heading in completely the wrong direction, because they were too embarrassed to admit they were lost.
I found myself repeating the same line over and over: if you don't understand something, just come and ask. Not because I expected people to know everything — because I couldn't help with a problem I didn't know existed.
One thing I learnt as a lead: helping someone doesn't always mean giving them the answer. Often that's the least useful thing you can do. I'd rarely just solve the problem for them outright — instead I'd hint them along, give them just enough to find a new path themselves. It wasn't a deliberate strategy so much as something I fell into and kept doing, without much thought, project after project, person after person.
Quite often, just from being pointed in a slightly different direction, they'd land on the answer themselves. They didn't need me to solve it — they needed someone to nudge their thinking and point them roughly the right way. Those were some of my favourite moments, not because I'd solved the problem, but because they had.
Where This Doesn't Hold
I don't want to make this sound tidier than it is. Not every silence is fear, and not everyone who goes quiet is stuck — some people genuinely think better alone, and interrupting that with "just ask me anything" can do more harm than good. Part of leading a team is learning to tell the difference between someone working through something in their own time and someone drowning quietly rather than admit it. It's not always obvious in the moment, and I don't think I ever fully solved it — it's more a thing you keep recalibrating, person by person.
There's also a version of "no question is too stupid" that gets used as a slogan without anyone actually meaning it — said in a meeting, then contradicted the first time someone asks something genuinely basic and gets a look instead of an answer. Saying it is easy. Building a team where people actually believe you meant it takes a lot longer, and you only find out you've built it the day someone tests it.
No Two People Start the Same
What I had to keep relearning as a lead wasn't about them — it was about me. I'd catch myself assuming a level of context that simply wasn't there. Someone six months into a project has a completely different starting point to someone who joined yesterday, and it was on me to notice which one I was talking to, not on them to catch up. The assumption I had to keep checking wasn't "will they ask" — it was "have I actually given them enough to ask from."
I don't know what someone knows. I don't know what they haven't been told. I don't know what assumptions they're working from unless I ask. That's not a compliment I'm paying them — it's a discipline I had to build in myself.
Looking back, I wasn't looking for Stuart to solve my problem that day — I just needed someone to help me see what I couldn't yet see. Years later, I realised the best mentoring works exactly the same way. The goal was never to create people who depended on me. It was to help create people who, one day, wouldn't need to ask me at all.
← Back to Articles