# Will Munslow's Manager Readme

**Software Engineer Manager II at One Identity**

# Motivation for this document

This Manager README is to help me get a clearer picture about how I want to approach challenges as a manager. I hope others can understand my approach and coach me to adopt better strategies.

# My role

I will contribute to the growth of my teammates by listening to their concerns and collaborating on removing roadblocks while setting reasonable expectations to continue moving forward. I want to encourage a happy, collaborative environment where everyone works together to achieve clear goals.

# What do I value most?

I value ownership. Every team member should feel a sense of ownership and responsibility to their projects. It's not necessary to be an absolute expert nor know every answer. Collaboration among members is important to help each other gain a better understanding of our work.

# My Expectations

I expect people to speak up when they see problems so we can find solutions, but remain respectful. Problems are mainly mistakes and oversights, not acts of malevolence. 

Day-to-day, team members are free to manage their own schedules and there's no expectation to be immediately available at a moment's notice. It would be nice to know if someone is unavailable for an entire day, but it's not strictly necessary. Eventually I'll start to worry if I don't hear from people.

# 1:1s

I ask 4 questions: 

- What are you up to?
- Are you happy with your current tasks?
- Is anything pissing you off?
- Is there anything you want me to do for you?

While I start the conversation, this is my time to listen.

# Personality quirks

I tend to think in very simple, pragmatic terms. I may ask you to explain an idea in a different way to help me get a picture of it in my mind. I am predominately optimistic and I perceive problems as challenges to be overcome. 

# Where to focus on your first 90 days?

Onboarding is a work-in-progress but a team member should be able to start making simple changes to the codebase within the first 30 days. This would mean they have set up a development environment, understand the ticketing system, understand git flow, etc. This usually takes far less than 30 days but there could be a lot of studying involved to gain context to feel confident about code changes.

Your area of focus will be clearer after your first month and you should focus on expanding your knowledge on your way to becoming an expert. After 90 days, you should feel comfortable making changes and having an good understanding of how those changes affect the overall system.