Chapter 3: The Knockout Organism
How corporate evolution selects for compliance over clarity.
By Ryan Stephen, former Director of Design at Sortly, Inc. Background in evolutionary biology, chemistry, and product design. These essays use one company as a specimen to examine what happens when organizations lose the ability to hear the people inside them, how AI is about to make it worse, and why designers might be the only ones left to ask why.
The Deletion
In genetics, a knockout experiment involves removing a specific gene from an organism to study what happens in its absence. You don’t remove all the genes and you don’t kill the subject. You disable one thing and watch. The organism usually survives, and sometimes even thrives, building its entire phenotype around the absence, developing compensatory behaviors that only make sense in the context of what is no longer there. The compensations are the data.
I spent over two years inside a company that was successful by any conventional metric. Revenue was climbing, the customer base was expanding, and the product carried thousands of five-star reviews from an audience that genuinely loved what it did for them. Yet the organization exhibited a structural pattern I couldn’t explain through normal business logic. Departments operated in near-total isolation in regards to shared success and collaboration because each team had its own individual definition of success. Information moved through meetings and approved channels, losing its sharp edges at every handoff, arriving somewhere downstream still technically accurate but no longer clear enough to act on.
My background is in evolutionary biology and genetics rather than business school, so when I tried to make sense of what I was observing I didn’t reach for management theory. I reached for what I already knew. What I saw was a knockout organism, a system missing a specific gene that had built its entire phenotype around that absence. You stop listening to the mission statement and start watching the organism.
The gene that was knocked out was meaningful communication, the flow that lets one part of an organization know what another part is actually doing, the transparency that gives employees enough safety to think clearly, the signaling that tells cells they belong to something coherent and alive.
In a healthy system, communication is the connective tissue. When it is present, departments can signal to one another, product decisions are informed by customer reality, and new employees inherit the wisdom of those who came before them. The organization actually learns, each cycle building on what the previous one discovered instead of starting over from the beginning.
The Ancestry
In genetics, the genotype is the code and the phenotype is its observable expression. Both matter.
Sortly’s genotype was written by agencies and freelancers working in isolation. They were not industry insiders and as far as I’m aware, none of the original agency teams work on the product while I was there. The original development firm delivered the codebase and moved on, and when they did, the knowledge of why the system worked the way it did left with the people who built it. The current team inherited code and data architecture from a group building deliverables rather than foundations, and that distinction compounds over time, each departure resetting the learning curve, the gap between what the code does and what anyone understands about why it does that widening as employees cycle through.
The agency’s involvement went deeper than code. During a brief Design and Discovery phase, JetRuby defined the business model, the competitor analysis, and the technical architecture. The strategic foundation was built by the same outside team that delivered the product MVP, and JetRuby later published the entire process on their blog as a startup success story, using Sortly’s origin as marketing content for their own services.
The most detailed account of why Sortly exists doesn’t live on the company’s own About page, which is essentially empty. It lives on that agency blog, framed as a case study, optimized for someone else’s keywords, structured to sell someone else’s services. A company in high growth trying to inspire its team with a meaningful vision has to point somewhere, and the only founding narrative available frames the origin as a transaction rather than a capability built.
The employees who encounter that story inherit something hollow, becoming beneficiaries of an outside process rather than authors of their own.
The marketing dashboard lights up green, the numbers do what numbers are supposed to do, and in the silence where a founding story should live, calls for meaning start to sound like noise, easily dismissed, because success has already been defined elsewhere, by other people, as a metric.
Silos
Without the connective tissue of authentic communication, departments became isolated organs. The marketing team published hundreds of articles on inventory management concepts the product had no native support for, concepts like reorder points, demand forecasting, and cost analysis, the organization publishing expertise with one hand while the product team operated as though that expertise didn’t exist.
Kitting and bundling is the clearest example because it is a highly desirable feature for any inventory management system so that smaller parts can be accurately tracked when connected into a larger item. Highly aligned industry features like that usually are the kind of proposal that arrives with the research already finished. The blog already had an existing article published calling kitting essential. The blog post, and help article, instructs users to manage kits manually by creating separate entries for each item, manually moving them to different folders, and manually updating quantities, which is the opposite of what kitting software is supposed to do.
The simplicity that fuels the brand becomes a ceiling on the product’s ability to mature.
Sortly’s market identity is built on design principles like aesthetic simplicity, ease of use, and user experience instead of complex industry jargon. It’s a strategy that favors the smooth surface of the front-end over the jagged, complex utility required by the industry.
Resistance to Definition
In my experience, inventory management terminology wasn’t welcome in product discussions, a remarkable thing to witness inside a company that sells inventory management software, the blog speaking the language fluently while the product avoided it and leadership showed little interest in closing that gap. The symmetry of Sortly’s branding felt perfectly aligned.
The organism resists being defined as what it is because definition requires commitment, and commitment requires the kind of frank internal conversation that real communication would have made possible. A website that communicates at a sixth-grade reading level (6th to 9th grade depending on page) works well for acquiring new users, but when the product team also avoids industry terms, building the technical features those same users eventually need becomes difficult. The simplicity that fuels the brand becomes a ceiling on the product’s ability to mature. When referencing competitors is met with resistance, the team loses its primary point of comparison, and without an external language to borrow, there is no way to articulate how the product differs from what exists or where it needs to go next.
Corporate Dialect
In the absence of authentic communication, a replacement developed, a safe emotionless language optimized for risk reduction rather than clarity. This happens at most corporate companies but uniquely awkward at a company that sometimes felt less defined than a 30-min Figma prototype. You could hear it in the public-facing copy, warm toward the customer but carefully avoiding anything specific about what the product would become, and in the values statement, RISE, which read more as aspirations the organization was working toward than behaviors it had consistently achieved.
The danger is that employees will mistake them for core values and become cynical when they see the organization failing to live up to them.
- Patrick Lencioni, Make Your Values Mean Something (HBR; 2002)
Sortly’s Glassdoor responses to company reviews, all publicly readable, follow a consistent pattern of responding to negative feedback with a similar “growth-oriented environment” script. You can see this pattern across several 2023 reviews where employees complained about “Management not listening” or “Lack of transparency”.
To be fair, HR teams are trained to respond to public reviews with caution, and defaulting to warm nonspecific language on a public platform is standard corporate practice, not a failure of any individual. But the pattern is illustrative precisely because it’s standard. When the organism’s trained response to a detailed structural critique is the same few sentences of generalized appreciation it applies to every other review, the dialect is functioning at scale, performing acknowledgment without creating communication. Whether it ever reaches the organs that could adapt in response is a question the organism’s current signaling pathways aren’t built to answer.
“Thank you for taking the time to share your experience. We’re saddened to hear that your time here isn’t reflecting the culture we aim to foster. Creating a supportive, growth-oriented environment remains a priority for us, and feedback like yours helps us look to where we may be able to improve.”
- Sortly Glassdoor response to a review describing micromanagement and a toxic work culture
What the Phenotype Tells Us
Sociologist Ron Westrum reached a similar conclusion from a different field. While studying safety failures in aviation and healthcare, he discovered that information flow is the best predictor of organizational behavior during a crisis, the critical variable being whether a signal can travel from the observer to the actor without distortion, and that in organizations where it cannot, the person carrying bad news tends to disappear rather than be heard.
Designers who walk into a company and feel that something is “off” without being able to name it are experiencing this phenotype. The knockout lens provides a structure for that intuition, revealing that every dysfunction is compensatory, a response to one missing thing, and that something in the system is actively producing the conditions that keep it missing.
The Pattern
In biology, horizontal gene transfer is when an organism acquires genetic material from another organism without being its offspring, inserting foreign DNA to try and fix a problem rather than letting the organism evolve the solution itself. When a problem emerged at the company level, solutions were sourced externally, bringing in fractional leaders, outside agencies, and consultants who arrived with strict mandates and timelines.
Bringing in external help naturally defaults towards execution rather than to diagnosis. If the mandate was to ship faster or turn things around, they operated within a logic of efficiency common in Silicon Valley. From the perspective of the existing team, however, these leaders often felt like extensions of the decision-making apparatus rather than additions to the human one. They arrived with no context for past projects, no knowledge of the talent already present, and usually without inventory management expertise.
“I want to build great products that users love” - generic product statement
Defaulting to existing relationships requires less energy than investing in an inherited team without established trust. This path of least resistance would allow product to move quickly, even at the cost of bypassing institutional knowledge. The actual experience of building a feature would not be a priority because the optics of shipping and alignment would serve as the primary goal. For employees who had already seen the pattern, watching new faces appear alongside new leadership while familiar ones quietly disappeared was its own kind of message. It is less energy for a system to replace individuals than to change its own fundamental behavior.
Selective Pressure
Selective pressure is the environmental force that determines which traits survive and which get eliminated. It operates through repetition rather than intention, favoring certain behaviors until the population shifts.
The pressure favors compliance, speed, and task execution, disfavoring curiosity, friction, and the impulse to ask why. The people who slowed the machine down to build understanding, who asked questions before committing to process, created drag. In a system optimized for shipping, those who create drag rarely stay for long.
Shipping was the feature.
You could watch it happen in real time when a new hire suggested using the company’s own blog as a research resource. The room would shift as if a silent tripwire had been touched. Their ideas were acknowledged warmly but would fade into indecision and “let’s do more research” motifs, leaving operational problems to persist even as the product continued to ship. Eventually the nervous system makes its own calculation that the environment is no longer worth the investment. Cortisol accumulates from the steady and patterned experience of offering something genuine only to watch it be absorbed without effect.
When you watch the color fade from enough colleagues after pushing for clarity or definition, you learn to read the room. It is just a form of basic pattern recognition, not unique to business or one specific company. Investors rarely fund startups simply because a pitch deck contains the right buzzwords; they back founding teams whose eyes light up when they discuss the problems they are solving together. A system that consistently rewards approved language over authentic conversation will naturally select for compliance over conviction, and this selective pressure works indiscriminately, filtering out friction, eventually eliminating passion because passion often looks like friction to the machine.
Vision Drift
Each new leader reoriented the roadmap around their own assessment of what mattered, projects that the previous team had been building toward getting deprioritized or abandoned entirely, foundational work particularly vulnerable because it was easy to cut and hard to defend to someone who had just arrived with a directive to show results. Over repeated cycles, the organization’s pool of accumulated ideas, its institutional memory, its sense of strategic direction, narrowed to whatever the newest leader had brought in. The product zigzagged between successive interpretations of what the company needed, none of these directions lasting long enough to reach completion before the next reset wiped the slate.
Memory Loss
Even simple organisms encode adaptive memory. Bacteria develop resistance. Animals learn to avoid predators. The species remembers so the individual doesn’t have to relearn the hard way.
Retrospectives were not standard, and scattered tracking made it impossible to reconstruct past failures or successes. Features were built and shipped only to be quietly removed without explanation. Months later, a new cohort would research and design those same features from scratch because the previous attempt had been erased from the collective memory, a compounding liability of uncaptured whys accumulating across every generation of employees who encountered the same dysfunctions for the first time, eating the same poisonous mushrooms because the system had no mechanism to encode don’t eat those.
Why the Gene Cannot Simply Be Restored
The pattern explains why restoration is not a matter of intent. Every adaptation the organism developed to survive without meaningful communication is now load-bearing in ways that only become visible when you try to remove one. The consultant cycles, the vision drift, and the memory loss are structural and interlocking. Removing any single piece requires an understanding of why it emerged in the first place, and that understanding walked out the door with the people who lived through it.
💬 Collaborate → Drop the following into your favorite AI:
Your role is a translator for the following metaphor: First, explain what growth means in business. Second, contrast growth and evolution in business.
Naming a problem is a signal that cannot be unheard, and it creates an evolutionary expectation for the system to adapt. For an organism that has learned to survive without meaningful communication, the simplest defense is to select against it. The cycle completes with clockwork precision because it has become a predictable mechanism of the organism’s survival.
There is a difference between growing pains and evolutionary development.
This essay is part of a series on design, communication, and the future of work. f you want to support this project given the legal risk, you can contribute to the 451 Firewall Fund. Read the full collection on Substack and Medium. The companion project lives at helloyouexperiment.com.