The microservice architectural style is taking the world by storm. Last March, O’Reilly hosted their first Software Architecture Conference, and a huge percentage of the abstracts the program committee received touched on some aspect of microservices. Why is this architectural style suddenly all the rage?
The cheat sheet I wish I had before I became a product manager.
My path into product management — like many others — was a non-traditional one. I started in advertising as an art director, later moved into user experience design and product design, then finally ended up in product management.
There’s been a lot of self-learning along the way. Some from reading as much as I can (thanks, Medium!) but most has been learned on the job, for better or worse.
Looking back, one of the biggest pieces of advice I wish someone had given me before I got into product management is actually a very simple one:
Prioritization is a perennial challenge when building a product roadmap. How do you decide what to work on first?
If you’ve put the effort into brainstorming new ideas, finding opportunities for improvement, and collecting feedback, you’ll have a solid product roadmap full of good ideas. But the order in which you tackle those ideas deserves just as much thought. You need to take the time to prioritize well.
The purpose of a product roadmap is to communicate direction and progress to internal teams and external stakeholders. It shows the high-level initiatives and the planned steps to get there.
As a design partner at GV, I’ve worked with more than 100 startups in the past 5 years. Before that, I was a design lead on teams at YouTube and Google, and an early employee at FeedBurner, a startup in Chicago.
In other words: I’ve seen a lot of design teams in action over the past decade. The people on these teams are invariably talented, smart, and hard-working.
I’ve come to recognize Fortunately, I’ve also seen solutions to these dysfunctions—proven, reliable, and simple techniques that teams can use to work better together. And finally, I’ve translated these ideas into a set of mantras that capture the best behaviors of successful design teams.