Broken Canon Key Takeaways

by Rick Ferrone

Broken Canon by Rick Ferrone Book Cover

5 Main Takeaways from Broken Canon

Inherited Management Assumptions Drive the Productivity Gap

Ferrone argues that the decades-long gap between computing power and output is not a technology failure but the cost of running firms on inherited industrial assumptions. Executing that flawed playbook more efficiently makes things worse, and AI trained on existing practice will reproduce the same defects. Firms must find and remove inherited defects before adoption scales them.

Diagnose Root Causes Before Buying or Building Solutions

Clustered complaints, recurring emergencies, and stalled work usually point to one missing constraint rather than many separate failures. The standard toolkit of reorgs, offsites, tools, and metrics patches symptoms because it never questions the industry playbook or the cause. As the handwashing example shows, a flaw can be visible yet survive for decades until someone diagnoses the context.

Align Mission, Measurement, and Cross-Functional Work

Private scoreboards, functional ROI estimates, and departmental KPIs can fragment effort even when every team looks strong locally. The book connects Apollo 13, arbitrary overhead splits, and the lost conductor role to show that shared purpose and integrated measurement are what turn expertise into teamwork. Without a conductor, cross-company productivity and communication go unmanaged.

Redesign Routines, Meetings, and Reporting Around Value

Inherited processes often persist after their original reason disappears, and standard meeting formats become a top drag on productivity. Ferrone urges leaders to strip work back to the plain objective, retire steps whose constraint is gone, and build internal reporting for the decisions managers actually make. Simplicity is an active discipline that exposes waste.

Quantify Bad Management and Pilot Repaired Routines First

Leaders should put a number on rework, competing priorities, delayed hires, and missed investments before choosing what to fix. Copying benchmarks is insufficient because rivals carry the same inherited practices, and buying technology before repairing routines invites AI to amplify the flaw. Pilot disciplined changes, then scale only what works.

Executive Analysis

The five takeaways form a single argument: the modern firm's productivity problem is a management-design problem inherited from an industrial canon, not a technology shortfall. Ferrone shows that firms patch symptoms, copy standard playbooks, and then layer AI on flawed routines, which only scales the defects. The cure is a disciplined sequence: surface the unwritten assumptions, diagnose the real constraint, align mission and measurement across functions, redesign routines and reporting around value, then quantify the cost and pilot repairs before scaling.

This matters because it gives leaders a practical alternative to reorganization, new tools, or louder execution: find and remove shared defects competitors also carry, then let technology amplify a repaired system rather than a broken one. As a management book, Broken Canon sits between operations improvement and strategy execution, offering a diagnosis-first playbook for firms stuck in the productivity paradox. Readers get a repeatable way to spot costly inherited routines, reframe decisions, and sequence change so improvements survive contact with budgets, meetings, hiring, and measurement.

Chapter-by-Chapter Key Takeaways

0. THE LOSS (Chapter 1)

  • The four-decade gap between computing power and output is not a technology failure; it is the cost of running firms on inherited industrial assumptions.

  • That inherited playbook costs real money even when profits conceal it, and executing it efficiently makes things worse rather than better.

  • AI trained on existing practice will reproduce and amplify the same defects, so adoption without redesign compounds the problem.

  • The long-delayed acceptance of handwashing shows that a flaw can be visible and still survive for decades. Fixes are easy to copy, but figuring out what is wrong takes context.

  • Firms that find and remove those inherited defects before competitors do gain a durable edge.

Try this: Audit inherited routines for defects before deploying AI, and quantify the hidden cost of running the industrial playbook even when profits mask it; fix visible flaws before scaling them.

1. THE ESCAPE (Chapter 2)

  • When a rough patch drags on for months and nothing you try holds, ask whether the job itself is set up the right way, not just whether you are working hard enough inside it.

  • Keep the routines that fill a calendar separate from the work that actually moves the company. A well-run operation elsewhere is a useful comparison, not a distraction.

  • Stay open to the answer that nothing is broken and the bar has simply moved. A new normal is almost impossible to see from inside the daily routine.

  • Write the problem down and notice which version you erase. The question you cannot stand to read is the one doing the damage.

  • Notice when you cannot stop working even with nothing on fire. The break you refuse to take is a sign of the problem itself.

