M360 Compass

M360 Compass · Management insights

First-time manager: ten mistakes you can prevent

· 6 min

A new supervisor listens to two technicians around a small mechanical assembly.

Becoming a first-time manager changes the work itself. The expertise that helped you solve problems remains valuable, but the team now needs priorities, decisions and support. The transition becomes difficult when you keep all your previous habits while adding responsibility for other people’s work.

The ten mistakes below are practical situations to notice, each paired with a replacement action. The aim is not to become flawless on day one. Choose the two situations most relevant to your week and prepare a specific attempt to handle them differently. Then check what changed with the people involved. A manageable practice is easier to learn from than an attempt to improve everything at once.

First-time manager: clarify your own role first

Take these questions into your first conversation about the role.

Three questions to settle with your manager
TopicQuestion
Expected resultWhat should move forward this month?
Decision authorityWhat can I decide on my own?
Previous roleWho will take over this task?

Before changing how the team works, ask your manager which results you now own. Which decisions belong to you? Which require approval? What part of your previous technical work will be transferred? Without answers, a promotion can create two overlapping jobs rather than one feasible role.

BDC’s delegation guide emphasizes defined roles and genuine room for employees to act. The ten situations here form an original practical review of your daily work. They are not a complete framework for every management context.

Explain your role to the team as well: what you will decide, what you want to understand and how people should flag an obstacle. An early conversation can reveal conflicting expectations that might otherwise remain hidden for several weeks. Be ready to adjust your understanding when the team describes dependencies you have not yet encountered.

Four mistakes that keep all the work on your desk

1. Redoing work whenever someone uses a different method. Before taking an assignment back, check the agreed result and constraints. If the approach differs but the result is appropriate, let the colleague proceed. Distinguish a personal preference from an actual requirement.

2. Delegating a task without defining the result. Explain the deliverable, date, resources and decision boundaries. Ask the colleague to restate what they plan to prepare. This can reveal uncertainty before it produces a complete round of rework.

3. Keeping every previous responsibility. List the technical activities you continue to perform. With your manager, decide which will be transferred, simplified or stopped. A promotion does not automatically add hours to the week or remove the need for management time.

4. Answering every question immediately. When a colleague can decide within their role, ask what they suggest and what information they need. Help them build a response instead of making yourself the only route forward. Intervene directly when the issue genuinely requires your decision or authority.

Three mistakes that make expectations hard to read

5. Changing priorities without explaining the trade-off. When a new request arrives, identify what moves behind it and who must be informed. The team should not have to discover on its own that two existing commitments can no longer be met together.

6. Waiting for a major problem before giving feedback. Describe a specific situation, the action observed and its effect on the work. Ask for the employee’s perspective and agree on another attempt. A broad label such as “unprofessional” leaves too little information for a practical adjustment.

7. Treating a meeting held as a decision made. End a discussion with the choice, the owner and the next check. If a decision is still missing, name who must make it and when. A long conversation does not replace an understandable commitment.

Use the same check for all three: “Does this person know what is expected after our conversation?” If the answer depends on what they must infer, clarify the expectation before closing the discussion. You can also ask them which remaining question would prevent them from starting.

Three mistakes that weaken conversations with the team

8. Assuming silence means agreement. Invite a specific response: “What obstacle do you see with this date?” Allow time to think. An open question can reveal a constraint that a quick “All good?” would leave undiscovered.

9. Promising something you cannot decide. Separate your intention from your authority. Explain what you can confirm, what needs checking and when you will return with an update. Keeping that update matters even if the final answer is not yet available.

10. Trying to correct the whole team at once. Choose one operating priority with the people affected. Explain the observed problem, proposed trial and review date. A series of changes without follow-up makes it hard to understand which adjustment actually helps.

Fictional example. Malik becomes a supervisor in an invented industrial-parts business in Granby. He notices that he takes back every order preparation and answers every question. The people and outcomes in this scenario are illustrative.

He chooses mistakes one and two. For a limited assignment, he defines the expected result and the points requiring approval. His colleague proposes a different method. Malik checks the agreed requirements, then lets her proceed. During the review, they discover that a reference document was difficult to find. They correct that issue before adding another improvement priority.

Prepare a realistic first improvement cycle

Choose no more than two mistakes for the first cycle. For each, record the replacement behaviour, the next opportunity to use it and a trace to review. That might be an instruction restated by the colleague or a decision with a clearly named owner.

Arrange a review with your manager or an experienced peer. Bring one fact, one question and the next adjustment. Avoid turning the conversation into a defence of your entire week. Feedback grounded in one situation is easier to understand and apply than a general assessment of your management potential.

M360 Compass RoleAlign documents roles, responsibilities, expectations and decisions. Performance and development connects feedback with development priorities and one-on-one follow-up. These capabilities can provide a framework for clarifying your role and reviewing a chosen practice over time.

They do not replace the judgment needed to hear a concern or resolve competing commitments. Bring an anonymized situation involving unclear ownership or follow-up to an M360 Compass demonstration. You can explore a concrete use instead of relying on a broad promise of becoming a better manager. Keep the next action small enough to practise during ordinary work.

For a related management tool, explore the RACI matrix. Use it to clarify a separate question, while keeping this method focused on the situation described here.

Frequently asked questions about a first management role

Should I stop doing all technical work?

Not necessarily. Clarify with your manager which technical contribution remains appropriate and how much time team management requires. The important thing is an explicit scope with realistic transfers, rather than silently carrying two complete roles at the same time.

How can I delegate while keeping appropriate follow-up?

Agree on the result, decision boundaries and a review point suited to the stakes. Leave room for the colleague’s method where possible. A planned check lets you assess progress without taking back every step of the assignment.

What should I do when I do not yet have an answer?

Explain what you know, what needs checking and when you will provide an update. Identify who can make the decision. Avoid a promise beyond your authority and keep the update time you announced, even when the final answer is pending.

How should I choose my first two priorities?

Look for repeated situations causing rework, conflicting expectations or stalled decisions. Choose issues where you can make a practical change soon. Check with your manager and team that the proposed adjustment addresses an observed problem rather than an assumption.