three offices that mostly run themselves, and a small exec team for the few things that don't stay local.
there is no ticket-pusher middle layer. partners claim work, form teams, and use retros to surface gaps. leads and PMs coordinate; they do not turn the organization into a reporting ladder.
three offices. denver is headquarters and the largest presence, amsterdam is the secondary office, and zurich is a satellite.
there's a small executive team for the decisions that actually cross offices: big budgets, governance, ties. everything else stays local.
executive responsibilities:
work happens in teams. you can be on more than one. they're not departments with org charts, just groups of people working on the same stuff. explore open positions across these teams
without a management hierarchy, mutuol relies on process and consensus to make decisions. this isn't perfect, but it's documented and it works.
for day-to-day decisions:
consensus within the team or office affected. if you're doing work that mostly impacts your local context, you decide. retros catch it when a local decision affects someone else.
for cross-team or cross-office decisions:
lazy consensus: propose the change, give reasonable time for objection, and proceed unless someone raises a block. objections require justification and an alternative proposal.
for organizational changes:
RFC-style proposals with documented discussion periods. major changes (budgeting, governance, partner policies) go through the exec team for sign-off.
when consensus fails:
if local consensus can't settle something, the exec team breaks the tie. it's meant to be rare; most things resolve in retros or just by talking.
offices run independently but need to not drift apart. here's how we do that. for details on work arrangements, see our work policy.