Laying the foundation for patterns in Gojek to reduce design and development effort on repetitive flows and interactions.

Problem

Gojek's rapid growth revealed a need for consistent design and technical processes to effectively cater to the needs of over 250 million of its users in 3 countries through 4 different apps.

Highlights of my role

• Core designer driving this project.
• Advocating for stakeholder buy-in as this majorly reliant on product adoption.
• Communication link between the product teams and engineering.
• Conducting secondary research to come to arrive a scalable solution.
• Driving discussions with the engineering lead to arrive at scalable technical solutions.
• Running workshops within the design systems team to gather inputs on the proposed approaches and overall progress.

Process

Starting with a not-so-clean slate

The interaction design team initiated an exercise to identify patterns within the Gojek app, discovering 15 potential patterns to standardise. However, momentum was lost due to lack of prioritisation. With the topic back in the spotlight, it was necessary to speak with products and determine which patterns were most important for users, in terms of consistency and design.

Prioritising patterns

Products were quick to respond with a bunch of flows that were repetitive and they felt could use some standardisation both in interactions and visuals. To name a few:

• Checkout flow used in products to allow users to review their order and make a payment.
• System permissions are used to request a user for device based permissions like access to location.