Zero Stage to Orbit – UX Journal

Digital design and improvement is only a child.

Properly, it was a child. We’re toddlers now, however in contrast to most different sciences and engineering, we’re simply barely exiting the cradle. We despatched individuals to the moon with much less processing energy than your common automobile’s key fob.

Virtually all human development was finished in the pre-digital period. Centuries. Millennia. Eons. Most of the people responsible for modern computing workflows are still alive.

Nonetheless, like most infants, we’re afraid to go away the cradle. However like all infants, finally, we have now to go away the cradle. And I believe we are prepared.

We’re going to be okay, and we’re going to outgrow this cradle collectively.

Two individuals you’ve by no means heard of, however know very properly

In 1903, a deaf Russian schoolteacher named Konstantin Tsiolkovsky printed a paper proving {that a} single rocket may by no means carry sufficient gas to attain orbit. The gas itself was too heavy. You wanted gas to carry gas, and gas to carry that gas, and the math was cruel. His resolution: staging. Burn a piece, drop the useless weight, burn the subsequent. It was inelegant. It labored. It grew to become the solely approach to attain area for the subsequent 120 years.

In 1996, a Hungarian-American linguist named Béla Bánáthy printed a mannequin for the way social methods change. Two phases: diverge to discover the downside broadly, converge to focus on motion. It was a device for serious about how advanced human methods evolve. 9 years later, the British Design Council tailored his mannequin into the Double Diamond. Uncover, Outline, Develop, Ship. It gave designers a shared language for the way work really strikes from downside to resolution. It was clear. It was helpful. It grew to become the approach issues are finished.

Each solved what felt like an unimaginable downside. Each delivered their payload. And each grew to become so foundational that questioning them felt like questioning gravity itself.

Wait. We’ve seen this before; flip the Double Diamond on its facet… no approach:

Maintain the fort! Is… is design considering simply multi-stage rocketry? Oh heavens, what have we finished?

The tyranny of the rocket equation

The rocket trade faces a legendary, seemingly unimaginable downside. It is referred to as single-stage-to-orbit (SSTO), and it has been the holy grail of spaceflight for many years — the dream: a automobile that launches from the floor and reaches orbit in a single steady burn. No boosters. No jettisoned gas tanks. No staging sequences — one machine, floor to orbit, clear and stylish.

It is successfully unimaginable (particularly with helpful payload and reusability) with chemical rockets.

The explanation is stunning in its cruelty. To achieve orbit from Earth’s gravity properly, you want gas. However gas has mass. And mass requires extra gas to carry. Which provides extra mass? Which requires extra gas? The Tsiolkovsky rocket equation is a tyrant: each kilogram of payload calls for exponentially extra propellant, and most of that propellant exists solely to carry different propellant — gas to carry gas to carry gas.

So the total trade constructed itself round the workaround: multi-stage rockets. You burn a stage, drop the useless weight, burn the subsequent stage, drop that. Saturn V had three phases. Falcon 9 recovers its first. The entire structure of spaceflight (the launch pads, the restoration ships, the mission management protocols, the hundreds of engineers managing staging sequences) exists as a result of we can’t escape the overhead of launching from the backside of a gravity properly.

This is not about rockets.

This is about the design-to-development pipeline. And the mapping is exact:

Every stage in the conventional pipeline is designed to compensate for the limitations of the earlier one. Analysis to inform design. Design to spec for builders. Specs to survive handoff. QA to catch what handoff broke. Retros to talk about why QA caught a lot. Course of to handle course of.

Gas to carry gas. The fashionable improvement pipeline is not an answer. It is a multi-stage rocket. And most of the vitality is going to overhead.

The launch pad financial system

Stafford Beer mapped this structure in 1972, although he was describing organizational cybernetics slightly than rockets. His viable system model confirmed how advanced organizations handle themselves: layers of coverage, intelligence, management, and coordination stacked above the operational items that do the precise work. Every layer communicates by artifacts. Every handoff introduces sign loss. The space between intent and execution is most by design.

Beer was not criticizing this. He was describing it. The mannequin works. It has labored for many years, and an infinite financial system has grown round it, making it work extra easily.

Take into consideration what exists as a result of we launch from the floor. Undertaking managers are the staging sequence coordinators, managing transitions amongst analysis, design, improvement, and QA. With out the phases, the coordination position transforms (it does not disappear, however the overhead coordination portion evaporates). Design methods grew to become gas standardization: not the craft of making coherent visible language (that is still important) however the bureaucratic layer of sustaining Figma libraries as translation paperwork between designers and builders. Dash ceremonies are mission management. Handoff documentation is payload fairing, the protecting shell that retains the intent from burning up throughout the transition between phases.

