Key Takeaways
Fix the tiny work failures that quietly tax every day
Small costs compound. Gilkey uses “broken printer” for recurring, fixable failures in how a team works. A faulty office printer can trigger repeated delays, interruptions, and frustration. In one organization, a therapist could not see patients for three months because she lacked an $8 computer cord. The object is minor; the work it blocks is not.
Look past blame. These failures are symptoms of team habits, the shared routines that shape how people coordinate. Gilkey argues that when work goes poorly, the first question should be how people are working together, not which person is defective. A team can often change its habits even when broader policies or structures are harder to move.
The printer is a useful diagnostic because it makes invisible organizational costs concrete. Repeated interruptions consume attention, while the frustration they create can make ordinary work feel needlessly hostile. This framing also redirects improvement from personality judgments toward observable processes. Its limit is important: a small annoyance can point to a much larger structural problem, and not every obstruction can be repaired by the team itself. The practical test is whether the team can change the cause within its authority, or needs to escalate it.
Change one visible habit before attempting to remake the culture
Move one stone. A team habit is a repeated, shared way of working, whether intentional or not. Gilkey recommends starting with one manageable change rather than launching a sweeping reform. A smaller effort can show results sooner, take less time to coordinate, and reveal who or what is resisting change. A month or two can be a useful sprint for a discrete habit.
Learn by acting. The first problem a team names may be a symptom, not the root cause. Repeatedly asking why, or mapping several possible causes with a fishbone analysis, can clarify what sits underneath. Still, teams need not solve the diagnosis perfectly before starting. The book’s eight areas for investigation are belonging, decisions, goals, planning, communication, collaboration, meetings, and everyday individual practices.
Small experiments work as both interventions and instruments of diagnosis. A team learns not only whether a new routine helps, but also which dependencies it exposes. That makes early progress valuable even when the initial diagnosis is incomplete. The caution is that “start small” should not become a reason to tolerate serious harm or defer changes requiring urgent attention. A sound experiment has a limited scope, a clear measure of improvement, and a route for raising problems that exceed the team’s authority.
Build belonging before demanding candor, coordination, or exceptional effort
Belonging creates context. Gilkey defines it as a sense of shared meaning, safety, and membership. When a project handoff goes wrong, a low-belonging team may blame people or add more participants. A connected team can treat the failure as a shared problem and work out what support or process was missing. Belonging helps people separate a work mistake from the value of the relationship.
Make it observable. Put values into daily behavior instead of leaving them on a wall. Learn what matters to teammates, make room for different ways of contributing, and recognize their work. Even small shared interests can build connection. Inclusion can also mean letting someone contribute in writing instead of requiring them to attend a meeting that does not suit their working style. Treat accidental friction as a “bump” before assuming hostile intent.
Belonging is not simply friendliness. Its functional value is that it gives people enough relational security to report problems, question plans, and repair mistakes. That makes it a condition for reliable performance, not a decorative extra. Still, warmth cannot replace fair workloads, clear authority, or protection from discrimination. A team should not interpret a request for belonging as an invitation to disclose private information. Inclusion is strongest when people have meaningful choices about how they connect and contribute.
Push routine decisions toward the people closest to the work
Reduce the bottleneck. Gilkey separates decisions into three levels: choices people can make without telling a manager, choices they can make but should report, and choices reserved for leadership. In a healthy team, the third kind should consume only a small share of a leader’s time. If routine work stops whenever the boss is busy, authority is too concentrated or expectations are unclear.
Make intent visible. A team member can explain what they plan to do and the reasoning behind it, allowing a manager to confirm, redirect, or ask questions without taking over the decision. A decision log can capture what was chosen and why. For consequential choices, time for discussion helps assumptions surface. For lower-stakes choices, teams can ask whether a decision is reversible and recoverable instead of treating every choice as permanent.
Delegation is often described as a matter of trust, but it also depends on risk design. People will not use authority if the penalty for a reasonable mistake is unpredictable. Clear decision boundaries and visible reasoning make autonomy safer for both the employee and the manager. The approach still needs exceptions: legal, safety, financial, and public consequences can justify tighter oversight. The goal is not to decentralize every choice, but to stop sending routine questions uphill simply because the organization has never clarified who may answer them.
Set goals teams can carry, then fund them with real capacity
Check readiness first. Readiness means a team’s capability to meet a goal. It depends on competence, available capacity, and habits that let people use both together. When leaders ignore readiness, teams may miss the goal or hit it through exhausting last-minute effort, which Gilkey calls “Dunkirk spirit.” Heroic recovery can hide poor planning and turn burnout into an expectation.
Make priority concrete. A “pull goal” connects work to meaning or motivation people already feel; a “push goal” relies more on pressure or reminders. Reframing a revenue target as helping more customers can make its purpose clearer. Each goal also carries TEAM costs: time, energy, attention, and money. If a team will not make room for those costs, the goal is not truly prioritized. Leave room for thoughtful failure so people can attempt work beyond the safest option.
This section links motivation to operational capacity rather than treating enthusiasm as a substitute for resources. A compelling purpose can help people persist, but it cannot create spare hours or remove conflicting assignments. Likewise, tolerating failure is useful only when failure produces learning and does not transfer preventable costs to customers or coworkers. Teams can strengthen the model by distinguishing an ambitious experiment from a poorly supported commitment. The useful question is not merely whether the goal inspires people, but whether the organization has changed the conditions needed to pursue it.
Make plans shared, usable, and easy to revise
Spread the planning skill. A plan needs a goal, a timeline, the people responsible, and a commitment to share, use, and update it. If only one person knows the plan, the team has a “ghost plan”: a private understanding that others cannot follow. In a military training example, a convoy faltered when its leaders were removed because the rest of the group did not know the objective or what to do next.
Leave room to adapt. Gilkey suggests planning only part of a project’s allotted time, leaving more time for execution, and avoiding a calendar filled to full capacity. Strategic work often takes longer than expected, so protect slack. Plans should guide action, not become untouchable instructions. When circumstances change, update the shared plan and tell the people affected rather than letting different versions quietly spread.
A plan is less a prediction than a coordination device. Its value lies in giving people a common reference point while preserving enough flexibility to respond to new information. The ghost-plan example shows why documentation alone is insufficient: a plan must be accessible, understood, and maintained. Too much detail can also create false confidence or burden the people doing the work. Useful plans distinguish firm constraints from adjustable methods, and make changes visible so that adaptability does not become an excuse for surprise.
Tune communication for clarity, not volume
Adjust four dials. Gilkey asks teams to examine communication frequency, amount of detail, breadth, and courage. Too many messages can bury important updates; too few leave colleagues chasing status. Excess detail can restrict judgment or overwhelm readers, while too little leaves them unable to act. Teams should also match the scale of the message to the scale of the problem and speak plainly enough to surface concerns.
Reduce avoidable work. Useful communication is proactive about progress, anticipates predictable questions, and stays concise when the message is transactional. Decide what needs attention now and what can wait for a regular update. Agree on which tools carry urgent messages, project discussion, reference documents, and task assignments. Team shorthand can save time, but it needs a shared explanation so new colleagues are not left decoding it.
Communication quality is better judged by whether the receiver can act than by how much the sender has said. This shifts attention from personal style to the design of the information flow: timing, audience, channel, and expected response. Concision is not always clarity, however. A short message can omit context, especially for new teammates or people outside the dominant workplace culture. Teams should test whether their conventions work for the least-informed recipient, not only for insiders who already know the shorthand.
Make teamwork visible enough to help without surveillance
Clarify the handoffs. Gilkey describes three functions in collaborative work: the doer produces it, the reviewer checks it, and the coordinator connects the work to teammates or stakeholders. One person may fill several functions, but naming them can expose bottlenecks. Clear task descriptions and shared project channels help prevent duplicated work, missing handoffs, and anxious status checks. Temporary project teams can form around a problem, with an owner responsible for assembling the right help.
Show progress, not busyness. Share drafts, explain important reasoning, and leave notes that help someone else pick up the work. Protect focus blocks, which Gilkey defines as roughly 90-minute to two-hour periods for concentrated work. When a problem appears, address the immediate issue, look for the process that caused it, and tell the team what happened. If a colleague falls behind, ask what support they need before taking work away.
Visibility is most valuable when it makes work easier to support, not when it measures presence. Shared artifacts and clear ownership can replace intrusive checking while giving teammates practical ways to help. This also makes collaboration more resilient when someone is unavailable. Yet transparency needs boundaries: constant draft reviews can interrupt concentration, and shared channels can become another flood of messages. Teams need a deliberate threshold for what to expose, when feedback is welcome, and which work deserves protected privacy until it is ready.
Treat every meeting as a costly purchase of attention
Count the real cost. A one-hour meeting can take about 90 minutes from each attendee once preparation and transition time are included. In Gilkey’s example, eight weekly meetings for eight people amount to 96 team hours each week. At an average of $50 per hour, that is about $4,800 weekly. Meetings are not free merely because no purchase order is required.
Make attendance purposeful. Give each meeting a facilitator, an agenda, and time to record next steps. Meetings can serve different jobs, including decisions, planning, brainstorming, relationship-building, reviews, or updates. Do not invite people merely so they can stay informed if a concise follow-up will do. When a meeting repeatedly compensates for a planning or communication failure, fix that underlying habit rather than adding another meeting.
Meeting math makes opportunity cost visible: the relevant comparison is not only the meeting’s expense, but also the focused work displaced by it. This is especially useful because organizations often scrutinize small purchases while treating employee attention as unlimited. Still, the calculation is an estimate, not proof that a meeting is wasteful. Coordination, shared interpretation, and relationship repair can be difficult to replace asynchronously. The right standard is whether the meeting’s purpose requires people to think together at the same time.
Run change as a shared experiment, not a leader's decree
Build alignment first. A team habit change needs someone to champion it and someone to manage the practical work. They may be the same person, but the roles differ: one builds support, the other keeps the project moving. Ask who might lose time, status, certainty, or a familiar way of working. Understanding that concern is not surrender; it helps the team shape a change that people can actually adopt.
Track what improves. Choose one small habit, define the pain it should reduce or the gain it should create, and check progress during an existing meeting. Work in short sprints within a monthlong or quarterlong effort. Expect resistance, unexpected effects, and benefits that become so normal they stop being noticed. If progress stalls, decide with the team whether to maintain the change, revise it, pause, or stop.
The political framing is valuable because shared routines are not neutral: people have invested effort and may depend on the current arrangement. Treating resistance as information rather than sabotage can reveal needs that a proposed solution overlooked. The experiment model also prevents a small process change from becoming a referendum on someone’s competence. But participation should not be confused with consensus on every detail. Teams need a way to hear objections, make a decision, and preserve accountability when the group remains divided.
Analysis
The book’s central move is to treat daily coordination as the working substance of organizational culture. Values and strategy matter, but they do not reliably change a team’s experience unless they are translated into repeated behaviors: who may decide, where plans live, how a meeting ends, and whether a colleague can ask for help without being punished. The “broken printer” image makes this argument memorable because it connects a small irritation to hidden costs in time, attention, and morale.
The strongest practical contribution is the combination of diagnosis with modest experimentation. Teams are encouraged to avoid blaming individuals too quickly, investigate root causes, and then change one habit at a time. This helps counter the common organizational reflex to announce a sweeping transformation while leaving everyday work unchanged. The model also connects operational performance to belonging, showing why trust and inclusion can improve the quality of information a team is willing to share.
There are limits to what local habit change can accomplish. A team cannot fix understaffing, discriminatory policies, unsafe conditions, or contradictory executive priorities through better agendas alone. The author acknowledges unequal power, but the practical emphasis on agency could still be misread as placing responsibility on workers who have little authority. Leaders must make clear which problems the team can solve and which require structural intervention.
Some recommendations are best treated as starting points rather than universal rules. Focus-block lengths, meeting cadences, and acceptable project completion rates vary across roles and industries. In safety-critical work, uncertainty and failure carry different consequences than in ordinary knowledge work. The durable principle is not a particular schedule or ratio. It is to make hidden costs visible, align responsibility with authority, and revise habits in response to evidence. Culture changes when those choices become dependable features of daily work, not when they remain polished statements on a wall.
Review Summary
Team Habits receives mostly positive reviews, with readers praising its practical advice on improving team dynamics and productivity. Many appreciate Gilkey's focus on collective habits and decision-making processes. Reviewers highlight the book's actionable frameworks, tools, and exercises for implementing positive changes in team behavior. Some readers found the content particularly valuable for managers and leaders. A few critics felt the book lacked depth or relied too heavily on subjective arguments. Overall, readers recommend the book for its fresh perspective on team building and organizational culture.
People Also Read
Glossary
Broken Printers
Fixable work frictionA metaphor for small, recurring failures in how people work together. The examples include a malfunctioning printer, confusing task channels, or missing access to a needed tool. Each problem may seem minor, but its repeated effects waste time, interrupt work, and wear down morale. The term encourages teams to repair everyday causes rather than dismissing them as trivial.
Workways
How work gets doneThe ways people work with one another, shaped by team habits, organizational policies, technology, regulations, and structure. Healthy workways support coordination; broken ones obstruct it. The book focuses on team habits because teammates can often change those routines even when other parts of the workplace are difficult to alter.
VUCA Environment
Volatile, uncertain conditionsAn environment characterized by volatility, uncertainty, complexity, and ambiguity. In such conditions, plans and priorities can change, and a shift in one part of a team can affect others. The concept helps explain why teams need clear routines while also making those routines adaptable.
Readiness
Capability to meet goalsA team or individual’s capability to accomplish goals, complete projects, and perform to standard. Readiness depends on knowing how to do the work, having enough capacity to do it, and having team habits that let people combine their skills effectively. Goals set without checking readiness can produce failure or exhausting last-minute effort.
Dunkirk Spirit
Heroic effort masking poor setupA pattern in which a team meets a daunting goal through extraordinary effort despite poor planning, weak decisions, or unrealistic expectations. Gilkey uses the historical Dunkirk evacuation as the reference for the term. Praising the effort without correcting the conditions can normalize crisis work and leave the underlying problems intact.
Pull Goals
Goals with intrinsic appealGoals that connect to motivations people already find meaningful, such as serving customers, mastering a skill, or helping colleagues. They tend to require fewer reminders than goals driven mainly by external pressure or reward. A business target can become more compelling when translated into a human outcome its team members value.
TEAM
Goal resource costsAn acronym for the four resources every goal consumes: time, energy, attention, and money. A goal is not a real priority simply because leaders announce it. Its TEAM costs should appear in schedules, workload decisions, focus, and budget. If those resources are not made available, the organization has not meaningfully prioritized the work.
Ghost Plan
Unshared team planA plan known to only some members of a team and not communicated to everyone who needs it. People left outside the plan may continue working from old assumptions, while those who know it expect them to act on information they never received. Sharing, revisiting, and updating a plan prevents this hidden divergence.
Focus Block
Protected deep-work periodA scheduled period, typically 90 minutes to two hours, for concentrated work that moves a project forward. Focus blocks help teams estimate capacity in realistic units and reveal when a workload cannot fit into available time. They need protection from meetings and interruptions to function as intended.
Crutch Meetings
Meetings replacing better habitsMeetings used to compensate for problems that should be handled through other team practices. A team might repeatedly meet because its plan is unclear, updates are not shared, or priorities are unsettled. The meeting may temporarily patch the problem, but addressing its cause can prevent the same meeting from recurring.
Green Hat
Protected project priorityA signal that one person currently owns the main effort on a project and should receive protected time and attention to advance it. Teammates can support the work by avoiding unnecessary meetings and interruptions. The responsibility should have a clear time limit or milestone, after which priority can transfer.
TIMWOOD
Checklist for work wasteA lean-management framework for identifying common sources of waste: transportation, inventory, motion, wait time, overproduction, overprocessing, and defects. Gilkey highlights motion, waiting, overprocessing, and defects as especially relevant to many creative teams. The categories help locate friction in the work process rather than attributing every delay to individual performance.
FAQ
What's Team Habits: How Small Actions Lead to Extraordinary Results about?
- Focus on Team Dynamics: The book emphasizes the importance of team habits over individual behaviors, highlighting how effective teamwork is crucial for organizational success.
- Framework for Change: It provides a framework for understanding and changing team habits, focusing on collaboration, communication, and decision-making processes.
- Practical Strategies: Charlie Gilkey shares practical strategies and tools that teams can implement to enhance their effectiveness and foster a supportive work environment.
Why should I read Team Habits by Charlie Gilkey?
- Improve Team Performance: The book offers insights into how small changes in team habits can lead to significant improvements in overall performance and morale.
- Applicable to All Roles: It is designed for everyone in an organization, from individual contributors to senior leaders, making it relevant regardless of your position.
- Actionable Advice: Readers will find practical tools and frameworks that can be implemented immediately to enhance teamwork and productivity.
What are the key takeaways of Team Habits?
- Team Habits Matter: The book stresses that team habits are the foundation of effective collaboration and should be prioritized over individual performance.
- Belonging is Essential: A strong sense of belonging within a team enhances engagement and productivity, making it a critical focus area for improvement.
- Iterative Improvement: The author advocates for continuous assessment and adjustment of team habits, encouraging teams to embrace change and learn from failures.
What are the best quotes from Team Habits and what do they mean?
- “If you do not change direction, you may end up where you are heading.”: This quote highlights the importance of actively addressing team habits to avoid stagnation and inefficiency.
- “Poor Planning Produces Poor Performance.”: This emphasizes that effective planning is crucial for achieving team goals and that neglecting this aspect can lead to failure.
- “Belonging is the key ingredient for transforming a group of people into a high-performing team.”: This underscores the significance of fostering a sense of belonging to enhance team dynamics and performance.
What are "broken printers" in the context of Team Habits?
- Metaphor for Issues: "Broken printers" symbolize small, often overlooked problems that disrupt team workflow and efficiency.
- Impact on Performance: These issues, while seemingly minor, can accumulate and lead to significant waste and frustration within a team.
- Encouragement to Act: The author encourages teams to identify and fix these "printers" to improve overall functioning and morale.
How does Team Habits define "workways"?
- Definition of Workways: Workways are the systems created by team habits, organizational policies, and technology that dictate how work is done.
- Healthy vs. Broken Workways: Healthy workways support productivity, while broken workways hinder performance and should be addressed.
- Empowerment to Change: The book emphasizes that everyone in the organization has the power to influence and improve their workways.
What is the "Voice of No" in Team Habits?
- Critical Role: The "Voice of No" is a designated role within a team that challenges ideas and plans, ensuring that all aspects are considered before moving forward.
- Encourages Healthy Debate: This role fosters an environment where team members can express concerns and ask tough questions, which is vital for effective decision-making.
- Promotes Clarity: By celebrating the "Voice of No," teams can clarify priorities and avoid scope creep, ultimately leading to more successful outcomes.
How does Team Habits define focus blocks?
- Dedicated Work Time: Focus blocks are defined as 90-minute to two-hour periods where team members can engage in deep, uninterrupted work to enhance productivity.
- Importance of Scheduling: The book emphasizes the need to schedule these blocks intentionally, ensuring that they are protected from meetings and other distractions.
- Capacity Measurement: Focus blocks can also be used to measure a team's capacity for work, helping to determine how many projects can realistically be undertaken at any given time.
What is the "3x Rule" mentioned in Team Habits?
- Project Estimation: The "3x Rule" suggests that strategic work will often require three times more effort than initially anticipated, highlighting the need for realistic planning.
- Avoiding Overcommitment: This rule helps teams avoid overcommitting by encouraging them to assess their capacity and the true demands of new projects.
- Strategic Planning: By applying the 3x Rule, teams can better allocate resources and time, leading to more successful project outcomes.
How can I improve decision-making in my team according to Team Habits?
- Remove Bottlenecks: Identify and eliminate bottlenecks in the decision-making process to empower team members to take initiative.
- Use Intent-Based Decision-Making: Encourage team members to state their intentions rather than waiting for orders, fostering a culture of ownership.
- Keep a Decision Log: Document decisions and the reasoning behind them to provide clarity and context for future reference.
How does Team Habits suggest handling failure?
- Embrace Failure as Learning: The book encourages teams to view failure as an opportunity for growth rather than a setback.
- Create Room for Experimentation: Allowing space for failure fosters innovation and encourages team members to take risks.
- Shift Incentives: Organizations should shift their focus from punishing failure to rewarding efforts and learning from mistakes.
How can I implement the concepts from Team Habits in my own team?
- Start Small: Begin by selecting one or two specific habits to change, focusing on areas that will have the most immediate impact on your team's performance.
- Engage the Team: Involve your teammates in the process of identifying and implementing changes, ensuring that everyone feels invested in the outcome.
- Track Progress: Regularly assess the effectiveness of the changes made, using metrics to measure improvements in team dynamics and productivity.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.