“Mike and I were the blockers.” Law firm owner Chuck reached that conclusion after digging into why cases kept slipping: the work kept coming back to him and his partner, waiting for a yes. EOS Implementer Brooke Lively shares their story in her recent, Scaling Law .
If decisions in your company keep landing back on you, her answer starts with what your team needs before they can own the work.
A culture of ownership forms when employees can answer three questions on their own: what they own, whether they’re winning, and what they’re allowed to solve. EOS supplies each answer. The V/TO and Accountability Chart give clarity, the Scorecard and Rocks give visibility, and Issues and Process give the authority to act.
If you’re figuring out how to roll EOS past the leadership team, Anne Schoolcraft’s guide on how to get more of your company using EOS walks through those steps. Brooke’s session tackles what comes first: giving your team a reason to want it.
Watch the session Brooke Lively — Certified EOS Implementer, founder of Scaling Law, and author of Scaling Law: How Visionary Law Firm Owners Use EOS to Build Value and Plan Their Exit .
Hosted by Samantha Ngo — Head of Marketing, Strety, and Lauren Shaver — Head of Community, Strety.
VIDEO
Why does everything keep coming back to you? Employees stop asking for permission once they know what they own, can see their own results, and trust that solving problems is welcome. Until then, escalating every decision is the rational move.
Brooke opened with the complaint she hears most from teams running on EOS: why won’t my people take ownership? A question as small as “can we order a new printer?” travels through three seats on the Accountability Chart and lands on the owner’s desk.
It’s easy to call that a people problem. Brooke asks a different question: what have we taught them? Leadership teams see EOS as clarity and Traction. The rest of the company often hears something else. The Scorecard sounds like a new way to track them. Rocks sound like extra work on top of the real job. The L10 sounds like one more meeting.
Brooke reframes EOS as freedom that comes from accountability. Your people get the freedom to own their work, know how they’re doing without waiting to be told, and fix problems without asking permission every time.
Do your people know what they own? Clarity means each person knows their seat, the results it exists to produce, and which decisions are theirs to make. Accountability tells someone what they’re responsible for. Authority tells them what they’re allowed to do about it. Ownership needs both.
That’s what tripped up Chuck and Mike. Their team had an Accountability Chart and knew their roles. What nobody knew was which decisions they could make alone and which needed partner approval. So every time they weren’t sure, they waited.
The fix was systematic. They clarified decision-making authority alongside roles and responsibilities. Then, when a question came to Chuck or Mike that belonged to someone else, they sent it straight back to the person who owned it. The work started moving because the partners stopped being required for every decision.
Vision matters here too. Your team doesn’t need to memorize the V/TO, and Brooke was clear about that: please don’t quiz your receptionist on your 10-Year Target. People do need enough context to make the call you’d make. Core Values give them a filter for how to behave. Core Focus gives them a filter for what you do, and what you don’t.
Brooke also flagged a trap: building all this clarity and then hiding it. A V/TO the team sees four times a year and an Accountability Chart sitting in a six-month-old email both send people back to their manager. Keeping both somewhere everyone can open them is what turns clarity into something people use. If you’re mapping out seats and who decides what, our guide to role clarity with a visual org chart walks through it.
Can your people see whether they’re winning? Visibility means the person doing the work can see their own numbers and Rock status every week, without waiting for a manager to report back. People can’t own results they can’t see.
Brooke’s second story came from a firm owner in Savannah. The business was growing fast, but he couldn’t tell whether they were winning until month-end results came in. By then it was too late to act. So his team started tracking the weekly numbers that drive those results. When someone’s hours dropped for lack of work, they could see it in time to redistribute it. In his words, he could finally see problems coming weeks before they hit.
A good Scorecard gives each person the information to manage themselves. If you know your Measurable, your goal, and where you stand this week, you don’t need your manager to tell you how you’re doing. Our EOS Scorecard overview covers how to set those measurables up.
That shift changes your 1:1s too. When the numbers are already visible, you can skip the “how’s it going? fine” status check. You can talk about what’s getting in the way, what decisions someone is wrestling with, and where they need help.
Rocks work the same way. “Good” isn’t a status. An owner should know what done looks like, have milestones that show where they should be, and call their Rock off track before anyone asks. Brooke’s point here: an off-track Rock is information. The dangerous one is the Rock everyone knows is in trouble and nobody flags.
This matters more as you grow. With five people, the owner can be the scoreboard. Add enough people and companies tend to add managers, then meetings to find out what’s happening, then more meetings to report it up. To grow ownership, visibility has to grow with the company.
Do your people know what they’re allowed to solve? Authority means people believe raising and solving an issue is welcome, and that something will happen when they do. People stop raising issues when raising issues doesn’t work.
Brooke described a team she worked with recently. When the owner stepped out of the room, someone said about a major issue: he won’t move on that, we’ve quit trying. They’d learned which problems to work around.
When teams saw issues raised and solved within a reasonable time, they started raising them earlier. Then they raised bigger ones. Eventually they brought opportunities too, beyond the safe problems.
That takes openness from leaders. People may bring you an issue you think is wrong, or one that points at you. If every issue gets defended against or taken over, your team learns to stop bothering.
IDS gives everyone a structure for thinking. Identify the real issue. Discuss it with the people who see it from different angles, because the receptionist knows things the CEO doesn’t. Solve it with who’s doing what, by when. Then disagree in the room and support the decision outside it. Our Level 10 Meeting guide covers where IDS fits in the agenda.
Process sets the guardrails. Brooke borrowed a phrase from her retail days: UBJ, use your best judgment. Good Process tells people where consistency matters and where judgment is welcome. That’s why EOS documents the 20% of steps that get 80% of the result. A 700-page binder removes judgment completely, and nobody reads it anyway.
Issues also need a home. Brooke drops hers into Strety at 4 a.m. on a Sunday when the thought hits, so it’s waiting on the Issues List for the next meeting with no email or interruption needed. Ask your team to speak up without giving them a place to do it, and issues end up on sticky notes, in someone’s head, or in a hallway comment that’s gone by Friday.
How do you give freedom without losing control? Clarity sets the boundaries, visibility shows you when something goes off track, Process creates guardrails, and IDS gives people somewhere to go when judgment is needed. Together they give leaders more control, with less hovering.
Brooke gets this question more than any other: how do you hand over decisions without people making expensive mistakes? Her answer is that freedom by design doesn’t mean everybody does whatever they want. It means people know what they own, whether they’re winning, and where they can use their judgment. That’s more control than 30 people lining up outside the owner’s door with questions.
It frees up the leader too. You don’t have to answer every question, be the scoreboard, or attend every meeting. Brooke put it simply: if we are always the answer, we are the ceiling.
Six questions to ask your team this week Brooke closed each section with homework. Ask these and listen to the answers:
Can you name the 5 Roles in your seat without looking? Hesitation here means clarity hasn’t reached the seat yet.What decisions can you make without asking me? Ask your direct reports. A vague answer shows where authority is still unclear.What’s your Measurable, what’s the goal, and are you winning? Everyone with a number should know all three.How do you know you’re having a good week before I tell you? Don’t help them answer. If the answer is “my manager seems happy,” the manager has become the Scorecard.Where do you keep your Issues? Paper, memory, or a shared Issues List tells you whether Issues have a home.Can you raise a concern without fear? This one is hard to ask face to face, and Brooke shares how she gets honest answers to it in the recording.Make ownership visible with Strety Brooke made one distinction throughout the session: clarity creates ownership, and software makes that clarity visible and usable. When the V/TO, Accountability Chart, Scorecard, Rocks, To Dos, and Issues all live in one place your whole team can open, you can let go without going blind.
Many teams use Strety well at the leadership level and are slower to bring the rest of the company in. Opening it up is how people find where they fit, see their own numbers, and drop an Issue on the list without waiting for the next meeting. Brooke even connected her own Scorecard to her email, phone, and texts, so client contact logs itself every week.
Watch the full session for Brooke’s live Q&A, including how to raise this with your leadership team when you’re not the one in charge.
Try Strety free for 30 days , invite your team in, and let them see what they own. The next printer question might get solved before it reaches your desk. 😌
Frequently asked questions What is a culture of ownership? A culture of ownership is one where employees make decisions and solve problems within their role without waiting for permission. It forms when people know what they own, can see their results, and know what they’re allowed to solve.
How do you get employees to take ownership? Make roles and decision rights clear, give people visibility into their own numbers, and respond well when they raise issues. Asking for ownership without those conditions in place usually produces more escalation.
What’s the difference between accountability and authority? Accountability defines what someone is responsible for. Authority defines what they’re allowed to do about it. Teams that clarify only accountability often find people still waiting on approval.
Why do employees push back on EOS? Employees often hear the Scorecard as tracking, Rocks as extra work, and the L10 as another meeting. Explaining EOS in terms of what it gives them, like clear ownership and fewer approvals, changes that response.
How do you roll EOS out beyond the leadership team? Start by making the V/TO, Accountability Chart, and Scorecard visible to everyone, then extend Rocks, Issues, and L10s to departments. Anne Schoolcraft’s EOS rollout guide walks through the steps.
How do you give employees more decision-making authority without losing control? Use Process to set guardrails, the Scorecard and Rocks to keep results visible, and IDS as the path for anything that needs a group decision. Leaders stay informed without approving every step.
What EOS software helps clarify seats, roles, and who owns what? Strety keeps your Accountability Chart and V/TO in one place your whole company can open, so anyone can check who owns a seat and where the company is headed without asking a manager. You can try it free for 30 days , no credit card required.
Can employees outside the leadership team use EOS software? Yes. In Strety, team members can track their own Scorecard numbers and Rocks, add Issues whenever they spot them, and run department L10s. Opening it up past the leadership team is how people get the visibility to own their results.