Need someone to lead product management at your software company? I build high-craft software and the teams that build it. 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

Should individual people have OKRs?
May 14: A good OKR describes and measures an outcome, but it can be challenging to create an outcome-focused OKR for an individual.
10 OKR traps and how to avoid them
May 8: I’ve helped lots of teams implement OKRs or fix a broken OKR process. Here are the 10 most common problems I see, and what to do instead.
AI is Smart, But Wisdom Requires Judgement
May 3: AI can process data at lightning speed, but wisdom comes from human judgment—picking the best imperfect option when facts alone don’t point the way.
Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.
What branding can teach about culture
Jan 8: Culture is your company’s point of view in action—a framework guiding behavior, even in the unknown. You can’t copy it; it must reflect your unique perspective.
Think Systems, not Symptoms
Dec 15: Piecemeal process creation frustrates teams and slows work. Stop patching problems and start solving systems. Adopting a systems thinking approach helps you design processes that are efficient, aligned with goals, and truly add value.
Your Policies Aren’t Your Culture
Dec 13: Policies guide behavior, but culture is the lived norms and values of your team. Policies reflect culture -- they don’t define it. Netflix’s parental leave shift didn’t change its culture of freedom and responsibility. It clarified how to live it.
Lighten Your Process Burden
Dec 7: Everyone hates oppressive processes, but somehow we keep managing to create them.

Older...

What I'm Reading