Key Takeaways
Finish the few important tasks, not the endless list
The queue never empties. Arnhym’s central claim is that work arrives faster than anyone can complete it. The trap is letting the nearest deadline decide what matters, while difficult, consequential work keeps slipping. Finishing does not mean clearing every task. It means choosing the work that matters most and carrying it through, even as new demands arrive.
Choose again before evening. Arnhym recommends pausing around 4 p.m. to revisit the day’s priorities and identify what still must be done. That reset helps distinguish meaningful unfinished work from busywork that can wait, be delegated, or be dropped. His own five-year delay in writing this book illustrates the problem: he knew the task mattered, but kept postponing the commitment to complete it.
The distinction between a full task list and a finished priority is a useful corrective to the modern habit of treating visible activity as progress. It also resembles attention management: every new request competes for limited working memory, so priorities need deliberate protection. Still, a late-day reset cannot solve chronic overload by itself. If essential work repeatedly rolls over, the real issue may be staffing, unclear goals, or an organization that rewards responsiveness more than completion.
Shrink the impossible into steps, and keep another route ready
One obstacle at a time. As Pasadena Chamber of Commerce CEO, Arnhym proposed moving the Army-Navy game from Philadelphia to the Rose Bowl. The 1983 event meant transporting nearly 10,000 cadets and midshipmen across the country, arranging lodging and meals, and raising about $6 million. His team faced a date change, a bankrupt airline, a rain-soaked field, and a goat that could not be brought into the country. Each problem required a workable alternative, not a retreat from the whole undertaking.
A logistical triumph, with a cost. Host families housed about 8,000 students, while roughly 2,000 stayed in hotels. More than 80,000 people attended. Yet a post-game investigation caused sponsors to withhold pledges, leaving bills unpaid even after the project was cleared. The lesson is persistence with contingencies, not the fantasy that effort guarantees a clean win.
The Rose Bowl story makes project management tangible: a vision becomes real through dependencies, schedules, transportation, funding, and contingency plans. This resembles reliability engineering, where teams anticipate failure points rather than assume the first design will hold. The financial aftermath matters as much as the attendance. A project can meet its operational objective and still fail financially, so leaders need separate measures for execution, impact, and solvency. Planning for a Plan B should include the funding model, not only the logistics.
A decision is a choice backed by commitment and action
Choosing is only the opening move. Arnhym distinguishes selecting a goal from deciding to pursue it. At nine, he resolved to attend West Point. His first application left him as the alternate, and the principal appointee took the place. Rather than abandon the goal, Arnhym improved his grades and fitness, pursued several appointment routes, and applied to civilian universities as alternatives. The following year, he earned a principal appointment to West Point and had other acceptances too.
Commitment makes a choice operational. In his account, a decision is not complete until a person accepts responsibility for acting on it. That requires discipline, preparation, and a willingness to move despite uncertainty. He also stresses that execution matters: a decision may not prove perfect, but careful, energetic execution gives it a chance to work.
This account captures a valuable difference between preference and intention. In behavioral science, people often act more reliably when goals are translated into concrete commitments and next steps. Yet commitment can become rigidity if it is treated as proof that the original plan must continue at any cost. The useful complement is a pre-agreed review point: stay committed to the purpose, while remaining willing to change the method when evidence shows it is failing.
Make accountability clear before missed deadlines become surprises
Name the expected result. Arnhym argues that people cannot reliably deliver what they have not been told to deliver. A job description, clear priorities, regular conversations, and a way to surface questions make expectations visible. His Friday report asks staff to identify next week’s five priorities, report what was completed or missed, and name where they need help. That gives a manager time to resolve confusion before Monday, rather than discovering a problem after a deadline passes.
Inspect, including yourself. Arnhym checks twice daily whether he is doing work someone else should own and what he failed to complete. He treats a missed task as a prompt to investigate: Was direction unclear? Was training missing? Did the manager create the blockage? Persistent underperformance may require a personnel change, but firing should not replace communication, coaching, and fair expectations.
The reporting routine turns accountability into a feedback loop rather than a courtroom. That distinction matters: frequent, specific feedback can reveal obstacles while there is still time to respond. Clear measures also need judgment. When employees are evaluated only on completed counts, they may optimize the report rather than the work, or hide uncertain news. Good accountability therefore tracks outcomes and quality, while making it safe to disclose delays early and requiring leaders to own the conditions they control.
Delegate authority, not just chores, or you become the bottleneck
Give people room to own outcomes. During the Orlando centennial celebrations, Arnhym delegated events to committee chairs and made sure they received public credit. The work continued while he took a new job in California. His point is that delegation means transferring enough responsibility and authority for another person to make progress, not simply assigning tasks that still require the leader’s approval at every turn.
Build capacity, not dependence. In one example, he allowed trusted finance chiefs to approve checks of $500 or less. That reduced routine decisions on his desk and signaled confidence in their judgment. He also argues that leaders should involve their teams in strategic planning, so employees help shape the plan rather than merely receive it. Training and clear boundaries make this autonomy safer and help people grow into larger roles.
Delegation is a form of organizational design: decisions should sit close enough to the relevant information to be made well and quickly. It also develops capability through practice, not just instruction. The risk is that empowerment without adequate training, resources, or escalation rules can feel like abandonment. Leaders should clarify which choices are delegated, which constraints matter, and when an issue should be brought back. Authority is meaningful only when people have the tools and backing to use it.
Protect time for priority work before interruptions claim it
Control the doorway to attention. Arnhym describes workdays filled with calls, meetings, and requests that can derail the priorities set in the morning. He arranged his email so it arrived only when he chose to check for messages, creating a gate he controlled instead of being interrupted continuously. He also used quiet time before others arrived and set a firm end time for meetings, sometimes reserving a few minutes for unexpected issues.
Make the schedule visible. His weekly staff report and late-afternoon review help identify what is unfinished and what must happen next. He also protects personal time, including regular weekend activities and evening conversations with his wife. The point is not to reject every interruption. Some people and decisions deserve immediate attention. It is to distinguish genuine urgency from a system that lets every request take over the day.
Interruptions carry a hidden cost: even a brief diversion can leave a person reconstructing the task they were doing. Batching routine messages and setting meeting limits can protect the attention needed for complex work. But strict boundaries can also make a leader inaccessible when a team needs help. The stronger design is selective availability: identify which issues merit immediate interruption, provide a clear route for them, and schedule the rest for a predictable response.
Turn introductions into relationships by listening and following through
A business card is not a relationship. Arnhym warns against treating networking events as competitions to collect contacts. He suggests noting something useful about a new contact, giving the conversation proper attention, and following up afterward. His own approach was to ask about the other person’s concerns and interests before describing his own work. He also recommends knowing the gatekeepers who manage access to busy decision-makers.
A conversation opened a door. At a gathering, Arnhym introduced himself to Yankees owner George Steinbrenner and praised the team’s support for West Point. When Steinbrenner asked how he could help, Arnhym explained that he was seeking sponsorship for a magazine feature about the academy. The Yankees agreed to sponsor it. The exchange worked because it combined attention, a relevant connection, and a clear request rather than a pile of business cards.
The book treats relationships as practical infrastructure: trust and familiarity can make cooperation, referrals, and access possible. This aligns with the idea of social capital, the value created by durable networks of mutual recognition and help. The caution is that listening should not become a disguised sales technique. If every question is merely a route to a pitch, people sense the calculation. Strong professional relationships are reciprocal, and they remain valuable even when no immediate transaction follows.
Change the system causing failure before blaming the people in it
Look for the cause beneath the behavior. At Fort Ord, Arnhym noticed that soldiers returned from training to find dinner sitting on steam tables for over an hour. Many left the base to eat, drank before dinner, and appeared in arrest reports. Rather than focus only on punishment, he changed the meal schedule so food was served shortly before the soldiers arrived. More soldiers ate on base, and the arrest statistics improved.
Adapt to the people and setting. Arnhym also describes moving from Army life into business, where habits that fit military culture did not always fit civilian offices. His advice is to observe the environment, listen, and adjust instead of demanding that a new culture accommodate old routines. When changing careers, he looked for skills that could transfer rather than assuming his previous title would do the work for him.
The Fort Ord example is a compact lesson in systems thinking: behavior often reflects the incentives and conditions surrounding it. Improving the meal addressed a plausible cause instead of merely escalating discipline. That approach is powerful, but it should not erase individual agency; the book does not establish that every incident had the same explanation. Good diagnosis tests a structural hypothesis, observes the result, and remains open to other causes if the pattern persists.
Treat loyalty as a promise you must keep earning
Past loyalty is not a blank cheque. Arnhym recounts buying more than a dozen cars over two decades from one dealer. After a highway accident left him without a usable car, he hoped the dealership would help him find a replacement. The staff did not coordinate an answer. A competing dealer understood the problem, located the model he wanted in Texas, and delivered it within days. Arnhym switched brands, despite decades of loyalty to the original one.
Keep commitments in ordinary moments. He argues that trust grows when people show up as promised, communicate promptly when plans change, and offer a practical alternative. The same principle applies inside an organization: leaders expect loyalty from employees, but must support them, recognize good work, and help them improve after mistakes. Loyalty is not demanded into existence; it is built through repeated, observable acts of reliability.
The dealership story shows why loyalty is better understood as a relationship than a stored balance. Years of past purchases did not protect the customer when a new need arose; attentive service did more to earn future business than automated outreach. This resembles service recovery, where a company’s response to a failure can shape trust more than routine transactions. Still, loyalty cannot mean unconditional allegiance. Customers and employees need the freedom to leave when promises are repeatedly broken.
Analysis
This is a leadership manual built from a career memoir, with the relocation of the Army-Navy game serving as its central case study. Its most useful argument is not that every task should be completed. The workday keeps generating new tasks, so the real discipline is selecting consequential work, committing to it, and organizing people and time around its completion. The book turns that principle into routines: a late-day priority review, weekly reports, explicit decision rights, direct communication, and attention to relationships.
The memoir gives those routines force. Moving thousands of students across the country requires far more than enthusiasm; it demands coordination across institutions, vendors, volunteers, transportation, housing, and public agencies. The project’s mixed outcome makes the story more instructive. The game drew a large crowd and advanced the academies’ western reach, yet the investigation disrupted pledged funding and left substantial bills unpaid. Success therefore depends on which outcome is being measured. Execution, public benefit, reputation, and financial sustainability can diverge.
Arnhym’s military background supplies memorable language for discipline, accountability, and contingency planning. It also creates a limitation: business is not combat, and the metaphor can make urgency sound more justified than it is. Civilian organizations depend on consent, learning, and trust; pressure alone can produce silence rather than performance. The book’s strongest examples soften that risk by asking leaders to listen, train people, delegate real authority, and redesign bad systems instead of reaching first for blame.
The advice is most effective as a set of practices to test, not universal laws. A fixed review time or weekly report may help one team and burden another. The underlying questions travel better: What matters most? Who owns the next step? What information or authority is missing? What evidence would show that the plan is working? In that sense, finishing is not simply personal grit. It is the result of clear choices, capable collaborators, protected attention, and honest feedback.
Review Summary
Glossary
MILES
laser-based training systemAn acronym for Multiple Integrated Laser Engagement System, an Army training system described by Arnhym. Weapons firing blank ammunition trigger eye-safe lasers, while sensors worn by soldiers or attached to equipment register hits. A sensor can signal that a soldier has been hit, making exercises more realistic than training with blanks alone.
H and I
harassing and interdicting fireA military tactic Arnhym describes as firing into an area to discourage enemy forces from approaching. He recounts using the idea of unpredictable deterrence in Vietnam and adapting it for nighttime patrols at Cam Ranh Bay, where crews threw grenades into the water to deter underwater attackers.
Zip Code Commanders
local host-family coordinatorsArnhym’s name for volunteers assigned to gather host families at designated schools and shopping centers around Los Angeles. For the 1983 Army-Navy game, they helped coordinate the distribution of cadets and midshipmen arriving at different airports, reducing confusion during transport and matching students with their hosts.
weekly to-do report
weekly priorities and reviewA short report Arnhym used to review employees’ work and prepare for the next week. It lists the employee’s five leading priorities, what was completed or left unfinished, and what help or guidance is needed. The report makes expectations visible and helps managers identify obstacles before they become missed deadlines.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.