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

Product Management

Go small

When a large company that doesn’t have a culture of innovation decides to start something new, it often fails because it throws too much money and too many people at the initiative.

Lots of funding changes what success means. The product can’t start small and grow. It needs to win big, fast. If it’s not an immediate breakthrough, it’s a failure.

But innovative products aren’t built that way. Great products are discovered over time, not invented in a flash of brilliance.

The product loses cohesion.

In the early days of a product, you’re still figuring out what you’re building. Strategy and plans shift rapidly. Big groups struggle with this. A big group needs extensive coordination and planning to align everyone’s work. It’s hard to spread new ideas and get everyone on board. So the rapid pace of change causes teams to drift. The organization stops working on common goals.

Large organizations need large amounts of coordination. They break in times of rapid change.

Things slow down.

In small groups, everyone knows the reason for a change in direction. They were probably involved in deciding to make the change. In large organizations, you need to practice change management to keep teams aligned. Without it, you’ll create frustration among those not involved in decisions. You can’t just make a decision and run with it.

Effective change management takes time. Every change takes longer to roll out. And because changes are more difficult, you’ll tend to avoid them. You’ll make fewer changes because they’re more difficult. The pace of innovation slows.

Small teams are more nimble than large teams. Early products must be nimble.

Culture suffers

When people form a new team, they develop customs and a culture that helps them all work together. There are unwritten rules that evolve. This can’t happen in a very large group.

But if you start with a small group, they’ll create these norms. Then as the group grows, new members will learn and adopt the culture.

Culture is the shared way that everyone behaves. It won’t emerge in a large group.

The product becomes boring

There’s a reason that design by committee is a pejorative term. Larger groups have more people to satisfy. Consensus gets harder to reach as more people get involved. Ideas can’t move as fast. The coordination and change management needs of a large organization result in specialization. When you’re only working on part of a product and not collaborating with other parts of the product, you make safer choices.

Effective innovation requires close contact and communication. People working closely and sharing ideas. Fast iteration loops. Low coordination overhead. Without those things, innovation suffers. Uniqueness takes a backseat. You build the obvious thing instead of the interesting thing.

The strengths of a large organization are the opposite of what makes innovation work. Starting something new requires that you start with a small team.

Recently Written

Your OKR Cascade is Breaking Your Strategy
Aug 1: Most companies cascade OKRs down their org chart thinking it creates alignment. Instead, it fragments strategy and marginalizes supporting teams. Here's what works better than the waterfall approach.
Your Prioritization Problem Is a Strategy Problem
Jul 23: Most teams struggle with prioritization because they're trying to optimize for everything at once. The real problem isn't having too many options—it's not having a clear strategy to choose between them. Without strategy, every decision feels equally important. With strategy, most decisions become obvious.
Behind schedule
Jul 21: Your team is 6 weeks late and still missing features. The solution isn't working harder—it's accepting that your deadlines were fake all along. Ship what you have. Cut ruthlessly. Stop letting "one more day" turn into one more month.
VC’s Future Lies In Building Winners
Jun 21: AI and megafunds are about to kill the traditional venture model, forcing smaller VCs to stop hunting for hidden gems and start rolling up their sleeves to fix broken companies instead.
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.

Older...

What I'm Reading