<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Growthana — Blog</title>
  <subtitle>Field notes on growth engineering — experiments, systems, and insights.</subtitle>
  <link href="https://growthana.com/feed.xml" rel="self"/>
  <link href="https://growthana.com/blog/"/>
  <updated>2026-09-11T00:00:00Z</updated>
  <id>https://growthana.com/blog/</id>
  <author><name>Growthana</name></author>
  
  <entry>
    <title>Growth engineering, explained</title>
    <link href="https://growthana.com/blog/growth-engineering-explained/"/>
    <updated>2026-09-11T00:00:00Z</updated>
    <id>https://growthana.com/blog/growth-engineering-explained/</id>
    <summary>Most growth work stalls because it&#39;s treated as campaign execution instead of system design. Here&#39;s the distinction we draw, and why it changes what gets built.</summary>
    <content type="html">&lt;p&gt;The teams we work with are usually busy running what already works — the channels that got them here, the campaigns that hit last quarter&#39;s number. That work is necessary and it consumes everyone. What it doesn&#39;t do is answer the question of what comes next.&lt;/p&gt;
&lt;h2&gt;The difference in practice&lt;/h2&gt;
&lt;p&gt;A marketing agency takes a channel and executes against it. More ads, more content, more email. The output is activity, measured in deliverables.&lt;/p&gt;
&lt;p&gt;Growth engineering starts somewhere else — with a hypothesis about where the leverage actually is, and then builds the mechanism that exploits it. The output is a system the company owns.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;If the engagement ends and the growth stops, it wasn&#39;t engineering. It was labor.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2&gt;What an experiment actually requires&lt;/h2&gt;
&lt;p&gt;A growth experiment isn&#39;t &amp;quot;let&#39;s try LinkedIn ads.&amp;quot; It has four parts:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;A hypothesis&lt;/strong&gt; — a specific claim about what will move a specific metric&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A success threshold&lt;/strong&gt; — decided before the test runs, not after&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A kill criterion&lt;/strong&gt; — the condition under which you stop&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A timebox&lt;/strong&gt; — fixed, so the test can&#39;t quietly become a program&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Miss any one of those and you don&#39;t have an experiment. You have an initiative, and initiatives don&#39;t produce learnings — they produce sunk cost.&lt;/p&gt;
&lt;h2&gt;Why this matters for what we build&lt;/h2&gt;
&lt;p&gt;Framing the work as engineering changes what you&#39;re willing to ship. You stop optimizing the funnel by a few percent and start asking which mechanism doesn&#39;t exist yet.&lt;/p&gt;
&lt;p&gt;That&#39;s a harder question. It&#39;s also the only one whose answer compounds.&lt;/p&gt;
</content>
  </entry>
  
</feed>
