Becoming a Manager? Here’s your Survival Guide
Becoming a manager is a jungle of creeping scopes, tangled dependencies, and hidden pitfalls. Your teams scramble to push projects through this wild mess to the other side, but need capable managers who can guide them down the right path and keep them functioning as an effective unit.
Unfortunately, not all managers are up to this task. Yes, managers inherently possess authority and influence, but these are tools, not privileges. Managers who wield them as blunt instruments are doomed to failure.
Good managers know how to wield their power with a light touch. They inspire and motivate instead of demand. They focus on the overall success and the team’s goal, not their own reputation. They survive and thrive as part of a team.
Becoming a manager might sound lofty and difficult, but it’s actually not. Anyone can learn good leadership, you just need to follow a few simple steps:
Define your Role
Before you embark on your journey of becoming a manager, you have to decide what kind of manager you want to be. What role will you play within your team? What specific tasks will be within your AOR (Area of Responsibility)? Which will you delegate?
Teams are like organisms who change based on the stimulus you provide. This means you have to carefully manage the team’s performance. Performance management is a cyclical process, in which your role is to set the employee’s expectation for their growth for a specific period, and help them stay on the path you set (through constructive feedback and reinforcing good behaviour). As they progress, you’ll also assess this growth and review it with them. Then the process begins again.
You can also decide which leadership style best fits your team. Here’s a few to consider:
- Directive leadership gives clear direction and guidance, which is ideal for leading uncertain or inexperienced employees, but not for veterans who dislike being micromanaged.
- Supportive leadership involves helping highly stressed or struggling employees deal with the demands of their position. This is done by removing obstacles or providing emotional support.
- Participative leadership promotes teamwork by encouraging input from every member. It’s great for when your team is composed of experienced individuals who want to be involved in decision-making.
- Achievement-oriented leadership focuses on growing individual contributions for the benefit of the larger whole. It works best with employees who can rise to the challenge of a competitive environment.
Build Structure for your Team
When you apply structure to your team’s operations, you introduce a predictable and repeatable process that can help you work more efficiently. Structure does not necessarily mean rigid and inflexible: you can introduce virtually any kind of structure you want, as long as it makes sense within the context of the team and helps them maximize their capabilities. Some examples include:
- Team Generalist: Anyone can pick up any task at any time (best for extremely small companies)
- Team Specialist: Everyone has a defined role that fits their strengths. Cross-training will help minimize downtime and cover for absences.
- Team Relay: Usually seen in companies who are moving to an agile environment. This is a transitional approach, and in the long term it is ineffective.
- Team Biathlon: Roles change in every sprint. This gives everyone a chance to cross train, and can help make a team stronger (but you might not want to make it your default structure).
- Team Handoff: Work is handed off from team to team, which works best when the entire company works in an agile environment.
- It’s also important to make sure your deadlines stick. For that to happen, they need to be achievable and genuine. If they’re not, people may just blow them off and assume there is no consequence to missing them.
Align Everyone in the Same Direction
The whole point of having a team is so that each individual member can contribute to a larger effort. But if those contributions are scattered and go off in different directions, then the end result is even worse off than before.
Part of your journey of becoming a manager, will require you to align your team’s efforts toward the team’s collective goal. This can be effectively accomplished by:
- Scrum meetings are daily or weekly standups that keep your team aligned by allowing everyone to share progress, delays, ideas, and issues. The frequency of your meetings can depend on the length of your sprint period, which can be daily, weekly, bi-weekly, or monthly. For example, a simple formula for a daily scrum is for each team member to report on “what I accomplished yesterday, and what I’m working on today.” Here at Unito, we prefer to do asynchronous daily scrums via a slack channel!
- Clearly communicating objectives: Your team can’t work together if they don’t know what they’re working towards. Make sure your team understands the immediate goal and the larger objective.
- Build trust: In order to effectively align your team, you’ll need to make sure they trust your judgement. Trust comes from being transparent about wins, fails, and progress. This boosts motivation and helps make your team more effective.
Scope Out the Problem
Let’s get it out of the way right now: you will run into problems throughout your journey of becoming a manager. Without question. The difference between a good and a bad leader is their response to said problems. Good leaders can get to the root of the problem quickly.
The Five Why’s method is a highly effective way of discovering the true cause of a problem. It involve digging into each problem by asking why it may have occurred, until the root cause is found. It’s a great way to break the issue down into manageable steps.
Trust your Team to Tackle it
Once you’ve identified the problem, it’s time to step back and let your team handle it. Give guidance and provide feedback, but trust them to do their thing.
Part of this trust is letting your employees make mistakes. They will have their own ideas and find their own solutions. Not all of those solutions will work. A good manager doesn’t condemn the person, but addresses the mistake instead. They focus on the problem, and trust the employee to learn their lesson and find a better way the next time.
Measure the Results
How can you know how well your team is performing if you don’t have any baseline by which to measure them? Part of your job of becoming a manager is to discover and implement a measure by which you can gauge how your team has improved.
This metric could be hours spent on a project, adherence to deadlines, number of tasks done within a period of time, or something else. The metric (or metrics) you choose will depend on your particular business, and your particular goals. Whatever metric you choose, make sure it’s an accurate measure of team quality and performance, and that gathering the information doesn’t interfere with team operations (if they have to stop work to fill out a spreadsheet, it’s intrusive). Also remember that as your team grows, your standards–and even the metrics themselves–must adapt accordingly.
Review the work
So you successfully navigated the jungle and emerged out the other side! The project is done, but you can’t relax just yet. You’ve got to do a project post-mortem first.
Project post-mortems expose gaps in your process and weaknesses in your team. These need to be brought into the open and examined with absolute objectiveness. No blame-casting or covering up. Teams need to review the project with total honesty if you’re going to learn from previous experience.
Improve and start the next project
Next, take the lessons you learned from the post-mortem and see what needs to happen in order to fix it. Perhaps you add another QA task to the project timeline, or you hire a new person to make up for a gap in skill.
Once you have these solutions in hand, you can run them through the GUT matrix (Gravity, Urgency, Trend) to assess which problems should be prioritized. If the problem has multiple causes, you can use the Ishikawa diagram to home in on the closest possible root cause. This is what you should prioritize fixing before the onset of the next project.
Share the Knowledge Outside your Team
You’re not the only one in the organization affected by the project. Other departments have a stake in what you do as well, even if you’re the sole PMO. Cross-functional teams could benefit from your hard-won wisdom. So can management, who are responsible for policies that can make your job either easier or harder.
Share your wisdom with other teams by hosting lunch and learn sessions, one-on-one meetings, or even posting on a public forum or wiki.
If you’re passing the project (or team) off to another PM, conduct a hand-off meeting where you discuss all relevant issues and schedules with the incoming group. Be open and honest about this information, and don’t forget to inform any clients or stakeholders that a switchover is taking place. Make sure the project archives are in a location the new group can easily access and organize them for efficient browsing.
Becoming a manager doesn’t happen overnight, for anyone. Stay the course and your team will grow along with you. And remember, if it’s lonely at the top, you’re not doing it right.
Got any tips on becoming a manager? Tweet us @unitoio!