Try this: Step outside the daily routine and write down the stuck problem, then compare job design with a well-run operation and ask whether the bar has moved or the work itself is misconfigured.

2. THE PROBLEM (Chapter 3)

  • When an organization is stuck, look for what's missing before you throw more money or people at it. Consultants, reorganizations, offsites, tools, and metric programs each helped a little, and none was enough. That pattern is the clue: the missing piece is something the standard toolkit doesn't cover.

  • The way your industry does things can be the obstacle, not the solution. If no one ever questions the usual playbook, you'll keep patching the same symptoms over and over.

  • The real constraint is often invisible from inside the operation. Not because the leader lacks information, but because people pay attention to what they're used to. Knowing how things run doesn't mean you can see what everyone has quietly agreed to ignore.

  • A cluster of unresolved complaints — weak hiring results, misalignment, execution drag, strategy that never reaches daily work, stakeholder pressure — points to one root cause, not five separate failures.

  • Problems with no owner don't get fixed. When every team is buried in current work and emergencies set the agenda, anything without a named owner and protected time stays exactly where it is.

Try this: Assign a named owner protected time to trace clustered complaints back to the missing constraint, and question whether your industry's standard toolkit is itself the obstacle.

4. THE BAIT (Chapter 5)

  • Start with the problems you can already feel, like work that keeps stalling between teams or the same emergencies coming back. Trace each one to the assumptions that keep causing it.

  • Watch where management attention goes. A growth-first lens points it outward at customers and markets, so the finance, HR, IT and planning work falls apart because no meeting owns it.

  • Choose productivity over cost cutting: get the same results with fewer resources, and prefer savings that recur every month to a one-time trim.

  • Remember that the standard playbook carries its flaws with it. Copying what everyone else reads means settling for a smaller payoff.

Try this: Trace recurring stalls to the assumptions that cause them, redirect management attention toward productivity and recurring savings, and stop copying a flawed standard playbook.

5. THE JOB (Chapter 6)

  • Treat flat results and lost directors as yours to answer for, not as the economy's doing.

  • When funding disappears, show donors what the work protects rather than making a louder argument for it.

  • Admit the problem is yours, even before you have a solution.

  • Compare yourself with people who have done more, and see what you still haven't fixed—but remember their rescue stories don't apply to your own house.

Try this: Own flat results and lost directors as your problem, show stakeholders what the work protects, and compare with stronger performers without importing their rescue stories wholesale.

6. THE PROCESS (Chapter 7)

  • Verify that the people writing your procedures are trained to design them, not merely to run them.

  • Pull each standing process back to the constraint that created it, and retire any step whose original reason has disappeared.

  • Replace coordination fixes like more meetings and shared tools with integration work that points every function at one objective.

  • Measure the productivity lost to poor cross-functional alignment, including meeting and follow-up hours, because domain excellence alone will not close that gap.

Try this: Pull each standing process back to its original constraint, retire steps whose reason has vanished, and measure the productivity lost to cross-functional misalignment before adding more coordination meetings.

7. THE MEETING (Chapter 8)

  • Treat simplicity as an active discipline: strip away piled-up tools and processes until the plain objective of selling profitably is visible again, since clarity is what exposes waste.

  • Expect meetings to repeat the same loop of homework, cancelled sessions and fresh assignments, and treat adding a facilitator or timekeeper as a sign the format itself is failing.

  • Assume that group discussion will not come together on its own, because private lobbying and not wanting to reverse a stated position push the decision toward a senior call or a vote.

  • When a decision is on the table, ask whether it is framed around current conditions or possible ones, since building solutions on top of an unexamined problem is how expensive integration work ends up capturing the wrong data.

  • Do not take the standard meeting format as proof of effectiveness; HBR surveys cited in the chapter rank meetings as the top drag on productivity, with managers judging 83% of scheduled meetings unproductive.

Try this: Strip meetings and processes to the plain objective, diagnose whether the decision is framed around current or possible conditions, and measure the productivity drag before adding facilitators.

