<?xml version="1.0" encoding="utf-8"?>
<!-- 
You're looking at an XML data file that is used to read
this site in feed readers. You probably want to hit the
back button and read this site in a browser instead.
-->
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Adam Kalsey</title>
<link rel="alternate" type="text/html" href="https://kalsey.com/" />
<link rel="self" type="application/atom+xml" href="http://kalsey.com/atom.xml" />
<rights>Copyright 2026 Adam Kalsey. Permission granted for non-commercial use. Republication is prohibited.</rights>
<id>tag:kalsey.com,2026://2</id>
<updated>2026-03-06T22:45:53Z</updated>
<subtitle>This is the blog of Adam Kalsey</subtitle>
<entry>
<title>Where Does Product Marketing Belong?</title>
<link rel="alternate" type="text/html" href="https://kalsey.com/2026/03/where_does_product_marketing_belong/" />
<id>tag:kalsey.com,2026://2.5102</id>
<published>2026-03-06T22:44:14Z</published>
<updated>2026-03-06T22:45:53Z</updated>
<summary>The debate about whether PMM reports to product or marketing has a simple answer once you ask the right question.</summary>
<author><name>Adam Kalsey</name><uri>http://kalsey.com</uri></author>
<category scheme="https://kalsey.com/tag/b2b" term="b2b"/><category scheme="https://kalsey.com/tag/b2c" term="b2c"/><category scheme="https://kalsey.com/tag/organizationdesign" term="organizationdesign"/><category scheme="https://kalsey.com/tag/productmarketing" term="productmarketing"/><category scheme="https://kalsey.com/tag/strategy" term="strategy"/>
<category term="Software Management" />

<content type="html" xml:lang="en" xml:base="https://kalsey.com/">
<![CDATA[<p><img src="/blog/2026/03/resized-product-marketing.jpeg" width="950" height="633.33333333333" alt="A man standing between a marketing office and a product bullpen" /></p>

<p>Some companies put product marketing in product. Some put it in marketing. There's a pattern—consumer companies lean product, enterprise companies lean marketing—but the reasoning behind it usually goes unstated.</p>

<p>Here's how I think about it.</p>

<p>Product marketing is about information transfer. Once you accept that, the org question gets easier.</p>
 <a href="https://kalsey.com/2026/03/where_does_product_marketing_belong/"<Read more &raquo;</a> ( words)
<p>See also: <a href="https://kalsey.com/2002/09/wireless_adoption/">Wireless Adoption</a>, 
<a href="https://kalsey.com/2020/09/how_to_understand_your_product_and_your_market/">How to understand your product and your market</a>, 
<a href="https://kalsey.com/2024/11/building_the_next_big_thing_a_framework_for_your_second_product/">Building the Next Big Thing: A Framework for Your Second Product</a>, 
<a href="https://kalsey.com/2020/09/the_kpi_that_measures_productmarket_fit/">The KPI that measures Product-Market Fit</a>
</p><p>Tagged as: <a href="https://kalsey.com/tag/b2b" rel="tag">b2b</a>&nbsp; <a href="https://kalsey.com/tag/b2c" rel="tag">b2c</a>&nbsp; <a href="https://kalsey.com/tag/organizationdesign" rel="tag">organizationdesign</a>&nbsp; <a href="https://kalsey.com/tag/productmarketing" rel="tag">productmarketing</a>&nbsp; <a href="https://kalsey.com/tag/strategy" rel="tag">strategy</a>&nbsp; </p>]]>
</content>
</entry>
<entry>
<title>The Rise of Vertical Software</title>
<link rel="alternate" type="text/html" href="https://kalsey.com/2026/02/the_rise_of_vertical_software/" />
<id>tag:kalsey.com,2026://2.5101</id>
<published>2026-02-16T04:38:27Z</published>
<updated>2026-02-16T04:48:51Z</updated>
<summary>AI makes execution cheap. Deep industry knowledge becomes the real moat.</summary>
<author><name>Adam Kalsey</name><uri>http://kalsey.com</uri></author>
<category scheme="https://kalsey.com/tag/ai" term="ai"/><category scheme="https://kalsey.com/tag/entrepreneurship" term="entrepreneurship"/><category scheme="https://kalsey.com/tag/productmanagement" term="productmanagement"/><category scheme="https://kalsey.com/tag/strategy" term="strategy"/><category scheme="https://kalsey.com/tag/verticalsoftware" term="verticalsoftware"/>
<category term="Product Management" />

