<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="https://elezea.com/wp-content/themes/elz_2023/styles/pretty-feed-v3.xsl" type="text/xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:wfw="http://wellformedweb.org/CommentAPI/" 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/"
  xmlns:slash="http://purl.org/rss/1.0/modules/slash/" >
  <channel>
    <title>Elezea by Rian van der Merwe - RSS Feed</title>
    <atom:link href="https://elezea.com/2018/08/products-as-functions/feed/" rel="self" type="application/rss+xml" />
    <link>https://elezea.com/2018/08/products-as-functions/</link>
    <description>A personal blog about product, technology, and interesting things that are worth sharing.</description>
    <lastBuildDate>Thu, 02 Apr 2026 17:43:52 +0000</lastBuildDate>
    <language></language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <generator>https://wordpress.org/?v=6.9.4</generator>
          <item>
        <title>Products as functions</title>
        <link>https://elezea.com/2018/08/products-as-functions/</link>
        <pubDate>Wed, 22 Aug 2018 13:14:51 +0000</pubDate>
        <dc:creator>Rian van der Merwe</dc:creator>
        <guid isPermaLink="false">https://elezea.com/?p=6505</guid>
        <description>
          <![CDATA[“Products are easier to reason about when you think of them as functions. They transform an input situation into an output situation.”]]>
        </description>
        <content:encoded>
          <![CDATA[<p>I’ve been really intrigued by Ryan Singer’s thinking around <a href="https://www.feltpresence.com/functions.html">Products as Functions</a>:</p>
<blockquote>
<p>Products are easier to reason about when you think of them as functions. They transform an input situation into an output situation.</p>
<p>This lets you describe what the product does as a transformation of the user&#8217;s circumstance instead of a bundle of features.</p>
</blockquote>
<p>I’ve been using this thinking on a new project we’re working on at <a href="https://postmarkapp.com/">Postmark</a>. I like this approach because it gives us a framework to communicate <em>why</em> something is a good idea to work on, and it focuses on the benefit for customers. If our answer to the question “How much better is this new outcome?” is “Not better enough”, then we need to define a better <em>Output situation</em>, which would lead to a better <em>Process</em>.</p>
          <br>
          <br>
          <hr>
          Thanks for still believing in RSS! Get in touch <a href="https://elezea.com/contact">here</a> if you'd like.]]>
        </content:encoded>
                      </item>
      </channel>
</rss>