Take a stroll with me by the design translation graveyard, period by period:

The Handoff Period:

• Zeplin (the unique “examine mode” bridge between Figma and dev).
• Summary (model management for Sketch information, as a result of designers wanted Git however may not use Git).
• InVision (prototype hyperlinks emailed to stakeholders who by no means clicked them).
• Crimson Line specs (before Zeplin automated it, individuals actually drew purple traces on screenshots with pixel measurements).
• Avocode (you don’t even keep in mind this one).

The Sapec Doc Period:

• Axure RP (200-page interactive specs no one learn previous web page 12).
• Balsamiq (wireframes as a deliverable, not a considering device).
• OmniGraffle (the Mac-only flowchart device that felt like a faith).

The Coordination Overhead Period:

• Basecamp (the unique “the place did the choice dwell?”).
• Confluence (the place documentation went to die).
• JIRA (the story factors industrial advanced).
• Rally (I can’t consider a intelligent factor to say).
• Microsoft Visio (each flowchart that ever lied about how a system really labored).
• Requisite Professional (IBM necessities administration, pure overhead in a field).

The Prototype-as-Proof Period:

• Flash/Macromedia Director (interactive prototypes that had been more durable to construct than the precise product).
• Dreamweaver (the unique “design in the browser” lie).
• Frontpage (we do not converse of this).
• GoLive (go away).

Not to point out the major device family tree of Corel, Photoshop, Fireworks, Sketch, Framer, Affinity, Figma…

None of those is unhealthy. All of them are overhead. And right here is the factor: a whole financial system is constructed on sustaining this overhead. Design system consultancies — Handoff workflow distributors. Agile teaching practices. Course of enchancment certifications. Convention circuits devoted to making the multi-stage rocket extra aerodynamic.

The launch pad trade does not need you to launch from orbit. As a result of the launch pad trade does not exist in orbit.

The only-stage delusion

Earlier than orbit was accessible, there was an earlier try to escape the gravity properly. The trade referred to as them “design technologists” or “full-stack designers.” The SSTO dream, translated to human kind: one one that may do analysis, design, front-end improvement, generally back-end, testing, and deployment. All phases in a single physique. No handoffs. The unicorn.

And like SSTO with chemical rockets, it was a physics downside.

No single human being may span all of these disciplines at manufacturing high quality. The gas was too heavy. You possibly can design and code, however your designs lacked the depth of a specialist, and your code lacked the rigor of a devoted engineer. You possibly can analysis and prototype, however neither at the degree a targeted staff would ship. The cognitive load of sustaining fluency throughout that many domains was the fuel-to-carry-fuel downside in human kind.

So individuals tried it. They burned out. They produced stretched-thin work throughout too many fronts. And the trade responded with a verdict that appeared like knowledge: “See? You want specialists.” Which was actually: “See? You want phases.” Which was actually: “See? You want us.”

Let’s do a roll name of everybody wanted to handle the strategy of processes:

The interpretation roles:

• UX Designer (vs. UI Designer vs. Visible Designer vs. Interplay Designer vs. Product Designer).
• Design Technologist (the SSTO unicorn who burned out).
• Frontend Developer (the one that interprets the mockup).
• UI Engineer (when “frontend developer” was not particular sufficient).
• Design Engineer (the newest try at SSTO, identical physics).
• Inventive Technologist.

The coordination roles:

• Product Supervisor (the human API between enterprise, design, and engineering).
• Undertaking Supervisor (the human API between the staff and the timeline).
• Program Supervisor (the human API between initiatives).
• Scrum Grasp (skilled ceremony facilitator).
• Agile Coach (teaching individuals to do ceremonies higher).
• Supply Supervisor (what).
• Launch Supervisor (what).
• Technical Program Supervisor (this is most likely the one which survives).

The handoff roles:

• Enterprise Analyst (interprets enterprise wants into necessities paperwork).
• Techniques Analyst (interprets necessities into technical specs).
• Options Architect (interprets technical specs into system design).
• QA Engineer (catches what the handoffs broke).
• QA Analyst (writes check instances from specs which have already drifted from intent).
• UAT Coordinator (manages the assembly the place stakeholders see what they requested for and notice it is not what they meant).

The design system forms:

• Design System Lead.
• Design System Engineer.
• Design Ops Supervisor.
• DesignOps (the total self-discipline).
• Design Tokens Specialist (sure, this is actual).
• Element Library Maintainer.
• Figma Librarian (everyone knows one).

The method administration layer:

