Tribar StudioCareers
Back to all tribes

Horizon

R&D. Crazy ideas. No deadlines. No roadmap.

Mission

Horizon builds things nobody requested. Most fail. One changes the company.

Horizon is Tribar's license to explore. No quarterly targets, no stakeholder demos, no "when will this ship?" pressure. They work on problems that are too early for a JIRA ticket. Most Horizon projects go nowhere. The ones that don't redefine what the company does.

Most fail. One changes the company.

Horizon's acceptance of failure as the cost of breakthrough.

What we measure

Intrapersonal

Exploration breadth — is each Horizon explorer generating enough surface area for luck?

How: Projects touched per quarter, external papers read, experiments run, prototypes abandoned (good signal)Where: Horizon personal journal (private), monthly 1:1 with Horizon leadWhen: Monthly check-in; no quantitative targetsSignal: An explorer hasn't started or stopped a project in 3 months — stuck, not deepInstrument: Horizon journal template, 1:1 conversation guide (not a dashboard)
Interpersonal

Cross-pollination — are Horizon's ideas reaching other tribes?

How: Internal talk invites from other tribes, "can you show us that thing?" requests, cross-tribe collaboration requestsWhere: Internal event calendar, Slack DMs, cross-tribe project requestsWhen: Informal — tracked by Horizon lead, reviewed quarterlySignal: No other tribe has requested a Horizon demo or collaboration in 2 monthsInstrument: No formal tool — this is a people-sensing metric, tracked in notes
Collective

Option value — how many strategic options has Horizon created for the company?

How: Number of viable "paths not taken" that Horizon has explored, potential pivots seeded, IP created, acquirable talent relationshipsWhere: Horizon portfolio review (internal, not shared broadly)When: Quarterly portfolio reviewSignal: The company has no explored options in a domain that suddenly becomes criticalInstrument: Horizon portfolio board, options register, IP tracker

Transition success rate — do Horizon projects that graduate actually succeed in production?

How: Of projects handed off to Delta in the last 2 years: how many are still live? How many changed strategy? How many were killed after honest evaluation?Where: Horizon→Delta handoff tracker, post-mortem for killed projectsWhen: Per handoff; reviewed annuallySignal: <30% of graduated projects survive more than 1 year in productionInstrument: Handoff tracker, post-mortem template, annual portfolio review

Innovation culture health — does the rest of the company feel permission to explore?

How: Hack day participation rate, unsolicited R&D ideas submitted by non-Horizon members, "I have an idea" sentiment from engagement surveyWhere: Hack day registration, idea submission platform, engagement surveyWhen: Per hack day; quarterly for surveySignal: Hack day participation <40% of eligible employeesInstrument: Hack day analytics, idea submission tracker, engagement survey innovation module

Rhythms

Show & tell

Every 2 weeks

Horizon demos whatever they're working on — working prototype, failed experiment, interesting paper, weird idea. No polish required.

Radical transparency about what exploration looks like (including failure).

Portfolio review

Quarterly

Horizon reviews every active project. Keep, kill, or incubate? No project survives without showing signal.

Prevents "zombie projects" that no one believes in but no one kills.

Horizon expedition

Yearly

One week. The entire Horizon tribe goes off-site with no agenda. Visit a lab. Attend a conference. Build something ridiculous. Read papers in a cabin.

Deliberate disconnection from company reality to find new signals.

Innovation day

Yearly

Company-wide. No sprint work. Everyone works on anything. Horizon facilitates, judges, and incubates the best ideas.

Democratizes exploration beyond Horizon.

Tools & artifacts

Horizon portfolio board

framework

Visual portfolio of all active Horizon projects. Each project has: hypothesis, signal level, time invested, kill criteria, next decision point.

Horizon

Kill criteria template

document

Every Horizon project starts with explicit kill criteria: "If X hasn't happened by Y date, this project is dead." Removes emotional attachment.

Horizon

Handoff package

document

Standardized handoff template for any project transitioning to Delta: what was learned, what works, what doesn't, what's unknown, recommended next steps.

HorizonDelta

Idea submission platform

platform

