Chapter 13 The Designer

For the next six months, Qiao Shan worked as a consultant on Project Horizon. He reviewed class designs. He playedtested abilities. He wrote strategy guides that the development team would use as a baseline for balance. The game went through three beta tests. Qiao Shan was there for each one, providing feedback that the team incorporated. The new game launched to critical acclaim. It had a class called "Strategist" — inspired by Qiao Shan's philosophy. The class description included a quote from him: *"Strength comes not from what you can do alone, but from what you can build with others."* The launch generated 100,000 concurrent players on day one. Debt Collectors guild moved to the new game as a unit. Qiao Shan didn't join as a player. He joined as a developer liaison — half-time consultant, half-time player. Liaison work settled into a bimodal existence. Tuesdays and Thursdays belonged to the studio, where his employee badge photographed him mid-sneeze and became office legend within the hour; weekends belonged to the servers, where he logged in under his own unremarkable name and answered newcomer questions in trade chat like any other helpful stranger with too much free time. The case that defined the role surfaced in month two: a petition from a raider with limited hand mobility arguing that Strategist rotations punished anyone unable to mash keys on rhythm, and that hold-to-confirm inputs deserved identical recognition. The ticket had bounced between departments for six weeks — liability said legal, scope creep said accessibility, not-my-metric said production. Qiao Shan wrote a single page reframing the whole dispute as consent applied to input: a choice offered rather than an accommodation granted, cost disclosed, dignity preserved. He walked that page desk to desk until three department leads co-signed it, and hold-to-confirm shipped globally before the next season turned. The petitioner spoke at the internal design review afterward and made the balance team cry twice, which he counted as better feedback than any survey. Anonymity revealed itself as the position's secret perk. Nobody on the new servers knew his face or his history, and he guarded that obscurity with real discipline until a pickup dungeon dismantled it — his Strategist parsed dead last on damage, took a thorough flaming from a sixteen-year-old tank, apologized with complete sincerity, and enjoyed approximately every second of being nobody again. Some reputations are best maintained by regularly escaping them. Migrating the guild consumed eleven days of logistics that Aurelia ran like a military operation. Name reservations were filed at dawn on transfer day; the charter's first page went up verbatim in whatever hall they claimed; the reimbursement fund crossed servers after its decimal points were audited three separate times by people who did not trust each other, which was precisely why the system worked. Five thousand players moved as one organization without losing a single roster record, and rival officers who had called the feat impossible quietly began photographing their own command structures for reference. The studio encountered the guild as data long before it met them as people. With written permission, analysts studied anonymized rotation logs to learn whether consent-based mechanics depressed throughput; every finding pointed the opposite direction, and two designers started attending open Ledger drills as silent observers with notebooks full of heresy. Trust compounded in both directions, slowly, the way it always does when nobody attempts a shortcut. His side of the bargain included mentorship nobody had requested. A junior product manager kept drifting toward engagement-hacking tricks — daily streak guilt, fear-of-loss popups — and Qiao Shan taught her the three questions adapted for features instead of recruits: what does this ask players to give, who benefits when they give it, and what happens to them if we shut down tomorrow. She taped the questions inside her notebook cover and eventually ran the live-service division, which surprised no one who had read her early tickets. Every major patch he personally leveled a fresh account through the support path start to finish and filed a one-page report under a signature nobody could trace. The team called those documents ghost reports and competed to spot them before anyone official did. Three balance changes in the first year traced directly back to pages written by a ghost who happened to hold a badge with the same sneezing face. Late one Friday he was leaving the building when the lobby news ticker caught his eye: an anniversary retrospective about the original Apex servers, a decade of history, nostalgia traffic surging across every archive site. Something in the phrasing itched beneath his skin like an unread ledger line. He rode the train home composing balance arguments against a feeling, lost the debate, and slept worse than any dashboard suggested he should. The badge outlived its eligibility for replacement. Human resources offered fresh photos quarterly; he declined quarterly, on the grounds that staff had suffered sufficient novelty, and by winter the sneezing portrait hung laminated above the coffee machine like a saint's day card nobody dared retire. His memos calcified into an internal genre. A proper Qiao Shan page, engineers explained to new hires, states what players are asked to give, names who benefits, and prices the trust being expended — three paragraphs maximum, no adjectives performing arithmetic's job. Review meetings began requesting such pages by name, which routed requests through his calendar, which quietly restructured his job around other people's features. Then came his structural bequest: the player council. Elected quarterly, granted standing agenda access, entitled to deliver one unfiltered grievance per session directly to production leadership, the body operated on rules lifted nearly wholesale from guild charters — governance problems, he had concluded, are one problem wearing different skins. Rival studios sent observers. Two copied the mechanism openly, which he logged as the correct quantity of flattery. Hana toured the office exactly once, pronounced the desk clinically lifeless, and returned days later bearing a potted cactus labeled resilience in marker. Real cacti surrendered to crunch schedules; hers lasted eleven months before wilting past rescue, whereupon the design team pooled cash for a plastic successor. Both pots shared the windowsill thereafter, true and false side by side, which designers called a metaphor and Hana called inventory. As for the anniversary-week unease, he handled a hunch the only way bookkeepers can: by filing it. A short memo requested five-year cost projections for legacy server infrastructure, and the response took six weeks, arrived strangely thin, and answered questions nobody had asked while skipping every one that mattered. Living inside ordinary time, he flagged the exchange as odd, scheduled a follow-up for next quarter, and kept the email — though much later, once everything surfaced, its thinness would read exactly like a confession. --- ---