Who owns the decision? The science of empowered teams

Most government software teams have an org chart. Far fewer have clarity on who's accountable for what—and who holds the authority to match. That gap is where dysfunction lives. Decisions stall in consensus. Engineers carry responsibility they have no power to act on. Product, design, and engineering blur together until everyone weighs in and no one owns the call. Real empowerment isn't a vibe. It's a structure: accountabilities and authorities, deliberately matched, role by role. In this Mission O/S Live, Rise8 VP of Enablement Adam Furtado and Rise8 Platform Engineering Enablement Lead Matt Pacione sit down with Matthew K. Parker—author and Senior Adviser to the Maryland Digital Service—to unpack the science of organizational design and a question every delivery team wrestles with: how do you give people real ownership without falling into the consensus trap? What they'll cover: Why government delivery so often defaults to either gridlock or chaos—and how matching authority to accountability fixes both How balanced teams distribute ownership across PM, design, and engineering—and why that structure holds up inside hierarchical, compliance-heavy government orgs What program leaders and engineering directors should and shouldn't own in relation to the teams actually shipping the work Why empowered roles and aligned autonomy satisfy deep psychological needs—and why that matters for retaining scarce technical talent in government If you lead, build, or deliver inside a government software org—and you want a team structure rooted in science, not just good intentions—you won't want to miss this one.