Adam Kalsey Copyright 2021 Adam Kalsey. Permission granted for non-commercial use. Republication is prohibited.,2021:/blog//2 2020-12-10T19:04:30Z This is the blog of Adam Kalsey, internet entrepreneur, product guy, technologist, and baseball fan. The Trap of The Sales-Led Product,2020:/blog//2.5059 2020-12-10T18:16:12Z 2020-12-10T19:04:30Z It’s not a winning way to build a product company. Adam Kalsey francis-macdonald-6otbby2PCbg-unsplash.jpg

When a customer requests a custom one-off feature, it can be hard to say no. It can be even harder when a new customer prospect promises to buy your product… but only if you’ll make a change for them. In the best case, the sales team has identified an opportunity and asks Product to evaluate it. In the worst case, Sales signed a contract with a promise to deliver a vague, poorly scoped feature.

This will come up from time to time in every company. When it happens too often, your product becomes sales-led, at the mercy of the whims of potential customers. In a healthy company, these requests are expansions to the product’s current capabilities. For example, the prospect requests an integration with a popular business intelligence tool you don’t yet support. When it happens this way it can be good. You’ve known for a while that you needed that other BI integration. Now you have a reason to prioritize your integration and your customer is a built-in beta tester.

In an unhealthy company, these requests from sales prospects aren’t something you’d planned on doing soon, if ever. They represent large shifts from how your product works today, they’ll take large amounts of investment to pull off, and they might even make the product worse for your other customers. Still, there’s pressure to “just get it done” because you need this sale to hit your financial targets.

(2018 words)

See also: How the Sales organization in a large company slows innovation, Building the Customer-Informed Product, The Hidden Cost of Custom Customer Features, Wireless Adoption

Tagged as:          

The Hidden Cost of Custom Customer Features,2020:/blog//2.5058 2020-12-08T04:32:05Z 2020-12-10T18:05:39Z One-off features will cost you more than you think and make your customers unhappy. Adam Kalsey Surprised child

The CEO sends you an email. "Skyhook Industries wants to know if we can add some features so they can use us for their water treatment division. They're one of the largest customers of our highway construction management product. Can we add their water treatment features and keep them happy?"

You reply that the product team saw this request already and learned that none of your other construction customers would find the feature useful. The company had no plans to start selling to the water treatment industry. The feature would be used by Skyhook and only Skyhook. You had told the customer that you would not be adding the requested feature.

The CEO comes back to you later. Skyhook's management is willing to pay your company $50,000 to develop the feature. It's not complicated to build, so a junior developer could build it. $50k is half a junior developer's salary, and it certainly won't take them 6 months to build. Sounds like pure profit and you make a top customer happy.

This is a common story at software companies all over. A customer wants a pet feature. Something no one else will ever use, something that doesn't fit your product vision. Usually, this is a very large customer and you're afraid they'll leave if you don't say yes. Sometimes this is a smaller customer that's promising to become a huge one if only you could do this one thing. Sometimes they're not a customer at all but promise to buy the product if you take care of their special need. Often, the customer is willing to pay you to build it.

Sounds like a win all the way around. But it's not.

(976 words)

See also: Evaluative and generative product development, Building the Customer-Informed Product, Credible Design, Discover your inner hamster

Tagged as:        

Domain expertise in Product Management,2020:/blog//2.5057 2020-11-17T03:07:45Z 2020-11-17T03:08:59Z When you're hiring software product managers, hire for product management skills. Looking for domain experts will reduce the pool of people you can hire and might just be worse for your product. Adam Kalsey Many software product management job advertisements request or require expertise in the problem domain the company competes in. With rare exceptions, a good product manager does not need to be an expert in the problem. Often, it's detrimental for a product manager to be a domain expert.

Products are about solving problems for customers. When a product manager is a domain expert, it is hard for them to avoid injecting their own views and desires into the product. They act as if they were the customer and solve problems they imagine a customer might have instead of ones that the customer actually has.

What's important is that a product manager possesses good technique. That they are able to execute a repeatable product discovery process. That they can analyze customer needs to identify problems that the customer needs solving. That they can use data to determine if the product is solving those problems for their customers. These are the skills and knowledge a product manager needs.

Hiring product managers based on their expertise with a specific market or customer type can lead to a product that's led by the product manager's understanding and biases instead of what the customer actually wants.

For this reason, we spend time coaching product managers to approach problems with a beginner's mind. To discover what your customer needs you must throw out your notions of what problems exist or how to solve them.

It's strange to ask someone to think with a beginner's mind but also require them to come with expertise.

This isn't to say a product manager should remain completely ignorant of the domain. A good product manager can learn what they need to know about the problem space in a few months. By interacting with your customers the product manager will continue to grow that knowledge over time.

This applies to customer types and markets as well. Managing consumer products isn't a mystical thing that an enterprise software product manager can't figure out. The tactics used to get product feedback can be different across customer segments. The go-to-market mechanisms will vary. But that's also true of different market categories or geographies or buyer types or product stages. If a product manager can be effective with pricing strategies for a mid-market SaaS accounting product, they can design effective pricing for mobile games or enterprise healthcare or consumer finance tools.

Someone does not need to be a mother to build software products for moms. They need to know how to talk to moms and elicit problems from them.

