- You're the CEO of the product. You drive the vision.
- You know your product from 0 to 100%. You know everything.
- If anyone wants something or know about one problem, you should be the first one to know this. Never go to team members.
- You should be able to identify problems, the source, before declaring it as "a problem to solve" for your team. AKA "false positives", "that's not a bug, that's the behavior", etc. Be the shield for this shit.
- People will use all kind of trickery to force you to do things for them. Learn how to say no. Learn how to prioritize. Remember you have your own interests to cover for your product.
- Always tell what you want to achieve, what is needed, how much time it will take and what will be the deliverable. The more defined the answers, the best for both team and you will be.
- You're the one taking the last decision. Everyone must acknowledge this.
- You should listen people, and rely on their expertise. They will tell you how to do something, but don't let them to change your high level achievement.
- Tell the people what you want to achieve.
- Call on people when they did stuff out of the planning. AKA: "I've been doing this nice animation, now the product looks nice", etc.
- Always talk individually, short meetings, instead big team meetings. Consensus always drive bad products.
- Nothing goes production without your approval.
- Enforce criteria acceptance: all features must be done according to the plan, not what the developers wanted to implement.
- Kick out toxic people from your team. The earlier, the better.
- Never let people insult you.
- If you happen to make a mistake, be the first one acknowledging this. Never try to justify incompetence. Always try to solve that to avoid new cases in the future.
- Try to help team members who aren't motivated. Talk to them. They're confused with their role in the project, usually.