Installing a Decision
System That Scales
How a lightweight strategy-to-execution system replaced intuition-driven chaos and delivered sustained growth.
Why this story exists
To show how ReThread partners help organizations replace intuition-driven chaos with a repeatable system for making better decisions without bureaucracy.
The Problem
Fitbod was growing, but product decisions were largely founder-led, loosely measured, and difficult to scale. Teams were shipping, but there was no shared system for deciding what mattered most, why, or how success was defined.
The Intervention
I designed and installed a lightweight strategy-to-execution system that connected company goals → measurable outcomes → solvable user problems → coordinated initiatives → shipped work.
The Result
Clear priorities, faster learning, stronger alignment, and sustained growth—without slowing the organization down.
This is the same problem most small businesses face too many ideas, no shared priorities, and decisions driven by urgency instead of evidence. The system below shows how to fix that without adding overhead.
The Reality on Arrival
When I joined Fitbod:
Most SMBs don't lack ideas or effort. They lack a way to turn goals into clear, shared decisions. That's what this work addresses.
How do you scale decision-making without slowing execution or alienating the people already doing the work?
Fitbod didn't need "more features."
It needed a system that could repeatedly answer:
What We Built: The Strategy-to-Execution System
This work unfolded in four connected layers. Each layer solved a specific failure mode common in growing organizations.
Driver Tree → OKR Hierarchy
Decision Clarity
What we built
A driver tree that connected:
This created a visible, measurable hierarchy that made tradeoffs explicit and prevented "random roadmap" decisions.
Why it mattered
- Reduced debate driven by opinion or seniority
- Made priorities legible across the organization
- Created a shared language for why work existed
If your roadmap changes every time someone has a new idea, you don't need better ideas, you need a hierarchy that forces tradeoffs.
Problem Statement Breakdown
Making Strategy Solvable
High-level goals are useless if teams can't act on them. To bridge that gap, I introduced a standardized problem statement breakdown used across planning cycles.
Each breakdown captured:
This converted abstract OKRs into concrete, solvable problems.
"We need more customers" becomes: Where do people drop off? Why? What would change their behavior first?
The OKR Roadshow
Inclusion Without Chaos
Instead of open-ended brainstorming or top-down mandates, I ran structured planning sessions—internally referred to as the OKR Roadshow.
How it worked
- Each session was anchored on a specific OKR and problem statement
- Teams contributed ideas within defined constraints
- Ideas were captured asynchronously and transparently
- No "blank whiteboard" sessions
This allowed broad participation without diluting focus.
You can involve your team without losing control if you constrain the problem first.
Synthesis → Themes → Roadmap
Where Strategy Survives Reality
Raw ideas are not a roadmap.
After ideation, ideas were:
- Clustered into themes
- Evaluated against OKRs and constraints
- Prioritized into investable initiatives
Only then were they translated into backlog items and sprint plans.
This step prevented:
- Roadmap bloat
- Feature creep
- Shipping disconnected work
Most planning fails after brainstorming. This is the step that turns ideas into decisions.
Keeping It Lightweight
To ensure the system stayed real (not theoretical), we paired it with a simple operating cadence:
Plan & Refine
Regular planning and refinement cycles
Commit
Clear commitment gates (lock → ship → learn)
Measure
Measurement tied directly to the OKR hierarchy
Iterate
Continuous iteration every ~6 months
You don't need weekly strategy meetings, just a repeatable rhythm for deciding, shipping, and learning.
Examples of How the System Played Out
Onboarding & Early Lifecycle Improvements
- Goal: reduce early disengagement by making value obvious quickly
- Approach: focused on personalization, progressive disclosure, and early wins
- Measured by: engagement and completion signals, not UI complexity
Android Parity & Wear OS Launch
- Goal: restore trust by delivering equivalent value across platforms
- Approach: addressed long-standing parity gaps
- Outcome: led development of a Wear OS app, featured at Google I/O (2021)
Research & Data as a Capability
- Established: research and measurement as inputs to decisions—not obstacles
- Result: reduced experiment cycle time by ~30%
- Impact: improved confidence in prioritization and sequencing
This is the same discipline that helps SMBs decide whether to invest in retention, acquisition, pricing, or operations next.
The Results
What I'd Do Differently
I would separate internal analytics needs from user-facing UI even more aggressively. Metrics belong in decision systems; they don't automatically belong in the product interface.
I would formalize engagement definitions earlier to prevent teams optimizing different interpretations of the same metric.
Not every number needs to be shown to customers. Decide first what drives behavior.
This story isn't about Fitbod.
It's about installing a decision system that:
- scales with the business
- replaces guesswork with clarity
- aligns people without micromanagement
- survives real-world constraints
That's the experience ReThread brings to small and growing businesses.
If your business feels busy but unfocused
if priorities shift weekly
if decisions rely on instinct more than evidence
This is the intervention: