Why New Managers Try to Fix Everything in Week One and Fail

Week one feels like you have to prove you deserved the promotion.

So you fix things. Meetings, processes, tools, priorities, roles. All at once. Fast.

By week three, half those changes are reversed, the team is exhausted, and you’ve burned credibility you hadn’t earned yet.

Fixing everything in week one is not leadership. It is anxiety in action.

What usually happens

Day two, you see a messy process. You change it. Day three, you change the meeting cadence. Day four, you reassign tasks. Day five, you announce a “new way of working”.

None of these changes are bad individually. The problem is speed and volume. The team went from a stable manager to a tornado in five days.

People start whispering: “Just wait, they’ll change it back next week.” And often, you do, because you changed things before you understood why they were that way.

You also miss the real problems, because you’re busy fixing visible ones. The loud process is rarely the broken one. The quiet bottleneck is.

Meanwhile, the team is spending energy adapting to your changes instead of doing the work. Output drops. You think they’re resisting. They’re just tired.

Why this becomes a problem

You lose trust. Change without context feels random. Random change feels unsafe. Unsafe teams slow down.

You fix the wrong things. You don’t have enough data in week one to know what actually needs fixing. You’re fixing symptoms you can see, not causes you haven’t found yet.

You create change fatigue immediately. If week one is five changes, what is month two going to be? People brace instead of engage.

You can’t follow through. Five changes at once means zero changes followed through well. Half-implemented changes are worse than no changes.

The mistake managers make

The mistake is confusing motion with progress.

New managers think: if I change things fast, they’ll see I’m serious.

What the team sees: this person doesn’t understand how we work yet, and they’re changing it anyway.

Authority in week one does not come from change. It comes from observation.

What to do instead

Week one: Observe. Listen. Note. Change nothing structural.

Use Listen / Map / Pick One.

1. Listen. Do 1:1s with every direct report in the first 5 days. 20 minutes each. Three questions only: What’s working? What’s stuck? What would you change if you were me? Write it down. Don’t promise fixes. Just listen.

2. Map. After the 1:1s, map what you heard. What came up three times or more? That’s your real priority list. Not the messy spreadsheet you noticed on day two.

3. Pick One. Choose ONE change for week two or three. The smallest change with the biggest relief. Announce it clearly, implement it fully, follow through. One well-executed change builds more authority than five rushed ones.

Everything else goes on a “later” list. Tell the team: “I heard X, Y, Z. We’re starting with X this week. Y and Z are next.” That transparency alone builds trust. They feel heard, and they see you can prioritize.

Resist the urge to “leave your mark” in week one. Your mark in week one is: steady, listening, not breaking anything. That is rarer than you think, and more respected.

Example

Fix-everything version: Week one: new meeting structure, new task tracker, new roles, new deadlines, new reporting format. Team spends the week learning your systems instead of shipping. Two good people start updating their resumes.

Observe-first version: Week one: 1:1s with everyone. Listen only. End of week: “Thanks everyone. Top three themes I heard: unclear priorities, slow approvals, meeting overload. Next week we’re fixing priorities first – one shared board, updated Mondays. The other two are coming after.” One change, clearly explained, tied to what the team told you. That lands. That builds buy-in.

Then actually fix priorities in week two. Fully. Then move to approvals in week three. Sequential, calm, complete.

How to apply this this week

  1. Freeze structural changes for 7 days. No new tools, no process rewrites, no reorgs. Observe only. Write down what you want to change, don’t act yet.
  2. Run 1:1s with three questions. What’s working? What’s stuck? What would you change? 20 minutes each. Take notes.
  3. Build a “heard list”. After 1:1s, tally repeats. Top 3 themes = your real roadmap. Share that list with the team.
  4. Pick ONE change for next week. Smallest effort, biggest relief. Execute it completely before touching the next one.
  5. Tell the team what you’re NOT changing yet. “I’m not touching the reporting format this month.” That sentence alone reduces anxiety. People fear the unknown change more than the known problem.

Final note

You were promoted to improve things. You will. Not in week one.

Week one is for listening and mapping. Week two is for one clean change. Week three is for follow-through.

Slow is fast in month one. Observe first, fix second. The team will trust your changes a lot more when they see you understood before you acted.

This article is based on the Plain Act approach to early management pressure.

---