Key Takeaways
At $7 million, Swan needed an operating system, not another pep talk
A plateau became a people problem. Swan Services, a fictional technology firm, had reached $7 million, then growth stalled. Revenue rose just 1.5 percent against a 14 percent plan, profits fell, clients slipped away, and leaders blamed forces beyond their control. At a disastrous meeting, Eileen’s data presentation led her best sales leader to consider resigning, while cofounder Vic challenged how they ran the company. The breakdown exposed more than poor sales. Swan lacked shared direction, clear ownership, useful measures, a disciplined way to resolve problems, consistent processes, and dependable execution.
A complete operating system. Eileen brought in an implementer to teach EOS, the Entrepreneurial Operating System. Its six connected areas address vision, people, data, issues, process, and execution. The point is not to bolt on a strategy in isolation. It is to make these basic management functions reinforce one another, aiming for strength across all six rather than perfection in any one.
The fable’s useful shift is from searching for one culprit to seeing a connected system. A sales slump, for example, may reflect fuzzy positioning, overloaded delivery teams, weak customer retention, or all three. This resembles systems thinking: outcomes often emerge from interactions among parts, not from a single bad actor. The framework’s simplicity is an advantage because leaders can remember and use it. Its risk is treating the categories as a checklist rather than investigating how problems actually travel across the organization.
Put one written destination in every leader’s hands
Replace six competing visions. Swan’s leaders each carried a different picture of the company’s future, even though they believed they had a plan. They used the V/TO, or Vision/Traction Organizer, to record the organization’s identity, market focus, long-range ambition, nearer-term picture, and execution priorities. The team first debated wildly different targets, from $30 million to $100 million in revenue. Later, as it learned more, it revised its long-range ambition to $25 million with a 20 percent profit margin. A written vision made disagreement visible and gave the team a way to make an actual choice.
Make the plan usable. The organizer connects future direction to practical goals for the year and the next quarter. It is reviewed and revised, not treated as a ceremonial plan that goes stale after a retreat. Its value is shared understanding: leaders can explain not only where the business is headed, but what they are doing now to get there.
A shared plan acts like a common map: it reduces the time teams spend discovering that they have been using the same words for different destinations. The important feature is not the document itself, but the repeated conversation around it. The Swan example also illustrates a healthy distinction between consistency and stubbornness. A long-range target should create focus, but new evidence can justify changing it. Without that permission, alignment can become group loyalty to an outdated ambition.
Design seats for the work before assigning people to them
Separate structure from biography. Swan’s leaders first mapped the functions the company needed, then assigned people to those roles. Their Accountability Chart clarified the responsibilities and reporting relationships for each seat. This prevented them from designing the company around whoever happened to hold a job already. It also exposed the confusion created when Eileen and Vic both tried to influence sales leadership. The team ultimately clarified the difference between Vic’s big-picture, relationship-focused visionary role and Eileen’s integrator role, which coordinates daily operations and resolves cross-functional conflicts.
Match strengths to responsibilities. The chart also exposed that Evan was overwhelmed as head of operations but was strong at leading developers. He moved into a role better suited to his abilities while Swan hired a new operations leader. The lesson is not that every company needs identical titles, but that important work needs a clear owner.
This is a decision-rights problem as much as an organization-chart problem. When several people believe they own the same outcome, teams can mistake constant consultation for collaboration and leave hard choices unresolved. Clear ownership can reduce that ambiguity while still allowing broad input. The approach needs care, though: one accountable leader should not mean one isolated decision-maker. Cross-functional consequences still require discussion, especially when sales promises affect delivery or staffing.
Track a few weekly signals instead of drowning in reports
Measure the business in time to act. Swan replaced sprawling reports with a Scorecard, a short set of weekly numbers showing trends over thirteen weeks. The goal was to include roughly five to fifteen measures, with a named person responsible for each. Leaders distinguished earlier indicators from final outcomes. For sales, initial prospect meetings can provide a warning about future contracts, while revenue reports what has already happened. The team set a target of twelve qualified initial meetings each week, reasoning that this activity could support two new customers a month.
Use numbers to raise questions. The Scorecard did not replace monthly or quarterly financial statements. It gave the leadership team a regular view of operating activity, from new leads to delayed projects and invoice corrections. When a number went off plan, the team added it to the issues list rather than derailing the meeting with an immediate debate.
A weekly Scorecard resembles a feedback control system: observe conditions often enough to adjust before a small deviation becomes a crisis. Leading indicators are especially useful when they connect plausibly to desired outcomes. But measures are proxies, not reality. If employees are rewarded for meeting a number without regard to quality, they may optimize the measure instead of serving customers. A good dashboard therefore supports judgment and investigation; it does not substitute for either.
Make meetings solve causes, not rehearse symptoms
Give the meeting a job. Swan’s leaders initially rated their internal meetings an average of four out of ten. They adopted a weekly Level 10 Meeting, a fixed, ninety-minute agenda designed to keep routine updates brief and reserve time for problems. Leaders quickly reviewed numbers, quarterly priorities, customer and employee concerns, and short action items. The central work was IDS: identify the real issue, discuss it openly, and agree on a solution or concrete next step.
Stop reopening old arguments. Swan’s executives had spent hours revisiting client losses and operational failures without reaching lasting decisions. IDS required them to find root causes before discussing remedies. When the team could not agree after hearing everyone’s view, Eileen, as integrator, made the call. That replaced a search for unanimity with a clear decision and an owner, while preserving space for dissent.
The meeting design addresses a common group failure: conversation can feel productive while leaving the underlying problem untouched. Separating quick reporting from problem-solving also protects attention from being consumed by whichever update is most dramatic. The discipline works only if people can raise inconvenient facts without retaliation. A fixed agenda may create order, but it cannot manufacture trust; leaders have to model candor and keep disagreement focused on the work rather than on personal worth.
Give the quarter a handful of owned, finishable priorities
Turn ambition into a ninety-day bet. Swan initially generated thirty-seven possible priorities, then narrowed them to five company Rocks for the quarter. Rocks are the few important outcomes a company or individual commits to completing within roughly ninety days. Each is made specific, measurable, realistic, and time-bound, and one person owns its completion. The team also set individual Rocks, while limiting the total so daily emergencies would not crowd out important work.
Treat misses as information. In Swan’s first attempt, leaders completed only 52 percent of their Rocks. They had chosen too many, started too late, or defined the work poorly. The system’s aim is around 80 percent completion, not a perfect score. A Rock that is almost finished still counts as unfinished, because fuzzy completion rules weaken accountability. The next quarter should reflect what the team learned about capacity and planning.
Quarterly priorities create a useful boundary around attention. They turn an endless list of worthwhile projects into a small set of explicit choices, making it easier to say no to work that is merely urgent. The ownership rule matters because shared responsibility can conceal inaction. At the same time, a low completion rate should prompt investigation, not automatic blame. Repeated misses may signal poor estimates, unexpected dependencies, or unrealistic workloads, not simply weak commitment.
Filter growth through the work your company does unusually well
Define the work worth pursuing. Swan clarified its Core Focus by identifying what it cared about and what it could do especially well: helping clients solve genuine business problems with appropriate technology. The definition gave the company a test for new opportunities. It also revealed that staff augmentation, where clients primarily rented developers rather than buying a solution, distracted operations and often fell outside that focus.
Focus changes marketing and sales. Swan defined its ideal customer profile, concentrated proactive sales efforts in the upper Midwest, and developed three differentiators to explain why the right prospects should choose the firm. It also created a visual account of the client experience. The company did not immediately abandon every existing staff-augmentation client. It limited the work, then found a specialist partner to serve those customers while Swan focused on better-fitting projects.
A clear niche is a resource-allocation tool, not just a slogan. It helps a small firm spend scarce sales and delivery capacity where it can build expertise and stronger relationships. The difficult test is whether leaders will turn down revenue that does not fit. Swan’s gradual transition shows how focus can be applied without treating every exception as an emergency. A niche should sharpen choices, not become an excuse to ignore a genuinely attractive adjacent opportunity.
Document essential workflows, then make consistency everyone’s job
Write the repeatable core. Swan’s operations leader, Evan, had been trying to finish a comprehensive procedures manual for years. The system instead asked the team to identify its Core Processes, document their major steps at a high level, simplify them, and make them available for employees to follow. The book calls this a 20/80 approach: capture the essential portion of a process that produces most of the useful results, rather than attempting to record every possible detail.
Make the handoffs visible. Swan named its key processes across marketing, sales, delivery, finance, and customer care. This gave sales and operations common language for discussing where client expectations were being lost. Documenting the process also created a basis for training and measurement. A procedure that sits untouched in a manual changes little; the aim is a shared way of working that teams can use and improve.
Standard work preserves organizational learning. When critical steps live only in one experienced employee’s head, the company becomes vulnerable to turnover and inconsistent service. The 20/80 principle sensibly resists documentation for its own sake. Still, a process should not become a script that blocks judgment. The strongest designs specify essential handoffs and quality standards while leaving room for employees to adapt when a customer’s situation genuinely differs.
Make cultural fit visible, specific, and discussable
Turn values into observable behavior. Swan identified a small set of Core Values by studying employees its leaders considered especially effective. The People Analyzer let them assess whether a person consistently demonstrated those values and whether the person understood, wanted, and could perform the responsibilities of a role. The book abbreviates that role-fit test as GWC. Together, these tools distinguish a capable person in the wrong seat from someone whose behavior conflicts with the company’s culture.
Make expectations fair and clear. When controller Carol fell below Swan’s values standard, Eileen brought specific examples to a private coaching conversation and asked whether Carol would work to change. The company used a staged warning process rather than expecting employees to guess what leaders wanted. Carol made an effort but eventually left. The framework also helped Swan recognize when someone, such as Evan, fit the culture but belonged in a different role.
Explicit standards can make feedback less arbitrary: an employee can respond to concrete behavior more readily than to a vague label such as “bad attitude.” The method also separates competence from cultural alignment, which are often blurred in performance reviews. Its danger is that values scoring can become a tool for enforcing similarity or silencing disagreement. Fair use requires behavioral evidence, consistent standards, and a real distinction between violating a value and challenging a leader’s preferred approach.
Build an operating rhythm that gives founders their lives back
Execution changed the founders’ days. Swan used weekly leadership meetings, quarterly planning sessions, and an annual review to refresh priorities, assess results, and resolve accumulated problems. Its first quarter was uneven, but its leaders gradually improved their planning and follow-through. By year-end, the company had reached about $7.6 million in revenue and 6 percent net profit, exceeding its $7.25 million and 5 percent targets. It also scored 81 on the book’s organizational checkup.
The gain was personal, too. Eileen had been working twelve to fourteen hours a day and missing family events. After Swan clarified roles, hired leaders, and delegated work, she reported working under fifty hours most weeks, attending her children’s activities, and taking a two-week vacation. The narrative’s measure of success is not growth alone. It is a company that can make progress without requiring its founder to personally absorb every unresolved problem.
The outcome completes the book’s argument: management systems matter when they change both organizational performance and the founder’s dependence on constant intervention. The case is a composite business fable, not a controlled demonstration that EOS caused each result. Still, the mechanism is legible: clearer ownership frees attention, regular review catches drift, and delegation reduces bottlenecks. Leaders should judge the system by whether those effects appear in their own context, not by copying Swan’s targets.
Analysis
Get A Grip is a business fable built around a practical management system for small and midsize entrepreneurial firms. Its narrative arc moves from a painful leadership rupture to a disciplined operating cadence, making implementation feel social and emotional rather than merely procedural. Eileen and Vic are not just learning tools. They are renegotiating authority, trust, work, and the friendship that founded their company. That drama is central to the book’s value: it shows why systems fail when leaders will not confront their own habits.
EOS can be understood as an organizational feedback loop. A written direction sets the destination, roles and measures reveal responsibility and performance, regular meetings expose deviations, and issue-solving converts information into action. Quarterly priorities limit competing demands, while process documentation helps repeat what works. The pieces reinforce one another. A Scorecard without decision-making is passive reporting; goals without ownership are wishes; accountability without trust can become surveillance.
The fable also places limits on its own evidence. Swan is fictional, even though the authors say its situations draw on many client experiences. Its successful trajectory illustrates a plausible mechanism, but cannot establish that the system alone produces revenue growth, higher profits, or better family life. The model assumes leaders are willing to clarify roles, measure work, and make difficult personnel decisions. In some settings, a strong emphasis on cultural fit and singular ownership could entrench managerial bias or narrow dissent. These tools need transparent standards and room for responsible disagreement.
The book’s most transferable insight is therefore not that every company should adopt every EOS tool unchanged. It is that entrepreneurial growth creates coordination costs that personal effort cannot solve indefinitely. Leaders need a shared plan, a small number of visible commitments, and a recurring forum where problems lead to decisions. The system is useful when it reduces confusion and dependence on founders, while remaining adaptable to the organization’s people, market, and actual constraints.
Review Summary
Get a Grip receives mostly positive reviews, with an average rating of 4.21 out of 5. Readers appreciate its practical approach to implementing the Entrepreneurial Operating System (EOS) through a business fable. Many find it helpful in understanding EOS concepts and their real-world application. Some praise the storytelling, while others find it simplistic or clichéd. The book is particularly valuable for business owners and leaders looking to improve their operations, though some small business owners find it less relevant. Overall, it's considered a useful companion to "Traction" for those interested in EOS implementation.
People Also Read
Glossary
EOS
Entrepreneurial management systemEOS, short for the Entrepreneurial Operating System, is the integrated set of management practices presented in the book. It helps a leadership team clarify its vision, assign responsibility, track operating data, surface and solve issues, standardize essential processes, and maintain execution through recurring priorities and meetings.
V/TO
Vision and execution organizerThe Vision/Traction Organizer is a compact planning document that records a company’s identity, focus, long-range target, marketing approach, future picture, annual goals, quarterly priorities, and unresolved issues. Leaders use it to align around both the company’s direction and the practical work required to advance toward it.
Six Key Components
Six areas of organizational strengthThe Six Key Components are the connected areas EOS asks a company to strengthen: Vision, People, Data, Issues, Process, and Traction. The model treats weakness in any one area as a possible constraint on overall performance. The goal is not perfection, but a healthy level of strength across all six.
Accountability Chart
Structure and role mapAn Accountability Chart describes the functions a company needs, the main responsibilities attached to each role, and who owns each seat. Unlike a conventional chart that may mainly show reporting lines, it is built by first deciding what the business requires, then assigning people to those responsibilities.
GWC
Three-part role-fit testGWC stands for gets it, wants it, and has the capacity to do it. It is a test of whether someone understands a role’s demands, genuinely wants the work, and has the ability and experience to perform it. In the book’s framework, a person needs a yes on all three dimensions to fit a seat.
People Analyzer
Values and role assessmentThe People Analyzer is a tool for assessing whether employees demonstrate an organization’s Core Values and fit the responsibilities of their roles. It makes expectations more explicit by combining ratings of values-related behavior with the GWC role-fit test. The authors present it as a prompt for specific, evidence-based conversations, not as a substitute for them.
Scorecard
Weekly operating measuresAn EOS Scorecard is a short list of weekly numbers used to monitor the health of a company or team. It commonly includes a few measures with named owners and a thirteen-week view of recent performance. The purpose is to spot emerging problems early and bring off-track results into a discussion, not replace financial statements.
IDS
Issue-solving sequenceIDS means Identify, Discuss, and Solve. Teams first clarify the underlying issue, then discuss it openly, and finally agree on a decision or plan intended to address it. In EOS meetings, the method is used to prevent teams from repeatedly debating symptoms without assigning action or resolving the cause.
Rocks
Quarterly priority commitmentsRocks are the small number of important outcomes a company or individual commits to completing in a roughly ninety-day period. Each Rock should be clearly defined, given one accountable owner, and reviewed regularly. The term emphasizes limiting priorities so essential work is less likely to disappear beneath daily demands.
Level 10 Meeting
Structured weekly leadership meetingA Level 10 Meeting is a recurring EOS meeting with a set agenda for brief updates, priorities, action items, and issue-solving. The meeting is designed to start and end on time and to reserve substantial attention for IDS. Participants rate the meeting at the end, using the score to identify ways to improve its usefulness.
Core Focus
Purpose and business nicheCore Focus describes an organization’s enduring purpose and the particular work it is especially well suited to perform. EOS uses it as a filter for decisions about customers, opportunities, and services. A clear focus helps a company avoid spreading scarce resources across work that generates revenue but distracts from its strongest capabilities.
Core Processes
Essential repeatable workflowsCore Processes are the handful of recurring workflows that make a business operate, such as sales, service delivery, finance, or customer care. EOS recommends naming and documenting their major steps at a high level, simplifying them, and training employees to follow them consistently rather than trying to record every possible detail.
Meeting Pulse
Recurring meeting rhythmThe Meeting Pulse is EOS’s schedule of recurring meetings, including weekly team meetings and quarterly or annual planning sessions. The rhythm gives leaders regular opportunities to review progress, adjust priorities, and solve issues. Its purpose is to keep communication and execution continuous rather than relying on occasional crisis meetings.
Delegate and Elevate
Shift work toward strengthsDelegate and Elevate is a method for reviewing a leader’s workload and identifying tasks to transfer to others. The leader lists routine responsibilities, considers what they enjoy and do well, and delegates work that is a poor use of their strengths where appropriate. The aim is to improve focus and reduce bottlenecks, not to discard necessary work.
FAQ
What's Get A Grip about?
- Entrepreneurial Fable: Get A Grip is an entrepreneurial fable that follows a fictional company, Swan Services, as it implements the Entrepreneurial Operating System (EOS) to overcome business challenges.
- Team Dynamics: The book emphasizes the importance of team health, accountability, and clear communication among leadership to drive the company towards its vision.
- Practical Tools: It introduces practical tools and frameworks like the Vision/Traction Organizer (V/TO), Accountability Chart, and Level 10 Meetings essential for business success.
Why should I read Get A Grip?
- Real-World Application: The book provides a relatable story that illustrates the real-world application of EOS principles, making it easier to implement these concepts in your business.
- Improves Leadership Skills: Readers can learn valuable lessons about leadership, team dynamics, and the importance of having a clear vision.
- Actionable Insights: It offers actionable insights and practical advice that can be immediately applied to enhance business operations and team performance.
What are the key takeaways of Get A Grip?
- Importance of Vision: A clear vision is crucial for guiding a company’s direction and ensuring team alignment, with the Vision/Traction Organizer (V/TO) being a key tool.
- Right People in Right Seats: Emphasizes ensuring team members fit the company culture and have the capacity to excel in their roles.
- Regular Check-Ins: Highlights the significance of regular check-ins, like Level 10 Meetings, to maintain accountability and track progress.
What is the Vision/Traction Organizer (V/TO) in Get A Grip?
- Strategic Planning Tool: The V/TO helps businesses clarify their vision and outline steps to achieve it, including Core Values and Marketing Strategy.
- Alignment and Communication: It serves as a communication tool that aligns the organization around a common vision.
- Regular Updates: The V/TO should be reviewed and updated regularly to reflect changes in the business environment and goals.
How does the Accountability Chart work in Get A Grip?
- Organizational Structure: The Accountability Chart visually represents the organization’s structure, detailing roles and responsibilities.
- Focus on Structure First: It emphasizes focusing on the structure rather than the people in roles for an objective assessment.
- Identifying People Issues: Helps identify people issues by assessing if individuals are in the right seats, prompting discussions about role fit.
What are Level 10 Meetings in Get A Grip?
- Weekly Check-Ins: Level 10 Meetings are structured weekly meetings designed to keep the leadership team aligned and accountable.
- Focus on Accountability: They emphasize accountability by requiring team members to report on their progress toward their Rocks (quarterly priorities).
- Issue Solving: The IDS (Identify, Discuss, Solve) process allows the team to address and resolve issues effectively.
What is the concept of "Rocks" in Get A Grip?
- Quarterly Priorities: "Rocks" are the three to seven most important priorities a company or individual must focus on each quarter.
- SMART Goals: Each Rock should be a SMART goal—Specific, Measurable, Attainable, Relevant, and Time-bound.
- Regular Review: Rocks are reviewed regularly during Level 10 Meetings to track progress and ensure accountability.
How does Get A Grip address team health?
- Building Trust: Emphasizes the importance of trust among team members as the foundation for a healthy team dynamic.
- Encouraging Conflict: Encourages healthy conflict as a means of addressing issues and making decisions without personal attacks.
- Commitment and Accountability: Once trust and conflict are established, team members can commit to decisions and hold one another accountable.
What are some best practices for implementing EOS from Get A Grip?
- Start with the V/TO: Begin by clearly defining your vision using the V/TO as the foundation for all other EOS tools and processes.
- Regular Meetings: Establish regular Level 10 Meetings to maintain accountability and track progress with a structured agenda.
- Focus on Team Dynamics: Prioritize team health by fostering trust, encouraging open communication, and addressing conflicts constructively.
What are the best quotes from Get A Grip and what do they mean?
- “Accountable means doing exactly what you say you’ll do.”: Highlights the importance of accountability in building trust and achieving results.
- “If you’re trying to delegate twenty hours worth of work each week, delegate it from the lower two quadrants.”: Refers to the Delegate and Elevate tool, encouraging leaders to focus on their strengths.
- “You have to have both.”: Underscores the necessity of having the right people in the right seats for organizational success.
How does Get A Grip illustrate the importance of having the right people in the right seats?
- Cultural Fit and Capacity: Emphasizes ensuring team members fit the company culture and have the capacity to excel in their roles.
- Objective Assessment: The Accountability Chart helps objectively assess whether the organization has the right structure to achieve its goals.
- Prompting Discussions: Identifies people issues and prompts discussions about role fit if someone is not performing well.
How can the tools in Get A Grip be applied to enhance business operations?
- Vision/Traction Organizer (V/TO): Clarifies vision and outlines steps to achieve it, aligning the organization around common goals.
- Accountability Chart: Clarifies roles and responsibilities, ensuring the right people are in the right seats.
- Level 10 Meetings: Maintain accountability and track progress, focusing on resolving issues effectively.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.