eWorkflow

My role

Main product designer, design manager, design lead, feature conceptualization.

Context

Project made under a contract with a software agency.

Project setup

We had previously done a smaller project for this client. He returned to us seeking collaboration to bring a bold and innovative idea to life. To create this product, we mobilized almost all of the developers available (7), the entire design team (3), one PM, and one PO (besides the entire QA team, 3 people). This ambitious project had a very tight timeline, so everyone made the highest effort to understand the segment, propose solutions, and implement them fast.

The problem

The world of publishing scientific papers is known only to those deeply involved with it. It's not something new, and the scientific community is very well established. When the technological advance gave the possibility to publish manuscripts online, it was a game-changer; a big step for researchers, and even a bigger one for humanity. But this jump happened decades ago, and the online services didn't catch up as the internet and its infrastructure evolved rapidly in front of our eyes. That would cause the publishing process to stay slow and not transparent for authors and reviewers during multiple stages. So, the scientific publishing process evolved, but not as much as it could, given the present state of information technology.

Product proposal

eWorkflow came to the market to revolutionize the process of publishing manuscripts online in all of the steps, from end to end. This ambitious platform include modules for authors, editors, publishers, and even reviewers. With the goal of speeding up and simplifying this process for all actors involved, the design team had a vital part, helping PMs and engineers shape features from scratch, even before something visual started to be drawn.