8. THE SOLUTION? (Chapter 9)

  • A choice that was wrong from the start cannot be saved by execution; how good the decision is determines how much any later work can achieve.

  • Leading with a proposed answer turns the discussion into a contest of opinions and leaves the cause of the problem untouched; a remedy offered before diagnosis is just a confident guess, whether the source is human or machine.

  • Urgency changes which part of a problem must be handled first, not whether the problem must be understood; separate immediate impact from underlying cause and work both.

  • Agree on what would count as a good solution before debating options, but keep fixing the problem as the primary test; cost, clarity, scalability and buy-in cannot substitute for a remedy that works.

  • Decision-making means guiding the process step by step rather than issuing a single verdict: define the problem, set criteria, choose, then check results against the goal and adjust; without that loop, a decision is only a preference.

Try this: Diagnose the problem before offering a remedy, agree on solution criteria, and guide a decision loop—define, choose, check results, adjust—rather than treating urgency as permission to skip understanding.

9. THE MAP (Chapter 10)

  • Define the outcome you want and the numbers that describe current performance before you consider any fix.

  • Walk the actual process instead of trusting the first explanation for a shortfall.

  • Find the cause before weighing fixes, then estimate how much each fix would move performance.

  • Treat colleagues inside the organization as customers: ask what is broken and what they need, collect answers individually, and save group time for reviewing findings, costs, and benefits.

Try this: Define the outcome and current numbers first, walk the actual process, and interview internal customers individually to find the cause before estimating any fix.

10. THE PILOT (Chapter 11)

  • Name a target ambitious enough that the current playbook cannot reach it, and expect the cautious people in the room to call it unrealistic.

  • Walk the floor and question routines inherited from when the company was a fraction of its size; practices nobody has revisited quietly set your ceiling.

  • Trace the numbers on your dashboards back to their source before you trust the color.

  • Treat speed as a risk rather than a virtue; acting fast on expert instinct buries the assumptions that later sink the plan.

  • Refuse to greenlight a revenue-only proposal; ask for cost, timeline and one clear recommendation, and judge the ideas doable before you judge them good.

Try this: Set a target the current playbook cannot reach, walk the floor to question inherited routines, trace dashboard numbers to source, and demand cost, timeline, and one clear recommendation before piloting.

11. THE GUIDE (Chapter 12)

  • Judge a growth push by whether it changes the company's trajectory, not by whether revenue moved; a few points of gain is just customer maintenance with a project's name on it.

  • Hunt for the unwritten operating rules that govern how work actually gets done, since a project can be executed cleanly and still fail against them.

  • Before signing off on a target, confirm the organization could staff, build and support it, not merely that customers could buy it; capability belongs inside any claim of achievability.

  • Fix the start of a deadline and state which finish you mean: revenue earned within the window, a monthly pace reached by the date, or an organization completed and able to produce the number.

  • Aim solutions at the obstacle, not the disappointing result; weak sales is a symptom, and there is nothing in it to fix.

Try this: Test growth targets against unwritten operating rules and staffing capability, define exactly which finish the deadline means, and aim solutions at the obstacle rather than the disappointing sales number.

12. THE GORILLA (Chapter 13)

  • Before you answer a slipping metric with more spend, more headcount, or another meeting, make sure you've actually found a cause and aren't just relieving the pressure to look busy.

  • Treat expertise as a source of blind spots as much as a guide: the more familiar an operation is, the more correct it appears, so get a read on it from someone outside the industry's habits.

  • Put three numbers on paper first (where you must land, where you stand, and the distance between), split the operation into products, services, or teams rather than judging it whole, and keep asking why each step exists until the answer is a reason and not a habit.

  • Match the scale of the method to the size of the gap; defect-elimination programs suit repetitive processes, and steady incremental improvement will not close a gap that calls for rebuilding rather than refining.

  • Sort customers by profitability before cutting costs or chasing growth: an even-service culture tends to protect the accounts that cost the most, and a minimum fee with tiered service levels can recover margin from that unprofitable tail.

Try this: Put must-land, current, and gap numbers on paper, get an outsider read on expertise blind spots, segment customers by profitability, and match the method's scale to the gap.

13. THE GOOD (Chapter 14)

  • Before work begins, have everyone say the goal back in their own words. A goal that reads clearly on paper can still be four different goals in four heads.

  • List the concrete habits you treat as good performance, like fast replies or early arrivals, and compare lists with your team. That's where the real differences show up.

  • Rewrite your mission until employees can repeat it from memory. If they can't recite it, each person will replace it with their own private interpretation.

  • Make the mission say something only your organisation could say. Standard language about improving lives gives the people expected to act on it nothing to act on.

  • Hold off on departmental fixes until every group agrees on what the goal is and what the work involves. Otherwise you'll spend the next phase stitching together incompatible efforts.

