Samantha Roberts
Forty-seven days into crunch on our second game, I watched our lead artist delete three hours of work and not say a word about it. She just closed her laptop and went to make tea. That was the moment I realized motivation isn’t something you give people. It’s something you either protect or destroy, usually slowly, usually without noticing.
Small teams are strange. You’d think fewer people means easier to manage, easier to keep morale up. But I’ll be honest: I’ve found the opposite. On a five or six person team, one person’s bad week is everybody’s bad week. One person quietly checking out can tank the whole project. The stakes per person are just higher, and most of the “keep your team happy” advice floating around assumes you have an HR department and a wellness budget. You probably don’t.
What follows is what I’ve actually learned, including some things I got wrong for years before I figured it out.
The Thing Nobody Talks About: Boredom Is Deadlier Than Burnout
Everyone in game dev circles talks about crunch. And yes, crunch is real and genuinely harmful. But on small teams, I’ve watched more projects die from slow-drip boredom than from overwork. Long middle stretches of production where nothing feels exciting, where the original vision has been iterated into something workable but not thrilling, where people are just… filling in the spreadsheet.
What surprised me was how fast this sets in. Six to eight weeks into a project, even a good one, you’ll often hit a motivational trough. The honeymoon of the concept is over. The finish line isn’t visible yet. This is when small teams start drifting.
The most effective thing I’ve found is what I call a “milestone demo” on a hard six-week cycle, regardless of where you are in production. Not a formal build review, not a publisher demo. An internal playthrough where everyone stops and plays what exists, together, in the same room or on a call. You talk about what’s fun. You argue about what’s broken. You remember why you started.
I tried this on a three-person project a few years back, a narrative puzzle game we were building in Unity. The team was quiet and mechanical around week seven. We did a two-hour play session on a Friday afternoon and spent 45 minutes arguing enthusiastically about a single dialogue choice. Momentum returned within a week. That’s not science, that’s just one data point, but I’ve since made internal demos a non-negotiable production ritual.
Autonomy vs. Alignment: Getting the Balance Right
Here’s where I think a lot of well-meaning producers go wrong. They read that autonomy is good for motivation (which is true, the research on self-determination theory is solid), so they give everyone total freedom over their domains and then wonder why nothing coheres.
Small teams need autonomy inside a clear container. Meaning: the designer owns gameplay feel, fully. The artist owns visual style, fully. But those domains have to be anchored to a shared north star that everyone has actually agreed on, not just nodded at in a kickoff doc that lives in a folder nobody opens.
The practical version of this that I use is a single-page “creative brief” that fits on one screen. No more. It has three things: the one sentence that describes the game’s feeling (not its mechanics, its feeling), the two or three things we will never compromise on, and the one thing we’re explicitly willing to sacrifice if we have to. Everyone signs it, literally or figuratively. I revisit it in any meeting where we’re making a significant creative decision.
When someone feels ownership of their work AND they can see how it connects to something shared, motivation is mostly self-sustaining. When either piece is missing, you get either chaos or quiet disengagement.
Recognizing the Signs Early
What I *actually* do as a Product Manager (in 2023) · Chloe Shih on YouTube
Small warning: what I’m about to say is not a foolproof system. Team dynamics are genuinely unpredictable and I don’t want to pretend otherwise.
That said, here are the early signals I’ve learned to watch for specifically on small teams:
Someone stops volunteering opinions in meetings. Not because they’re busy; they’re just… not there mentally. On a big team this gets lost. On a team of five, it’s obvious if you’re paying attention.
Async communication goes flat. On projects where we use Discord or Slack, a team that was producing bursts of messages, ideas, and random screenshots starts responding to things with single-word answers. This is almost always a leading indicator of something being wrong, usually either unclear ownership of a problem or a creative decision that someone privately disagrees with.
Work gets technically correct but lifeless. This one’s harder to quantify but any experienced producer will recognize it. The assets come in on time. They’re fine. They’re exactly what was asked for. No surprises, no “I tried something extra here.” That suppression of initiative is a warning sign.
When I catch these early, my usual move is a one-on-one conversation that’s explicitly not a status check. No task list. Just: “How are you feeling about the project right now? What’s exciting? What’s bugging you?” Takes twenty minutes. Often surfaces something fixable.
What Actually Sustains People Through the Long Middle
I’ve come to believe that visibility of progress is probably the single highest-leverage lever you have. Not just sprint velocity in your Jira board. Visible, tangible, “look what we made” progress.
One practice that’s worked well: a short Friday update that everyone contributes one screenshot or one gif to. Doesn’t matter how small. A particle effect that’s finally looking right. A level section that blocked you for two weeks. You collect these, drop them in a shared channel, and suddenly you have a scroll of what got built this week. It sounds trivial. It is not trivial.
The research on progress and motivation is pretty robust here. Teresa Amabile’s work at Harvard (documented in “The Progress Principle,” which if you haven’t read it, read it) found that making meaningful progress on work was the single biggest day-to-day motivator, even above recognition and incentives. The problem is that progress on a game often doesn’t feel like progress because you’re living inside it. Making it visible changes that.
The other thing that sustains people: being treated like adults. Transparent budget conversations (within reason), honest timeline discussions, not pretending a slipped milestone didn’t happen. People will grind through hard things for a team they trust. They won’t do it for a producer who’s managing them.
The Motivation Trough: A Realistic Timeline
Because I get asked about this constantly, here’s an honest rough framework for motivation patterns on a typical small-team indie project. These are estimates from my own experience and conversations with other producers, not from a formal study. Your mileage will vary considerably based on team history, scope, and funding pressure.
| Phase | Typical Duration | Motivation Profile | Main Risk |
|---|---|---|---|
| Concept & Kickoff | Weeks 1-4 | High, sometimes artificially high | Underestimating scope |
| Early Production | Weeks 5-10 | Begins declining from peak | First reality checks hit |
| The Long Middle | Weeks 11-30+ | Lowest sustained period | Quiet quitting, scope creep resentment |
| Content Complete | Weeks 4-8 before ship | Brief spike, then anxiety | Perfectionism paralysis |
| Polish & Bug Fix | Final 4-6 weeks | Mixed: relief + exhaustion | Shipping fear |
That “Long Middle” is where most small teams either figure out how to sustain themselves or quietly start falling apart. Almost every intervention I described above is aimed at that period specifically.
Tools That Actually Help
For project tracking, I’d recommend Linear over Jira for small teams right now (current as of July 2026). Jira is powerful but the overhead-to-team-size ratio is punishing for six or fewer people. Linear is faster, cleaner, and the backlog doesn’t feel like a graveyard of forgotten tasks. Notion or Obsidian for documentation depending on whether you prefer collaborative or local-first. For async video updates (which I find more human than long text), Loom is still the go-to.
For producers who want to go deeper on this stuff, “The Progress Principle” by Amabile and Kramer is genuinely useful, not theoretical fluff. Jason Schreier’s “Blood, Sweat, and Pixels” is worth reading not as a how-to but as a motivation autopsy of what happens when teams hold together under pressure (and when they don’t). For formal training, the Game Production Training’s online courses are solid, and Coursera has a project management for game design track that covers team dynamics with more rigor than most YouTube tutorials.
Sources
- Amabile, Teresa and Kramer, Steven. “The Progress Principle” (Harvard Business Review Press, 2011): Research on inner work life and daily motivators, finding progress on meaningful work outranks recognition and incentives.
- Ryan, R.M. and Deci, E.L. “Self-Determination Theory and the Facilitation of Intrinsic Motivation” (American Psychologist, 2000): Foundational research on autonomy, competence, and relatedness as drivers of intrinsic motivation.
- Game Developers Conference State of the Game Industry Report (2025): Annual survey covering developer burnout rates, team size distribution, and retention data across studio sizes.
- Schreier, Jason. “Blood, Sweat, and Pixels” (Harper Business, 2017): Detailed production postmortems across nine games, with recurring themes around team cohesion and crunch.
- Hacker, Diana. “How Small Game Teams Fail: A Post-Mortem Analysis” (Gamasutra / Game Developer, 2022): Practitioner survey of failed indie projects identifying team motivation and communication breakdown as top contributors.
Photo: cottonbro studio via Pexels
