A group project forms
Benchmark: You wait to see what role you get assigned.
Milestone: You already know whether you tend to take charge, prefer to support, need structure, or work best with flexibility, and you say so early.
Yes, the group work skill. Stay with us. This one's worth it.
8
Collaboration & Teamwork
Yes, the group work skill. Stay with us. This one's worth it.
If you groaned a little when you saw this module's skill, you're not alone. Most people have at least one group project story that still makes them tense up: the partner who disappeared, the group member who took over everything, the project that fell apart two days before it was due.
Most students don't know that instructors often groan too. Group work has a reputation problem on both sides of the classroom.
So this module won't pretend group work is great. It will help you understand why it so often goes badly, starting with how you tend to operate, so you can do something about it next time.
Benchmark collaboration shows up. Milestone collaboration makes the group better.
Below, in plain terms, is the difference between where most students start and where you're headed.
Lesson 1.2 explains Benchmark, Milestone, and Capstone.
The shift from Benchmark to Milestone is the shift from "doing your part" to paying attention to how the team is working, and doing something about it when it isn't.
At the Benchmark level, "contributing" can mean almost anything: agreeing with whatever's already been decided, or tossing out an idea that's interesting but unrelated to what the team is trying to do. At the Milestone level, your contributions are tied to what the team is trying to accomplish. That means understanding the goal well enough to know whether an idea moves the team toward it, and being willing to say so, even if it means setting aside an idea you personally like.
Instead of "We should also add a section about X" (because it interests you), ask: "Does X help us do what the assignment is asking for?"
This is probably the biggest gap between Benchmark and Milestone, and the source of most group work horror stories. At the Benchmark level, conflict tends to get avoided (hoping it fixes itself), absorbed (quietly doing extra work to make up for it), or escalated (going straight to the instructor without talking to the group first). At the Milestone level, conflict gets addressed directly: you say what you need or expect, and you're willing to adjust your own behavior based on feedback, not just wait for others to change.
Instead of silently redoing a teammate's section because it "wasn't right," try: "I noticed we have different ideas about how this section should look. Can we talk about what we're each picturing?"
A lot of group trouble starts before anyone does any work. Nobody spells out what the project needs, so roles land by accident: whoever speaks first, whoever cares most, or whoever feels guilty.
At the Milestone level, you help the group name the tasks, then match them to people's strengths. That's what makes the work fair, and it's why understanding your own style (and asking about other people's) matters so much in this module.
Instead of "I'll just do the slides because nobody else will," ask: "What does this project need, and who's strongest at what?"
Group projects almost never go exactly as planned. Someone's role changes, a deadline moves, the assignment gets clarified halfway through. Benchmark collaboration treats these changes as disruptions. Milestone collaboration treats them as normal, and handles them in a way that keeps the group working well together.
This is where trust gets built or lost. A team that can absorb a change without anyone feeling blindsided, dismissed, or stuck with extra work is a team that's actually collaborating, not just dividing up tasks.
If a teammate has to step back because of a work or family emergency, Milestone collaboration means adjusting the plan together, not quietly resenting them or scrambling alone.
This module gives you a tool, your 16Personalities results, to understand your own collaboration tendencies before you're in the middle of a group situation.
Benchmark: You wait to see what role you get assigned.
Milestone: You already know whether you tend to take charge, prefer to support, need structure, or work best with flexibility, and you say so early.
Benchmark: You assume they don't care, and either pick up the slack silently or write them off.
Milestone: You see a moment for direct, low-drama communication, and you reach out before it becomes a bigger problem.
Benchmark: You stay quiet and hope it resolves on its own, or pick a side privately.
Milestone: You treat the disagreement as information about priorities, working styles, or unclear expectations, not just a personality clash.
Benchmark: You feel thrown off and frustrated that the plan isn't the plan anymore.
Milestone: You expect it, and focus on how to adjust together rather than who's to blame.
You don't have to become a different kind of person to be good at this. The goal is to know your own tendencies well enough to use them on purpose, not to turn introverts into extraverts or planners into improvisers, and to understand that other people's tendencies aren't wrong, just different.
Collaboration isn't a "soft skill" in the sense of being optional or easy. In a recent national survey of employers, teamwork ranked second only to problem-solving among the skills they look for on a new graduate's resume. Almost nothing important gets built by one person alone.
In this module, you'll build a real profile of how you work with others, strengths, struggles, and all, that you can use. It's also a strong choice for the fourth skill in your STAR(T) Stories.
Employer data: National Association of Colleges and Employers (NACE), Job Outlook 2025 (opens in a new tab). Skill definition and Milestone indicators are based on the Kentucky Council on Postsecondary Education's Kentucky Graduate Profile (opens in a new tab).