The Organ-Rejection Test for Innovation Teams
Three conditions that stop the core org from rejecting your new-bets team like a foreign body.
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 4
- Confidence
- 85%
New R&D or incubation teams inside established companies usually fail culturally before they fail technically: the rest of the organization sees them as a foreign body consuming scarce resources on work unrelated to the mission, and rejects them. Adriel Frederick, running Reddit's new-product incubation group after years on growth and marketplace teams, names three conditions that must all hold for the graft to take.
Origin
Adriel Frederick's framework, formed from the opposite vantage point — years on Facebook growth and Lyft marketplace teams watching (and resenting) R&D groups — then applied when he took over Reddit's new-products incubation team.
Core principles
- 01Organ rejection is the default failure mode of an innovation team, not an edge case.
- 02Every internal team is competing for resources; a team seen as playing in a corner is a target.
- 03Legitimacy comes from perceived mission-criticality, shared upside, and preserved innovation rights elsewhere.
- 04The goal state is 'you are one of us,' not 'go behave in your corner.'
How to run it
- 1
Anchor the team's work to the core mission
The rest of the company must see what you're doing as core and critical to the mission, not adjacent play. If the work looks unrelated to what everyone does every day, resentment builds and the team becomes a resource target.
Pro tip Test it by asking a core-team engineer to explain, in one sentence, why your team's work matters to the mission. If they can't, you've failed this condition.
Watch out Framing your team as 'the future' while others do 'the boring present' actively invites rejection.
- 2
Make the win everyone's win
Structure the work so that when the innovation team succeeds, the whole organization feels it won — not just the R&D team. Shared upside converts spectators into supporters.
- 3
Preserve innovation rights across the rest of the org
Set up the work so nobody believes all innovation now happens on your team. Other teams must still get to innovate; your team's remit is specifically what the org needs but no other team has capacity to take on.
Pro tip Scope your team's charter as capacity-relief, not creativity-monopoly: 'the thing the org needs that nobody else can staff.'
Watch out The killer resentment is 'we're stuck with the operational stuff and they get all the fun.' If that sentence is being said, this condition has failed.
- 4
Check for the hug
The success criterion is cultural: everyone wants to hug the team — 'you are one of us.' If the org's posture is 'go off in your little corner and behave,' you have a rejection in progress and must return to steps 1-3.
In the wild
Frederick's Reddit X team shipped a creator avatar marketplace where artists make art, list it for sale, and other users buy and use it. NFTs were chosen as the underlying technology specifically because they give a creator a public way of acknowledging their rights to a piece of content — real IP protection in a market for digital art — rather than as a trend play.
→ The product performed strongly, and the choice of technology was defensible on mission grounds (creator rights) rather than novelty grounds, which is exactly what step 1 demands.
Frederick's own history is on growth and marketplace teams — 'as far as you get from the new stuff team.' From there he repeatedly watched R&D groups get rejected: teams fighting for resources look at the innovation group as having headcount they can't get, and conclude 'we've got to get rid of that because they're not helping us do what we are here to do.'
→ That firsthand resentment became the diagnostic — he now designs innovation teams explicitly against the failure mode he used to feel.
Common mistakes
Positioning the team as separate and special
If the work looks different from the rest of the body, the organization rejects the ideas entirely. Separateness reads as illegitimacy, not focus.
Letting the innovation team be the only place innovation happens
Concentrating creative license in one team leaves everyone else feeling stuck with the operational grind, guaranteeing the political knives come out at the next resource cycle.
Winning alone
If the R&D team's success does not register as everyone's success, each win increases isolation rather than reducing it.
Is it for you?
Best for
Leaders standing up an incubation, R&D, or new-bets team inside an established company with entrenched core product orgs.
Not ideal for
Startups where the whole company is the innovation team, or fully autonomous spun-out units with separate P&Ls and no shared resource pool.
From the transcript
“what I've seen happen a lot is organ rejection”
“the rest of the company needs to see what you're doing as being core and critical to the mission”
“it has to be everyone's success”
“you have to set up the work that these teams are doing such that people don't believe all Innovation is gonna happen on that team”
“make sure that we are part of the organization and everyone wants to hug us”
From the episode
Humanizing product development
Adriel Frederick (Reddit, Lyft, Facebook)