Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Smart Teams

Smart Teams

How to Move from Friction to Flow and Work Better Together
Make your team's daily coordination less draining, from meetings and messages to shifting deadlines.
by Dermot Crowley 2023 248 pages
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat team productivity as a design problem, not an individual virtue.

The hidden team tax. A technology company’s managers received 300 to 500 emails a day, blaming head office, customers, and suppliers. At a three-day conference, their email volume fell to about one-third of normal. The group realized that much of its own overload came from internal habits: copying everyone, relying on email even for nearby colleagues, and extending threads with Reply All. The lesson is broader than inbox management. Meetings, interruptions, and last-minute requests also create friction, the lost focus and time between people working together.

Small drag compounds. Like barnacles on a boat, minor disruptions can build unnoticed until work slows across the team. Individual productivity tools help, but cannot overcome a culture that continually creates noise and rework. Improving the way people coordinate is a separate, shared responsibility.

Analysis

What's striking is the shift from blaming workload to examining the system that generates it. That is a classic move in systems thinking: outcomes often arise from repeated interactions, not from one worker's effort or character. The conference example makes the feedback loop visible because the email volume changed when the group's behavior changed. Still, some communication is imposed by customers, regulation, or time zones. A team should distinguish avoidable internal noise from necessary coordination before setting reduction targets, or it may mistake fewer messages for better work.

Choose actions that protect your focus and keep teammates moving.

Serve both sides. Crowley adapts a lesson from game theory: the strongest outcome comes when people pursue their own effectiveness while considering the group. He calls this game theory productivity. A selfish colleague protects personal focus but may leave others waiting, such as a director who accepts meeting invitations and then fails to appear. A selfless colleague answers every email immediately or attends every meeting, preserving others' flow at the cost of personal focus and capacity.

Find the serving middle. A serving mindset means pausing before communicating, meeting, or collaborating to ask whether an action helps both the individual and the team. It is not a demand to accommodate everyone. It is a practical check against exporting one's own inconvenience to colleagues or absorbing every request without question.

Analysis

This is a useful correction to the familiar idea that productivity means maximizing individual output. In organizations, work is interdependent: one person's speed can create another person's rework, while constant availability can fragment the whole group's attention. The framing resembles cooperative game theory, where durable gains depend on how choices affect other players. Yet a shared-good test needs boundaries. When priorities truly conflict, teams need explicit decision rights and workload negotiation, not a vague appeal to be considerate. Otherwise, the most conscientious people may carry a disproportionate share of the burden.

Turn recurring friction into a few team-owned rules.

Make values observable. Four qualities describe the smart team player: purposeful, mindful, punctual, and reliable. Together, they support focus, respect, trust, and impact. But broad qualities are hard to act on or hold one another accountable for. Productivity principles translate them into specific behaviors tied to actual situations, such as deciding who belongs on an email or when a meeting should wrap up.

Build rules together. Teams should identify recurring problems, then flip each into a practical behavior. For instance, a pattern of late meetings can become an agreement to arrive a few minutes early. Crowley recommends developing roughly eight to twelve principles, not an exhaustive rulebook. Silent brainstorming can give quieter participants room to contribute; prioritization then narrows the list. Principles created with the team are more likely to feel owned than rules handed down by a manager.

Analysis

The move from abstract values to observable behavior is important because teams cannot reliably improve what they cannot recognize. This connects to implementation intentions, the idea that a specific cue and response make action easier than a general intention. Co-creation also improves legitimacy: people are more willing to follow standards they helped shape. A risk is that group agreements become performative, especially if senior leaders ignore them. The principles need to be few, revisited, and applied consistently, including when a powerful person is the one creating the friction.

Choose communication channels by purpose, not habit.

Match tool to task. The book distinguishes real-time options, such as conversation and meetings, from anytime options, such as email and shared posts. A brief conversation may settle an issue that would otherwise generate a long thread. Meetings suit collaborative discussion and decisions, while email can carry substantial information that recipients can review in their own time. Shared platforms can keep discussion attached to a topic or project, though their constant feeds can create a new source of distraction.

Make messages easy to use. Before sending, clarify the intended outcome and who needs the message. The SSS approach structures an email with a clear subject, an upfront summary, and supporting information. The reader gets the point and required action quickly, with detail available if needed. The sender should also question CC and Reply All, since easy distribution can impose attention costs on everyone copied.

Analysis

The channel question is really a question about coordination costs. A medium shapes who sees information, when they see it, and how much context travels with it. Shared channels can improve collective awareness, but visibility is not free: notifications and ambient conversation can turn collaboration into continuous interruption. The useful principle is not to replace email with a fashionable platform, but to agree on norms, notification settings, and response expectations. Without those agreements, organizations simply move the same overload into a different interface.

Cut meeting waste before asking people to work faster.

Reduce the meeting burden. Crowley proposes four separate targets: hold 25 percent fewer meetings, shorten their duration by 25 percent, reduce attendance by 25 percent, and waste 25 percent less time. These are practical prompts, not a claim that meetings should disappear. A meeting with eight participants consumes four hours of collective time even if it lasts only 30 minutes. The book cites a Bain finding that decision effectiveness falls by 10 percent for each attendee above seven, while noting that larger groups can still help with idea generation.

