Certificate Topics — Dream Teams — Working Together without Falling Apart (Year 1 Foundations)

School: Minister Destiny Testimony Schools Track: Adult Class: Certificate Topics — Year 1 (Foundations) · Home: Schools — Adult track Certificate behind this topic: "Dream Teams: Working Together without Falling Apart (Blinkist Summary)" — LinkedIn Learning, earned by Minister Destiny Marie Morgan (May 29, 2025) Presented by: Minister Destiny Marie Morgan, Muslim Ordained Minister

This lesson is educational information from Minister Destiny Testimony Schools. It teaches the public body of knowledge in this subject — the same ground Minister Destiny studied for her certificate — in this school's own words. It is not the original course, it does not award the original credential, and it is not legal or medical advice. If you are in danger right now, call 911.

Before you start

• This school never asks your name. Your progress is saved only in your own browser on this device — the school collects and keeps nothing. If you pass this unit's quiz (80% or higher, retakes allowed), you earn a downloadable certificate with a blank line — you write your own name on it after you save it. Quiz answers are not shown; if you miss a question, re-read the lesson and try again.
• The certificate behind this topic was a summary of the book Dream Teams by author and journalist Shane Snow. This unit does not reproduce that summary or the book. It teaches the public teamwork literature — research on cognitive diversity, disagreement, and team safety that any reader can check in the sources listed — and attributes the book's framing ideas to Shane Snow where they appear.
• The central puzzle: teams of brilliant people fail constantly, and ordinary people on the right kind of team do extraordinary work. This unit explains why.

The lesson

Part 1. Cognitive diversity — different toolkits, better answers

In Dream Teams, Shane Snow argues that the differences that matter most on a team are the ones inside people's heads: their perspectives (what they notice, shaped by their experience) and their heuristics (the mental shortcuts and methods they reach for when solving a problem). Two engineers trained in the same school may look diverse on paper and think nearly identically; a nurse, a mechanic, and an accountant facing the same problem carry three different toolkits, and the problem gets examined from three directions.

This is not just a book's opinion. Researcher Scott Page and colleagues have shown, in models and in studies summarized across the teamwork literature, that on hard, novel problems a group with diverse toolkits can outperform a group of individually stronger but similar thinkers — because similar thinkers share the same blind spots and get stuck in the same places. Homogeneous teams feel smoother: agreement comes fast, meetings end early, everyone nods. That smoothness is the warning sign. For routine work, similarity is efficient. For the problems teams actually exist to solve — new, tangled, high-stakes — comfort is expensive.

The practical lesson: staff hard problems with genuinely different minds on purpose — the person from the other department, the newcomer who asks naive questions, the skeptic whose experience runs against the plan.

Part 2. Cognitive friction — disagreement that does work

Diversity guarantees friction: different toolkits produce different answers, and different answers collide. Shane Snow's framing, consistent with the wider research, is that teams do not succeed by avoiding that collision — they succeed by harnessing it. Organizational research distinguishes task conflict (disagreement about the work: the plan, the evidence, the method) from relationship conflict (disagreement about each other: motives, competence, character). Task conflict, held inside respectful norms, improves decisions: weak assumptions get tested, missing evidence gets named, and the second-best idea often repairs the best one. Relationship conflict does the opposite damage — people stop sharing information, and the team loses exactly the diversity it recruited.

Working rules for productive disagreement are consistent across the literature. Attack the idea in the open, never the person in any setting. Require the strongest version of the opposing view to be stated before it is answered. Separate idea generation from idea judgment, so a strange suggestion survives its first minute. Let the person closest to the evidence speak before the most senior person anchors the room. And time-box debate: when the decision is made, the team closes ranks behind it — disagree, then commit — instead of re-litigating in the corridor.

Part 3. Intellectual humility and psychological safety

Two inner conditions decide whether diversity and friction help or destroy. The first is intellectual humility: treating your own knowledge as partial. Shane Snow highlights it as a dream-team trait — the expert who says "here's what I might be missing," the leader who changes position when the evidence changes. It is not self-doubt; a humble expert still argues hard. It is accuracy about the borders of what you know.

The second condition is the team's, not the individual's: psychological safety, the shared belief that speaking up — a question, a half-formed idea, an admission of error, a dissent — will not be punished or mocked. Google's Project Aristotle, a large internal study of its own teams published through Google's re:Work site, found psychological safety to be the most important of five dynamics distinguishing its effective teams, ahead of dependability, structure and clarity, meaning, and impact. Researcher Amy Edmondson's earlier work established the same link in hospital and workplace teams: groups where members can report errors and ask for help learn faster. Safety is not softness. In safe teams, standards stay high and feedback gets more direct — because candor is no longer confused with attack.

Part 4. Norms and decision rights — the operating system

Goodwill is not a system. Teams that hold together under strain run on explicit norms: agreed, written, revisit-able rules for how they work — how decisions get made, how disagreement is conducted, how meetings run, and how information travels. A norm is only real if a new member hears it in week one and sees it enforced — kindly and consistently — in week two.

Inside norms, the highest-leverage item is decision rights: for each kind of decision, who proposes, who must be consulted, who decides, and who is simply informed. Most team resentment is not about outcomes; it is about discovering that a decision you thought was yours was taken elsewhere, or that a "group decision" was actually one person's preference wearing the group as a costume. Pair decision rights with a decision log — what was decided, by whom, on what evidence, and when it will be revisited — and the team gains a memory that survives mood and turnover.

Part 5. How teams fall apart — silence, factions, and blame

Teams rarely explode. They decay through three recognizable patterns. Silence comes first: meetings end quickly, nobody objects, and the real conversation moves to private chats and parking lots. Silence is rarely agreement; it is the sound of people concluding that speaking costs more than it buys. Factions come second: the team splits into camps that pre-meet before the meeting, interpret every proposal by its author instead of its content, and keep score across months. Faction is what cognitive diversity becomes when trust fails — the same differences, weaponized. Blame completes the pattern: when something breaks, the team's energy goes to locating a person rather than a cause, so information about the next problem gets hidden earlier and deeper.

Each pattern has an early tell a leader can catch. Silence: ask what the strongest objection to the current plan is, and wait — really wait — for an answer. Factions: rotate who works with whom, and make cross-camp pairs own deliverables together. Blame: in the first review after a failure, ban person-language for the first half hour and map the process that allowed the failure instead.

Part 6. Repair conversations — putting a team back together

Because friction is guaranteed, repair is a core team skill, not an emergency extra. A repair conversation has a reliable shape in the conflict literature. Name the break specifically and soon — "In Tuesday's meeting I cut you off twice and the room went quiet; that is on me" — because vague apologies for "any tension" repair nothing. Describe impact without assigning motive: what happened and what it cost, not what the other person "was trying to do." Listen to the other account fully before defending yours. Agree on one concrete change — a norm, a signal, a sequencing fix — small enough to actually happen this week. And close the loop: revisit it briefly at the next meeting.

Leaders carry extra duties here: apologize first and in the open when the fault is theirs, protect the person who raised the problem from retaliation including the social kind, and never let a repair conversation become a trial of somebody's character. Teams that repair visibly teach every member that honesty about breakage is survivable — which is psychological safety, maintained.

Words to know — Dream Teams — Working Together without Falling Apart

• Cognitive diversity — differences in perspectives and problem-solving methods inside a team; the variety of mental toolkits available to it.
• Heuristic — a mental shortcut or method a person habitually uses to approach problems.
• Cognitive friction — the collision of different viewpoints on a team; harnessed well, it tests and improves ideas.
• Task conflict — disagreement about the work itself — plan, evidence, method — which can improve decisions inside respectful norms.
• Relationship conflict — disagreement about people — motives, competence, character — which damages trust and information-sharing.
• Intellectual humility — treating your own knowledge as partial: arguing hard while openly tracking what you might be missing.
• Psychological safety — the shared belief that speaking up, dissenting, or admitting error will not be punished or mocked.
• Decision rights — the agreed allocation of who proposes, who is consulted, who decides, and who is informed for each kind of decision.
• Disagree and commit — debating fully before a decision, then supporting it together afterward instead of re-litigating it.

Myths vs facts — Dream Teams — Working Together without Falling Apart

• Myth: A dream team is a collection of the most talented individuals available. Fact: Research including Scott Page's work shows diverse toolkits can outperform stronger but similar thinkers on hard problems; how the team works beats who was recruited.
• Myth: Good teams agree quickly and rarely argue. Fact: Fast, comfortable agreement is a warning sign on novel problems; productive task conflict is how weak assumptions get caught.
• Myth: Psychological safety means being nice and avoiding hard feedback. Fact: Safe teams give more direct feedback, because candor is not confused with attack; standards stay high.
• Myth: Silence in meetings means everyone is aligned. Fact: Silence usually means people have concluded speaking costs more than it buys; the real conversation has moved elsewhere.
• Myth: When something fails, finding who is to blame fixes it. Fact: Blame drives information underground; mapping the process that allowed the failure is what prevents the repeat.

Think it through — Dream Teams — Working Together without Falling Apart

A four-person team is planning a community health fair. All four think alike — trained in the same program, friends for years. Their plan comes together in one smooth meeting. In week two, a new volunteer with a logistics background joins and keeps raising failure scenarios: rain, a double-booked hall, a speaker cancelling. Two members complain she is "negative." The team leader asks you what this unit would say.

Walk it through: (1) Cognitive diversity (Part 1): the original four shared one toolkit and one blind spot — the plan felt smooth because nobody's experience covered logistics failure. The new volunteer is not a problem in the team; she is the missing perspective arriving on schedule. (2) Friction type (Part 2): her objections are task conflict — about evidence and method — and the complaints about her attitude are the first move toward relationship conflict, which is the destructive kind. (3) Safety (Part 3): how the leader responds now decides whether anyone raises a risk again; thanking her in the room, by name, for the catches is the safety-building act. (4) Norms (Part 4): give risk-raising a formal home — a fifteen-minute pre-mortem at the next meeting, where the whole team lists how the fair could fail and assigns countermeasures. The "negativity" becomes a role the team owns together, and the plan gets stronger in public instead of the volunteer getting quieter in private.

Try this — Dream Teams — Working Together without Falling Apart

• ☐ For one real problem, list the mental toolkits in your team — and name the perspective that is missing
• ☐ Run a fifteen-minute pre-mortem on a current plan: assume it failed, and list why, before anyone defends it
• ☐ Write down decision rights for one recurring decision: who proposes, who is consulted, who decides, who is informed
• ☐ Practice one repair conversation using the Part 6 shape: name the break, describe impact, listen fully, agree one concrete change
• ☐ In your next meeting, ask for the strongest objection to the plan — and wait in silence until someone answers

Resources to keep — Dream Teams — Working Together without Falling Apart

• Google re:Work (rework.withgoogle.com) — Google's free publication of its Project Aristotle findings on team effectiveness and psychological safety.
• Purdue OWL (owl.purdue.edu) — free guidance on group writing and collaboration for teams producing shared documents.
• Institute for Public Relations (instituteforpr.org) — free research library, including work on teams, trust, and organizational communication.

What you earned / what's next — Dream Teams — Working Together without Falling Apart

✅ Dream Teams — Working Together without Falling Apart complete (quiz score 80% or higher): You can explain cognitive diversity and friction, run productive disagreement that stays on the task, build intellectual humility and psychological safety, set norms and decision rights, spot silence, factions, and blame early, and repair a team with a structured conversation.

Your certificate

Minister Destiny Testimony Schools Certificate of Completion — Dream Teams — Working Together without Falling Apart

This certificate is presented by Muslim Ordained Minister Destiny Marie Morgan

Awarded to: ______________________________ (write your name here after you download — your name is never collected or stored by this school)

Date completed: ______________

Strong teams are not the ones that never disagree — they are the ones whose differences make them wiser. You have learned to build that kind of team. — Minister Destiny Marie Morgan

This is a certificate of educational completion from Minister Destiny Testimony Schools. It is not a state license, a government certification, or the original course credential.

What's next: Return to the Certificate Topics for your next Year 1 Foundations topic.

Sources

• Snow, Shane — Dream Teams: Working Together Without Falling Apart (book, cited as the certificate's subject) — the cognitive diversity, friction, and intellectual humility framing attributed to its author.
• Google re:Work — Google (rework.withgoogle.com) — Project Aristotle's five dynamics of effective teams, with psychological safety first.
• Edmondson, Amy — research on psychological safety and team learning, as summarized in the public teamwork literature — safety, error reporting, and learning behavior.
• Page, Scott E. — research on diverse problem solvers, as summarized in the public teamwork literature — when diverse toolkits outperform similar high-ability groups.

Your Progress — On Your Device Only — Dream Teams — Working Together without Falling Apart

• Learning outcomes: On completing this unit, the student can:
• Define cognitive diversity in terms of perspectives and heuristics, and explain when it outperforms individual ability
• Distinguish task conflict from relationship conflict and apply rules for productive disagreement
• Describe intellectual humility and psychological safety, including Project Aristotle's five dynamics
• Write team norms and allocate decision rights for a recurring decision
• Recognize silence, factions, and blame as decay patterns and name an early countermeasure for each
• Conduct a repair conversation: name the break, describe impact without assigning motive, listen fully, and agree one concrete change
• Study time: Approximately 1.5 hours — an estimate covering reading, activities, and the test. Students move at their own pace.
• Assessment: A 10-question test drawn only from this unit's lesson. 80% or higher passes and earns the unit certificate. Answers are not shown; your score is saved only in your own browser on this device, and retakes are allowed.
• Level: Certificate Topics — Year 1 (Foundations) · Adult school · working rank on completion path: Freshman → Sophomore.
• Version: Version 1.0 — October 2026.

Minister Destiny Testimony Schools — Adult. Educational information only. Help lines: 911 for emergencies · 988 Suicide & Crisis Lifeline (call/text 988).