• Dash Facilitator.
• Retrospective Facilitator.
• Kanban Stream Supervisor.
• Worth Stream Mapping Guide.
• Lean UX Coach.
• DevOps Engineer (when the deployment pipeline wanted its personal specialist).
• Platform Engineer (when DevOps wanted its personal specialist).
• SRE (when Platform Engineering wanted its personal specialist).

However the analysis was improper, not about the symptom (the burnout, the mediocrity throughout disciplines) however about the trigger. The design technologist did not fail as a result of nobody individual can possess all the abilities. The design technologist failed as a result of nobody can maintain all the abilities whereas nonetheless preventing gravity. They had been nonetheless launching from the floor, nonetheless hauling the translation overhead, simply with one individual doing all the hauling as an alternative of a staff.

The issue was by no means the variety of phases. It was the gravity properly.

You had been by no means supposed to launch from right here

This is the place the rocketry lens reveals one thing the customary “AI adjustments the pipeline” framing misses.

I’ve written about Zero-Vector Design before: the elimination of middleman translation instruments between intent and artifact. The web site demo. The diamond is respiration in a different way. All of that holds. However the rocketry metaphor reframes it. This is not a procedural problem. It is a structural one.

The gravity properly is the translation layer itself. Not any specific device or handoff or ceremony, however the elementary structure of separating “the individual with the intent” from “the artifact the buyer touches.” Each course of enchancment, each higher handoff template, each tighter dash cadence is optimizing the rocket. Constructing a extra environment friendly multi-stage automobile to escape the identical gravity.

Zero Vector does not construct a greater rocket. It eliminates the launch.

When the individual with the imaginative and prescient operates instantly by AI brokers (researching, designing, constructing, testing, transport in a steady loop), the phases collapse. Not as a result of the disciplines turn out to be irrelevant. Analysis nonetheless issues. Structure nonetheless issues. Testing completely nonetheless issues. However the handoffs between roles, the translation artifacts, the distance between what you meant and what will get constructed: that collapses to zero.

• Multi-stage: The analysis staff writes a report. The designer interprets the report into wireframes. The developer interprets the wireframes into code. The QA finds the gaps between wireframes and code. Everybody meets to talk about the gaps. One other dash begins.
• From orbit: You analysis it. You design it. You construct it. You check it. You ship it. Similar thoughts. Similar session. Zero translation.

You are not in the gravity properly trying up. You are in orbit, and from orbit the query is genuinely puzzling: why would you descend to the backside of a gravity properly simply to launch again up once more?

I’m introduced again to considered one of my favourite books, Arthur C. Clarke’s “The Fountains of Paradise,” the place the second people study to construct the area elevator, the constraints of the gravity properly go away, and we acquire entry to the universe.

Rational actors defending their gravity properly

The resistance to this framing is not mental. It is financial. And I would like to be exact right here, as a result of this is the part the place the argument dangers sounding prefer it assaults individuals. It does not.

Have a look at who advantages from the multi-stage rocket. Not the practitioners (they are exhausted by it). Not the prospects (they obtain intent degraded by 4 handoffs). The beneficiaries are the infrastructure suppliers. The businesses are promoting launch pad gear.

Design system consultancies that cost six figures to construct and keep part libraries, which are, at their core, translation paperwork between design and engineering. Handoff workflow instruments that monetize the hole between Figma and manufacturing code. Agile teaching companies that promote course of optimization for the staging sequences. Dash planning software program. QA automation suites constructed particularly to catch translation errors launched by staging. Convention circuits devoted totally to making ceremonies extra environment friendly, handoffs cleaner, and burndown charts extra exact.

The institutionalization of all of us is so full that we don’t keep in mind, recall, or think about a time or future the place this isn’t crucial. Like each Kafkaesque nightmare, it feels regular as a result of it is all we all know.

I need to watch out. The individuals in these roles are expert, considerate, and working rationally inside the system because it exists. A launch pad engineer is not a villain for constructing launch pads when each rocket on Earth wants one to fly. These professions emerged to remedy actual issues, they usually solved them properly.

However when orbit turns into accessible, the launch pad engineer faces a structural query. A few of that experience interprets instantly: you continue to want high quality considering, architectural judgment, somebody who is aware of what “good” appears like, and can not ship till they see it. A few of it does not. The coordination overhead, the handoff administration, the translation layer itself: that portion evaporates. And the individuals who constructed their skilled id round managing overhead will, naturally, defend the overhead. Not as a result of they are unhealthy actors. As a result of they are rational actors in a system that rewarded overhead administration for many years.

