Prototyping in Gojek Design

The goal is to translate the static design into a near-real experience prototype.

We transform designs and requirements into high-fidelity, interactive experiences which capture, test, and convey intent, resulting in increased confidence in design, through rapid build-measure-learn feedback loops.

Need to prototype the search flow before building it? credit: @luieryando

Why bother doing it?

These are our learnings when building prototypes within Gojek’s design process

  • Prototypes help you uncover the user journey possibilities, especially using real-case scenarios.
  • Less guessing work. Sometimes edge cases can only be discovered once you prototype your static design.
  • Build to learn before building to ship. You will get to know what are the missing aspects of your flows when you’re in the “build mode”.
  • Fail cheaply. We can test your product/design even before the actual development.
  • Getting buy-ins. A prototype is worth 1,000 meetings — (Credit: IDEO) holds true since it’s easier to just show the actual thing than to offer a verbal explanation.
  • Early innovation. Prototyping isn’t a question of if, but when. Sooner or later your users will start using your product so either you spent time building something that no one might use or you can try to build a prototype and test it.
More advanced and dynamic prototype, credit: @luieryando

Our workflow

We’re a small team, with only 3 team members. We are trying to be more flexible in taking any prototype request. There are 2 things that we use as guidelines- The working model and prioritization criteria

  • Ticket request. For any ad-hoc tasks, depending on the requirements, we can quickly build a high-fidelity, interactive prototype. For example, if you want to know how navigation, gestures, tools, or other types of interactions will feel once they’re in users’ hands, and/or if you want to conduct some user tests.
  • Temporary team member. Our prototyper can become temporary members of your team, working side-by-side with designers, product managers, researchers, and/or engineers for rapid and highly productive experimental iteration.
  • Experimentation. In collaboration with just about anyone with a compelling idea, we can support explorations and user research with secure, robust, and highly functional prototypes.
  • Timeline
  • Impact
  • Product relevance
  • Clear objectives
  • Researcher involvement
  • Final UI readiness

Design tools vs Code

In our team, we are also trying to become more ‘technical’ as we are learning to work with code.

Design Technologist
We can simulate how the server and client app work together in Protopie. Mocking notification flow, exchanging messages between 2 prototypes. Credit: @riyadhirachman
We create design system components using Protopie library. Credit: @luieryando



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store