The 10x Leverage Desk
Spend your finite time only on problems with 10x positive or negative impact — and physically move yourself into the details until they're solved.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 90%
You always have more problems than time, and once senior, every problem that reaches you is 'important.' The filter is impact magnitude: work only on problems that carry a ~10x positive or negative swing (the multiple scales with the company — 100x at Binance, maybe 3x elsewhere). In fintech these are almost always a growth problem or a compliance problem. Then embody the choice: like white-pages founder Alex Algard's literal moving desk, relocate yourself into the highest-leverage team, get into the granular details with humility, and stay until the problem is solved or the opportunity realized — then move on.
Origin
Mayur Kamat combines Shreyas Doshi's leverage principle (referenced in the episode) with Alex Algard's 'moving desk' practice at Whitepages and CZ's hands-on ownership at Binance.
Core principles
- 01You have finite time and more problems than you can solve — impact magnitude is the sort key
- 02Work only on ~10x-positive-or-negative problems (calibrate the multiple to your company)
- 03In fintech, the 10x problems are almost always growth or compliance
- 04High-leverage problems are usually buried in details, not in strategy choices
- 05It takes humility to do 'below your level' detail work — and that's exactly where the leverage is
- 06Keep a mostly-empty calendar; a full calendar is a badge of shame, not honor
How to run it
- 1
Identify the 10x problem
Scan your problem set and keep only those with a roughly 10x positive or negative impact. Ignore the merely-important. In fintech, look first at growth and compliance.
Pro tip Adjust the multiple to context — 100x at Binance-scale, 3x at a smaller company — but keep it a high bar.
- 2
Move your desk into that team
Physically embed with the team that owns the highest-leverage problem and become the working product manager on it, not a reviewing executive.
Pro tip Algard would attend the sub-team's standups and give his update there, then give his update on the same work in the leadership meeting an hour later.
- 3
Get into the details with humility
Drop the 'this is below me' reflex. The devil is in the details — know every screen, every drop-off, every metric — and be senior enough to be told 'no' by the expert PM who knows better.
Pro tip Mutual respect matters: the best sign is a lead PM comfortable saying 'no' to the founder on their own product area.
Watch out Leaders who consider detail work beneath them will systematically miss the highest-leverage fixes, which are rarely strategy decisions.
- 4
Solve it, then move on
Stay until the problem is solved or the opportunity realized, then hand it to the team you trust and move your desk to the next 10x problem.
Pro tip Protect open calendar space so you actually have time to embed — you can't do this buried in recurring one-on-ones and standups.
In the wild
At Whitepages, founder Alex Algard had no fixed office — just a movable desk he'd relocate into whichever department held the highest-leverage opportunity, sitting there until the problem was solved. When Kamat pitched hiring a PM for SEO, Algard (an SEO legend) instead made himself the PM for that scrum for three months.
→ You could literally visualize the highest-leverage problem by where the founder's desk was; the SEO effort had a dedicated founder-owner.
At N26, Kamat might focus for a month on converting signed-up users into long-term daily-active users, running experiments on early onboarding screens, rewards, incentives, and loyalty — then, once the PMs have it functioning, move to compliance or fraud issues in France.
→ Time is continuously reallocated to wherever the current 10x leverage sits.
Common mistakes
Believing detail work is beneath you
'Why would I do that, a PM or analyst should' thinking keeps leaders out of the details where the real leverage lives; most high-leverage wins are unglamorous detail fixes, not strategy calls.
A full calendar
Hundreds of recurring meetings and one-on-ones leave no room to embed on a high-leverage problem — a packed calendar is a badge of shame, not a signal of importance.
Is it for you?
Best for
Senior product leaders and founders who must allocate scarce personal time across many important problems
Not ideal for
Individual contributors with a single assigned scope, or cultures where an executive embedding reads as disruptive micromanagement
From the transcript
“you work on problems that have a 10x positive or a negative impact”
“in most fintech companies one of two problems it's a growth problem or a compliance problem”
“he would move his desk to one of the departments which you think had the highest leverage opportunity and he would sit there uh at…”
“a lot of the high leverage problems are not as I said not strategy decisions”
“a full calendar is a badge of shame, not a badge of honor”
From the episode
Unconventional product lessons from Binance, N26, Google, more
Mayur Kamat (CPO at N26, ex-Binance Head of Product)