<content type="html" xml:lang="en" xml:base="https://kalsey.com/">
<![CDATA[<p><img src="/blog/2026/02/resized-Niche Software Rise.png" width="950" height="536.47058823529" alt="The Rise of Vertical Software with a man looking at towers of software" /></p>

<p>AI is making output cheap. That's the headline.</p>

<p>Anyone can generate competent code, decent copy, solid designs. The bar for execution gets higher because everyone can reach it. When execution is easy, what you execute on becomes the differentiator.</p>

<p>The value has shifted to inputs. Higher quality input creates higher quality output. Garbage in, garbage out still applies—but now "garbage" means "the same prompt everyone else is using."</p>

<h2>Taste Becomes the Moat</h2>

<p>For building software, the valuable skill is knowing WHAT to build. Making trade-off decisions. Having taste.</p>

<p>If anyone can build anything, the people who know what's worth building win. That's not something AI gives you. That's judgment. Experience. Understanding of a problem space that goes beyond what you can prompt for.</p>

<p>This is why "vibe coding" only gets you so far. You can tell AI to build you an app. But knowing which app to build, what features matter, what trade-offs are acceptable to your users—that requires understanding your users better than AI can.</p>
 <a href="https://kalsey.com/2026/02/the_rise_of_vertical_software/"<Read more &raquo;</a> ( words)
<p>See also: <a href="https://kalsey.com/2020/10/understanding_vision_strategy_and_execution/">Understanding vision, strategy, and execution</a>, 
<a href="https://kalsey.com/2025/07/your_prioritization_problem_is_a_strategy_problem/">Your Prioritization Problem Is a Strategy Problem</a>, 
<a href="https://kalsey.com/2002/01/usability_required/">Usability Required</a>, 
<a href="https://kalsey.com/2002/08/total_experience/">Total Experience</a>
</p><p>Tagged as: <a href="https://kalsey.com/tag/ai" rel="tag">ai</a>&nbsp; <a href="https://kalsey.com/tag/entrepreneurship" rel="tag">entrepreneurship</a>&nbsp; <a href="https://kalsey.com/tag/productmanagement" rel="tag">productmanagement</a>&nbsp; <a href="https://kalsey.com/tag/strategy" rel="tag">strategy</a>&nbsp; <a href="https://kalsey.com/tag/verticalsoftware" rel="tag">verticalsoftware</a>&nbsp; </p>]]>
</content>
</entry>
<entry>
<title>Using Chatbots as a Tutor</title>
<link rel="alternate" type="text/html" href="https://kalsey.com/2026/02/using_chatbots_as_a_tutor/" />
<id>tag:kalsey.com,2026://2.5100</id>
<published>2026-02-12T03:52:18Z</published>
<updated>2026-02-15T05:04:55Z</updated>
<summary>A prompt that turns your LLM chatbot into a custom tutor.</summary>
<author><name>Adam Kalsey</name><uri>http://kalsey.com</uri></author>
<category scheme="https://kalsey.com/tag/ai" term="ai"/><category scheme="https://kalsey.com/tag/chatgpt" term="chatgpt"/><category scheme="https://kalsey.com/tag/claude" term="claude"/><category scheme="https://kalsey.com/tag/learning" term="learning"/><category scheme="https://kalsey.com/tag/llms" term="llms"/>
<category term="Products and Tools" />

