The Great Game Of Business By Jack Stack

How to Actually Implement Open Book Management Without Breaking Your Company

The Great Game of Business By Jack Stack is often sold as a cultural transformation tool, but in practice it's really just a financial literacy program wrapped in a transparency framework. You teach employees how to read a profit and loss statement, you share key business metrics openly, and you tie bonus payouts to unit-level financial performance. That's it. The magic isn't in the concept. It's in the execution, and most companies mess up the execution. I spent about eighteen months rolling this out at a mid-size manufacturing operation. We had roughly 140 employees across three departments, and the initial P&L education sessions went poorly for the first four weeks. People would show up, stare at a spreadsheet, and mentally check out. Here's what worked after that period of failure. Stop using corporate consolidated financials. That's the first and most important mistake people make. A consolidated P&L tells your assembly line workers absolutely nothing about their daily decisions. Stack's original approach at Spinergy was to break financials down to the cash unit level. Each self-contained operational unit gets its own P&L. In our case, we split the floor into three cells. Each cell had its own revenue attribution, material costs, labor costs, and overhead allocation. When you give a team a P&L that reflects their actual slice of the business, suddenly the numbers mean something.

Teach financial literacy in 90-minute sessions, twice a month, for six months minimum. One session is not enough. I watched a group of warehouse supervisors finally connect the dots between overtime hours and margin compression during week seven of the program. They had been working unauthorized overtime for months because nobody knew it was eating into their unit's profitability. Once they could see it on their own P&L, they started managing their own scheduling. That's the whole point. The numbers need to drive behavior, not sit in a binder on a breakroom shelf. Implement the GGP dashboard, and keep it to five metrics maximum. Most people I've seen overcomplicate this. They track twelve different KPIs and nobody pays attention to any of them. Pick five numbers that directly reflect unit performance. Revenue per unit, cost of goods sold, labor efficiency, scrap or waste rate, and days sales outstanding if you handle your own receivables. Post these updated weekly. Not monthly. Weekly. People lose interest if the data is stale. I've seen teams stop caring within two weeks of switching from weekly to monthly updates on the shop floor dashboards. The edge case that almost killed our rollout was departmental sabotage. Our maintenance supervisor refused to put his team's costs into the unit P&L system. He argued that maintenance was a shared service and shouldn't be allocated to production cells. He was partially right. Flat allocation rates created some ugly distortions where a cell with older equipment looked worse than a cell with newer equipment, even though both were performing identically in terms of output quality and on-time delivery. The workaround was to track maintenance costs separately and show them as a line item above the unit P&L rather than allocating them downward. It made the numbers fairer and he came around. Fairness matters more than accounting purity in these situations.

Bonus structures tied to unit performance need a floor and a ceiling. Without a floor, people get demotivated when the unit hits a rough patch through no fault of their own. Without a ceiling, you create perverse incentives where teams will cut corners on safety or quality to push their numbers up. We set our floor at 70 percent of target performance triggering a proportional but reduced bonus, and our ceiling at 130 percent. Beyond that, bonuses rolled up to a company-level pool instead of scaling infinitely. This prevented the kind of gaming behavior where people would dump maintenance work into the next sprint just to keep their current period metrics clean. Here's something most guides don't mention. Your middle managers will resist this more than anyone else. The Great Game of Business By Jack Stack removes the information asymmetry that middle management has traditionally used as a source of power. When the janitor can read the same P&L as the VP of operations, the middle manager's role shifts from gatekeeper to coach. That's a harder shift than people anticipate. I had two directors threaten to leave during the first quarter of implementation. They framed it as philosophical disagreement. It was really about losing control of the narrative around company performance. The cash share or profit-sharing component needs to be calculated and communicated in real time or close to it. Quarterly payout cycles kill motivation. People forget what decision they made three months ago. When we switched to a monthly calculation with quarterly actual payouts, engagement on the dashboard went up measurably. Monthly calculations with quarterly payouts gave people frequent feedback while keeping the actual cash flow manageable for the business. Don't try to do weekly payouts unless your accounting system can handle it without extra headcount.

Training materials are widely available online. The original GGP curriculum from the Richard Rumelt and Jack Stack team has been adapted by various facilitators over the years. You don't need to buy anything proprietary to start. The core materials are essentially financial literacy workshops built around actual company P&L statements. Free templates exist for unit-level P&L structures and dashboard layouts. What you can't get for free is the discipline to run the sessions consistently and the political will to share information that some executives believe they should hoard. The main bottleneck that causes failure is underinvestment in the training phase. People treat the financial literacy piece as optional prep work before the real program starts. It's not optional. It's the foundation. If your people can't distinguish between gross margin and net margin, or they don't understand what depreciation does to a P&L, then showing them unit-level financials is just showing them numbers they can't interpret. Budget at least forty hours of formal training per employee before you expect behavioral change. That's what our experience showed. We tried to compress it into twenty hours once and regressed back to old behaviors within six weeks. Another counter-intuitive finding is that smaller units tend to work better than larger ones. There's a temptation to keep unit sizes manageable for administrative simplicity, but the psychological connection between individual action and financial outcome weakens significantly above forty to fifty people per unit. People in a unit of thirty can see how their daily decisions move the needle. People in a unit of eighty feel like cogs. If your organization is large, break it into more units even if it means some of them are smaller than you'd prefer administratively.

This approach does not work in environments where revenue is entirely unpredictable or where individual contribution to financial outcomes is genuinely impossible to isolate. Service businesses with long sales cycles, project-based firms where revenue recognition spans quarters, and organizations where product pricing is set entirely at the corporate level with no unit-level discretion will struggle to make the framework meaningful. In those cases, you can adapt the principles by focusing on cost-side metrics and operational efficiency measures rather than revenue-linked bonuses, but the motivational impact is noticeably weaker. That's a limitation worth acknowledging before you commit resources to implementation.