<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:media="http://search.yahoo.com/mrss/"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments for Tyner Blain	</title>
	<atom:link href="https://tynerblain.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>https://tynerblain.com</link>
	<description>Software product success.</description>
	<lastBuildDate>Thu, 23 Apr 2026 13:18:02 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		Comment on Epic Problem Statement by Problem Statement		</title>
		<link>https://tynerblain.com/2020/07/03/epic-problem-statement/#comment-1473692</link>

		<dc:creator><![CDATA[Problem Statement]]></dc:creator>
		<pubDate>Thu, 23 Apr 2026 13:18:02 +0000</pubDate>
		<guid isPermaLink="false">http://wptynerblain.wpenginepowered.com/?p=2066#comment-1473692</guid>

					<description><![CDATA[[&#8230;] is Scott Sehlhorst’s take on the problem statement along with a description of how he views backlog hierarchy (Epic -&#062; Feature -&#062; User Story) He [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] is Scott Sehlhorst’s take on the problem statement along with a description of how he views backlog hierarchy (Epic -&gt; Feature -&gt; User Story) He [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Goldilocks and the Three Products by Featuritis vs. the Happy User Peak &#8211; My WordPress Site		</title>
		<link>https://tynerblain.com/2006/04/14/goldilocks-and-the-three-products/#comment-1470157</link>

		<dc:creator><![CDATA[Featuritis vs. the Happy User Peak &#8211; My WordPress Site]]></dc:creator>
		<pubDate>Mon, 01 Dec 2025 21:15:15 +0000</pubDate>
		<guid isPermaLink="false">http://wptynerblain.wpenginepowered.com/2006/04/14/goldilocks-and-the-three-products/#comment-1470157</guid>

					<description><![CDATA[[&#8230;] by: Scott Sehlhorst &#124; Apr 15, 2006 10:05:22 AM      ?Stop your presentation before it kills again! Your turn: [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] by: Scott Sehlhorst | Apr 15, 2006 10:05:22 AM      ?Stop your presentation before it kills again! Your turn: [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on How To Deal With Untestable Requirements &#8211; Rewrite Them by David Grund		</title>
		<link>https://tynerblain.com/2005/11/30/how-to-deal-with-untestable-requirements-rewrite-them/#comment-1466977</link>

		<dc:creator><![CDATA[David Grund]]></dc:creator>
		<pubDate>Fri, 19 Sep 2025 15:17:34 +0000</pubDate>
		<guid isPermaLink="false">http://wptynerblain.wpenginepowered.com/2005/11/30/how-to-deal-with-untestable-requirements-rewrite-them/#comment-1466977</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://tynerblain.com/2005/11/30/how-to-deal-with-untestable-requirements-rewrite-them/#comment-8&quot;&gt;Scott Sehlhorst&lt;/a&gt;.

Scott and Roger,

To me another part of this discussion comes back to confusion or disagreement on the definition of Stakeholder Needs(Goals) vs Requirements and Validation vs Verification.

Re-writing as a two needs: (I like to make sure not just to write the need in a simple form but then add the why.
[Business Need: We need to achieve a 20% profit margin.
Why: In order to make our time investment valuable compared to other opportunities.]

[Customer Need: The car needs to last seven years without repairs as long as the owner maintains the car according to a certain maintenance schedule and doesn&#039;t have an accident. 
Why: Our previous research has shown that consumers will pay more for a car with a higher useful lifetime. Our research has also shown that our part cost vs reliability spike once the failure rate equivalent to a design lifetime of 7 years is exceeded. This will let be achieve a 20% profit margin because we can charge X without excess cost.]

[Requirement: The results of running the lifetime-quality-test 2025 Ver3 for sedans on the vehicle design will predict fewer than 1% of cars will have a warranty repair during their first 7 years of usage, with a 90% confidence level. 
Observation: The lifetime-quality-test is a version controlled document the describes the procedure for how components are tested.]

Writing the requirement is coming to an agreement in the present day on how we will define a way we can measure to say a design is complete. Its making sure we have an agreed stopping point in the design.
On defining what success means in the present.

We then execute the design and verify the design meets the requirement in order to tell the engineers to stop working.

Then in 7 years we validate whether the design met the assumed customer need of operating for 7 years and if meeting that Customer Need led to the Business need being met.
Validation is where we do the big lesson learning. This is where we know take time to think and make judgements about the inference processes and estimates we made in the design and whether they conformed to reality or not and therefore if we need to change or update them.
It&#039;s also the time where we should check if meeting the assumed customer need led to acheiving the overarching outcome of higher profitability. If not we should question the assumptions that lead us to define the Customer Need the way we did.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://tynerblain.com/2005/11/30/how-to-deal-with-untestable-requirements-rewrite-them/#comment-8">Scott Sehlhorst</a>.</p>
<p>Scott and Roger,</p>
<p>To me another part of this discussion comes back to confusion or disagreement on the definition of Stakeholder Needs(Goals) vs Requirements and Validation vs Verification.</p>
<p>Re-writing as a two needs: (I like to make sure not just to write the need in a simple form but then add the why.<br />
[Business Need: We need to achieve a 20% profit margin.<br />
Why: In order to make our time investment valuable compared to other opportunities.]</p>
<p>[Customer Need: The car needs to last seven years without repairs as long as the owner maintains the car according to a certain maintenance schedule and doesn&#8217;t have an accident.<br />
Why: Our previous research has shown that consumers will pay more for a car with a higher useful lifetime. Our research has also shown that our part cost vs reliability spike once the failure rate equivalent to a design lifetime of 7 years is exceeded. This will let be achieve a 20% profit margin because we can charge X without excess cost.]</p>
<p>[Requirement: The results of running the lifetime-quality-test 2025 Ver3 for sedans on the vehicle design will predict fewer than 1% of cars will have a warranty repair during their first 7 years of usage, with a 90% confidence level.<br />
Observation: The lifetime-quality-test is a version controlled document the describes the procedure for how components are tested.]</p>
<p>Writing the requirement is coming to an agreement in the present day on how we will define a way we can measure to say a design is complete. Its making sure we have an agreed stopping point in the design.<br />
On defining what success means in the present.</p>
<p>We then execute the design and verify the design meets the requirement in order to tell the engineers to stop working.</p>
<p>Then in 7 years we validate whether the design met the assumed customer need of operating for 7 years and if meeting that Customer Need led to the Business need being met.<br />
Validation is where we do the big lesson learning. This is where we know take time to think and make judgements about the inference processes and estimates we made in the design and whether they conformed to reality or not and therefore if we need to change or update them.<br />
It&#8217;s also the time where we should check if meeting the assumed customer need led to acheiving the overarching outcome of higher profitability. If not we should question the assumptions that lead us to define the Customer Need the way we did.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Top ten tips for preventing innovation by How to Prevent Innovation &#124;		</title>
		<link>https://tynerblain.com/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-1465685</link>

		<dc:creator><![CDATA[How to Prevent Innovation &#124;]]></dc:creator>
		<pubDate>Tue, 26 Aug 2025 19:55:52 +0000</pubDate>
		<guid isPermaLink="false">http://wptynerblain.wpenginepowered.com/2006/03/06/top-ten-tips-for-preventing-innovation/#comment-1465685</guid>

					<description><![CDATA[[&#8230;] Top ten tips for preventing innovation give some great ideas many companies are already doing but you may find some your company hasn&#8217;t mastered ???? For example: [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Top ten tips for preventing innovation give some great ideas many companies are already doing but you may find some your company hasn&#8217;t mastered ???? For example: [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Reaching Consensus on How by Food for Agile Thought #495: State of Enterprise AI 2025, Reinventing Yourself, GenAI-Enabled Feature Factory, Good Enough Agile’s End &#8211; Royal Consultants, A Royal Property Consultants LLC Business		</title>
		<link>https://tynerblain.com/2025/05/26/reaching-consensus-on-how/#comment-1461637</link>

		<dc:creator><![CDATA[Food for Agile Thought #495: State of Enterprise AI 2025, Reinventing Yourself, GenAI-Enabled Feature Factory, Good Enough Agile’s End &#8211; Royal Consultants, A Royal Property Consultants LLC Business]]></dc:creator>
		<pubDate>Fri, 30 May 2025 12:50:53 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2535#comment-1461637</guid>

					<description><![CDATA[[&#8230;] Source: Reaching Consensus on How [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Source: Reaching Consensus on How [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on The Secret of Diminishing Returns by Food for Agile Thought #490: Escaping the Feature Factory, Funding Agility, Prioritization Comparison, AI PM Course: RAG, PRD, Agents &#8211; Royal Consultants, A Royal Property Consultants LLC Business		</title>
		<link>https://tynerblain.com/2025/04/20/the-secret-of-diminishing-returns/#comment-1460808</link>

		<dc:creator><![CDATA[Food for Agile Thought #490: Escaping the Feature Factory, Funding Agility, Prioritization Comparison, AI PM Course: RAG, PRD, Agents &#8211; Royal Consultants, A Royal Property Consultants LLC Business]]></dc:creator>
		<pubDate>Fri, 25 Apr 2025 13:50:01 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2531#comment-1460808</guid>

					<description><![CDATA[[&#8230;] Source: The Secret of Diminishing Returns [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Source: The Secret of Diminishing Returns [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Problems in the Solution by Food for Agile Thought #483: Leadership Blindspots, Tyranny of Incrementalism, AI Prototyping &#38; User Research, Who Does Strategy? &#8211; Royal Consultants, A Royal Property Consultants LLC Business		</title>
		<link>https://tynerblain.com/2025/03/02/problems-in-the-solution/#comment-1460026</link>

		<dc:creator><![CDATA[Food for Agile Thought #483: Leadership Blindspots, Tyranny of Incrementalism, AI Prototyping &#38; User Research, Who Does Strategy? &#8211; Royal Consultants, A Royal Property Consultants LLC Business]]></dc:creator>
		<pubDate>Fri, 07 Mar 2025 10:55:19 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2510#comment-1460026</guid>

					<description><![CDATA[[&#8230;] Source: Problems in the Solution [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Source: Problems in the Solution [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Problems in the Solution by Ross Beurmann		</title>
		<link>https://tynerblain.com/2025/03/02/problems-in-the-solution/#comment-1459981</link>

		<dc:creator><![CDATA[Ross Beurmann]]></dc:creator>
		<pubDate>Mon, 03 Mar 2025 16:14:21 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2510#comment-1459981</guid>

					<description><![CDATA[Very good read!  I think a lot of company&#039;s believe that customer acquisition through M&#038;A should be seamless, but integration is tough not just from a solution perspective, and I think it gets over simplified in the calculus during the due diligence efforts.  If the due diligence could be more open and not firewalled from the team that will inherit the new solution and team, it may be better, but that is not ideal if the deal falls through.]]></description>
			<content:encoded><![CDATA[<p>Very good read!  I think a lot of company&#8217;s believe that customer acquisition through M&amp;A should be seamless, but integration is tough not just from a solution perspective, and I think it gets over simplified in the calculus during the due diligence efforts.  If the due diligence could be more open and not firewalled from the team that will inherit the new solution and team, it may be better, but that is not ideal if the deal falls through.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on The Wrong Measure Will Misdirect You by Crafting Effective Need Statements: A Comprehensive Guide - OpenGrants		</title>
		<link>https://tynerblain.com/2023/11/01/the-wrong-measure-will-misdirect-you/#comment-1458257</link>

		<dc:creator><![CDATA[Crafting Effective Need Statements: A Comprehensive Guide - OpenGrants]]></dc:creator>
		<pubDate>Sat, 14 Sep 2024 01:40:34 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2456#comment-1458257</guid>

					<description><![CDATA[[&#8230;] need statement should reflect real-world challenges. Citing recent studies can be powerful; for instance, a survey found that employees use an average [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] need statement should reflect real-world challenges. Citing recent studies can be powerful; for instance, a survey found that employees use an average [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Goal-Driven Documentation by Khushi		</title>
		<link>https://tynerblain.com/2006/10/09/goal-driven-documentation/#comment-1458128</link>

		<dc:creator><![CDATA[Khushi]]></dc:creator>
		<pubDate>Sat, 31 Aug 2024 23:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://wptynerblain.wpenginepowered.com/2006/10/09/goal-driven-documentation/#comment-1458128</guid>

					<description><![CDATA[Great post! However, I wonder if this is suitable for users who are beginners. We are assuming prerequisite knowledge of the tool here. They&#039;d want to understand the tool, right? I do agree that getting the job done is a priority is for most of the users. But how about the users who don&#039;t know anything about the tool? We could introduce the feature first and then add some use cases.]]></description>
			<content:encoded><![CDATA[<p>Great post! However, I wonder if this is suitable for users who are beginners. We are assuming prerequisite knowledge of the tool here. They&#8217;d want to understand the tool, right? I do agree that getting the job done is a priority is for most of the users. But how about the users who don&#8217;t know anything about the tool? We could introduce the feature first and then add some use cases.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Uselessly Wide Estimation Ranges by Problem Statement		</title>
		<link>https://tynerblain.com/2023/10/23/uselessly-wide-estimation-ranges/#comment-1456373</link>

		<dc:creator><![CDATA[Problem Statement]]></dc:creator>
		<pubDate>Fri, 01 Mar 2024 01:00:42 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2449#comment-1456373</guid>

					<description><![CDATA[[&#8230;] the problem statement – and the power of quantification – to identify when there is value in learning before making a [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] the problem statement – and the power of quantification – to identify when there is value in learning before making a [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Probabilistic Thinking in Problem Statements by Problem Statement		</title>
		<link>https://tynerblain.com/2023/10/18/probabilistic-thinking-in-problem-statements/#comment-1456372</link>

		<dc:creator><![CDATA[Problem Statement]]></dc:creator>
		<pubDate>Fri, 01 Mar 2024 01:00:13 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2444#comment-1456372</guid>

					<description><![CDATA[[&#8230;] you quantify the impact, express it in a range so that you recognize the uncertain nature of [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] you quantify the impact, express it in a range so that you recognize the uncertain nature of [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Problem Statement Impact and Assumptions by Problem Statement		</title>
		<link>https://tynerblain.com/2023/10/11/problem-statement-impact-and-assumptions/#comment-1455455</link>

		<dc:creator><![CDATA[Problem Statement]]></dc:creator>
		<pubDate>Wed, 25 Oct 2023 13:53:59 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2437#comment-1455455</guid>

					<description><![CDATA[[&#8230;] Quantifying the impact of your problems puts them in perspective. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Quantifying the impact of your problems puts them in perspective. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Biasing with Problem Statements by Problem Statement		</title>
		<link>https://tynerblain.com/2023/10/03/biasing-with-problem-statements/#comment-1455450</link>

		<dc:creator><![CDATA[Problem Statement]]></dc:creator>
		<pubDate>Tue, 24 Oct 2023 12:25:45 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2433#comment-1455450</guid>

					<description><![CDATA[[&#8230;] A good problem statement is from the perspective of your customers. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] A good problem statement is from the perspective of your customers. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Problem Statements Solve for SomeWhen by Problem Statement		</title>
		<link>https://tynerblain.com/2023/09/25/problem-statements-solve-for-somewhen/#comment-1455178</link>

		<dc:creator><![CDATA[Problem Statement]]></dc:creator>
		<pubDate>Tue, 26 Sep 2023 12:12:42 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2427#comment-1455178</guid>

					<description><![CDATA[[&#8230;] A good problem statement also drives a discussion about the context in which people experience the problem. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] A good problem statement also drives a discussion about the context in which people experience the problem. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on A Better Problem Statement Template by Problem Statement		</title>
		<link>https://tynerblain.com/2023/08/17/a-better-problem-statement-template/#comment-1455113</link>

		<dc:creator><![CDATA[Problem Statement]]></dc:creator>
		<pubDate>Tue, 19 Sep 2023 13:48:03 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2374#comment-1455113</guid>

					<description><![CDATA[[&#8230;] followed up his series of posts on problem statement with an article describing his favorite formulation for Problem Statements. Turns out it&#8217;s roughly the structure described [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] followed up his series of posts on problem statement with an article describing his favorite formulation for Problem Statements. Turns out it&#8217;s roughly the structure described [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Problem Statements Solve for Someone by Problem Statement		</title>
		<link>https://tynerblain.com/2023/09/18/problem-statements-solve-for-someone/#comment-1455111</link>

		<dc:creator><![CDATA[Problem Statement]]></dc:creator>
		<pubDate>Tue, 19 Sep 2023 13:27:41 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2420#comment-1455111</guid>

					<description><![CDATA[[&#8230;] Once you start reshaping into a description of a problem, a good problem statement template nudges you towards more in-depth discussion of who is affected. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Once you start reshaping into a description of a problem, a good problem statement template nudges you towards more in-depth discussion of who is affected. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Problem Statements Provide Purpose by Problem Statement		</title>
		<link>https://tynerblain.com/2023/08/10/problem-statements-provide-purpose/#comment-1455110</link>

		<dc:creator><![CDATA[Problem Statement]]></dc:creator>
		<pubDate>Tue, 19 Sep 2023 13:25:40 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2368#comment-1455110</guid>

					<description><![CDATA[[&#8230;] To reduce the confusion, delays, and waste teams face as a result of not knowing why something is being asked for and not knowing what good enough looks like. (Problem Statements Provide Purpose) [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] To reduce the confusion, delays, and waste teams face as a result of not knowing why something is being asked for and not knowing what good enough looks like. (Problem Statements Provide Purpose) [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on A Better Problem Statement Template by Scott Sehlhorst		</title>
		<link>https://tynerblain.com/2023/08/17/a-better-problem-statement-template/#comment-1455028</link>

		<dc:creator><![CDATA[Scott Sehlhorst]]></dc:creator>
		<pubDate>Thu, 07 Sep 2023 15:50:31 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2374#comment-1455028</guid>

					<description><![CDATA[Yes, I love what you&#039;ve pulled together on problem statements, Kent.  Thanks!]]></description>
			<content:encoded><![CDATA[<p>Yes, I love what you&#8217;ve pulled together on problem statements, Kent.  Thanks!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Problem Statements Shape Better Products by Problem Statement		</title>
		<link>https://tynerblain.com/2023/07/31/problem-statements-shape-better-products/#comment-1454561</link>

		<dc:creator><![CDATA[Problem Statement]]></dc:creator>
		<pubDate>Thu, 17 Aug 2023 16:54:54 +0000</pubDate>
		<guid isPermaLink="false">https://wptynerblain.wpenginepowered.com/?p=2351#comment-1454561</guid>

					<description><![CDATA[[&#8230;] To empower product leaders to shape their product strategy through choosing what to do and choosing what not to do. (Problem Statements Shape Better Products) [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] To empower product leaders to shape their product strategy through choosing what to do and choosing what not to do. (Problem Statements Shape Better Products) [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