<content type="html" xml:lang="en" xml:base="https://kalsey.com/">
<![CDATA[<p>Claude and ChatGPT each have the concept of Projects -- a collection of related chats with an instruction that guides each chat. I've been using this as a way of learning new topics, using an instruction that tells the LLM how to design and deliver lessons to me.</p>

<p>Each day, I open up the chat and ask for the next lesson, and the LLM writes me a custom 10 minute read that adds to my knowledge. So far I've used this to learn a new statistical technique, improve my pasta-making skills, and refresh topics I've read in business books.</p>
 <a href="https://kalsey.com/2026/02/using_chatbots_as_a_tutor/"<Read more &raquo;</a> ( words)
<p>See also: <a href="https://kalsey.com/2025/10/ai_as_your_strategic_thinking_partner/">AI as Your Strategic Thinking Partner</a>, 
<a href="https://kalsey.com/2002/09/email_marketing_usability/">Email Marketing Usability</a>, 
<a href="https://kalsey.com/2002/08/ignoring_customers/">Ignoring customers</a>
</p><p>Tagged as: <a href="https://kalsey.com/tag/ai" rel="tag">ai</a>&nbsp; <a href="https://kalsey.com/tag/chatgpt" rel="tag">chatgpt</a>&nbsp; <a href="https://kalsey.com/tag/claude" rel="tag">claude</a>&nbsp; <a href="https://kalsey.com/tag/learning" rel="tag">learning</a>&nbsp; <a href="https://kalsey.com/tag/llms" rel="tag">llms</a>&nbsp; </p>]]>
</content>
</entry>
<entry>
<title>How to Interview Product Managers</title>
<link rel="alternate" type="text/html" href="https://kalsey.com/2025/11/how_to_interview_product_managers/" />
<id>tag:kalsey.com,2025://2.5099</id>
<published>2025-11-09T21:05:18Z</published>
<updated>2025-11-09T21:58:56Z</updated>
<summary>Most people never learned to interview, so when thrust into hiring a product manager they ask bad questions. Here&apos;s how to ask better ones, with lots of examples of real questions.</summary>
<author><name>Adam Kalsey</name><uri>http://kalsey.com</uri></author>
<category scheme="https://kalsey.com/tag/hiring" term="hiring"/><category scheme="https://kalsey.com/tag/interview" term="interview"/><category scheme="https://kalsey.com/tag/productmanager" term="productmanager"/><category scheme="https://kalsey.com/tag/questions" term="questions"/>
<category term="Product Management" />