What are the rare exceptions? If the problem domain has deep tribal knowledge that's not expressed anywhere or requires extensive training to understand, a product manager won't be able to learn enough fast enough to know if they understand the customer needs well. The quality of a product manager's decisions will suffer. If there aren't sufficient checks on those decisions, problems will arise. A product manager for firmware in implanted medical devices likely needs more than superficial medical knowledge. A product that manages compliance for a highly-regulated environment would benefit from someone that knows the laws well.

Another exception is the creation of a new product category. If you are solving problems that customers don't know they have it's hard to talk to customers about those problems. This is a much more rare state than most entrepreneurs and product people think it is. You probably aren't Steve Jobs. Steve Jobs probably wasn't Steve Jobs.

This all applies to software products only, since that's what I know. Building performance racing carburetors for vintage motorcycles or designing complex financial investment vehicles might need domain expertise. Or might not. I have no idea.


See also: How to scale your product team from one product manager to an entire organization, How the Sales organization in a large company slows innovation, Developer Experience Principle 1: Easy to Understand, Product Manager Career Ladder

Tagged as:    

Strategy Means Saying No,2020:/blog//2.5056 2020-10-28T04:13:31Z 2020-10-28T17:03:28Z An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore. Adam Kalsey It's not the notes you play, it's the notes you don't play. - Miles Davis


There are three types of opportunities you'll come across. Those you've decided to tackle, those you've decided to ignore, and those you didn't know existed. By defining which ones you'll ignore alongside those you'll tackle, you bring clarity to how you think about a problem.

I once worked with an executive that called himself an "and leader." When confronted with his organization asking if they should focus on this or that, he would proudly say yes to both.

This is a failure of leadership.

Anyone can say yes to everything. They don't need a leader to do that for them. Thinking strategically means deciding what you'll do. The list of things you'll do is only meaningful if there's a limit to the list.

Leaders communicate strategy by explaining what the organization is going to do, but often forget to communicate what they've chosen not to do. It is more effective to include negative choices when communicating strategy. It’s easier for people to understand the choices you made when you put them in the context of the choices of what to leave out. They're two sides of the same coin. Communicate them as such.

By having a clear strategy that covers both what you'll do and what you won't do you'll improve your organization's ability to make decisions themselves and to execute.

An effective strategy acts as guide rails. If people know what to say no to, it's clear whether you'll pursue or evaluate a new opportunity that appears.

See also: Understanding vision, strategy, and execution, Brain drain, How Companies Respond to the Risks of Personal Brands, How Companies Respond to the Risks of Personal Brands

Tagged as:      

Understanding vision, strategy, and execution,2020:/blog//2.5055 2020-10-24T22:02:09Z 2020-10-24T22:11:22Z Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy. Adam Kalsey What's the relationship between a product vision, strategy, and execution? Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy.

(781 words)

See also: Strategy Means Saying No, Think or do, Building the Customer-Informed Product, Time-based information

Tagged as:          

How to advance your Product Market Fit KPI,2020:/blog//2.5054 2020-10-21T18:28:22Z 2020-10-21T18:58:13Z Finding the gaps in your product that will unlock the next round of growth. Adam Kalsey Finding the gaps in your product that will unlock the next round of growth.

Once you're tracking your product-market fit KPI and you understand why your biggest fans love you product, the next step to advancing your product is identify product improvements that will turn more people into fans.

Your best-fit customers are the ones that absolutely love your product and all like it for the same reasons. You asked your customers how disappointed they'd be if your product went away. The ones that would be extremely disappointed are your top customers. Then you asked what they like best about your product. The most similar answers are your top product attributes.

The people who identify the top product attributes as their favorite thing about the product are your ideal customers. Getting more of those requires that you expand the number of attributes that people love while expanding the group of customers that love them.

To expand these and advance your product-market fit, ask one more question. "How could we improve this product?"

Then ignore most of the answers.

It's tempting to look at what the biggest fans are asking for and build those features. If you do this you'll end up building things that the early adopters want instead of what the broader market wants. You'll be improving the product for those that already are customers instead of making the product more attractive to people who aren't already customers. You'll expand the number of top attributes, but not the number of customers that love them.

Likewise, you should ignore the improvement ideas from people who say they wouldn't be at all disappointed to lose your product. These people are far enough away from your target market that building for them will take your product off on a tangent.

The opportunity for product improvement lies in those end users that would only be somewhat disappointed if they couldn't use your product. They like the product but could live without it. These users are telling you, "I really want to love your product, but..." If you want to make your product better, work to convert these users into your best fans.

You need to be careful, though. Changing the product to better cater to these users could move your product in a direction that's less attractive to your existing customers. To increase your product-market fit, you need to make these people happier. But without moving the product away from the things that make your biggest fans happy.

The secret to doing this is to realize that not all your "almost fans" are the right market. The right market is the subset of these users are most like your ideal customer.

Look at the clusters of attributes your biggest fans loved most. Then find the almost-happy users that identified these same attributes as the best thing about your product. This is the cohort of users that like your product for the right reasons. Now, look at what they think would improve the product. Fix these things and you'll move these customers into the raving fan category.

Take this cohort's answers to "what could we improve" and cluster them. Find common requests. These requests are the gaps in your product that will unlock the next round of growth.

You asked, "How could we improve this product?" You ignored most of the answers. The only answers you're listening to are from users who like but not love your product, like the same things as your top fans do, and are asking for the same things that others like them want. These users want to love your product and want to love it for the right reasons. They just need a little nudge.

See also: How to understand your product and your market, Don't use NPS to measure user happiness for enterprise software, Ask One Question To Help You Reach Product-Market Fit, The KPI that measures Product-Market Fit

Tagged as: