Home Creators Posts Import Register Favorites Logout

Content

CHAPTER 127: The Wedding, the Five Rules, and the Two Teams

Claire got married one Saturday in April at a Sonoma vineyard she had chosen because the catering cost $45 per person instead of the $120 the San Francisco venues charged.

"It's the same wine," Claire had told Margaret when Margaret suggested a place in Napa. "It's the same food. It's the same ceremony. The difference is that in Sonoma I save eight thousand dollars and with those eight thousand dollars I pay two months of NG Store servers."

Margaret didn't argue. Margaret had stopped arguing with Claire about money when Claire was fourteen and proved to her with a spreadsheet that the brand-name cereal and the generic had the same nutritional value. There were battles Margaret had learned not to fight, and anything that involved Claire and a spreadsheet was one of them.

The vineyard was beautiful in the way that Sonoma things are beautiful: effortlessly. Green hills with rows of vines that extended to a horizon of oaks. A white wooden pergola where Claire and David stood in front of a judge Claire had chosen because he was the most efficient in the county: a 12-minute ceremony, no frills, no unnecessary readings. Claire had optimized her own wedding the way she optimized everything: finding the exact point where the quality was maintained and the waste disappeared.

George was the best man. He stood next to David in a suit Margaret had bought him because George would have gone in the same unironed shirt he wore for the Edge interviews. The suit fit him well. George looked like what he was: a thirty-year-old man who resembled his father and who was about to watch his sister get married with the same expression Richard had: restraint that restrained nothing because the emotion overflowed anyway.

Claire walked toward the pergola on Richard's arm. Richard walked slowly, measuring each step so his legs wouldn't tremble. Margaret was in the front row with a handkerchief that was already wet before Claire reached the pergola. Richard didn't cry. Richard was of the school of men who don't cry in public, a rule he had kept for sixty-five years with the discipline of a mechanic who takes care of his tools. But his lip trembled in a way that anyone who knew him would have identified as the Richard Hightower version of crying: the tremble that said everything the voice wasn't going to say.

David waited with the calm of a man who knew Claire was going to arrive because Claire always arrived where she said she was going to arrive, at the time she said she was going to arrive, with the budget she had allocated to arrive. David was a financial consultant, a man who understood structures and loads and the patience necessary to build things that don't fall down. Loving Claire required exactly that: understanding the structure, accepting the load, and having the patience of someone who knows that what he's building is worth the effort.

The ceremony lasted 12 minutes. As Claire had planned.

* * *

The reception was on a vineyard terrace with a view of the hills. Sixty people. Half were family and friends. The other half was NGS.

It was the first time George saw the two families together in a space that wasn't an office. Marcus Webb sitting next to Richard, telling him about the Oakland murals Richard knew from the shop. Marcus had drawn the wedding invitation by hand: a watercolor of the vineyard with the initials C and D intertwined in the corner, in the style Marcus used for the games' concept art but applied to something that had nothing to do with vampires or insects or witchers. The invitation was framed on the newlyweds' table.

Daniel and Alex argued about servers with David, who as a financial consultant understood enough about infrastructure to follow the conversation without fully understanding it. Elena and Priya at a table with Margaret, the three of them laughing at something George couldn't quite hear but that he suspected involved stories of George as a child that Margaret kept as ammunition for exactly these occasions.

Tomás was at the bar with his red notebook, because Tomás carried his red notebook everywhere and because someone had asked him what it was and Tomás was explaining his bug-tracking system with the passion of a man who loves what he does even though what he does is find things that are wrong. Torres, the writer, talked with the mother about crime novels with the enthusiasm of someone who finally found a person who read the same thing he did.

And Lena.

Lena played the piano at the reception. The vineyard had an upright piano on the terrace that no one used and that was tuned out of obligation: half the keys perfect, the other half slightly off. Lena sat down and played a piece she had composed for the wedding. It wasn't Dirtmouth or City of Tears or the Slavic folk she was composing for The Witcher. It was something new. Something with no name or genre or reference. Something that sounded like what George felt when he looked at Claire and David together: the calm certainty that something was right. That two people had found the way to fit their edges together without filing down their corners, and the piece captured that without words because words would have been too small for what the music was saying.

Richard listened with his eyes closed. Margaret cried again. Claire didn't cry because Claire didn't cry in public. But David saw her squeeze the napkin with her left hand throughout the piece, and David knew that the napkin was the Claire who couldn't cry in public crying in private.

George gave the best man's speech after the piece. It was short. George wasn't one for long speeches. He said Claire was the smartest person he knew and that David was the bravest man he knew for having married her. The NGS team laughed. Claire didn't laugh. Claire looked at George with the expression she only gave George: that of a sister who knows her brother has just said something that is true and that is funny at the same time, and that the combination of truth and humor was the Hightower way of saying I love you without saying I love you.

George looked at the sixty people on the vineyard terrace. The blood family and the work family, mixed for the first time in a space where no one talked about engines or sales or deadlines. And he thought that the two families resembled each other more than it seemed: both built piece by piece, with patience, with no instructions, with the trust that the right people in the same place for enough time end up forming something that works.

* * *

A month after the wedding, George wrote the document that was going to define how NGS grew.

He titled it "Operational structure of NGS for the expansion phase" in front of the team. In his head he titled it "How NOT to be Ubisoft," because everything the document said was designed to avoid what George had lived through in his previous life.

At Ubisoft, George had watched a creative studio become a corporation. The process was gradual and invisible: each new hire added a layer. First a manager. Then a manager of the manager. Then a producer who supervised the manager of the manager. Then an approval process that required every decision to pass through three levels before being executed. Then meetings to discuss the approval processes. Then meetings to plan the meetings. The result was that an artist who wanted to change the color of a wall had to ask permission from his lead, who asked permission from the art director, who asked permission from the producer, who discussed it in the weekly meeting, who approved it in the next sprint. Two weeks to change a color. In a studio where the color of the wall should have been the decision of the artist who was painting it.

George wrote five rules in the document. Five. Not fifteen. Not a thirty-page procedures manual. Five rules that fit on one sheet and that anyone in the studio could memorize.

Rule 1: No team has more than 20 people. If a team grows beyond 20, it subdivides into two teams with two leads. The reason: in a team of 20, every person knows everyone else. In a team of 40, there are people who don't know each other. And the people who don't know each other don't collaborate, they compete.

Rule 2: The leads work. Not only manage. The art lead paints. The programming lead programs. The design lead designs levels. If a lead spends more than 50% of their time in meetings and emails instead of producing work, something is wrong and has to be corrected.

Rule 3: Zero producers. The word "producer" doesn't exist at NGS. The leads are responsible for their teams, their deadlines, and their quality. They don't need someone to tell them when to deliver or to make PowerPoints about the project status. If a lead can't manage their team without a producer, the lead needs to be replaced, not assisted.

Rule 4: Meetings of 30 minutes maximum. With a visible timer. If a decision isn't made in 30 minutes, the meeting wasn't necessary or the decision needs more information than a meeting can provide. In both cases, sitting 60 minutes in a room solves nothing.

Rule 5: Any person in the studio can talk to George directly. No intermediaries. No schedulers. No "send an email to my assistant." George has no assistant. George eats in the cafeteria with the team. George answers emails the same day. If a junior artist has an idea they want to discuss, they discuss it with George. Not with their lead who discusses it with their director who discusses it with George three weeks later when the idea is no longer relevant.

George presented the five rules to the team one Monday in May. He wrote them on the whiteboard with permanent marker, as Daniel had written NGN three years earlier so no one would erase them.

"We're going to grow," George said. "From 45 people to more than 100. Each new person is an opportunity for the bureaucracy to grow. These five rules are the vaccine. If someone proposes a process that violates any of these rules, the answer is no. It doesn't matter how reasonable it sounds. It doesn't matter how many studios do it. It doesn't matter if the management book says it's best practice. The answer is no."

Claire, who was sitting in the front row with her accounting notebook, added a sixth rule that wasn't in George's document:

"Rule 6: If Claire says there's no budget, there's no budget. This isn't a George rule but a rule of reality."

The team laughed. George didn't add it to the whiteboard. He didn't need to: it was inscribed in the structure of the universe with the same permanence as the laws of thermodynamics and the tendency of projects to cost more than estimated.

* * *

In June, George divided NGS into two development teams and one support team.

