Chapter 73 : The Team Expansion
[Gardner Analytics Office. June 2015, Monday, 8:45 AM]
The elevator was new. Not literally new. The freight elevator had been in Manny's building since the 1970s. For decades it hauled sandwich supplies between the ground floor and the storage basement. But Sarah had commissioned its renovation three weeks ago. Seventy-five people climbing two flights of stairs twenty times a day was an engineering problem. Sarah solved engineering problems with infrastructure.
The elevator's door opened onto the second floor with a grinding mechanical complaint that Marcus had diagnosed as "a bearing issue that will either fix itself or kill someone, probably in that order." Ethan stepped out into a space he barely recognized.
Seventy-five people. The number had materialized through a hiring velocity that Sarah managed with the same precision she applied to training pipelines. Candidate throughput, conversion rates, onboarding latency: she tracked each metric in a spreadsheet that had grown from one tab to twelve. The two floors above Manny's had been reconfigured twice in four months: first the expansion into the adjacent unit, then the second-floor buildout. Now a full renovation was turning the old storage space on the mezzanine into a row of glass-walled meeting rooms with whiteboards.
The faces were the problem. Ethan walked from the elevator to his office: a twenty-step path through the second floor's engineering section, and counted the people he recognized. Fourteen. The remaining eighteen were names on an org chart that Sarah updated weekly and Ethan reviewed with decreasing frequency. He knew their ratings. Talent Resonance tagged everyone who passed through his visual field, a persistent background hum of numbers attached to faces, but ratings weren't names, and names weren't relationships.
A woman at a desk near the window looked up as he passed. Her badge read HELEN, not to be confused with Helen Park, Vincent Mora's VP of Engineering at Hooli, a coincidence that the universe apparently found amusing. Gardner's Helen was a 6.5, hired two weeks ago for the documentation product's quality assurance team. She smiled politely at Ethan. The smile of a person greeting a colleague whose name they knew from press releases rather than conversation.
"Good morning," she said.
"Good morning, Helen."
The fact that he knew her name produced a micro-expression of surprise: the brief widening of eyes that communicated he knows who I am — that told Ethan more about his company's culture than any employee survey could. The CEO knowing a QA engineer's name was noteworthy. At a fifty-person company, it would have been default. At seventy-five, it was exceptional. At a hundred, which the hiring pipeline projected by September: it would be impossible.
Sarah was waiting in the conference room. Not the door-table. That relic now sat in the mezzanine storage area. A real conference table had replaced it. The new one seated twelve and had been purchased from an office furniture liquidation sale for a price that Sarah described as "offensive to the concept of depreciation." The chairs were ergonomic. The projector was ceiling-mounted. The whiteboard covered an entire wall.
"Organizational review," Sarah said. She'd prepared slides, not the minimal presentations she used for investors, but a comprehensive analysis of the company's structural problems, formatted with the rigor of an engineering post-mortem . Sarah treated organizational dysfunction like software bugs: system failures with identifiable root causes and fixes you could implement.
Slide one: Communication Breakdown.
"Three instances last week of teams duplicating work because they didn't know the other team was working on the same feature. The documentation product team built a prompt optimization module. The research team built a prompt optimization module. Neither team knew about the other until they both submitted pull requests to the same repository on the same day."
Slide two: Decision Bottleneck.
"Every technical decision above team-lead level requires your approval. You approved fourteen decisions last week. Average time from request to approval: three-point-four days. That latency is killing velocity. Engineers are waiting for you to review things you don't have time to review."
Slide three: Cultural Drift.
"The original team, the people who were here before the Series A, and the new hires operate as separate tribes. They eat at different tables. They use different Slack channels. The original team calls the company 'we.' The new hires call it 'Gardner.' That distinction matters."
Priya entered during slide three, carrying her I survived peer review mug and a stack of papers that represented the GPT-2 evaluation results she'd been compiling since the training completion. She sat beside Sarah with the practiced efficiency of two people who'd learned to share meeting space without territorial negotiation.
"The research team has the same problem," Priya said. "I have twelve researchers now. Four are original hires who understand the architecture's history. Eight are new hires who understand the architecture's math. The history people don't trust the math people's instincts. The math people don't trust the history people's assumptions. I spend forty percent of my time mediating instead of researching."
The diagnosis was clear. The prescription was structural.
"We need a formal hierarchy," Sarah said. Slide four: an org chart. Clean lines. Defined roles. Reporting structures that eliminated the ambiguity of a flat organization trying to operate at seventy-five-person scale.
The chart showed three pillars. Engineering (under Sarah, now formally COO). Research (under Priya, now formally CRO). Business Operations (under a new hire, VP of Operations, position unfilled). Ethan sat above all three as CEO, with direct reports limited to Sarah, Priya, the future VP of Ops, and Monica in her advisory capacity.
"COO," Ethan said, reading Sarah's proposed title.
"Chief Operating Officer. It's what I've been doing for six months without the title. The title gives me authority to make decisions without routing them through you." Sarah's voice carried the matter-of-fact directness she used for proposals she'd already decided were correct. "You approved fourteen decisions last week. I could have approved twelve of them. The remaining two required your technical judgment. Two decisions per week is a reasonable load for a CEO. Fourteen is not."
"CRO," Priya said. "Chief Research Officer. Same logic. Research direction, hiring, publication decisions. I'm making them anyway. The title makes it official and stops the new researchers from escalating to you every time I say something they disagree with."
The promotions were necessary, overdue, and. Ethan admitted to himself as he studied the org chart: a recognition that the company had outgrown his ability to operate as both its architect and its manager. The first year had been building: code, architecture, models, the technical foundation that everything rested on. The second year was becoming management: people, processes, communication, the organizational infrastructure that let the technical work continue without the founder's hands on every keyboard.
"Okay," Ethan said. "Sarah, COO. Priya, CRO. Effective immediately. VP of Ops, start the search this week."
Sarah changed the slide. The org chart updated with their names. The structure materialized on screen with the clean lines of a system designed to function at scale. The Transformer architecture had the same clean lines. Layer upon layer, each one handling a specific function, the whole greater than its parts.
Priya left to inform her research team. Sarah stayed to discuss implementation details, reporting cadences, decision authorities, escalation procedures. The administrative machinery of a company that was becoming what Ethan had built it to become, at the cost of the intimacy that had defined its beginning.
The callback from the first month, three people in a room above a sandwich shop, sharing stale Cheerios and writing code that would change the world. The memory surfaced sharply across sixteen months of distance. The company had thirty-five hundred square feet, seventy-five employees, twelve million dollars in the bank, and a CEO who missed writing code like a grounded pilot misses flying.
That night, after the office cleared, Ethan sat at his desk in the quiet building and wrote a function. Nothing useful: a small Python script that sorted a list of numbers using an attention-based comparison operator. It was a toy. It served no purpose except to let his fingers remember what they'd once done every day. The code was clean. The syntax was correct. The output was trivial.
He saved the file. Closed the laptop. The building was dark except for the server rack's status lights and the glow of Manny's exit sign two floors below.
Seventy-five people. Three C-suite officers. An org chart with clean lines and defined roles. A company that operated whether its founder wrote code or not. That was the goal. It didn't feel like achievement. It felt like distance: the space between a founder and the thing they'd founded, widening with every hire, every process, every structural decision that converted chaos into order.
The elevator groaned in the shaft. Marcus was still in the building: the infrastructure team worked late because infrastructure problems manifested at 2 AM with the malicious timing of gremlins in the machine. His keyboard clicked somewhere on the mezzanine level, the sound carrying through the empty office like a heartbeat in a quiet chest.
Ethan deleted the Python script. The code had served its purpose: a reminder that the hands that built the company's architecture still worked, even if the company no longer needed them to.
✦ ━━━━━━━━━━━━━━━━━━━━━━━━ ✦
Read more chapters for free at unwrittenrealm.com
✦ ━━━━━━━━━━━━━━━━━━━━━━━━ ✦
TL;DR — Patreon has the chapters ahead.
Silver / 10 ahead
Gold / 15 ahead
Platinum / 20 ahead, no weekly wait
That's it. patreon.com/fanficwriter1
If reviews aren't your thing, no pressure — they do help though.