Anyone in the company can submit an idea. Horizon reviews monthly. Best ideas get a "Horizon exploration grant" — 2 weeks of Horizon time to validate.

HorizonAll tribes

Tech radar

document

Living document tracking emerging technologies across four categories: adopt, trial, assess, hold. Updated quarterly.

HorizonForgeDelta

Responsibilities

  • Long-term research and exploration
  • Prototype development of unproven ideas
  • Emerging technology evaluation
  • Academic partnerships
  • Patentable inventions
  • "What if?" — full-time
  • Technology scouting and trend analysis
  • Internal incubation of new product concepts

Deliverables

Working prototypes
Research papers and internal talks
Proof-of-concept demos
Strategic recommendations (build / buy / wait / ignore)
Patent filings and IP documentation
Incubation exit packages (handoff to Delta)
Success metric

Not measured in quarters. Have any Horizon projects changed the company's direction in the last 2 years?

Relationships

How Horizon connects to every other tribe — what flows, when, and through what ritual.

Feeds
DeltaPer handoff (quarterly average)

Technology prototypes, feasibility assessments, handoff packages for incubated projects, new tech recommendations

Ritual:Horizon→Delta handoff review
If this breaks: Horizon builds things Delta doesn't know about and can't productize
Shadow risk: Horizon may treat a partner's constraints as lack of courage and use novelty to outrank operational knowledge.
Repair: Restate the partner's constraint as a design input, define a stop condition, and name who carries the experiment's cost.
ForgeMonthly

Emerging technology evaluations, architecture recommendations for future platform investments

Ritual:Tech radar review
If this breaks: Forge doesn't know about technologies that could reshape the platform
Shadow risk: Horizon may treat a partner's constraints as lack of courage and use novelty to outrank operational knowledge.
Repair: Restate the partner's constraint as a design input, define a stop condition, and name who carries the experiment's cost.
AtlasQuarterly

Strategic options — technologies that could create new markets or disrupt existing ones

Ritual:Strategic options review
If this breaks: Atlas doesn't know about technology shifts that could affect market position
Shadow risk: Horizon may treat a partner's constraints as lack of courage and use novelty to outrank operational knowledge.
Repair: Restate the partner's constraint as a design input, define a stop condition, and name who carries the experiment's cost.
ThreadPer project; quarterly archive

Research findings, failed experiment documentation, technology evaluation reports

Ritual:Knowledge harvest
If this breaks: Lessons from Horizon's failures are lost instead of informing future exploration
Shadow risk: Horizon may treat a partner's constraints as lack of courage and use novelty to outrank operational knowledge.
Repair: Restate the partner's constraint as a design input, define a stop condition, and name who carries the experiment's cost.
The tribe under strain

To remain unconstrained, exceptional, and ahead of people focused on ordinary limits.

This is a protective pattern, not a verdict. It describes what can happen when the tribe's gift is driven by fear, anger, grief, scarcity, or status.

What activates it

An idea is evaluated too early, constrained by delivery, or compared with present-day obligations.

How it can appear

Horizon can escape into novelty, become contemptuous of maintenance, destabilize commitments, or chase distinction through originality.

What it costs

Partners carry the practical consequences while Horizon preserves the identity of being visionary and misunderstood.

The integrated gift

Imagination with return paths: exploration that respects constraints and hands learning back to the collective.

Core question

What could exist five years from now?

Information pipeline
1
EchoUnderstand humans
2
AtlasUnderstand markets
3
DeltaBuild solutions
4
ForgeCreate leverage
5
PulseMeasure outcomes
6
OrbitEnsure adoption
7
ThreadPreserve knowledge
8
HorizonExplore the unknown
9
VaultRun the business
Operating modes
Explorer

The core Horizon identity — finds emerging technologies and unproven ideas worth exploring

Builder

Builds prototypes, proofs-of-concept, minimum viable somethings

Optimizer

Sharpens the investment thesis — when a prototype shows promise, optimizes the path to productization

Guardian

Ensures Horizon doesn't become a boondoggle — tracks what was learned, even from failures

Catalyst

Transitions successful prototypes into Delta — creates the bridge from research to production

Visionary

Sets the 5–10 year technical vision — the future that seems impossible today but inevitable tomorrow