<content type="html" xml:lang="en" xml:base="https://kalsey.com/">
<![CDATA[<p><img src="/blog/2025/11/resized-interviewing-product-managers.jpeg" width="950" height="545.6457925636" alt="Two people talking in an office with the headline Interviewing Product Managers" /></p>

<p>Few people are ever trained in interviewing future hires. You're handed someone's resume and tossed into a meeting with the candidate.  The hiring manager might tell you what topics they want you to cover. </p>

<p>So you think back to the questions people asked you and ask versions of those. What are your strengths and weaknesses? Tell me about your greatest accomplishment? How do you prioritize?</p>

<p>But these don't really tell you anything about the candidate. They don't give you great signal about their relative skill in doing the job. What if their greatest accomplishment has nothing to do with building products? And even if it does, what are you going to learn from them describing it?</p>

<p>When you ask them how they do something, you'll get an idealized version of what they <strong>would</strong> do, instead of a realistic description of how they really work. </p>

<p>The best way to improve your questions is to define your intent up front. Identify the traits and skills you're looking for, and think of a way the candidate can demonstrate that skill in an interview. This usually involves asking them to describe real-world situations that used the skill.</p>

<p>For all your questions, write down what you are trying to learn by asking it. Think through what a strong answer would be and how you'd distinguish from a weak answer. </p>

<p>During the interview, probe their answers to find out what they specifically did. Product managers accomplish almost all their work through the team, so it can be hard to get them to say what they actually did. Getting this is crucial.</p>

<p>To get you started, here are some examples of questions I use in actual product management interviews.</p>
 <a href="https://kalsey.com/2025/11/how_to_interview_product_managers/"<Read more &raquo;</a> ( words)
<p>See also: <a href="https://kalsey.com/2020/08/software_engineering_manager_interview_questions/">Software engineering manager interview questions</a>, 
<a href="https://kalsey.com/2020/11/domain_expertise_in_product_management/">Domain expertise in Product Management</a>, 
<a href="https://kalsey.com/2008/03/spring_training_facilities_in_the_off_season/">Spring Training facilities in the off season</a>, 
<a href="https://kalsey.com/2004/06/customer_reference_questions/">Customer reference questions.</a>
</p><p>Tagged as: <a href="https://kalsey.com/tag/hiring" rel="tag">hiring</a>&nbsp; <a href="https://kalsey.com/tag/interview" rel="tag">interview</a>&nbsp; <a href="https://kalsey.com/tag/productmanager" rel="tag">productmanager</a>&nbsp; <a href="https://kalsey.com/tag/questions" rel="tag">questions</a>&nbsp; </p>]]>
</content>
</entry>
<entry>
<title>AI as Your Strategic Thinking Partner</title>
<link rel="alternate" type="text/html" href="https://kalsey.com/2025/10/ai_as_your_strategic_thinking_partner/" />
<id>tag:kalsey.com,2025://2.5098</id>
<published>2025-10-12T19:24:50Z</published>
<updated>2025-10-13T03:15:13Z</updated>
<summary>AI becomes a lens on your own logic. It doesn’t replace your judgment—it sharpens it. By asking questions you wouldn’t think to ask yourself, it turns private reasoning into something visible and testable.</summary>
<author><name>Adam Kalsey</name><uri>http://kalsey.com</uri></author>
<category scheme="https://kalsey.com/tag/ai" term="ai"/><category scheme="https://kalsey.com/tag/assumptions" term="assumptions"/><category scheme="https://kalsey.com/tag/leadership" term="leadership"/><category scheme="https://kalsey.com/tag/productmanagement" term="productmanagement"/><category scheme="https://kalsey.com/tag/strategy" term="strategy"/>
<category term="Product Management" />

