Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Product Management

Different roadmaps for different folks

Your customers need fewer details than your co-workers. Your product organization requires a different level of detail than your sales and marketing teams. The people working on other parts of your product need more detail than those working on other products. And the members of your product team need specific details that no one else does.

overly-complicated street map

This is a common failure mode of roadmaps. You spend a lot of time crafting the perfect roadmap slide and then share it with everyone. Product management won’t let sales share the roadmap directly with customers because it needs to be explained by a product manager to make sense. Meanwhile, engineers lose sight of the big picture because the roadmap doesn’t serve their needs—they end up focusing solely on the issue queue.

Think of a world map—it doesn’t show every town, and the towns that are shown don’t have every road detailed. A town’s road map won’t show hiking trails or elevations. Different people need different maps for different purposes.

Unfortunately, a whole category of tools has emerged that bake these failings right into a company’s processes. They take your Jira board and turn it into a presentable roadmap. Even if they allow you to create different versions of the roadmap, they don’t make it easy to include entirely different content for different audiences.

You need to tell your customers what problems you’re planning to solve. You need to tell your company why you’re solving those problems. Marketing needs an idea of when you’ll solve those problems. And your product teams need to discuss how you’re solving those problems.

These are all different roadmaps of the same thing.

Recently Written

A Framework for Scaling product teams
Oct 9: The people, processes, and systems that make up a product organization change radically as you go through the stages of a company. This framework will guide that scaling.
My Networked Webcam Setup
Sep 25: A writeup of my network-powered conference call camera setup.
Roadmap Outcomes, not Features
Sep 4: Drive success by roadmapping the outcomes you'll create instead of the features you'll deliver.
Different roadmaps for different folks
Sep 2: The key to effective roadmapping? Different views for different needs.
Micromanaging and competence
Jul 2: Providing feedback or instruction can be seen as micromanagement unless you provide context.
My productivity operating system
Jun 24: A framework for super-charging productivity on the things that matter.
Great product managers own the outcomes
May 14: Being a product manager means never having to say, "that's not my job."
Too Big To Fail
Apr 9: When a company piles resources on a new product idea, it doesn't have room to fail. But failing is an important part of innovation. If you can't let it fail, it can't succeed.

Older...

What I'm Reading