# What Actually Belongs on a Teamwork Slide Canonical URL: https://headwayskills.com/knowledge/teamwork/teamwork-slide/ Markdown URL: https://headwayskills.com/knowledge/teamwork/teamwork-slide.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving teamwork at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer A teamwork slide works when it names specific behaviors, not values. What to put on one, how many slides you need, and how to close so the room acts. ## Key facts - Title: What Actually Belongs on a Teamwork Slide - Category: Teamwork - Primary skill: Teamwork - Related skills: Communication, Influence - Primary keyword: teamwork slide - Source page: https://headwayskills.com/knowledge/teamwork/teamwork-slide/ ## What this page covers - A teamwork slide works when it names specific behaviors, not values. What to put on one, how many slides you need, and how to close so the room acts. - Practical guidance for teamwork slide - How this topic connects to Teamwork ## Detailed explanation You have a slot to fill and a deck due, and every search result for a teamwork slide is trying to hand you a template. A teamwork slide works when it names specific behaviors instead of values. Rather than putting up "communication, trust, respect," put up what those look like in practice: doing what you said you would do, raising the disagreement before the decision, backing the decision once it is made. Behaviors can be observed and acted on. Values can only be agreed with. That gap is why most teamwork decks get polite nods and change nothing. Once you decide what the slide is for, the rest of the build gets much easier. ## What should actually go on a teamwork slide? Start by noticing what the top search results give you and what they leave out. Search "teamwork slide" and the first page is almost entirely template catalogues — SlideTeam, SlideEgg, SketchBubble, SlidesCarnival, SlideModel, PowerSlides — and several of the "guides" ranking alongside them, like ExpertSlides and SlidesAI, are blogs owned by the same vendors. They are excellent at layout. They are near-silent on content, because template keywords are what converts for them. Where those pages do name content, they converge on the same list: communication, dedication, respect, collaboration, trust, shared goals. Every one of those is a value. Nobody in your audience disagrees with a single one, which is exactly the problem — a slide nobody can disagree with is a slide nobody has to do anything about. Swap each value for the behavior underneath it. Reliability is not a virtue on a slide; it is "you do what you committed to, and when you cannot, you say so early." [Constructive disagreement](/knowledge/teamwork/disagree-and-commit/) is not "open communication"; it is "you argue the decision, not the person, and you stop when it turns personal." Accountability is not "shared responsibility"; it is "[when someone misses a commitment](/knowledge/teamwork/how-to-hold-someone-accountable/), you raise it directly, specifically, and soon — not three weeks later to someone else." Those versions are concrete enough that a room can tell whether it does them. ## How many slides do I need, and how much goes on each one? The conventions here are consistent enough to be useful, though treat them as practitioner norms rather than research findings. [Presentation guidance](/knowledge/communication/presentation-skills/) published by Cornell's INFO 2951 course and by the MIT iCampus Prize both point at the same range: around ten slides as an upper bound for a standard talk, no more than about five for a short one, and no more than three to five key points on any single slide. For a teamwork topic that maths out neatly. Three behaviors, developed properly, will fill a ten-minute slot. Six will not fit and will not stick. Both sources are also blunt about the failure mode: do not put up bullet points and read them. Use the slide to carry an image or a very small number of words that reinforce what you are saying out loud. This matters more for teamwork than for most subjects, because the topic is abstract and the temptation is to compensate by loading the slide with definitions. A dense slide is usually a sign that the speaker has no example ready. ## Should I just download a teamwork template? Yes, for the layout. The design work is genuinely solved, and there is no prize for rebuilding a grid from scratch the night before. The risk is that a template quietly writes your content for you. Most teamwork decks arrive pre-filled with the same value words, a stock photo of hands stacked in a circle, and an "Our Values" slide with four blanks. Fill those blanks and you have shipped the generic deck with your name on it. Take the frame, delete the placeholder text entirely, and write your three behaviors into the empty boxes before you touch the colors. ## How do I make teamwork sound like more than a buzzword? Lead with the failures rather than the virtues. The same template libraries that publish the values list also publish a challenges list, and it is far more usable: absence of team identity, [difficulty making decisions](/knowledge/decision-making/group-decision-making/), poor communication, conflict and tension, lack of participation. That list works better because every item names something the room has actually watched happen. "We value collaboration" is unarguable and therefore inert. "We take four meetings to make a two-minute decision" is arguable, recognizable, and slightly uncomfortable — which is the state an audience has to be in before anything changes. Name the failure, then name the behavior that prevents it. That pairing is the whole slide. ## Should I use the forming, storming, norming, performing model? It is the model most often recommended for teamwork decks, and it is genuinely good at what it does: describing the arc a team moves through, including the phase where things get worse before they get better. If your audience is anxious that the team is fighting, showing them that storming is a stage rather than a verdict is a real contribution. Its limit is that it describes what happens *to* a team over time. It does not tell any individual in the room what to do on Monday. If you use it, use it as a single orienting slide and then move to behaviors — otherwise you have given a lecture on group dynamics, which informs people without moving them. ## What's a good example to put on a teamwork slide? Use one from your own team, and expect to supply it yourself. The benefit claims circulating across teamwork decks — increased efficiency, better problem-solving, more ideas, stronger project results — travel without any sourced figures attached to them. You are unlikely to find a clean, attributable statistic on the first page of results, so plan to carry the argument with a specific incident instead. The strongest example is small and recent: a handoff that worked because someone flagged a slip early, or a decision that stalled because nobody said the objection out loud until afterward. Anonymize it if you need to. One real thing that happened in this room beats any number you could cite. If you are not sure which behaviors to pick, that is usually a signal about your own working habits rather than a research problem — it is worth checking [where your own habits stand](https://assessment.headwayskills.com/) before you decide which ones to ask of everyone else. Both are learnable, and knowing your own answer tends to make the example obvious. ## How do we split a group presentation without it feeling disjointed? Rehearse with everyone present, more than once. The guidance from SlidesAI and SketchBubble on group presentations puts most of its weight here: joint rehearsal fixes timing, reduces nerves, and is what makes the delivery feel like one talk rather than four. Then plan the handoffs explicitly. The recommendation is simple — summarize your section in a sentence before passing to the next speaker. It is worth doing properly for this topic in particular, because a team presenting about teamwork demonstrates its own thesis or undermines it in the seams. A clean handoff is an argument. Four people reading their own slides and stopping mid-thought is a counter-argument, and the room will register it whether or not anyone says so. ## What should the last slide say? Ask for one thing, not five. A single behavior the team commits to trying — "we raise the objection in the meeting, not after it" — has a real chance of surviving the week. A list of five gets remembered as "we should communicate better," which is where it started. Then follow it up. A presentation that ends and is never mentioned again reverts to nothing within a fortnight. Bringing it back once, at the next team meeting, is what turns the slide into a practice. ## The skills behind a deck that actually changes something Read those eight answers together and a pattern shows up: almost none of the difficulty was in PowerPoint. The hard parts were knowing which behaviors genuinely make a team work, getting them across so the room follows, and asking for something people will actually do. **Teamwork** supplies the substance. What belongs on the slide is not a values list but the actual moving parts — being excellent at your own role while respecting other people's, putting the team's purpose ahead of your own agenda, being reliable enough that commitments mean something, arguing decisions without making them personal, then committing to what the team lands on, and raising a missed commitment directly rather than letting it sit. Those are the sentences that survive a slide. **Communication** decides whether any of it lands. Lead with the main point rather than building to it, keep it short, be direct, and adapt to the room you actually have. It also pays to be honest with yourself about which kind of meeting you are running — a team-building session, an information briefing, and a problem-solving session need different decks, and mixing them is the most common reason a presentation feels unfocused. **Influence** is what separates a deck that informs from one that changes something. Work out what is in it for the room before you open the template. Establish rapport before you make the case, keep it simple, and use an example or a demonstration rather than a bullet list. Go for a small win instead of a full yes. Then follow up on what was agreed — persisting after the room empties is the part almost everyone skips. Those three keep showing up long after this particular deck is done, and they are three of a wider set of twelve work skills the free Job Skills Test measures. Knowing which of them is currently your thinnest is more useful than any template, because it tells you where practice actually pays — and none of them is fixed. It takes about seven minutes to see [where each of yours stands](https://assessment.headwayskills.com/). ## You already did the harder part You may notice some of this in how you already work — checking in before a deadline slips, saying the awkward thing while it still matters. The interesting thing is that you went looking for what belongs on the slide rather than which template looked best. That instinct is the same one the whole topic rests on: caring more about whether something is true than whether it looks finished. Skills like these are built rather than issued, and you can build them without becoming a different person at work. They also tend to matter more, not less, as the work gets bigger — the first time you present is a slot in a meeting; later it is a budget, a hire, or a team that needs to move together. Which makes now a reasonable moment to find out where yours currently stand. ## Find out where your work skills stand The one thing left is to look at your own answer. The **free** Job Skills Test is a short self-assessment of your work skills — it shows you where you stand across all twelve, and which two or three would make the biggest difference to how the next few years go. It takes seven minutes and you get the result immediately. You do not need to prepare anything, and you can do it before you finish the deck. **Take the skills test** *Free, 7 minutes, no sign-up needed.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? A teamwork slide works when it names specific behaviors, not values. What to put on one, how many slides you need, and how to close so the room acts. ### Which Headway skill does this connect to? This guide connects primarily to Teamwork. It also relates to Communication, Influence. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/teamwork.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/teamwork/teamwork-slide/ Preferred summary: "A teamwork slide works when it names specific behaviors, not values. What to put on one, how many slides you need, and how to close so the room acts." ## Change log - 2026-07-07: Content collection version published.