ConcernedApe Had Help on the Table. He Left It There.
Put this on while you read
In October 2021, Eric Barone posted a 50-second gameplay clip to Twitter alongside a short blog post. No studio announcement. No team credits. Just a brief note: he was building a new game called Haunted Chocolatier, alone as ConcernedApe again, and would share more when there was more to share.
Stardew Valley had sold 15 million copies by then. The free updates he’d shipped after launch, multiplayer in 1.3 and a full new island region in 1.5, had been built by one person. He’d ported the game to six platforms. He was a millionaire many times over, with a decade of proof that he could build things people wanted. Every rational signal pointed toward a studio.
He started over with the same constraint he’d had in 2011.
Barone had left a job at a movie theater in Redmond, Washington in 2011 with a concept for a farming RPG. He had a computer science background but no professional game development experience: no shipped titles, no industry contacts, no formal training in pixel art or music composition. He had the game he wanted to exist, which didn’t, and the time to try.
He taught himself to draw pixel art by doing it, building the visual language of the game as the game developed around it. The music came the same way: listening hard to the games he admired, figuring out what made a winter soundtrack feel like winter, composing each track to fit a specific time and season. The code connected everything: scheduling systems, friendship mechanics, crop timers, procedural cave generation, dozens of NPCs moving through daily routines. He built each piece and rebuilt it when it wasn’t right.
His publisher, Chucklefish, signed on in 2012 to handle distribution. Development stayed entirely his.
The timeline slipped. Followers of his Tumblr dev blog had been checking in since 2013, watching target dates move. The scope was real: a full RPG with seasonal content, a combat system, romance mechanics, a main story layered over years of optional side content. Adding people was the obvious answer to a timeline that kept expanding.
He kept going alone.
Stardew Valley launched February 26, 2016. It sold a million copies in the first 33 days and has since passed 30 million.
What that constraint produced isn’t only a headcount argument. Stardew Valley is a remarkably unified object. The pixel art, score, writing and systems share a sensibility, not because they were produced to a style guide but because the same person made all of them, with the authority to change anything the moment it felt wrong. The music doesn’t feel sourced from a contractor. The writing doesn’t feel like it passed through a separate team’s voice. Nothing in the game argues with itself.
That coherence was enabled by the constraint. Barone could reprioritize any morning without a meeting. He could cut a feature before it accumulated advocates. If the winter palette felt wrong in November 2013, he changed it that afternoon, and the decision cost nothing but his time.
The scope he brought to launch reflects the same discipline. Stardew Valley shipped without multiplayer, which came in 1.3 years later. Without voice acting. Without the feature surface that signals ambition to a publisher but dilutes what a game actually is. What launched was everything Barone had decided belonged there and nothing that hadn’t earned its place.
The 1.5 update in December 2020 is where the compounding becomes visible. Ginger Island, a full new region with new characters, new crops and a substantial endgame, would have shipped as paid DLC from a studio. Barone patched it in for free and kept going. The patch notes read like a sprint review summary. One person wrote them.
◆ Before you read on
What's the PM move here?
Think about the last time your team asked for more headcount to hit a roadmap target.
You predicted:
Most scope conversations happen under pressure. The roadmap is too large for the team, so the proposal is to grow the team. That framing treats scope as the fixed variable and headcount as the adjustable one. The choice of which to hold constant is itself a decision, one most organizations never make explicitly.
What Barone worked out, first by necessity and later by choice, is that scope and team size aren’t independent. Every person added to a creative project adds communication overhead, alignment work and competing aesthetic preferences. Decisions that one person makes in an afternoon become proposals requiring consensus. The thing you’re building starts to take on the shape of the team building it. Sometimes that’s fine. Often the shape of the team is not the shape the product needs.
The Scope Questions Most Teams Skip
What can we build well at the size we actually are? Not what do users want, not what would win a roadmap review. What is actually possible, finished and coherent with the team that exists.
Adding someone changes more than headcount. Who makes decisions. What gets preserved. What aesthetic preferences the product absorbs.
If the team stays this size, what has to go? Scope that only survives by growing headcount is borrowing against coherence.
The Haunted Chocolatier announcement is where the solo constraint stops looking like circumstance. By 2021, Barone had every option: the capital, the credibility and every signal the market could give him. He chose the same constraint he’d started with in 2011 because he’d seen what it produced.
The game that launched after four and a half years of one person’s decisions is not the game that would have shipped in two years with a team of six. It’s a different object, assembled differently, coherent in a different way.
30 million people found the one that shipped.
◆ Your Take
When you last asked for more headcount, what scope decision were you avoiding, and what would the product look like if you'd made it instead?
When you read this before, you wrote:
Your takeaway: