Building a Studio That Outlasts Its Founder
Michael Condrey left Sucker Punch Productions in 2016. He had spent roughly a decade there, rising from programmer to co-president, and the studio came up with its current name on his watch. The interesting part isn't that he left, or even that the studio kept going strong after he departed, it's what his departure revealed about how a creative organization actually survives when the person everyone watched suddenly walks away. I ran into something similar when a lead engineer on my team decided to leave mid-development on a system overhaul we'd been running for fourteen months. The way people handled that gap told you everything you needed to know about whether the organization was actually resilient or just quietly held together by one person's attention. Condrey's time at Sucker Punch overlapped with the release of Infamous (2010), Infamous 2 (2011), and InFamous: Second Son (2014). Those weren't just commercial hits, they were proof-of-concept runs for a studio that operated with unusually flat decision-making structures for a PlayStation first-party developer. Creative decisions about the supernatural power systems, the moral choice mechanics, the urban exploration design — none of it required going through six layers of management approval. That kind of autonomy is easy to talk about in a keynote but genuinely difficult to sustain at scale. My own attempt at replicating a similarly flat structure for a live-service backend failed because someone always needed to make a call and nobody had actually agreed on who that person was. The workaround was painfully simple: I wrote down the decision rights. Not a RACI matrix, just a one-page document that said "if this crosses above X threshold, Person A decides; if below, Person B decides." It took two weeks to get everyone to sign off on it, and then it saved approximately three hours a week in meetings that used to orbit the same question. What Condrey modeled was organizational excellence without the organizational theater. Studios under Sony's first-party umbrella typically carry heavy process requirements — compliance checks, milestone reviews, quality gates. Sucker Punch found a way to run those gates without letting them become the entire point. The infrastructure existed but stayed invisible to the people actually shipping content. That's the counter-intuitive insight most people miss: the best organizational frameworks are the ones that don't feel like frameworks when you're inside them. You know they're there only when they break, which is usually during a crisis nobody planned for. I learned that the hard way during a porting deadline when our build system started failing at 3 AM and the person who understood the pipeline architecture was on vacation with no reception. Having a flat org chart didn't help because flat doesn't mean knowledgeable everywhere. What helped was documentation that wasn't written as policy, just as notes from someone who had actually dealt with the failure mode before.
Condrey also demonstrated something about leadership visibility that contradicts the usual founder-worship narrative. He eventually became comfortable with a setup where his name wasn't attached to the studio and where the credit structures reflected collective output rather than individual heroism. That sounds like virtue signaling until you consider what happens to studios where the founder's identity is inseparable from the brand. When that founder leaves or loses interest, the whole organization enters a credibility crisis. Sucker Punch didn't have that problem in any dramatic sense because they had already built their identity around the games rather than the executive. The tradeoff is that this model requires patience most people don't have. You can't fast-forward cultural maturity, and trying to force it usually creates the exact fragility you're worried about. The organizational excellence piece also shows up in how they approached failure internally. During the development of InFamous: Second Son, the team made calls about tone and scope that surprised stakeholders. Instead of escalating every variance, the leadership pattern was to set boundaries upfront and then trust the team to operate within them. This is different from micromanagement disguised as empowerment, which is what you get when you hear "we trust our teams" from someone who hasn't actually given anyone room to fail. The boundary-setting itself is the hard part. You have to define what "wrong" looks like before anyone crosses the line, and most organizations skip that because it feels negative to talk about failure modes in a planning meeting. Condrey and his leadership team didn't skip it, apparently, because the studio shipped three major titles across a seven-year window with consistent quality bars rather than one hit and two disappointments. There are clear downsides to this approach, and they deserve being stated plainly. Flat organizations with high autonomy don't scale linearly. Once you pass roughly forty to fifty people on a single project, communication overhead rises sharply regardless of how many tools you buy. I saw this firsthand when a team grew from thirty-eight to fifty-two and suddenly a decision that used to take an afternoon in Slack required a scheduled meeting with three people from different departments. The culture that worked at thirty-eight people required explicit reinforcement at fifty-two. Condrey's model isn't broken at that size, it just stops being self-sustaining without deliberate maintenance, and most people underestimate how much maintenance looks like. It's not a newsletter or an all-hands. It's the ongoing work of redistributing decision rights as the org chart shifts, which is exhausting and rarely recognized in performance reviews.
Another limitation worth noting is that this style of leadership depends on hiring people who don't need to be managed in the traditional sense. That works beautifully if your hiring bar is high enough to filter for self-direction. It does not work during layoffs or restructuring periods when you're forced to bring in people at lower experience levels. The autonomy model shifts from empowering to neglectful very quickly when the people operating it haven't developed the judgment the system assumes they have. I've watched competent teams become dysfunctional simply because the organization stopped hiring for autonomy and started hiring for availability. The framework itself didn't change, but the input changed and nobody recalibrated the expectations. If you're looking for something concrete to take from Condrey's track record, the practical takeaway is narrower than most leadership articles suggest. It's not about adopting flat hierarchies or removing middle management. It's about writing down decision rights, defining failure boundaries before crises happen, and accepting that organizational resilience requires more maintenance than most executives budget for. The rest is packaging.
Get the Full Details
