Tales & Co.COACHING
N 41.0082° · E 28.9784° · Istanbul
← Perspective
Field Notes

A New Manager's Roadmap Starts With Defining the Job

A roadmap for a new manager is usually written as the team's plan. The manager's own job, what their week is actually for, is missing from it.

7 min readOctober 2026

A new manager's roadmap is usually written as the team's plan

A new manager is usually expected to produce a document within the first few weeks. Their own manager asks for it, or HR has a template ready, or the manager writes one to feel on firmer ground. The name varies: a ninety-day plan, a 30-60-90, a roadmap. The contents are remarkably constant. Listen and learn in the first month, set priorities in the second, show early results in the third.

There is nothing wrong with the template. The sequence is sensible, and it spares the manager the anxiety of a blank page. Read closely, though, almost every line describes the team's work: which process will be reviewed, which target set, which project accelerated. The manager's own work, meaning what their hours go to and what they stop giving hours to, appears nowhere in it.

The line the template leaves blank

That gap is a particular risk, because most new managers reached the seat by being very good at their own work, in a role where the job was clear. When the new job goes undefined, the most familiar work fills the space. The manager keeps doing the team's work and solving the problems they know best, and for a while experiences that as success. Why that skill backfires is the subject of the piece on the skill that got them promoted. A roadmap that plans the team's work and leaves the manager's role unwritten quietly sends the manager back to their old job.

The role is defined in three sentences

The method we use starts before any roadmap: the new manager writes down, in three sentences, what their job in this role is. The sentences should be short, but not general. A sentence like leading the team to success describes nothing, because it is true of every manager and changes no week. A good one changes what the manager does next Tuesday.

Three sentences

  • The decisions only I make: the ones nobody else in the team makes, or should.
  • The work I no longer do myself: work I do well, and that someone else in the team will do from now on.
  • What I will be judged on in six months: the one or two things my own manager will actually look at.

The first sentence usually comes easily, because the authority arrived with the announcement. The third makes the manager ask, for the first time, what their own manager expects rather than guess at it. The gap between the third sentence and what the manager's manager actually watches explains many of a new manager's early surprises. The second is almost always left blank, or written last.

Naming the work given up

The second sentence is hard because the work to be given up is usually part of who the manager is. The manager who came from sales still wants the hardest customer, the one from engineering the knottiest problem, the one from finance the most sensitive spreadsheet. Letting that work go feels like a loss, so it goes unwritten. Yet when the work given up is not written down by name, the manager's calendar drifts back to it and leaves no room for the rest of the role. What that drift looks like is in the piece on the manager who still does the work.

A new manager's role is announced by the calendar of the first weeks, not by the announcement.

The definition is tested against the manager's own calendar

Once written, the three sentences are still a hypothesis. The most honest test is the manager's own calendar. At the end of the second week the manager sorts the past week's hours by the three sentences: which went to decisions only they can make, which to the work they meant to give up, which to what they will be judged on.

Reading the week

The result is rarely what the manager expected. Most of the week went to neither the first sentence nor the third. It went to the old work and to meetings other people called. That is not a failure. Early weeks look like this because the calendar predates the manager and carries the predecessor's habits. The finding is not that the calendar is wrong, but that the manager can only see it against a definition written down in advance. Without one, the same week is remembered only as a busy week.

What follows is not a rebuilt calendar, which is rarely possible in the first month. The manager picks two changes for the next week: a protected hour for a decision that belongs to the first sentence, and one item from the second handed over, with its name and its new owner said aloud. It looks small. Two weeks later the same reading shows the calendar moving towards the definition, and the manager knows what worked from their own week, not a guess.

The role the team reads

A team, too, learns the new manager's role from their week, not from the announcement. When the manager solves a problem personally, the team learns that the problem now belongs to the manager. When they leave a decision with the team, the team learns whose decision it is. These lessons are given early and are hard to unlearn. Without anyone saying it aloud, the new manager's role has been declared in the calendar of the first few weeks.

The stops on the roadmap are conversations with the manager's own manager

The template marks its stops with results: an assessment after the first month, a plan after the second, early wins after the third. The roadmap we suggest puts something else at the same stops. Each stop is a conversation with their own manager, the three sentences on the table.

Three stops

  • At the end of the first month, the definition is shown for the first time and the manager's manager corrects it. The third sentence is usually the one corrected most.
  • At the end of the third month, the calendar is discussed alongside the definition: whether the work meant to be given up was given up, and if not, what stood in the way.
  • At six months, the definition is rewritten, because the role is no longer the one the manager saw in the first weeks.

Where the expectation shifts

These conversations matter because the expectation set at hiring often differs from the one applied later. The interview asked for a transformation, and by the third month the manager's manager is rewarding a quiet quarter. Or the reverse. The shift comes from changing priorities, not bad faith, and nobody tells the new manager. A written definition makes the moment the expectation shifts visible; a manager without one learns of the shift on the day of the review.

How questions left unasked in the first ninety days return is in the piece on a new manager's right not to know. These three conversations put the most important of those questions, what the manager will be judged on, on the calendar.

From the field

Managers moving into a new role often come to us with a roadmap already written. It is usually a good one: priorities ranked, targets dated, the first win chosen. The conversation then turns to why their weeks feel scattered anyway.

The page we ask for first

So in the first conversation we set the roadmap aside and ask for the three sentences. The first takes a few minutes. At the third, the manager often stops, realising they have been working to a guess about something their manager never said. Where the second should be, there is usually a gap. The rest of the conversation is spent on that gap: which work is given up, to whom, and in what order. For someone now managing their former team, the question weighs differently, as set out in the piece on managing a former team. A roadmap for a new manager works when it writes down what the manager's week is for before it says where the team is going.

How we work begins with those three sentences. Our other pieces sit on the Perspective page.

For managers moving into a new role

Let's talk about the job itself before the plan.

The first conversation starts not with a ninety-day plan but with three sentences on what the manager's job in this role actually is.

Request a conversation
TALES & CO.   /   ENTERING
Click to enter
2026 · Vol I