How to build a product roadmap everyone understands. Product roadmaps are one more tool at your team’s disposal to communicate what your priorities are at any given time period. However, it’s questionable how best that they can be used. Are they granular lists of product releases by date? Or are they more high level overviews of the themes you’ll be tackling now, next and later?
Take on your competition with these lessons from Google Maps. It’s a common perception that a new product must be 10x better than the incumbent to be truly disruptive. But this doesn’t always pan out, with users oftentimes failing to see exactly why the product is better. Bret Taylor, during his time building Google Maps, discovered something — “you have to make your users a little uncomfortable to make “better” matter.”
Step out of execution mode. Get inspired. Really think about your product. Here are three great reasons to come to Cleveland for two days in September for Industry 2016, the product conference. Speakers include Google Venture Partner Ken Norton, HubSpot VP of Product Brad Coffey and a host of other phenomenal product leaders.
Ode to a non-technical product manager. Many product managers and would-be product managers who do not have a strong technical background can’t help but feel a little insecure. Particularly if they happen to be working with a highly skilled, super smart team building a high-tech product. Should they have technical skills on par with the rest of the team? Hunter Walk argues no, that it’s more important for that person to be technically curious, but hold one superpower that separates her from the generalists.