It wasn't an easy decision. For nine years, NGS had functioned as a single team where everyone worked on the same game. Castlevania was everyone's. Isaac was everyone's. Hollow Knight was everyone's. Los Santos was everyone's. The culture of the studio was that each person contributed to a single project and that the project was everyone's. Two teams meant that culture divided. That the people of Team Witcher weren't going to see what Team Souls did until it was finished. That Marcus Webb was going to lead the art of both games but that his time was split in two. That Lena was going to compose for both but that her head had to inhabit two opposite musical worlds.

George announced the division at a company-wide meeting. Forty-five people in the conference room Claire had expanded for the third time because every time NGS grew, the room got small and Claire solved the problem by moving a wall with the same naturalness with which she moved a cell in a spreadsheet.

"Team Witcher," George said. "Twenty people initially, thirty-five when we're in full production. I direct. Lena composes. Elena leads level design. Torres leads narrative. The most ambitious RPG we've made."

"Team Souls," he continued. "Fifteen people initially, thirty in production. A new project director I'm going to hire externally. Marcus Webb leads art. Priya leads environments. The most difficult action RPG we've made."

"Support team: Daniel and his engine team maintain NGN 2.0 for both projects. Alex and his team maintain NG Store. Tomás splits QA between the two games. Claire supervises everything from orbit."

The room processed the information. George saw the expressions: curiosity in the programmers who wanted to know which team they were going to be on, enthusiasm in Elena who was already thinking about the Witcher levels, a shadow of concern in Marcus who knew that leading art for two simultaneous games meant his brain was going to live in two different centuries at the same time.

"Are you going to direct both?" Claire asked from the front row.

"I'm going to direct Witcher daily and Souls creatively. Team Souls is going to have a project director who handles the day-to-day. I define the vision and review weekly."

"George, that's impossible."

"I've done it before."

Claire looked at him. George looked at her. Claire didn't know that "I've done it before" referred to the years at Ubisoft where George had watched creative directors supervise multiple simultaneous projects. They did it with PowerPoints and status meetings; George was going to do it with creative vision and weekly review. But the principle was the same: one person could maintain the creative coherence of two projects if they delegated the execution.

"If it doesn't work," Claire said, "we'll know in three months."

"It's going to work."

"That's what you said about Los Santos. And Hollow Knight. And Isaac. And Castlevania."

"And it worked every time."

"Every time was one project. This is two."

"It's two projects with forty-five people who know what they're doing. I trust the team."

Claire nodded, moved less by conviction than by what she had learned in nine years: that arguing with George about the viability of something George had decided to do was like arguing with gravity about the direction things fell. Gravity didn't listen to arguments. Neither did George. And both, so far, had been right.

* * *

George let each person choose their team.

He didn't assign anyone. He put the two lists on the whiteboard, below the five rules written in permanent marker, and said each person could sign up wherever they wanted with one condition: the teams needed a balance of skills. If all the artists chose Witcher, George would reassign to balance. But the preference of the individual was the priority.

The results were revealing. The artists split half and half: the ones who preferred medieval stylized realism chose Witcher, the ones who preferred dark Gothic chose Souls. Marcus Webb chose Souls without hesitation: "The monsters of Lordran are the most interesting thing I've drawn since the Knight." The programmers leaned toward Witcher because the RPG had more complex systems: narrative branches, alchemy system, NPC AI with contextual reactions. Dark Souls was simpler in code but more precise: every frame of combat mattered, every hitbox had to be exact. The level designers split by philosophy: Elena chose Witcher because the design of narrative missions was her specialty. The designers who preferred the design of interconnected spaces, the legacy of Hollow Knight, chose Souls.

In a week, the teams were formed. Team Witcher: 22 people. Team Souls: 15. Support team: 8. Total: 45. Exactly the same people. But organized differently. Like two families within the same house, each one with its personality, each one with its project, each one with the certainty that what they were building was the most important thing they had done.

George looked at the two lists on the whiteboard. Below Team Witcher, the names of the people who were going to build the Continent. Below Team Souls, the names of the people who were going to build Lordran. And below both lists, the five rules written in permanent marker that guaranteed no team would grow enough to forget that people mattered more than processes.

Two teams. Two worlds. One office. Five rules. And a director who carried two notebooks in his backpack every morning, the brown leather one and the black one with the red edge, like a man who walks with two maps of two countries that didn't exist yet but that he was going to build with the hands of forty-five people who chose where they wanted to be.

The witcher and the knight were going to be born at the same time.

End of Chapter 127

Comments

No comments found for this post.