You just took the job. The offer letter is signed, the org chart is open on your screen, and somewhere in the back of your mind a clock has already started ticking. Ninety days. That is the window in which the people around you, your CEO, your peers, your new engineers, quietly decide what kind of leader you are going to be.

Here is the trap almost every new VP of Engineering walks into: you look at the roadmap, you look at the team, and you conclude that the first real move is to hire. More senior engineers, a missing staff-level architect, that platform team you were promised in the interview. So you wait. You post the reqs, you run the loops, and you tell yourself the wins will come once the seats are filled.

They will not come, at least not on the timeline you need. Hiring is slow, it is noisy, and it is largely outside your control. And the research on leadership transitions is blunt about what happens when you spend your opening window waiting. In his study of executive transitions, Michael Watkins found that the leaders who stumble are usually the ones who fail to secure early wins, the visible, credibility-building results that convince others the new leader is worth following (Watkins, The First 90 Days, 2013). Early wins are not a nice-to-have. They are the mechanism by which you earn the right to make the bigger, slower bets later.

So the question is not whether you can ship early wins without new hires. The question is how. And the answer has less to do with heroics than you might expect. It has to do with grit, with progress, and with paying very close attention to the team you already have.

Start by believing the talent is already in the room

There is a seductive story that says your team is under-resourced and that is why things are slow. Sometimes that story is even partly true. But adopting it wholesale, on day one, before you have looked closely, is a failure of what psychologists call a growth mindset: the belief that capability can be developed rather than being fixed and finite (Dweck, Mindset, 2006).

When you treat your current engineers as a fixed quantity of horsepower that simply is not enough, you stop looking for the potential that is already there. When you treat them as people who can grow, stretch, and surprise you, you start finding capacity you did not know you had. The distinction matters enormously in your first quarter, because you cannot hire your way to a growth mindset, and you cannot fake one either. Your team will know within weeks whether you see them as the problem or as the solution.

Practically, this means your first two or three weeks are for listening, not restructuring. Talk to every engineer you can. Ask what is slow, what is broken, what they have wanted to fix for a year but were never given room to. You will hear the same three or four things over and over. Those recurring answers are your early-win backlog, handed to you for free by the people who understand the system better than you do.

Chase progress, not grand gestures

Once you know where the friction lives, resist the urge to announce a transformation. New leaders love a bold vision because it feels like leadership. But the most reliable engine of team motivation is something far humbler.

Teresa Amabile and Steven Kramer analyzed nearly twelve thousand daily diary entries from professionals and found that the single most powerful driver of positive emotion, motivation, and engagement at work was simply making progress in meaningful work. They called it the progress principle, and they found that even small wins had an outsized effect on how people felt and performed (Amabile & Kramer, The Progress Principle, 2011). The corollary is just as important: small setbacks dragged people down more than small wins lifted them up, so protecting momentum matters as much as creating it.

Karl Weick made the same argument a generation earlier. He observed that framing problems as enormous and monolithic tends to paralyze people, while redefining them as a series of small, concrete, winnable steps unlocks action. Weick called this the strategy of small wins, and he showed that a series of modest victories attracts allies, builds confidence, and creates momentum that larger efforts can ride on (Weick, "Small Wins," American Psychologist, 1984).

For you, in your first ninety days, that translates into a simple discipline. Pick problems that are real, visible, and finishable inside a few weeks with the team you already have. A flaky test suite that eats a day of engineering time every week. A deploy process that takes three hours and three people. An on-call rotation that is quietly burning out your best senior engineer. None of these require a new hire. All of them, once fixed, produce a result everyone can see and feel.

Let the metrics do your talking

Early wins are only wins if other people recognize them as such. This is where many engineering leaders undersell themselves. They fix something genuinely important and then describe it in language that only engineers understand.

You have a better option, and it is well established. The research behind the DORA program, synthesized by Nicole Forsgren, Jez Humble, and Gene Kim, identified a small set of metrics that reliably distinguish high-performing engineering organizations: deployment frequency, lead time for changes, change failure rate, and time to restore service (Forsgren, Humble & Kim, Accelerate, 2018). These four measures are powerful for you as a new leader precisely because they are legible to people outside engineering. When you cut deploy time from three hours to twenty minutes, you can say so in a number your CEO understands, and you can show the trend line.

Measure the baseline in your first week, before you change anything. Then, when your team clears the friction you identified, you will have a before and an after. That contrast, not your job title, is what builds your credibility.

Grit is a team sport, and it needs safety

Angela Duckworth's research defines grit as passion and perseverance toward long-term goals, and it consistently predicts who finishes hard things (Duckworth, Grit, 2016). But grit is not just an individual trait you bring to the role. Part of your job in the first ninety days is to build the conditions in which your team's grit can actually show up.

Those conditions have a name. Amy Edmondson's work on psychological safety, later echoed in Google's own Project Aristotle study of its teams, found that the highest-performing teams were not the ones with the most talented individuals but the ones where people felt safe to take risks, admit mistakes, and speak up (Edmondson, The Fearless Organization, 2019). A team that has just watched a new VP arrive is, by default, a little afraid. If your first moves are blame and reorganization, you suppress exactly the honesty you need. If your first moves are listening, protecting people, and shipping small fixes together, you give perseverance somewhere safe to take root.

And perseverance is the point. The improvements that matter most, the ones you will build once your credibility is established, are long games. Deliberate practice, the effortful, focused refinement that Anders Ericsson identified as the path to expert performance, is by definition not comfortable and not fast (Ericsson, in Duckworth, Grit, 2016). You will not get the room to run those long games unless you first prove, in your opening quarter, that you can deliver.

What to do on Monday

You do not need a bigger team to be a good leader in your first ninety days. You need to see the team you have clearly, to chase visible progress rather than grand announcements, to measure your wins in language everyone understands, and to build the safety that lets your engineers persevere.

The hires will come. When they do, they will join a team that already has momentum, a leader who has already earned trust, and a culture where progress is the norm. That is a far better thing to hire into than a team still waiting for its new boss to prove that the wait was worth it.

Ninety days from now, someone is going to decide what kind of leader you are. Give them something they can see.