What is the actual job of a CEO?

Rather than treating leadership as a vague mix of hustle and charisma, Peter and Jon compare two competing frameworks that both come from highly successful operators. Peter argues the CEO’s job is to set the vision, build the team, and make sure the company never runs out of cash. Jon reframes the role as raising standards, increasing focus, and increasing pace.

Truth is, there’s no “better” framework. It’s more so about uncovering the deeper principles beneath both models and adapting it to your organization’s current needs.

The alternative framework is more operational and cultural.

Raising standards means teaching teams what excellence looks like, not just demanding it. Increasing pace is less about arbitrary deadlines and more about shortening the OODA loop (observe, orient, decide, act) so organizations can iterate faster on marketing channels, hiring strategies, or product features.

The frameworks aren't contradictory. They're complementary.

One addresses what to build; the other addresses how to build it. Together, they reveal that leadership isn't about answering emails or attending meetings. It's about the handful of things that won't happen without deliberate intervention: maintaining focus, enforcing standards, controlling speed, setting direction, building teams, and managing resources.

Everything else is noise.

KEY TOPICS (02:05) Two Frameworks for the CEO’s Job (07:09) Why Real Prioritization Has to Hurt (11:06) Raising Standards, High Care vs. High Honesty (17:25) Developing Taste and Knowing What “Good” Looks Like (25:37) OODA Loop: Observe, Orient, Decide, Act (34:14) What Happens When CEOs Don't Set Clear Vision (Whiplash and Cynicism) (40:30) Don't Run Out of Money: Cash Conversion Cycles and Personal Liability (43:21) Accounting as Control: How CFOs Direct Energy in Organizations

Stay connected for more insights and strategies by following: Jon: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@MatznerJon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ on X and at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠lazyleverage.beehiiv.com⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Peter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@pslohmann⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ on X and at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠peterlohmann.com

Have you ever bought new tech, spent months implementing it, and seen zero throughput improvement? You’re not alone. It's an age-old problem plaguing small businesses.

Whether it's switching property management software or adopting ChatGPT company-wide, the result is the same. Lots of disruption yet no meaningful change.

The culprit isn't the technology itself. It's how we deploy it. In the audiobook 'Beyond the goal', Dr. Eliyahu Goldratt identified four critical steps for technology rollout in the Theory of Constraints work, and most businesses overlook at least a couple of them.

Step one is easy: identify what the technology can do (it's on the vendor's website). Step two is to ask, “Does this technology diminish your actual constraint?”.

Step three is to identify old accommodations. These are the rules your team created to cope with historic limitations.

Step four is to identify new rules.

Technology becomes a burden if you keep operating under old policies. Companies spend millions on ERPs without updating the implicit rules designed around previous limitations, then wonder why productivity stays flat.

Jon extends this to the AI hype cycle, in which venture-backed firms are buying pool cleaning companies claiming AI will revolutionize operations. But until someone explains how AI solves managing $21/hour workers in wealthy homeowners' houses, it's just expensive posturing.

The constraint isn't following up on leads but managing low-cost local labor. Writing emails faster doesn't address that!

KEY TOPICS: (10:26) What to Do When A Lot of Work Nets Zero Results (16:01) Step One: Identify the Power (18:28) Step Two: How Does It Diminish the Constraint? (21:10) Missing the Step Between Goals and Rocks (28:17) Step Three: Identify Old Accommodations (33:45) Step Four: Identify New Rules (37:00) Why ChatGPT Adoption Isn't Driving Revenue Growth (46:45) You Must Be Intimately Familiar With Both Your Constraint and the Available Tools

Stay connected for more insights and strategies by following: Jon: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@MatznerJon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ on X and at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠lazyleverage.beehiiv.com⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Peter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@pslohmann⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ on X and at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠peterlohmann.com

The best operators in M&A make hundreds of millions because they "model deals elegantly," but billionaires "can barely do the math. They just only do deals where they can't lose."

At least that’s what Jon and Peter believe. It's Warren Buffett's philosophy in action; that price is your due diligence.

Metrics should be entered manually, not automated. The psychological weight of pulling numbers and inputting them weekly creates accountability that automated dashboards never achieve. It's the difference between ownership and passive observation.

They distinguish between dashboards (lagging indicators like revenue) and scorecards (controllable activities like reviews requested). This separation, learned from their EOS coach Chris Kaplan, prevents teams from chasing metrics they can't influence week-to-week.

Next we’re asking, “Should you judge people on outcomes or process?” Saban (echoing Bill Walsh) says focus on the controllables. That is, the score takes care of itself. But Jon admits he's "constantly ripped in half" between mandating process and demanding results. Peter suggests it depends on performance level: high performers get freedom, struggling performers get prescription.

They tackle paired metrics as protection against perverse incentives, using India's snake-bounty program as a cautionary tale. When the government paid for dead snakes, people started breeding them. Similarly, optimizing turn time without pairing it with customer satisfaction leads to cutting corners.

Finally, Jon and Peter riff on Saul Alinsky's "Rules for Radicals", particularly when he says that, when pressure increases, people try to diffuse responsibility.

As a manager, your job is keeping accountability focused: "You are responsible for everything that does and doesn't happen to make this number improve."

Key Topics: (07:47) Why Automation Kills Accountability (10:20) Building Your First Scorecard: Start Imperfect and Iterate (12:41) Dashboard vs. Scorecard: Lagging Indicators vs. Controllable Activities (19:57) Control the Controllables, Not the Score (37:27) How Incentives Create Perverse Outcomes (41:14) Why DLER Must Be Balanced with Customer Satisfaction (45:38) Change the Metric, the Goal, or the Person (48:56) High Care, High Standards.

Stay connected for more insights and strategies by following: Jon: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@MatznerJon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ on X and at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠lazyleverage.beehiiv.com⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Peter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@pslohmann⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ on X and at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠peterlohmann.com