My final group project for one of my psych classes senior year was an absolute catastrophe.

It was assigned a week before finals, great timing, so we all silently entered a mutual pact of academic procrastination. Finals came and went, and I was in full victory lap mode: writing more than ever, playing Disco Elysium, hanging out with friends before they scattered across the country. One day, I organized a walk with a friend around Beebe Lake. While walking, I get a text from one of my group mates asking me to finish my five pages of research writing within three hours since the project was due that day at 5:00 p.m.

My spine stiffened. Of course, I received no warning the project was due this early and had done zero preparation beforehand. To this day, I have no idea how such an important deadline was never discussed.

I sprinted back home and opened up the Google Doc.

It was a massacre.

I've been writing for over five years, but what I opened my eyes to was a diabolical affront to my very soul. It was as if my group members had each written their sections in a unique alien language, with no understanding of what the other students had done. Terms were thrown out like leftover lasagna, lacking definitional consistency within a group's assigned section and between sections. Some words looked like someone lost a fight with autocorrect. Citations that violated every law of MLA, APA, and common sense.

I scurried to write my section within three hours and handed it in just in time. When I finally hit submit, I turned off my computer, stared at the ceiling, and watched my writer's pride evaporate through the ceramic tile. It's probably one of the worst writing assignments I've ever done. To be clear, this group project's horribleness was partially me, partially my group members, and partially the professor.

You've probably experienced a terrible group project yourself.

You get put with students who you swear were dragged from the pits of Tartarus. So, like always, you do the entire project the night before on a 3:00 a.m. caffeine binge. Or, you give up and resign to learned helplessness.

Group projects don't have to be this way. Collaboration in general is one of the most fulfilling, powerful ways of building not only your career prospects, but making the world a better place.

So, after that catastrophe, I researched heavily into what makes collaboration work, reading dozens of books including Collaborative Intelligence and Dare To Lead, as well as diving deep into Bright Future Now (BFN), a live cohort course whose soul purpose is to help us understand what collaboration is and how we can do it better.

I learned there are three main collaborative challenges leading to so many group projects that suck. Let's walk through each so we can unsuck the suck.

Collaboration Challenge 1: Poor Stress Regulation & Self-Understanding

It may seem like the problems leading to my catastrophic group project were external. Poor time management, poor synchronization, poor communication. But all of these challenges have internal roots.

We knew about this project for two months. Two months. And yet every single one of us waited until the last possible moment, our nervous systems so flooded by other finals and deadlines that this project became the thing we collectively agreed to ignore. When the deadline appeared like a bear on a hiking trail, we had nothing. No shared understanding of what we were writing. No communication about who was responsible for what. No foundation whatsoever.

Every external challenge is rooted in an internal one.

This doesn't mean external change is unhelpful. It means all change has to be rooted in internal understanding first. We weren't bad students. We were stressed students who lacked the self-regulation skills to start before our nervous systems were screaming at us. We weren't in medieval times, but we were wearing so much psychological armor it's a wonder we could still carry a backpack. (Check out The Stress Regulation Skill College Freshmen Are Missing to learn more about this.)

This isn't just a collaboration problem. It's a general problem. A staggering number of college students spend most of their semester in what I call the defensive zone: that tight-chested, shallow-breathing, can't-quite-focus state where your body is convinced a lion is chasing you, but the lion is just a Canvas notification. Some of us shut down into apathy, scrolling through TikTok while the deadline blinks in our peripheral vision. Some of us live in a wired-and-tired state, running on cortisol and dining hall coffee. Others are in chronic fight-or-flight, snapping at roommates because we haven't slept properly in weeks.

The causes are layered. Lacking self-regulation and self-understanding skills. Poor bodily health from bad sleep, worse nutrition, and exercise routines that consist of walking to class. Relational challenges of loneliness, comparison, and achievement complexes. The larger social structures like grades and the job market pressing down on us like atmospheric pressure we can't see but always feel. Oh, and not reading enough Conscious College.

When we bring that unprocessed stress into collaboration, our shadows come along for the ride. One member wants to work only for the grade because of parental pressure. Another is overly controlling because the last group project burned them. A third disappears entirely, too overwhelmed to even open the shared doc. None of this gets discussed because groups rarely create a trusting enough culture for anyone to name what's actually happening. So the stress sits under the surface like heat beneath a pot lid, until it blows.

And when we're in that defensive zone, the deeper cognitive modes we need for collaboration become almost impossible. Systemic thinking, perspective-taking, creative problem solving: these require a nervous system that feels safe enough to think beyond the next deadline. (Check out Parsing AI Truth From Bullshit In College for more on how stress shapes our thinking.) (Check out Stop Letting Emotions Run Your College Life to learn more about navigating emotions.)

But this lack of self-understanding isn't just an individual challenge. It translates to the whole group. Because when we don't understand ourselves, we definitely don't understand how differently other people participate in collaboration.

Collaboration Challenge 2: Unawareness of Collaboration Style Differences

We all have characteristic ways we like to collaborate: how we process problems, where we get energy, what frustrates us when working with others. I learned a lot about this from Collaborative Intelligence by Dawna Markova, though I've adapted the framework based on my own experience and biases.

These collaboration styles have a light and dark side. Unfortunately, they don't let you use the force. Each style can be incredible for a group, especially when you have balance between them. Strong collaborators learn to switch between styles depending on what's needed. But when we attach too hard to one, it causes problems.

Here's the sneaky part: we project our collaboration style onto others.

We assume everyone thinks, processes, and cares about the same things we do. In that doomed group project, I was operating as an innovative relational collaborator. I wanted to explore interesting angles, connect ideas across sections, make the thing mean something. So when I saw my group members operating through what I'd call a procedural shadow, just doing the bare minimum to check a box, I lost motivation. They probably looked at me and thought I was the problem too.

Here are the four collaboration styles in brief, light and shadow included. See if you can intuit which one or two you lean toward. It's not a black-and-white description; most of us shift between one or two depending on context.

Procedural

Procedural thinkers organize and implement. They're drawn to order, efficiency, and results.

On the light side, they set goals, create systems, and ensure follow-through. They like predictability and clearly defined steps. They get energy from action and closure.

On the shadow side, they become rigid, controlling, and action-obsessed. They rush to closure before the problem is fully defined. They tie self-worth to productivity, output, and being "on top of things." The kind of person who color-codes their Google Calendar and judges you for not having one.

Innovative

Innovative thinkers thrive on possibility, creativity, and connecting ideas that don't obviously go together.

On the light side, they love exploring abstract concepts and patterns. They generate new ideas or frameworks. They tend to disrupt status quo thinking.

On the shadow side, they exaggerate possibilities and lose touch with practical constraints. They're ungrounded, scattered, and addicted to novelty. They hoard inspiration without executing on it. I feel personally attacked writing this.

Relational

Relational thinkers are attuned to people, feelings, and group dynamics.

On the light side, they read emotional cues and anticipate unspoken needs. They focus on inclusion, harmony, and team well-being. They value trust and shared experience.

On the shadow side, they consult everyone before acting, stalling decisions in the name of inclusion. They become enmeshed, conflict-avoidant, and emotionally overextended. They sacrifice their own needs to maintain harmony or loyalty. If you've ever spent forty-five minutes deciding where to eat because one person didn't want to "impose" their preference, you've met this shadow.

Analytical

Analytical thinkers focus on logic, understanding, and structured analysis.

On the light side, they seek clarity, coherence, and logical explanations. They enjoy problem-solving and making sense of complexity. They prefer to reflect deeply before responding.

On the shadow side, they get stuck in past frameworks and resist approaches that haven't been fully vetted. They retreat into solitary thinking when collaboration is needed. Isolated, overly critical, and paralyzed by reflection. The person who rewrites the group's outline three times but never actually writes a paragraph.

How We Process Information

The second layer of collaboration style differences isn't about how we collaborate but how we prefer processing information. This doesn't mean we naturally process one type of information better than another. That's scientifically dubious. But we do develop preferences based on how we've grown.

The three types are auditory, kinesthetic, and visual. Personally, I resonate with all three in different contexts. I prefer visual thinking in reading and writing because, well, I've written over 400 blog posts. I love discussing ideas with others. And I am literally walking half the day. In the group project above, we cared way too much about the visual writing product, but never did the visual mapping work of seeing how everyone's sections connected to everyone else's. We never drew the web. We never talked through the structure out loud. We never walked through the logic together. As a result, we were all scatterbrained.

That's not the only reason we were scatterbrained though. The last and possibly most underappreciated collaboration challenge cuts deeper than style or stress. We simply lack the fundamental skills.

Collaboration Challenge 3: Bad Collaborative Wayfinding

In the group project at the beginning, there was no work done to come to common ground. We just used the project document given to us by our professor, which is what most students do. But this left us feeling a lack of purpose and ownership in what we were doing. We weren't aligned with each other in goals, process, or even basic definitions. We didn't do collaborative wayfinding.

Collaborative wayfinding is the meta-skill in collaboration of defining the common ground and navigating the problem space to design and implement solutions.

