<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Career on Alan Mond&#39;s Blog</title>
    <link>https://alanmond.com/tags/career/</link>
    <description>Recent content in Career on Alan Mond&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://alanmond.com/tags/career/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Death by a Thousand Questions: Working With Problem Admirers</title>
      <link>https://alanmond.com/posts/working-with-problem-admirers/</link>
      <pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate>
      <guid>https://alanmond.com/posts/working-with-problem-admirers/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;A &lt;em&gt;problem admirer&lt;/em&gt; is someone who can describe every reason an idea might fail, but does not feel responsible for helping it succeed.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR.&lt;/strong&gt; Problem admirers often feel like blockers, but brought in early, they can be some of the most valuable reviewers you have. Their objections become your FAQ, rollout plan, and Alternatives Considered section. Ignore them and you ship with avoidable wounds. Listen too much and the project dies in committee. This post is about threading that needle.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
