Originally posted by tomtomagain
View Post
OK let's be thorough about this.
Objectives of a Manager.
1. Set clear expectations with the CEO or your manager
You’ve been hired to fill a hole, and there will be organizational pressure for you to contribute immediately. Review your objectives with the CEO to make sure they have the right expectations for what you’ll be doing. Your primary goal for the first month is to effectively join a team.
2. Schedule a one-on-one with everyone on the team
Depending on the size of the company, this may take a few hours or the entire first month. Find time to meet with everyone individually.
I prefer walking one-on-ones – there’s something focusing and invigorating about walking together and looking ahead as opposed to staring at each other across from a conference room table.
3. Ask everyone this question
“What can I do to make your life easier?”
You’re showing that you’ve here to help, not to command. How they answer is almost as important as what they say. You’ll get a true indication for how they perceive the PM role, and what they need from you.
4. Take a load off their back
Hopefully you’ll walk away from the meeting with something you can take from them that’s cutting into their productivity. Maybe an engineer would love for you to take over bug triage.
5. Schedule time with your lead engineer to walk through the product’s technical architecture, in deep detail
Don’t shy away from asking questions or drilling down on things that didn’t quite make sense.
Too often PMs try to impress their engineers with their technical acumen, but in my experience engineers are much more impressed with PMs who are willing to ask questions and say “I don’t understand that.”
6. Resist the urge to jump in and start changing things
You’re going to want to start making changes to the product and the development process. I recommend holding back a bit in the beginning.
Your ideas and thoughts will be better formed after you’ve had a chance to settle in, gain credibility, and absorb all of the nuances. You’ll also be demonstrating that you’re a listener.
etc ....
(Text from Ken Norton, Google Ventures)
Comment