On Organizational Molting

I’m living in the chaotic middle of the so-called SaaSpocalypse, leading an AI and knowledge engineering team through the process of helping to evolve a legacy SaaS platform and, at the same time, developing new AI native platforms. 

I’m starting to write more to force myself to step back from the day to day turbulence of innovating during what feels like a major technical phase change and take time to observe and reflect. How are jobs changing? How are teams changing? What does that tell us about emerging forms of organization around software development?

To start, like everyone else, we are in the thick of the same difficult questions many teams are facing, e.g.:

• Which emerging AI capability sets fit into legacy platforms to transform existing workflows?

• Which capabilities can only be realized on AI native architectures?

• What AI tools should our teams deploy?  How does that affect historical processes? What level of trust can we put into them?  

I try to anchor my thinking in systems. What has been most interesting over the last couple of years is how the transformation of labor across traditional SaaS departments has not felt centrally mandated. It has felt local, tool driven, and person led.

Many teams are simplifying and piloting new workflows themselves, often starting at home or as pet projects before those workflows quietly migrate into the enterprise substrate.

There has been a real but largely unnamed emergence of new types of work and coordination. The value of these tools at the individual level was so obvious and transformative that organizations began changing whether it was formally acknowledged or not.

The word that keeps coming to mind is molting.

I suspect the metaphor slipped in subconsciously after weeks of hearing all of the hype about Moltbook, but I am keeping it. I am a faux naturalist, and this gives me an excuse to think about biology.

Invertebrates such as lobsters and spiders molt to grow larger, shedding rigid exoskeletons that no longer fit. Reptiles shed to expand. Mammals molt seasonally. In our house, this mostly means our floors are perpetually covered in fur from two dogs.

In biology, molting is not a strategic planning session. Spiders do not gather to debate timing. It is triggered. Growth pressure builds. The old shell tightens. The organism sheds.

The metaphor feels uncomfortably appropriate for SaaS right now.

A caveat, though. Molting does not necessarily imply headcount expansion or contraction. In biological systems, shedding can occur as a result of changing environmental conditions. The organism is not always becoming bigger or smaller. It may be adapting to a new scale or to a new context.

Inside some of our teams, one source of molting pressure seems to be coming from expanding output. Teams using AI are producing materially more. Prototypes compress. Workflows accelerate. Certain historical bottlenecks dissolve (and new bottlenecks emerge). That increased productive capacity creates tension with legacy processes and role boundaries, while also introducing a new challenge: the time and discernment required to evaluate which outputs are actually valuable.

In some areas, we are actively expanding teams. In others, efficiencies are accelerating historical workflows. The question is not simply about headcount. It is also about what higher levels of output, faster iteration cycles, and broader individual capability mean for how work is coordinated.

The shell that tightens may not be headcount. It may be inherited structure.

In many places, especially in the early wave, organizations tried to bolt constrained AI tools such as chatbots and limited use wrappers onto workers who had already swallowed the red pill. The result was predictable. Dissonance. Resistance. Quiet workarounds.

The organism had already grown. The exoskeleton had not caught up.

What I am seeing now is less about AI adoption and more about structural shedding. Titles remain the same, but daily workflows, tools, and boundary lines have shifted materially. Product managers prototype - product or feature ideation is literally functional prototype development. Engineers write specifications and orchestrate coding agents. QA manages and audits continuous loop testing. Sales automates research. Customer success builds tailor-made internal onboarding tools.

The shell is cracking in places, even if the nameplate on the door has not changed.

Molting is not always pleasant. It is not euphoric. After shedding, organisms are soft. Vulnerable. Exposed.

That vulnerability maps cleanly to the present moment. Best practices shift weekly. Security risks are real. Data governance is complicated. Systems emergence, by definition, produces unexpected structures from complex substrates. Not all of them are elegant.  Many teams are effectively molting alongside rapidly improving coding tools.

Over the past year, I have been running a slightly nerdy experiment alongside all of this. Every couple of months, I rebuild roughly the same type of application using whatever AI stack is current at that moment. Usually it is something in food science, regulatory compliance, or risk modeling, which sounds dull until you try to encode it and discover how many edge cases the real world contains.

I am hardly the only one doing this. Plenty of people are stress testing these tools inside their own domains. The interesting part is not that each version improves. It is the magnitude. This has been widely documented and quietly felt.

The most recent cycle, using Antigravity, Codex, the latest GPT models, and Gemini, felt different immediately. Tasks that used to require careful sequencing and multiple layers of coordination began to compress. Context persisted longer. Iteration tightened. The system did not just answer isolated questions. It participated in the build.

If molting requires growth pressure, this feels like that pressure.

We are swimming in hype, no doubt. This is the sort of moment that produces sweeping declarations and commemorative hoodies. Slopes flatten. Technologies stall. Regulation appears precisely when it is least convenient. It would be unwise to assume inevitability.

Still, even discounting enthusiasm, the transformation gradient is real.

When the cost of producing structured thought declines, even modestly, the ecosystem responds. More prototypes appear. Internal tools emerge without ceremony. Someone casually mentions they automated a workflow over the weekend that once required a quarterly roadmap discussion.

These are small signals. But they accumulate.

This does not look like the death of software. If anything, it looks suspiciously like proliferation. As Steven Sinofsky has argued, when the cost of creation drops, the surface area expands. We Cheaper inputs tend to produce more complex ecosystems, not fewer organisms.

The more subtle shift is inside teams.

The once comfortable boundaries between product, design, engineering, and QA are becoming negotiable. An idea moves to prototype in hours. Specifications become collaborative loops. Testing is more embedded and tightly coupled with faster, AI-driven engineering cycles. The handoffs, once ritualized, grow shorter and occasionally vanish.

No one announces this. There is no End of Department X memo. It simply becomes less obvious where one function stops and another begins.

One caution here.

Acceleration does not imply an explosion of bespoke, user-specific apps and shadow agents running everywhere. Large organizations cannot function that way. Agreed processes, shared data models, and consistent systems remain foundational. You do not replace institutional workflow with improvisation. You do not replace Salesforce with a prompt.

But something more subtle may already be happening.

Much of the experimentation around AI tools is not happening in sanctioned architecture reviews. It is happening at the edges. In pet projects. In internal prototypes. In workflow automations that begin as personal efficiency hacks and quietly demonstrate value.

That bottom-up activity is not the end state. It is the discovery phase.

In prior eras, formalization preceded experimentation. Today, experimentation often precedes formalization. Teams are discovering what should become standardized by first building it informally.

The risk is uncontrolled sprawl. The opportunity is insight.

If anything, the challenge for leadership is not to suppress improvisation nor to canonize every experiment. It is to observe carefully which emergent workflows represent genuine institutional leverage and should be codified into shared systems.

Improvisation expands the frontier. Process consolidates the gains.

The two are not substitutes. They are phases.

And when boundaries blur, organizations adjust. Not dramatically. Gradually. Like furniture being rearranged in the dark while everyone pretends the room looks the same.

The louder prediction is that all of this ends in widespread professional redundancy. Perhaps some roles shrink. Historically, when production costs fall, effort tends to migrate rather than disappear entirely.

When compute became cheap, we did not stop building software. We built far more of it. When information became searchable, we did not stop researching. We researched differently.

The deterministic view that agents will produce a permanent class of unused white collar labor assumes institutions fail to redeploy attention. That seems less like a technological law and more like a management decision.

As execution compresses, differentiation shifts upward, toward systems design, coordination, incentive alignment, proprietary workflows, and the ability to make sense of historical data without drowning in it.

The spectacle will continue. Benchmarks will rise. Headlines will oscillate.

But the pressure to molt is quieter.

It shows up in how quickly something real can be built, how few approvals it requires, and how many teams begin to behave as though acceleration is normal.

Molting is not dramatic from the inside. It feels messy. Awkward. Slightly itchy.

But it is how organisms grow.

And if the pressure continues, even without theatrics, the larger story may not be machine intelligence itself as AI embeds further into the stack, but how institutions shed the shells that once made sense, and what new forms take their place.

If anything, we should take a humble and experimental approach. It feels like AI acceleration calls into question traditionally rigid organizational structures. If change becomes the norm, the goal should not be constructing the next hardened shell too quickly. It should be learning how to operate in softer states.

Historically, companies respond to disruption by re-orging. New titles. New reporting lines. A new box diagram that attempts to restore clarity. That instinct is understandable. Exoskeletons provide safety. They define roles, boundaries, and authority.

But if the environment itself is shifting quickly, prematurely hardening around a new model may simply create the next shell that will need to be shed. 

Instead of asking “What is the new permanent structure?” it may be more useful to ask “What kinds of teams are adaptive under continuous acceleration?”

We are already seeing hints: 

• Small cross-functional pods that own a problem end to end, rather than passing it through departments

• Individuals who are less defined by title and more by surface area of agency

• Teams that treat AI systems as collaborators embedded in the workflow rather than external tools bolted on top

• Organizations that invest less in rigid process documentation and more in shared context and rapid feedback loops.

In some cases, a product manager becomes part prototyper. An engineer becomes part systems integrator and auditor of model behavior. QA becomes continuous risk management embedded in build cycles. Customer success builds internal automation to serve clients better rather than escalating everything upstream.

These are not radical revolutions. They are quiet recombinations.  

The common thread is not a new org chart. It is an increase in trust, communication density, and shared visibility into systems. When boundaries are fluid, coordination becomes more important, not less.

Core values. Clear communication. Distributed ownership. Comfort with experimentation. Psychological safety for trying things that may not harden into policy.

Those feel more durable than titles.

AI acceleration does not just test technical architecture. It tests institutional metabolism. How quickly can a team sense change, adapt, and integrate new capability without collapsing into chaos or calcifying into bureaucracy?

It may be that the organizations that thrive are not the ones that declare the cleanest new structure, but the ones that tolerate ambiguity long enough for a better one to emerge.

If molting is inevitable, the question is not how quickly we can construct the next hardened structure. It is how well we can operate while the structure is in motion.

There is a natural instinct, especially in moments of uncertainty, to respond with definition. New reporting lines. New titles. A new operating model. A clearer box diagram. Structure feels stabilizing. It gives shape to ambiguity.

But if the underlying capability environment continues to shift, prematurely freezing into the next design may simply create another shell that will need to be shed.

In systems domains, emergence is not managed by dictating form. It is shaped by adjusting conditions. Strong feedback loops. Clear interfaces. Shared context. Trust. Distributed competence. The ability for small experiments to occur without threatening the whole.

Applied to organizations, this suggests a quieter discipline. Invest in communication density. Increase visibility into workflows. Shorten feedback cycles. Allow teams to recombine around problems. Strengthen shared principles rather than rigid process. The goal is not structural perfection. It is adaptive capacity.

If acceleration continues, the advantage will not go to the organizations that define the cleanest new hierarchy. It will go to the ones that can sense change early, redistribute effort intelligently, and integrate new capability without collapsing into chaos or retreating into bureaucracy.

In other words, they will be the ones that metabolize change most effectively.