Plan from purpose outward. The 5W approach starts by defining why the meeting exists and what it must produce. Then choose who needs to attend, where it should happen, and when. A focused agenda guides timing. The meeting itself can devote a brief opening to objectives, most of its time to the agenda, and a brief close to owners and next steps.

Analysis

Meetings are a striking example of collective cost hidden inside individual calendars. Treating attendee time as a shared resource makes the expense legible and encourages organizers to ask whether a meeting is the right tool at all. The distinction between creation and decision-making is also valuable: open-ended idea generation may benefit from a larger group, while decisions often need a smaller, empowered set of people. Still, strict attendance limits can exclude relevant expertise. The purpose and decision rights should determine the room, not a numerical rule applied mechanically.

Make project purpose, ownership, and progress visible to everyone.

Expose the moving parts. Even a report or team event can be a project if it requires several steps. Productive collaboration depends on alignment about the goal, agreement about how people will work together, and awareness of whether the collaboration is working. For a project, clarify why it matters, what objectives and tangible deliverables define completion, who leads and contributes, and when key work is due. Breaking deliverables into tasks makes responsibilities and dependencies easier to see.

Use tools at the right scale. A complex project with many contributors may need scheduling software; a smaller effort may need a shared board, mind map, or checklist. The tool should be useful, easy to use, and adopted by the people who need it. A polished project plan is not a substitute for communication, a capable team, or regular checks on progress and stakeholder needs.

Analysis

Visibility reduces the cognitive burden of remembering who is doing what and helps a team detect delay before it becomes a crisis. This is consistent with distributed cognition: groups think and coordinate through shared artifacts as well as through individual minds. The book's insistence that tools must actually be used is especially practical, since software adoption often fails when it adds work without changing coordination. Yet visibility can become surveillance if managers track activity rather than outcomes. Clear deliverables and trust matter more than a dashboard full of updates.

Replace reflexive urgency with timely, negotiated responses.

Separate urgent from insistent. Email, phones, and instant messaging can make every incoming request feel immediate. Crowley argues that much workplace urgency is false, or is created by late planning. His active mindset sits between passivity and reflexive reaction: respond thoughtfully, while planning ahead enough to prevent avoidable crises. He suggests devoting about 10 percent of time to planning and spending most work time in this active mode, with immediate reaction reserved for genuinely urgent matters.

Negotiate the request. When work arrives, assess whether it is truly urgent and reasonable. A request may be ignored, negotiated, questioned, or handled promptly, depending on those conditions. Managers should act as buffers, asking when work is actually needed and considering the team's existing commitments before passing on pressure. If a deadline cannot move, scope, resources, or quality may need discussion.

Analysis

The distinction between urgency and importance helps explain why people can end a full day with little meaningful progress. The recommendation to negotiate is especially strong because it treats capacity as a real constraint rather than a personal failure. In behavioral terms, a pause interrupts the cue-response loop that makes notifications feel like commands. The framework does need contextual judgment: in safety-critical work or during genuine emergencies, fast reaction is essential. The goal is not to suppress urgency, but to reserve it for situations where speed changes the outcome.

Treat interruptions and delegation as designed exchanges, not drive-bys.

Protect attention on both sides. Before interrupting, ask whether the issue needs attention now, capture it for later if not, and notice whether the other person can engage. If an interruption is necessary, agree on a short time or return when they can focus. When interrupted, choose deliberately: give the person full attention, or explain when a focused conversation will be possible. Splitting attention while pretending to listen often frustrates both people.

Delegate with enough runway. Crowley warns that last-minute delegation creates pressure and can set colleagues up to fail. For a simple task, specify the outcome and relevant constraints. For a more complex assignment, plan the work together, adapting the guidance to the person's experience. The interview with leadership coach Scott Stein describes beginning collaboratively, then handing over more planning as the team member gains capability.

Analysis

Both interruption and delegation transfer cognitive work from one person to another. A well-formed request supplies context and reduces the recipient's need to infer hidden expectations; a poorly timed interruption transfers the cost of the sender's memory lapse to someone else's concentration. The approach also resembles progressive autonomy in education: support is highest during learning, then recedes as competence grows. Care is needed, however, not to turn every small request into a process. The amount of structure should fit the stakes, complexity, and experience involved.

Build culture through small team projects leaders visibly sustain.

Start where influence exists. A micro-culture is a team's local way of working, which can differ from the wider organization's habits. Teams can shape this local environment even when they cannot change company-wide systems. Crowley describes a progression from disruptive work patterns, through individual productivity and collaboration, toward a superproductive culture where shared practices persist over time. Each step requires more than personal training: teams need common behaviors, and leaders must make those behaviors normal.

Make change concrete. Instead of launching a giant culture campaign, choose one focused project, such as reducing unnecessary email, improving agendas, or dialing down false urgency. Work on it for a month, keep it visible, and then add another effort. Leaders must model the standard, protect the team's time, and avoid creating the very friction they ask others to remove. Small projects give people something specific to practice and review.

