The First 90 Days: How Trust Gets Built

What the Onboarding Checklist Doesn’t Cover

“Is this really my desk?” On their first morning, a new colleague usually appears at the front desk with some version of this question. A campus before the students arrive is the quietest it will be all day, so that awkward first hello sounds louder than it should. My part is simple. I set up the desk and the accounts, walk them through how a day on campus flows, and hand them their first week’s schedule. On paper, onboarding mostly starts here and rolls forward into 30-, 60-, and 90-day goals. But after watching many colleagues’ first 90 days from the closest seat in the building, I’ve learned something. New people are watching far more than the goal document.

A new colleague in their first week is a much sharper observer than you’d expect. They quietly take note of who interrupts whom in meetings, how the air shifts when a mistake comes up, and whether “I’ll get back to you on that” actually gets followed through. A 30-60-90 plan tells them the order of the work, but it can’t tell them whether it’s safe to work on this team. That answer gets built slowly, out of small everyday scenes.

How the Team Responds to the First Mistake

The day a new person makes their first mistake, the team’s everyday self is on full display. Once, a teacher about three weeks in misread a class assignment in Rubric, and a notification text went out to the parents of the wrong class. They came to the desk white as a sheet. What the team did was simple. First, we sent the correction together, and that afternoon we sat down to look at why the screen had been so easy to misread. Nobody asked whose fault it was. That teacher told me something later: that afternoon was when they started trusting this team.

We weren’t always like this. A few years back, when a teacher two months in entered the wrong quantity on a textbook order, the first thing out of my mouth was “You really should have double-checked” (it was an afternoon I was racing a settlement deadline, not that that’s an excuse). After that, their visits to the desk dropped off noticeably, and they left before reaching 90 days. Only in the exit conversation, when they said, “I thought this was a place where you handle things on your own,” did I understand what signal my one remark had sent. A new colleague whose first mistake is met with blame learns to hide mistakes before anything else, and on a team that hides mistakes, problems only surface after they’ve grown. Which is why I’ve come to think of the first mistake as the earliest chance we get to show how this team handles problems.

The Sense That It’s Safe to Ask

The tone of the questions a new colleague brings to the desk changes over time. What starts as “Sorry, I know you’re busy, but…” becomes, at some point, “Is this actually how we’re supposed to do this?” I take that shift as the single most reliable sign that onboarding is going well. Being able to ask without apologizing means they’ve come to believe that not knowing won’t be counted against them.

This sense doesn’t grow on its own. A team that answers a repeated question with “I told you this last time” and a team that answers “That one trips everyone up. It got me too at first” will have completely different 90 days. The faster the floor moves (think ELA or Playfit), the more this holds. Only when the urgent question tossed out five minutes before class is welcomed, again and again, does a colleague become someone who asks instead of guessing alone at the moments that truly matter.

The Experience of Small Promises Kept

“I’ll let you know after lunch.” Sitting at the desk, I say this several times a day. Trust also accumulates through the experience of that unremarkable sentence actually coming back after lunch. A teacher who joined last winter mentioned in their first check-in that finding the makeup class schedule meant scrolling way back up the group chat, and the following week, a weekly makeup schedule started appearing on the whiteboard next to the desk. Watching your own words turn into something visible is more powerful than it sounds. New colleagues judge a team not by its big promises but by the count of small ones kept. Small promises are as easy to break as they are to keep, which is exactly why they expose a team’s everyday habits for what they are.

So when I welcome a new colleague, I hold myself to one rule. Never make a promise I can’t keep, and once made, follow through on even the trivial ones, or be the first to say why it’s running late. I’ll confess I’ve broken this rule myself. Last spring, I told a new teacher I’d have their supply-ordering account open “by tomorrow,” then let three days slip by. Head office approval was the holdup, but for those three days I never brought it up first. Only when they carefully asked again did I apologize, and since then I’ve made a habit of sending word that something will be late before it is. The same goes for the person who’s new. What a new hire needs in the first 90 days is not flawless results but the sight of small tasks being finished predictably. The existing team relaxes as it watches, and starts handing over bigger things, bit by bit.

Trust Isn’t Planned. It Accumulates

30-60-90 goals are still useful. They sort out priorities and make expectations clear on both sides. The document just doesn’t build trust on its own. Trust accumulates slowly: in how the team responds to the first mistake, in the moment questions no longer need an apology attached, in the repetition of small promises kept.

If you’re the one joining, I’d suggest easing up on the effort to look perfect and choosing instead to ask early and flag early. If you’re the team doing the welcoming, it’s worth deciding in advance how you’ll receive a new colleague’s first mistake and first question. Those few scenes determine years of working together. As someone who has watched countless first 90 days on campus, I believe trust isn’t something you declare you’ll build; it’s something you prove, one everyday response at a time.