<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Product-Decisions on Brian Faust</title><link>https://vacua.dev/tags/product-decisions/</link><description>Recent content in Product-Decisions on Brian Faust</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://vacua.dev/tags/product-decisions/rss.xml" rel="self" type="application/rss+xml"/><item><title>A Characterization Test Is Not a Product Decision</title><link>https://vacua.dev/thoughts/a-characterization-test-is-not-a-product-decision/</link><pubDate>Fri, 01 Mar 2019 00:00:00 +0000</pubDate><guid>https://vacua.dev/thoughts/a-characterization-test-is-not-a-product-decision/</guid><description>&lt;p&gt;A label setting behaved differently in test and production. Some customers
had come to depend on the difference even though the product already let them
choose the label size they wanted.&lt;/p&gt;
&lt;p&gt;A characterization test could record both defaults. It could tell us which
callers would notice if we made them equal. It could not answer the important
question: should the difference survive?&lt;/p&gt;
&lt;p&gt;Keeping it would protect customers who had never configured the setting.
Removing it would give every environment one rule and make the customer&amp;rsquo;s
choice explicit. The same observation supported arguments for either response.
Only one response matched the product we wanted to operate.&lt;/p&gt;</description></item></channel></rss>