Analysis

The micro-culture idea is a realistic response to the limits of formal authority. Local norms can change through repeated practice, visible modeling, and social reinforcement, even when organization-wide incentives remain imperfect. The project approach also makes cultural change testable: a team can observe whether a new meeting practice saves time or whether a communication norm reduces noise. The hard part is sustaining the change when attention moves elsewhere. Leaders need to protect the experiment from conflicting demands, while checking that local efficiency does not simply shift costs onto neighboring teams.

Analysis

Smart Teams reframes productivity as a property of relationships and routines, not simply the sum of individual time-management skills. Its central contribution is to make ordinary coordination visible as work: an email, a late arrival, an unclear delegation, or an unnecessary meeting can consume attention far beyond the person who initiated it. The book's examples, especially the managers whose email traffic dropped during a shared conference, help readers see that overload is sometimes socially produced rather than externally imposed.

The practical architecture is coherent. First, people adopt a dual concern for personal and collective effectiveness. Next, a team converts that concern into observable agreements, then applies those agreements to communication, meetings, projects, urgency, and delegation. Finally, leaders reinforce the behaviors through small, sustained projects. This is a socio-technical argument: norms, tools, schedules, and leadership behavior jointly shape outcomes. Replacing email alone will not help if the replacement channel creates constant interruption; teaching focus alone will not help if managers continue to schedule every available hour.

The framework's strength is also its main limitation. It places substantial responsibility on teams and leaders to manage friction, while some causes of overload are structural: staffing, conflicting organizational incentives, customer demands, and unequal authority. A micro-culture can improve daily work, but it cannot always compensate for targets that reward speed over quality or for workloads that exceed capacity. The book's own emphasis on negotiating priorities points toward this boundary. Productivity principles should expose these conflicts, not disguise them as individual failures to be mindful or reliable.

The most durable lesson is therefore not to maximize activity, but to reduce avoidable coordination costs without sacrificing necessary collaboration. Teams can test this by choosing one costly pattern, agreeing on a behavior change, and reviewing whether work becomes clearer, calmer, and more dependable. That makes productivity a shared practice rather than a slogan.

Summary in 30 Seconds
Team productivity depends on shared routines as much as individual focus. Agree on 8 to 12 practical behaviors for recurring problems, choose communication channels to fit the task, and make project goals, owners, and deadlines visible. Cut meeting counts, duration, attendance, and wasted time by 25 percent each. Reserve about 10 percent of work time for planning, negotiate deadlines, and improve one team habit at a time.
Contains spoilers

Last updated:

Report Issue
Want to read the full book?

Glossary

game theory productivity

Personal and team benefit

Crowley's term for working in ways that support an individual's effectiveness while also helping the team succeed. It rejects both self-interest that disregards colleagues and self-sacrifice that destroys one's own capacity. The idea encourages people to consider how each interaction affects both their work and the work of others.

serving mindset

Balance self and group

A way of working that aims to preserve personal productivity while supporting the productivity of colleagues. It involves pausing before communicating, meeting, or collaborating to consider timing, purpose, and effects on others. It is a middle ground between prioritizing only oneself and accommodating every request at personal cost.

productivity principles

Specific team behavior agreements

Clear, situation-specific behaviors that turn broad qualities such as reliability or mindfulness into practical expectations. Teams identify recurring sources of friction, then define actions that address them. The principles are intended to be created with the team, limited to the most relevant behaviors, and practiced consistently until they become part of how the group works.

active mindset

Thoughtful response to work

A working stance between passively waiting and reflexively reacting. Someone with an active mindset responds to incoming requests with attention to current priorities, while anticipating upcoming work and planning to prevent avoidable urgency. The approach reserves immediate reaction for cases where the situation genuinely requires it.

SSSH

Manage requests and expectations

A four-part method for handling a request without either ignoring it or dropping everything. Acknowledge receipt promptly, state when the task can be completed, schedule the work, and remain accountable for delivery or renegotiation. It is intended to reassure the requester while giving the recipient a realistic way to manage workload.

5W approach

Plan cooperation systematically

A set of planning questions: why is the interaction needed, what must it achieve, who should be involved, where should it happen, and when is the right time? For meetings, the approach starts with purpose and content before arranging participants, setting, and timing. This sequence helps prevent logistics from taking precedence over the reason for meeting.

SSS approach

Structure readable emails

A format for email consisting of a specific subject, a short summary near the beginning, and supporting information afterward. The structure helps recipients understand the purpose and required action quickly, while keeping background material available for those who need it. It is meant to make communication easier to scan and respond to.

micro-culture

A team's local work norms

A local set of shared habits and expectations within a team, which may differ from the wider organization's culture. A manager or team can encourage more productive ways of communicating, meeting, and collaborating even without authority to redesign the entire organization. Those behaviors may also influence neighboring teams through example.

Download PDF

To save this Smart Teams summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.30 MB     Pages: 14

Download EPUB

To read this Smart Teams summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.39 MB     Pages: 18
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...