<content type="html" xml:lang="en" xml:base="https://kalsey.com/">
<![CDATA[<p>I use AI as a strategic thinking partner. Not to make decisions for me—that would be abdicating leadership. I use it to expose my own assumptions and clarify my thinking.</p>

<h2>The Dialogue Approach</h2>

<p>The process: I frame a business challenge. The AI asks questions and makes assumptions. I clarify what I meant. This back-and-forth exposes assumptions I didn't know I was making.</p>

<p>Last month, I was struggling with a product roadmap decision. I thought I had considered all angles, but through this dialogue, I discovered I was unconsciously prioritizing technical elegance over customer adoption speed. This wasn't a deliberate choice—it was an unexamined assumption the conversation helped surface.</p>
 <a href="https://kalsey.com/2025/10/ai_as_your_strategic_thinking_partner/"<Read more &raquo;</a> ( words)
<p>See also: <a href="https://kalsey.com/2025/07/your_prioritization_problem_is_a_strategy_problem/">Your Prioritization Problem Is a Strategy Problem</a>, 
<a href="https://kalsey.com/2020/10/strategy_means_saying_no/">Strategy Means Saying No</a>, 
<a href="https://kalsey.com/2025/05/ai_is_smart_but_wisdom_requires_judgement_/">AI is Smart, But Wisdom Requires Judgement </a>, 
<a href="https://kalsey.com/2008/05/product_leadership/">Product Leadership</a>
</p><p>Tagged as: <a href="https://kalsey.com/tag/ai" rel="tag">ai</a>&nbsp; <a href="https://kalsey.com/tag/assumptions" rel="tag">assumptions</a>&nbsp; <a href="https://kalsey.com/tag/leadership" rel="tag">leadership</a>&nbsp; <a href="https://kalsey.com/tag/productmanagement" rel="tag">productmanagement</a>&nbsp; <a href="https://kalsey.com/tag/strategy" rel="tag">strategy</a>&nbsp; </p>]]>
</content>
</entry>
<entry>
<title>Your OKR Cascade is Breaking Your Strategy</title>
<link rel="alternate" type="text/html" href="https://kalsey.com/2025/08/your_okr_cascade_is_breaking_your_strategy/" />
<id>tag:kalsey.com,2025://2.5097</id>
<published>2025-08-01T22:41:31Z</published>
<updated>2025-08-01T22:57:54Z</updated>
<summary>Most companies cascade OKRs down their org chart thinking it creates alignment. Instead, it fragments strategy and marginalizes supporting teams. Here&apos;s what works better than the waterfall approach.</summary>
<author><name>Adam Kalsey</name><uri>http://kalsey.com</uri></author>
<category scheme="https://kalsey.com/tag/alignment" term="alignment"/><category scheme="https://kalsey.com/tag/goals" term="goals"/><category scheme="https://kalsey.com/tag/leadership" term="leadership"/><category scheme="https://kalsey.com/tag/management" term="management"/><category scheme="https://kalsey.com/tag/okrs" term="okrs"/><category scheme="https://kalsey.com/tag/strategy" term="strategy"/>
<category term="Management &amp; Leadership" />

<content type="html" xml:lang="en" xml:base="https://kalsey.com/">
<![CDATA[<p>How do you distribute your strategy across your organization? A common approach is some form of "goals flow downhill". A leader tells their direct reports what needs to be done. Those reports each figure out how they’ll contribute to the strategy and create goals for their department or team. Then those department goals get passed down to the next rung of the ladder, and sub-goals are created and further passed down, until everyone knows what they’re working on. <!-- <img src="/blog/2025/08/resized-OKR Cascade Min.png" width="950" height="633.33333333333" alt="Tree with goals falling off it, and the text "Your OKR Cascade is Breaking your Strategy" /> --></p>

<p>The idea is to be able to trace the actions of an organization all the way from the bottom up to the corporate strategy. And to visualize how the strategy cascades into execution throughout the company.</p>

<p>Some OKR guides make this cascade explicit, requiring every one of your KRs to be an Objective for one of your subordinate teams.</p>
 <a href="https://kalsey.com/2025/08/your_okr_cascade_is_breaking_your_strategy/"<Read more &raquo;</a> ( words)
<p>See also: <a href="https://kalsey.com/2023/10/how_i_use_okrs/">How I use OKRs</a>, 
<a href="https://kalsey.com/2025/05/10_okr_traps_and_how_to_avoid_them/">10 OKR traps and how to avoid them</a>, 
<a href="https://kalsey.com/2025/07/your_prioritization_problem_is_a_strategy_problem/">Your Prioritization Problem Is a Strategy Problem</a>, 
<a href="https://kalsey.com/2020/10/strategy_means_saying_no/">Strategy Means Saying No</a>
</p><p>Tagged as: <a href="https://kalsey.com/tag/alignment" rel="tag">alignment</a>&nbsp; <a href="https://kalsey.com/tag/goals" rel="tag">goals</a>&nbsp; <a href="https://kalsey.com/tag/leadership" rel="tag">leadership</a>&nbsp; <a href="https://kalsey.com/tag/management" rel="tag">management</a>&nbsp; <a href="https://kalsey.com/tag/okrs" rel="tag">okrs</a>&nbsp; <a href="https://kalsey.com/tag/strategy" rel="tag">strategy</a>&nbsp; </p>]]>
</content>
</entry>

</feed>