From my perspective, Gateway isn’t a Ship of Theseus paradox at all. ScholarOne Manuscripts still exists, not despite how we’re transforming it, but because of how we’re transforming it. For us, the metaphorical keel of ScholarOne is editorial judgment and trust. Everything we rebuild in Gateway exists to carry that judgment further.
To be honest, from the inside rebuilding doesn't always feel tidy. Some days it feels exactly like a paradox, usually around 11pm the night before a release.
Building vs. rebuilding
Building something new is hard. Rebuilding something people already rely on is hard in a different way. Every decision gets measured against something users know by heart, including the parts they've learned to work around. And the ship can't stop sailing while you work: ScholarOne has to keep running while we replace planks underneath it.The first real job of a rebuild is making a map. Before we could redesign anything, we had to catalog what legacy actually does: every capability, every setting, every path a user might take from submission to decision. I expected that part. What I didn't expect was how much of the system lives between the features. A reviewer submits a report, an editor's task list updates, a notification goes out, and each step depends on a configuration someone set up years ago. None of that connective tissue shows up on a feature list. People experience it as "the system just works," and they only notice it when it's gone.
So rebuilding a screen turned out to be the easy part. Rebuilding the handoffs between screens is where most of the work lives, and it matters more every year. With submissions climbing and reviewers stretched thin, each of those handoffs is either saving an editor time or quietly costing it.
One million* ways to run a journal
*Only a slight exaggeration.When we started Gateway, "streamline the workflow" sounded like one job. It turned out to be hundreds of different jobs. Our clients have each shaped ScholarOne to fit how their journals run.
I've come to see every configuration as a decision someone made for a good reason. Before we change how something works, we have to understand why it works that way for you.
If we had wanted to, we could have just made Gateway a prettier version of the ScholarOne you already know. But as submissions skyrocket, and peer reviewers, authors, editors, and admins feel the pressure of keeping up with the publishing process today, there’s more at stake. By understanding why ScholarOne works the way it does, we can figure out new ways to achieve the same outcomes, with fewer clicks and less clutter.
Workarounds turned out to be some of our best research. When a client builds a clever path around something, it marks exactly where the product stopped serving them. So we stopped asking how to rebuild each feature and started asking what each one was for. Once you know the outcome someone needs, you're free to find a better route to it. Sometimes the answer was to keep the old route. Sometimes it was to retire it.
The friction worth keeping
I'm on record wanting no more pop-ups, ever. I stand by that. Twelve clicks across four pages to finish one task is friction, and removing it is most of what the Gateway redesign is about.But I've learned that not all friction is the enemy. Some pauses are where the thinking happens: the moment before a decision, a check before a manuscript moves forward. Remove the wrong friction and editors don't get faster. They just get an easier path past the part that matters.
So for every screen, we ask which steps protect someone's judgment and which ones only cost them time. The decision step is a good example. In legacy, editors had to leave the manuscript to record a decision, which is pure friction. But the decision itself is the moment we most want an editor to slow down. So we moved the decision panel beside the manuscript: the trip between pages is gone, and the pause stays where it belongs. The panel also appears only when the workflow says a decision is due, so the guardrails your configuration sets stay intact. That kind of trade-off came up again and again across 57 editor interviews this past year.
And guess what? I’m still team no pop-ups.
Good, then better
I'm a recovering perfectionist, with a heavy emphasis on recovering. If we'd waited for Gateway to be perfect, it would still be living in a design file. Instead, we shipped, listened, and kept going.Shipping early changed who our best critics were. The publishers who launched Gateway before they had to became a running conversation, telling us in weeks what a design review might have missed for months. We're not done, and I don't expect to be. A rebuild like this is less a finish line than a habit: release, hear from you, improve.
Shipping before you're sure is uncomfortable, and some things take longer than planned. We're also working toward smaller, faster releases. When the next improvement is weeks away instead of months, "good enough to ship" gets a lot less nerve-wracking.
What I know so far
A few things I'm more sure of than I was a year ago:- The keel matters most, and protecting editorial judgment is the point of all of this.
- Every configuration has a story worth hearing before it gets redesigned.
- And the best version of this ship gets built with the crew, not just for them.
I’ll keep bringing the boat metaphors. At this point, I can't help it.