The system was rational. The gravity properly was actual. The overhead was crucial.

Till it was not.

Each “course of enchancment” in the conventional pipeline is constructing a extra environment friendly multi-stage rocket. Higher handoffs. Cleaner specs. Tighter dash ceremonies. And none of its questions whether or not we should always nonetheless be launching from the floor.

Subject notes from orbit

Principle is snug. Let me let you know what it really appears like.

I constructed Fictioneer, an AI-powered story improvement platform, with a crew of AI brokers. Not a metaphorical crew. An precise working staff: a strategist, a frontend engineer, a backend specialist, a researcher, a advertising and marketing lead, a content material czar. Every agent holds area experience, follows established patterns, and works by structured workflows. I’m the operator. They are the crew.

There is no design-to-development handoff as a result of there is no hole between design and improvement. Intent strikes by the brokers into the artifact. Analysis flows into structure, flows into code, flows into testing, flows into deployment. One session. Zero distance. No translation artifacts.

This isn’t a utopia, and the area elevator and orbital launches have their very own total set of risks, challenges, and prices. It isn’t a panacea; it is simply the subsequent step in the evolution. A brand new set of issues to remedy, which I believe is higher than looping round the identical set of outdated issues time and again.

And I would like to be trustworthy about what orbit prices, as a result of I do not need to promote paradise. I’ve written about this at size: the loneliness of constructing at forge temperature, the presents of collaboration that evaporate when the warmth arrives. That is actual, and orbit does not repair it.

There is no staff standup the place somebody catches the flaw in your information mannequin. No design evaluation the place a colleague pushes again on your navigation structure. The standard gates you’d usually distribute throughout 5 individuals, you maintain alone (with agent assist, however nonetheless). That is not nothing. (And truthfully, some days it is so much.)

However right here is what adjustments. In the multi-stage rocket, most of your vitality goes to hauling gas. Coordinating handoffs. Managing translations. Writing specs that survive the hole between what you meant and what another person builds. In orbit, all of your vitality goes to the work itself. The analysis. The design. The structure. The craft. The stuff that really reaches the individual on the different finish.

That is not a small distinction. That is a unique physics.

Why are you launching from the floor?

The rocket equation is a tyrant, and the total spaceflight trade organized itself round submission to that tyranny. Launch pads. Staging sequences. Restoration ships. Mission management. All of it was constructed to handle a constraint that was, for many years, immovable.

However the constraint moved.

And now the query is not how to construct a greater multi-stage rocket. Not how to optimize the handoffs, enhance the dash cadence, or produce cleaner translation paperwork between design and improvement. These are all solutions to a query that stopped mattering.

The query is: why are you continue to launching from the floor when orbit is accessible?

I’m not being rhetorical. I’m genuinely asking. If the translation layer is the gravity properly, and AI brokers collapse the distance between intent and execution to zero, and the abilities that really matter (analysis, design considering, architectural judgment, style, craft) are extra essential in orbit than they ever had been on the floor, then what is the argument for constructing one other multi-stage rocket?

And look, I used to be at NASA when the Artemis II missions had been being deliberate, and I had contact with these groups in my position as an IT Specialist/Digital Service Skilled. The SLS is reusing the method developed in the 60’s and 70’s. Many criticize it. I’m ending this article on Feb twenty first, 2026, launch date is slated for March sixth, 2026. I need to see Artemis succeed as a lot as anybody else in the company.

However most of us aren’t really launching rockets (at the least, I’m not anymore), we’re transport SAAS, we’re transport cell apps, we’re transport consumer-grade digital merchandise. So why can we cling to the multi-stage strategies of the previous?

Consolation, possibly. Familiarity. The cheap worry that orbit is simply one other SSTO dream that may flame out on the approach to area. The sunk price of a profession organized round staging sequences. These are truthful considerations.

The gas ratio is nonetheless the identical. The overhead is nonetheless overhead. The interpretation tax nonetheless compounds with each handoff. And the instruments that make orbit attainable are not theoretical anymore. They exist. They work.

The gravity properly was actual. The infrastructure was crucial. The trade that grew round it was rational and constructed by sensible individuals fixing real issues.

And, I’m additionally unsure right here, additionally mid-journey, additionally discovering orbit’s actual constraints in actual time. My profession, work, and livelihood are simply as a lot in danger as everybody else’s. However that doesn’t low cost the information about the transition to new capabilities.

And now that orbit is accessible, the launch pad is optionally available.

The gravity properly is only a cradle. And nobody stays in the cradle perpetually.

The article initially appeared on Substack.
Featured picture courtesy: George Pisarevsky.