I’ve worked with a lot of interns over the years. Two of them illustrate something I’ve been thinking about better than any abstract argument could.
The first came in the way most good interns do — uncertain, eager, and honest about both. When they didn’t know something they said so. When they got something wrong they flagged it. When a task was outside their experience they asked for help rather than quietly guessing. Their internship was, by design, a learning environment, and they treated it like one. They grew visibly, rapidly, in ways that were satisfying to watch.
The second was different. They arrived with some experience, absorbed a few new things early on, and then — somewhere in the middle of the internship — decided they had learned enough. When gaps appeared they papered over them. When they didn’t know something they performed knowing it. After getting something right once, they resisted doing it again, as if repetition was beneath them. They didn’t last.
The difference wasn’t talent. It was what each of them did with the gap between what they knew and what was being asked of them. One said the true thing. The other didn’t. And the whole arc of both internships followed from that single difference.
I Don’t Know Is A Complete Sentence
There is a particular kind of performance that happens when someone doesn’t know something and doesn’t want to admit it. It has a texture you can feel in a room. The slightly too-confident answer. The deflection toward a related thing they do know. The vague affirmative that neither confirms nor denies. The follow-up question that seems clarifying but is actually buying time.
All of it is understandable. People worry that admitting ignorance makes them look bad. They worry it will cost them credibility, opportunity, the perception of being the right person for the job. And in some environments those worries are justified — which is the uncomfortable part of this conversation and we’ll get to it.
But in most environments, most of the time, the calculus is exactly backwards. Not knowing something and saying so is almost always more useful than pretending to know and getting it wrong downstream. The gap that gets named early can be filled. The gap that gets hidden becomes a problem that surfaces at the worst possible moment, usually when there’s no time to address it cleanly.
I don’t know is a complete sentence. It doesn’t need to be followed by an apology, a justification, or a performance of how hard you’ve been trying. It just needs to be followed by whatever comes next — a question, a request for help, a plan for finding out. The sentence itself is not a confession of failure. It’s an invitation to solve a problem together instead of alone.
I Don’t Need The Why
The other thing I keep running into — and it’s related, though it takes a different shape — is the over-explanation of ordinary human things.
Someone is going to be late. Someone needs to leave early. Someone has a conflict, an appointment, a day where life got in the way of the schedule. These are not extraordinary events. They are the texture of working with human beings who have lives outside the job.
And yet the message that arrives is often a small performance. An accounting of circumstances, a pre-emptive defense, a careful construction of justification designed to demonstrate that the lateness or the absence is not a moral failing. As if the information itself — I’ll be late, I need to step out, I can’t make it today — isn’t enough on its own. As if it needs to earn its own acceptance.
It doesn’t. Or at least it shouldn’t.
What I actually want, as someone on the other end of that message, is the information. Not the story around it. You’re going to be late — great, thank you for telling me, I’ll adjust accordingly. You need a day — noted, hope everything is okay, see you when I see you. The why is almost never relevant to what I need to do with the information. And the performance around it — the careful justification, the preemptive apology — tells me something about the environment that I’d rather be fixing than receiving.
(This could easily tumble into other topics I’d love to dive into: “A manager’s job is less ‘saving the company’ and more ‘making the company a place people want to work.’” or “Silos and solos create traps and hole-ohs.” Both are posts I plan to write separately.)
The Environment Has To Earn It
Here’s the uncomfortable part.
People don’t perform around their ignorance or over-justify their human needs because they’re weak or dishonest. They do it because somewhere, at some point, the environment taught them to. A manager who responded to “I don’t know” with visible frustration. A culture where admitting a gap was treated as evidence of inadequacy rather than an opportunity to fill it. A workplace where being late once became a data point that followed someone around.
You can’t expect honesty from people in an environment that punishes it. The behavior is rational. The problem is the environment.
Which means that building a team where people say the true thing requires something from leadership and culture before it can require anything from individuals. The honesty has to be received well before people will offer it freely. Trust has to be established before it can be assumed.
What Trust Actually Looks Like
When a studio culture gets this right — when people feel genuinely safe saying I don’t know and I’ll be late without bracing for impact — something changes in how the team operates.
Gaps get filled before they become problems. The person who doesn’t know something says so early enough that someone can help them. The person who needs a day flags it with enough notice that the work can be covered. Nobody is managing impressions instead of doing work. Nobody is carrying a hidden gap that’s quietly growing into something that will surface at the worst possible moment.
People help each other openly. Growth happens in the light instead of the shadows. The intern who doesn’t know something asks the question out loud and gets an answer that benefits everyone in earshot. The experienced developer who hasn’t used a particular tool in years admits it rather than struggling in silence, and the team adjusts.
This is what trust produces. Not a team where everyone is equally capable or equally available. A team where the gaps are visible, which makes them fillable, which makes the whole thing work better than any team where everyone is performing competence they may or may not actually have.
Say The True Thing
You can’t always control the environment you’re in. Some places will punish honesty and there isn’t much you can do about that except decide whether to stay.
But where you do have control — in how you respond when someone says I don’t know, in whether you make it safe to flag a conflict without a performance of justification, in the signals you send about what kind of honesty is welcome here — the behavior you model tends to make room for others to do the same.
Say the true thing. Receive the true thing well when someone offers it to you. I’ve discovered that’s most of what trust is made of.