Think of it like this: if collaboration is sailing a ship, wayfinding is everything from choosing your destination to reading the wind to adjusting course when a storm rolls in. Our manner of navigating that group project was: oh shit, deadline's coming. Everyone on deck. Let's enter that whirlpool.

There are two parts to collaborative wayfinding: Common ground and navigation. You can also think of them as alignment and execution. Neither one ever officially ends but rather moves back and forth between each other.

Common Ground

Common ground is a shared understanding of what the collaboration is, why it's important, and how it will be done. Without it, you're five people rowing in five directions and calling it teamwork.

Most students' common ground is getting a written letter combined with a mathematical sign formally called an A+. I'm not blaming you. It's how many academic systems train us. But we can do better than that.

Real common ground includes purpose (why does this project matter beyond the grade?), outcomes (what does success look like?), and process. Process alone has layers: What design approach are we using? Who owns what? How is power distributed? What are our roles? Then there's scope (how much effort and time will this take), constraints (what do we know we're not doing?), motivations (why ar ewe doing this?), and context (what shared context is this project affecting?). The stuff that sounds boring to talk about upfront but saves you from a 3:00 a.m. panic attack later.

Navigation

Navigation is the meta-process of defining the problem space and finding and testing solutions. If common ground is agreeing on where the ship is going, navigation is the act of actually sailing it.

If we don't have good stress regulation and self-understanding (Challenge 1), of course we'll navigate poorly. A dysregulated crew can't steer through fog. If we don't understand each other's collaboration styles (Challenge 2), we'll misread the signals our crewmates are sending.

The beautiful thing about navigation is that there are near-infinite ways to do it. What you need to do is choose navigation pathways that are timely, wise, supported, and efficient. Most design thinking processes boil down to four steps that show up everywhere from IDEO to the Five Step Octalysis Design framework.

Almost all of them come together under four steps:

• Explore: Draw the problem space
• Ideate: Come up with ideas for that problem space
• Execute: Take action on those ideas whether it be creation, conversation, or something else
• Test: Test the ideas in cycles of reflection and iteration, going back through the four steps

The specific design process you use matters less then having the design frame in the first place. This is the juice I wish my group was thinking about before collaborating.

Pre-Sensing Failure Points

The strongest collaborators aren't just good at understanding collaboration intellectually. They can sense it in their bones. The hairs on their arms rise. Their gut squirms when the collaboration is pointed toward failure. This isn't mystical. It's pattern recognition trained through experience.

Pre-sensing failure works in three moves.

1. Intuiting: Sensing something might lead to a failure state. You notice the group is avoiding a conversation, or someone's been quiet for two meetings, or the timeline feels impossibly tight but nobody's saying it.
2. Extrapolating: Seeing how that small signal might cascade into a larger problem.
3. Responding: Doing something about it now, before the cascade hits.

Not sensing failure points leads to the three common outcomes that haunt group projects: Bad grade, which is the obvious one. No learning, which is the one nobody talks about but everyone feels. And overwork, where one person carries the team and silently resents everyone else for a semester.

Luckily, the more you build your pre-sensing abilities, the better you'll be able to respond before they happen.

The Beauty of Collaboration (Conclusion)

Collaboration isn't something to leave on the sidelines. It's a meta-skill that will improve every area of your life. In an age of AI, collaboration skills are one of the biggest differentiators we have. Machines can write decent paragraphs and crunch data faster than any study group. What they can't do is navigate the messy, emotional, deeply human process of building something meaningful with other people.

The collaboration skills we've been talking about aren't just relevant for group projects. They're the same meta-skills that organizations, communities, and civilizations need. The reason it's so hard in a group project is that nobody teaches it at any level. Imagine how different collaboration would look if every student, if all of society, came equipped with the skills above. If we understood our stress patterns. If we knew our collaboration styles and could recognize them in others. If we practiced wayfinding before we needed it.

There's one more thing on top of everything in this article I've been thinking about. It's one last token I'll leave for you as a thanks for reading. Why is collaboration really so hard?

Among many things, I think it's because deep down, we're scared. Scared of opening ourselves up profoundly to others. To really collaborate, I mean really collaborate, we can't just understand ourselves. We must be willing to show that self to others, make it vulnerable to change. That's an intimate act most college students, including past me, aren't often ready to stomach. Collaboration asks you to hold your own perspective loosely enough that someone else's can reshape it. That requires trust. That requires a nervous system calm enough to stay open. That requires the kind of self-knowledge most of us are still building.

Perhaps if I'd read this article before that final group project, I would have avoided such a catastrophic end to my senior year. But then I wouldn't have had time to play as much Disco Elysium.