Dropbox co-CEO Ashraf Alkarmi has opened up about how he handles disagreement with his co-CEO, founder Drew Houston. His playbook leans on data, direct conversation, and the kind of full-throated commitment that follows once a decision is made.
Quick take:
- Alkarmi became co-CEO of Dropbox in May, alongside founder Drew Houston.
- He previously held senior leadership roles at Vimeo and Meta.
- Rule one is to build trust and respect before any disagreement matters.
- Rule two is to be a truth teller, grounded in facts and data.
- He describes his style as radical candor, delivered with care.
- When debate stalls, Houston uses the word "final" to close the topic.
- Once closed, both sides "disagree and commit," a phrase coined in Jeff Bezos's 2016 shareholder letter.
- Alkarmi is set to become sole CEO eventually as part of the succession plan.
How the dynamic actually works
According to businessinsider.com, the first move is establishing a base of trust and respect so that pushback is read as good faith rather than ego. The second move is being a truth teller, grounding your position in facts, data, and clear reasoning instead of indirect or passive-aggressive channels. Alkarmi frames this as "radical candor," with the "with care" part doing a lot of quiet heavy lifting. When the debate still does not resolve, Houston signals that the decision is made by saying the word "final." Alkarmi then treats the call as his own and commits to making it work, a conscious echo of Bezos's "disagree and commit" principle.
Our analysis
For our readers this is a clean demonstration of decision hygiene at the top of an org chart. The trust-first, truth-teller pair is servant leadership made operational: earn the right to be heard, then be heard with candor. The "final" keyword is a small but useful pattern, an explicit, low-ceremony way to close a debate and shift into execution mode without anyone having to read body language. The "disagree and commit" step is the one most teams skip, which is how you end up with a leader who is publicly on board and privately routing around the call. The piece Alkarmi does not describe is the after-action review: how the pair revisits a "final" decision when reality pushes back. That is where most leadership teams either compound their learning or calcify around sunk calls. Watch that gap. It will determine whether the Dropbox co-CEO chapter reads as a succession success story or a slow internal tug-of-war.
What it means for you
You do not need two CEOs to use this. You need a teammate, a stand-up, a retrospective, or a 1:1 where decisions actually land. Try this on your next sprint planning: name the person whose call it is, ask for the data behind the disagreement, and decide on a code word that ends the debate. After the decision, state the commitment out loud and put it in the retro board. If you are the one who lost the argument, your job is to make the chosen path succeed and to flag in the next retro whether the decision held up. Servant leadership shows up here as a behavior, not a poster, cleaning up after your own position when the room has moved on.
Worked example
Say you are a scrum master and your engineering lead wants to drop the sprint goal mid-iteration to chase a customer escalation. Trust is already there from months of 1:1s. You lay out the data: cycle time impact, WIP limits, and the goal's link to a stakeholder commitment. The debate runs hot. The product owner says "final," meaning the sprint goal stays put. You commit out loud, support the escalation as a parallel workstream, and park a check-in item for the retro. Two weeks later, if the data says the call was wrong, you raise it as a blameless learning, not a gotcha.
Bottom line
Alkarmi is set to become sole CEO eventually, which will test the dynamic in reverse, going from co-pilot to single point of accountability. The recipe is simple to state and hard to run: trust plus candor plus an explicit close plus full commitment. Most teams are missing at least one step, and the step they are missing is usually the last one. Fix that and your retros will start sounding different.
Key takeaways
- Build trust before you need to challenge a peer's call.
- Ground disagreement in data, not office politics.
- Pick a code word that ends debate and shifts the room to execution.
- "Disagree and commit" means you stop relitigating once the call is made.
- Revisit "final" decisions in retros so the team learns instead of defends.
Frequently asked questions
Who is Dropbox's co-CEO and when did he start?
Ashraf Alkarmi became Dropbox co-CEO in May, alongside founder Drew Houston, and is set to become sole CEO eventually.
What does Alkarmi say is the first rule of disagreement?
Build trust and mutual respect first, so feedback is read as good faith rather than ego.
How does the Dropbox co-CEO dynamic end a debate?
Drew Houston uses the word "final" to signal the decision is made, and both sides commit to executing it.
Where does the phrase "disagree and commit" come from?
It comes from Jeff Bezos's 2016 shareholder letter and is used by Alkarmi to describe how he supports decisions once they are final.
What is the part of the playbook Alkarmi does not describe?
He does not lay out how the pair revisits a "final" decision in a retro or after-action review when the outcome pushes back, which is the step that determines whether the team actually learns.
Inspired by reporting from: businessinsider.com