Leading Successful Product Teams
-
Avoid meetings as much as possible. Instead of having them, communicate asynchronous to each other via tools such as Linear, GitHub, Figma, Slack, and similar.
-
Provide at least three days of focus time per week for designers and developers in the team. There should be no interruptions whatsoever during this time. Let them do their work.
-
Trust your team to make decisions, they’re the experts. Your job is to make sure they know where they’re heading, clear any roadblocks from the way, and protect them from external cruft.
-
Default to openness. The team should be sharing what they’re doing whenever they can. Building things transparently increases visibility and accountability and makes them push towards higher quality.
-
Define just the right amount of process. Too much process and it will slow down your team and their performance, while not enough will create inconsistency.
-
Don’t do team wide standups or sync meetings, except one meeting at the start of every week. Here you can walk through the tasks and discuss how the team feels, what motivates them right now, and if there are any blockers.
-
Use as few tools and platforms as possible to get the work done and stay focused throughout the week.
-
Automate everything you can. The team should value the time of their colleagues, users, and their future selves. Always be proactively looking for ways to automate repetitive tasks.
-
Care for the people who use the product. The whole team is there to make their day-to-day work better and more pleasant through great user experience.
-
Most collaboration and discussion should happen asynchronously, using the previously mentioned tools. This requires clear and thoughtful communication from everyone.
-
When useful, have the team members pair up to solve tough problems. Make sure all decisions are documented.
-
Provide weekly updates to the rest of the organization about progress. What has been worked on, what is being worked on, and what happens next.
-
Create a public roadmap that holds the whole team accountable.
-
Focus on persistent iteration over flashy launches.
-
Don’t be afraid to throw things away.
-
Shipped is better than perfect.
-
Be kind.