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

Management & Leadership

Think Systems, not Symptoms

Designing processes can be tricky. Often, people create individual processes to solve specific problems. Running around plugging holes might feel effective in the moment, this piecemeal approach is counter productive.

When you focus only on individual problems, you risk creating a heavy and cumbersome process. Over time, these processes can feel authoritarian and arbitrary, leading to frustration and disengagement among your team. Instead, it’s crucial to adopt a systems thinking perspective.

Systems thinking helps solve complex problems by looking at how the components of a system interrelates. The systems thinker evaluates actions in context of all the other actions, activities that take place. To apply systems thinking to your policy creation instead of focusing on isolated incidents, consider the overall problems facing your business. Ask yourself:

  • What outcomes are we trying to achieve?
  • How can we create those outcomes effectively?
  • What else will happen if we implement this policy?

By shifting your focus to the larger issues at hand, you can design processes that are not only efficient but also aligned with your business goals.

Evaluate the underlying causes of problems rather than just treating the symptoms. This way, you can create policies that genuinely add value and support your team, rather than constraining them.

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