Try this: Have every team restate the goal and compare their lists of good-performance habits, then rewrite the mission until it is memorable, unique, and agreed before departmental fixes begin.

14. THE MISSION (Chapter 15)

  • Agree on what mission means in your organization before you draft one, and keep it separate from vision so the two do not become interchangeable labels.

  • Write the mission as a result you can verify and reach, then use it to guide targets, budgets and trade-offs.

  • Revise the mission when conditions change, as Apollo 13 did when the goal moved from landing on the moon to getting the crew home alive.

  • Retire the mission once it is achieved and replace it with a new one, rather than letting it persist as a slogan after the finish line is crossed.

  • Check rewards and pay against the mission. If the goal cannot be measured, you may be paying people for the wrong behavior and only discover the cost later.

Try this: Define mission as a verifiable result distinct from vision, align targets, budgets, and rewards to it, and revise or retire it when conditions change or the finish line is crossed.

15. THE GAaP (Chapter 16)

  • Finance and operations see the same business from different angles. Set up your systems so each transaction can carry both an external account and an internal account.

  • Keep GAAP statements for investors, lenders, and auditors. Give managers a separate reporting set built around the decisions they actually make.

  • When a standard P&L makes leasing look cheaper than buying, or blends this month's costs with revenue from work completed a year earlier, fix the report instead of doubting the manager reading it.

  • Question the reporting categories you inherited, even when your ERP automates them. The standard accounting structure can hide cost drivers and accountability, just as regulator accounts once did.

  • Give internal reporting the same design attention and training as external compliance. Most finance expertise is built for outsiders, not for the company's own operating questions.

Try this: Build internal reporting that carries both external and internal accounts, keep GAAP for outsiders, and question inherited categories so managers see cost drivers and decision-relevant numbers.

16. THE VALUE (Chapter 17)

  • ROI for a single function isn't a measurement—it's an estimate shaped by negotiation. Shared outputs make any clean attribution arbitrary.

  • Functions whose value lies in avoided harm, such as compliance, safety, and quality, can't be scored on ROI without implying the standard itself is negotiable.

  • Judge a function by whether it expands what the whole system can achieve, not by local output the next stage can't absorb.

  • How overhead costs get spread across departments can move a function's apparent return more than its actual performance, so the number reveals accounting choices as much as team contribution.

  • A precise figure built on arbitrary splits is more dangerous than an honest gap, because it invites confident action on bad data.

Try this: Stop treating functional ROI as objective truth, assess whether a function expands system capacity, and flag arbitrary overhead splits rather than acting on precise but fabricated attribution.

18. THE SCREEN (Chapter 19)

  • Recruit deliberately, develop continuously, and work hardest at keeping the people you want to keep.

  • Look past the keyword ranking your applicant tracking system produces and judge candidates on what they accomplished and how well, not on the certificates and tool names they list.

  • Hire for transferable skills and treat industry familiarity as something a new employee picks up in weeks, which means deliberately inviting candidates from other sectors instead of letting the software filter them out.

  • Own the hiring decision yourself as a manager. Decide whether you are filling a role quickly or building the strongest team before a stretched calendar decides it for you.

Try this: Audit screening filters for keyword bias, hire for transferable skills, and keep ownership of the selection decision while recruiting deliberately and developing continuously.

19. THE HIRE (Chapter 20)

  • Give one manager clear ownership of each hire, because responsibility split among HR, the applicant tracking system, and the hiring manager is where failed hires escape scrutiny.

  • Audit what your screening filters actually remove; a blank field is not evidence of an absent ability, and a boldly stated accomplishment is not a confirmed one.

  • Compare the roughly one week a year a ten-person manager spends screening with the cost of a single failed hire; the math rarely supports skimping on screening.

  • Ask every candidate how they handled a real conflict or setback, then tailor the follow-up to their own history rather than relying on passion or generic questions.

  • Keep HR's controls over job descriptions, pay, diversity, and background checks while moving the selection decision to the manager who will work with the person.

Try this: Give one manager clear ownership of each hire, audit what filters remove, ask tailored conflict-and-setback questions, and preserve HR controls while moving selection to the working manager.

