MMarketing Against The Grain
← All frameworks
InnovationBrian Balfour

Second- and Third-Layer Validation

Test the company-specific incentives that appear only beneath a proven idea.

Difficulty
Advanced
Time to result
~weeks to results
Steps
5
Confidence
95%

Treat external success as evidence that a mechanism can work, not proof that it will transfer unchanged. First identify why the strategy succeeded in the reference company. Then examine second- and third-layer differences in product behavior, customer incentives, privacy, status, workflow, and value exchange. Build a test that exposes those differences rather than merely reproducing the visible feature. Zapier’s user-generated workflow idea looked analogous to sharing templates in Miro or Notion, but many Zapier users regarded workflows as proprietary secret sauce and had an incentive not to share. Deeper validation should seek both invalidating nuances and small adjustments that could align the mechanism with the new context.

Origin

Kieran Flanagan and Brian Balfour developed this rule from Zapier’s unsuccessful attempt to adapt a proven user-generated template loop.

Core principles

  • 01A strategy proven elsewhere remains uncertain in a new company.
  • 02Surface analogies hide product-specific incentives and constraints.
  • 03The first implementation rarely provides a complete signal.
  • 04Deeper customer research can reveal invalidating or unlocking nuances.
  • 05Evidence from another company is a prior, not a guarantee.

How to run it

  1. 1

    Model the reference mechanism

    Explain why the strategy worked in the external company, including the customer incentive and distribution loop.

    Pro tip Focus on causal behavior rather than copying visible features.

    Watch out A similar interface does not imply a similar incentive structure.

  2. 2

    Map contextual differences

    List differences in product use, customer motivation, privacy, status, ownership, and competitive sensitivity.

    Pro tip Prioritize differences that could reverse the user’s incentive to participate.

    Watch out Do not dismiss company-specific nuances as edge cases before testing them.

  3. 3

    Collect customer evidence

    Ask target users what they would do, why they would do it, and what would stop them.

    Pro tip Probe actual past sharing behavior rather than relying only on hypothetical answers.

    Watch out Internal enthusiasm can mask a missing customer incentive.

  4. 4

    Run a mechanism test

    Build the smallest experiment that tests participation and value exchange, not just technical feasibility.

    Pro tip Measure where the loop breaks and ask participants why.

    Watch out A shallow implementation may generate an ambiguous false negative.

  5. 5

    Explore deeper layers

    Investigate whether a nuance invalidates the strategy or whether a specific adjustment makes the pieces fit.

    Pro tip Test permission controls, anonymization, rewards, or narrower use cases when they address the discovered barrier.

    Watch out Do not continue iterating after evidence shows the core incentives fundamentally conflict.

In the wild

Zapier’s workflow-sharing experiment

Zapier explored allowing users to share workflows that would automatically become searchable templates, following patterns associated with products such as Miro and Notion. The analogy appeared strong, but many Zapier customers treated their workflows as competitive secret sauce and therefore had a reason not to share them publicly.

A company-specific customer incentive weakened an otherwise proven user-generated growth mechanism.

Common mistakes

Copying the visible feature

The visible interface may be incidental while the real growth mechanism depends on hidden incentives.

Treating market precedent as certainty

Evidence from other companies lowers uncertainty but does not resolve product-specific risk.

Stopping after the first layer

An initial test may not reveal the nuance that either invalidates or unlocks the mechanism.

Is it for you?

Best for

Companies adapting a known tactic, channel, or product loop from another business.

Not ideal for

Simple operational practices whose mechanism does not depend materially on customer behavior or product context.

From the transcript

there's just some inherent risk built up because it's hard to capture like all the things when you're starting to rule that out.

Kieran Flanagan · 41:00

That's what I kind of mean by the second and third layer.

Brian Balfour · 41:00

you get to the nuance, the tweak that just like puts the pieces into this perfectly locked puzzle and it ends up unlocking something.

Brian Balfour · 41:00

From the episode

Brian Balfour Reveals How To Build An A+ Marketing Team From Scratch (#183)

Brian Balfour