Context Over Control: Debate Upstream of the Solution
Empower teams by aligning on goal, hypothesis, and data—never by prescribing the solution.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 92%
Ramp's radical empowerment works because leaders refuse to debate solutions. Instead they align teams upstream—on the goal, the hypothesis, the data behind the hypothesis, and the metrics—then let the people closest to the ground pick the solution. The leader's real job becomes 'repeater in chief': continuously feeding teams the context they're missing.
Origin
Geoff Charles at Ramp, contrasting his earlier micromanaging instincts with the hands-off style of Ramp's CTO Kareem, who was 'extremely hands-off' on product decisions because the team was tightly aligned on goals.
Core principles
- 01Solutions come better from teams closest to the ground once they share the leader's context
- 02Junior leaders fixate on solutions; the real disagreements live upstream in data interpretation, hypotheses, and goals
- 03A leader's leverage is repeating context, not making decisions—'I spend most of my time just repeating myself'
- 04The contract with a team is their strategy and roadmap, not their day-to-day choices
How to run it
- 1
Align on the goal first
Establish what you want to see in the world before anything else. Most misalignment traced back to skipping this and jumping to solutions.
Watch out Being prescriptive about the solution without aligning on the goal upstream is exactly when things went wrong at Ramp.
- 2
Agree on the hypothesis and its data
State why you believe reaching the goal will work, and the data the hypothesis rests on. Debate the interpretation of the data, not the feature.
Pro tip When a team pushes a solution you doubt, move the conversation up a level—question the hypothesis or the data, not the design.
- 3
Hand the solution to the team
With goal, hypothesis, and metrics shared, let the team closest to the customer design the solution. Their proximity produces better answers than yours.
- 4
Run as repeater-in-chief
Spend your time surfacing context the team can't see because they aren't in the rooms you're in, and represent them in those rooms. Publish goals weekly, have directs review each other's, and reserve 1:1s for what the team needs from you.
Pro tip Use a bi-weekly team-wide meeting to broadcast missing context and go deep on the day's most important topics; keep status out of 1:1s.
In the wild
Charles's boss, CTO Kareem, was extremely hands-off on actual product decisions because they were so aligned on the goals themselves—the biggest cultural difference from Charles's prior companies.
→ Enabled a culture where the CEO has less say in the product and engineers have more, driving Ramp's velocity.
Common mistakes
Debating the solution instead of the upstream
When leaders argue about the right solution, they're litigating the wrong layer. The productive debate is about data interpretation, hypotheses, and goals—resolve those and the solution follows from the team.
Prescribing without aligning
Being prescriptive on a solution while skipping alignment on goal, hypothesis, and data is what caused failures at Ramp—it strips teams of ownership and gets the answer wrong anyway.
Is it for you?
Best for
Product and engineering leaders scaling past the point where they can personally make every call, with a high-talent team.
Not ideal for
Low-trust or junior teams that genuinely lack the context or judgment to own solutions safely.
From the transcript
“whenever things went wrong at ramp it was when I was being prescriptive with regards to the solution without actually explaining and aligning Upstream on…”
“the solutions actually can come much better from teams that are much closer to the ground”
“I spend most of my time just repeating myself uh most of my time just sharing the context that I I think they might be…”
From the episode
Velocity over everything: How Ramp became the fastest-growing SaaS startup of all time
Geoff Charles (VP of Product)