KIPI 2022

Introduction

KIPI is an hybrid international symposium events organized by PPIA (Indonesian Students’ Association of Australia). The following project will only show one milestone out of three (KIPI 2022, a PPIA bi-annual event). However, the tools and design thinking process remains the same.

Annually, PPI DUNIA organizes an international symposium and in 2022, PPI-Australia was selected to be as the host and organizer of SI XIV. Perhimpunan Pelajar Indonesia Australia (PPIA) **or Indonesian Students’ Association of Australia. For approximately one year, PPIA create and organized multiple events and named it Road to SI. Our events / milestones are as follow:

1. KIPI 2022 (the International Conference for Indonesian Student 2022)
2. Career Fest 2022
3. Symposium International XIV

And I was assigned to lead the project to create a “Road to SI” website.

Problem

When our group were given this assignment, our group has already many projects ongoing. As a result and initiative, I decided to create a second group full of UIUX Designers to help with project. After a group was created, we started by creating our brief

Our Process

For most part, our team will be given a brief to start our project and below are the methods that we do to achieve our results

Design Thinking Process

Our team goes through traditional design thinking process:

1. Empathize (Remote Meeting)
2. Define (Confluence & Trello)
3. Ideate (Figma)
4. Prototype
5. Test (Remote Unmoderated Testing & Post Interview Questions)
6. Implement (Webflow)

Onboarding

Some of our members are quite new and unfamiliar with our tool, hence we create a quick introductory course. Some of the workshops we made include:

1. Intro to Figma and UI/UX,
2. Designing website using Webflow,

Gathering Requirements

Each milestones, we start our process by conducting stakeholders interview to gather project requirements, to generate our In Scope Items and Out of Scope Items. By doing so, it allows us to understand each other’s expectations of what is possible and not within the time frame.

Design, Test, Implement, and Iterate

As the Project Lead, I am responsible to organize our user stories, lead design jams, and also guide our developers to implement the pages from Figma to Webflow. Our team are divided into 3 sub-teams*:

1. Project Manager
2. UX Designers
3. Website Developers
4. Graphic Design (from another team)

Balancing work load

Our group also manage our tasks and work using Agile methodology and utilize INVEST criteria to makes sure that each members do not get any burnouts and are able to manage their schedule (university and work) outside of creating the website. And after each milestone, we will do a quick one-on-one to get feedback on how to improve our flow better.

Explore Solutions

Iteration 1

We start our design by together creating our own version of the page matching the brief and the requirements.

Iteration 2

Based on informal feedback between one another of our team, we then re-iterate through our own design. At this point, the team is separated into 2 groups:

1. UX Designers → to produce the wireframes, LoFi, and HiFi
2. UI Designers → using our final LoFi and test out different color pallettes and fonts

Our initial assumption was to create something that is VIBRANT despite being a serious event which is why we picked something that is more colorful. However based on the feedback we received, the color feels a tad to childish for a serious event.

‍

Iteration 2 of KIPI page with multiple versions

‍Iteration 3

One of the feedback we received was:

We understand that the team tries to use a vibrant color pallette to make it look approach more appealing to younger audience. However, we feel the color look a bit unprofessional and a bit childish for a conference.

After another round of informal feedback, our team re-iterate through by creating a moodboard from several websites as our inspirations and try to re-discover our design to match our design brief and audience. In the end, rather than to use colour to engage our user’s attention, our approach was to create something more modern and minimalistic.

Iteration 4

For our final design, we are able to create something that is well matched with what our stakeholders and audience wanted. Something that looks modern yet professional fitting to the theme of the event.

We also took the time to conduct Usability Testing to several people (N<10)*, we found out something that is quite significant:

Most users that does not come from academia background or does not have the intention to persuade PhD, do not understand the term “Call for Paper” nor “Call for Poster” when most of our stakeholders assume that the general public would already know what that means

As a result, we change our writing to mention briefly what are those and included a link to allow user to understand the purpose of a conference.

*Our demographics include both Male, Female, Gen Z and Gen Y