21. THE TEAM (Chapter 22)

  • People become a team only when everyone is aiming at the same destination. Without that, getting along and talking constantly is cooperation, not teamwork.

  • Departmental boundaries are not the defect. Different jobs are the raw material of a team; the real problem is that each job gets its own private scoreboard.

  • Look at the measurement system before the culture. Budgets, KPIs and incentives that point each function at a separate target will outlast any amount of communication training, offsites or collaboration software.

  • Apollo 13 shows what shared purpose can do at its best: people with unrelated expertise and no common vocabulary achieved the near impossible once a single objective overrode every departmental one.

Try this: Fix private scoreboards and establish a shared destination before investing in culture or communication, because departmental boundaries are raw material, not the defect.

22. THE MANAGEMENT (Chapter 23)

  • Swap satisfaction scores for retention, then map complaint types against account losses so you can tell an annoyance from a deal-breaker and stop paying to over-serve customers who were never going to stay.

  • Put a dollar figure on each team's output, accounts saved or losses avoided, so people can see the impact of their work rather than the volume of activity they completed.

  • Build the budget as an investment plan by naming what every function delivers and what that delivery is worth; a department whose value you can't state is a department you can't manage.

  • Treat "Sales overpromised" as an explanation, not an exemption: partial influence over retention still measures something real, while speed and closure metrics measure only effort.

  • Watch for the systemic version of the same failure, a mission nobody remembers, functional goals pointing in different directions, activity substituting for value, because it produces the same result company-wide that Lamar's dashboard produces on one team.

Try this: Map complaint types to account losses, put a dollar value on each team's output, build budgets as investment plans, and treat sales overpromising as a measurable influence rather than an exemption.

23. THE PLAN (Chapter 24)

  • Treat the weaknesses every competitor shares as your opening: when firms work from the same standard practices, correcting common flaws is where an edge comes from, and automating a flawed process only makes the flaw run faster.

  • Make the Mission measurable before anything else, with targets for market share, revenue growth, or customer impact, then align company, functional, team, and individual goals beneath it; this makes the existing purpose explicit rather than inventing a new one, and should take weeks.

  • Spread the basic problem-solving approach beyond the first group and bring internal customers into the sessions; without better decision-making, results will stay a matter of guesswork.

  • Sequence the rollout so the Mission and decision-making come first, budgeting waits for its cycle, Functional ROI starts as a pilot in a simple function, and talent management runs alongside with managers taking over résumé review as a pilot; beginning with the largest, highest-impact effort will stall before it starts.

  • Plan for training, steady communication, and help guiding people through change instead of new technology, added staff, or a reorganization, and expect the plan to force existing projects to be modified, reprioritized, or stopped.

Try this: Sequence change with a measurable mission and decision-making first, pilot functional ROI in a simple area, and plan training and communication instead of leading with technology or reorganization.

24. THE CONDUCTOR (Chapter 25)

  • Fixing hiring, measurement, and departmental goals still leaves a gap if no one coordinates effort across functions.

  • A company needs a shared goal, a way to measure value, and a conductor who keeps every function playing in tune.

  • The conductor role faded away as companies specialized, and the corporate ladder still rewards depth in one function over breadth across the company.

  • No one owns cross-company communication or productivity, so meetings, reports, and processes go unmanaged.

  • Strong departmental numbers can hide wasted work, so check whether the work behind them was ever needed.

Try this: Appoint a conductor for cross-functional productivity, give every function a shared goal and value measure, and check whether strong departmental numbers hide work that was never needed.

25. THE CHOICE (Chapter 26)

  • Put a number on what bad management costs you: rework hours, time spent sorting out competing priorities, hires never made, investments never funded. Quantify it before deciding what to fix.

  • Don't rely on matching benchmarks, since rivals carry the same inherited practices and constraints; only dropping them changes what your company can reach.

  • Fix the routine behind a tool before buying more technology, because systems you already own pay off only once the routine they serve works.

  • Expect AI to amplify whatever practice it touches, so repair the underlying process first or the flaw gets pushed deeper into workflows at scale.

Try this: Quantify the cost of rework, competing priorities, and delayed investments, repair the routine before buying technology, and assume AI will amplify whichever practice it touches.

Continue Exploring