Menyikapi menjamurnya aplikasi standalone milik pemerintah, serta keharusan masyarakat untuk menggunakan beragam aplikasi untuk tujuan berbeda-beda, dipadu dengan kurang efektifnya upaya sosialisasi, serta rumitnya koordinasi antar institusi negara di Indonesia, maka low hanging fruit yang masyarakat butuhkan adalah suatu hub pintar (“Smart Assistant”) yang bisa berkomunikasi dengan ratusan apps yang dibuat pemerintah, untuk bantu mencari informasi.
Dengan cara ini, user bisa mengakses informasi dari seluruh aplikasi milik pemerintah. Idealnya sampai melakukan proses interaksi yang dibutuhkan, tanpa harus menginstall aplikasi-aplikasi tersebut terlebih dahulu, atau minimal supaya mendapatkan kejelasan aplikasi apa yang harus ia install.
Persyaratan yang penting untuk segera diterapkan untuk mendukung model hub-and-spoke ini ini adalah mewajibkan semua app yang dibiayai APBN/APBD untuk membuka API untuk koneksi data. Rumah untuk model ini (hub) bisa dibuat di aplikasi eKTP, atau non-govt made.
Model ini tidak ideal, tapi ini cukup fleksibel untuk memfasilitasi strategi transisi ke depannya, mengingat belum terlihat adanya upaya untuk melakukan koordinasi agenda antar instansi, dan pembuatan aplikasi digital masih dianggap sebagai suatu prestasi kerja. (byms)
Indonesia is among the countries where its general population skipped desktop computers upon the digital evolution, and jumped straight into smart mobile phones. It challenges tech startups due to the different behavior and ability of this user segment.
For example, from User Research we discovered that among the biggest friction for buyers to close a transaction in OLX was in comparing products from different sellers, which is easy to do on desktop computers due to the ability to open multiple tabs, but it’s inherently difficult to do on a native mobile app due to limited screen estate.
While extreme users tend to have their own hacky ways to compare products, or simply switched to using a desktop, for the new users it’s a rather painful experience of going back and forth through different products or having to jot down notes on paper.
Our idea for a solution comes from another user research insight that even though most products in OLX are one of a kind (single-item inventory), buyers often manually take notes of interesting products they might want to buy later. It’s among the most surprising findings as in our initial hypothesis believed that since OLX is not an online shop with replenished stocks, users don’t need a product-saving feature.
Thinking to accommodate both the need to save a product listing, and compare several products to make decision, we’re introducing the ability to save favorites, and develop a page to do side-by-side comparisons of similar products.
We ended up including “Favorit” (Favorites, en.) as one of the menu items on the bottom menu bar, and reorganize the less important functions into sidebar or Settings. After launch, from analytics we discovered that Favorites has becoming one of the most used features in the All-New OLX version, and contribute a significant return traffic to products bookmarked. (byms)
The All-New OLX has bottom bar with “Favorit” menu.
Dalam interaksi di dunia online, kita sering sekali menemukan istilah “UI/UX” dipakai untuk mencerminkan aktivitas perancangan pengalaman pengguna.
Sering juga kita menemukan dalam komunikasi di dunia kerja cetusan semisal “UI masih nunggu UX” saat mengacu pada belum siapnya wireframe atau wireflow.
Padahal, jika mengacu kepada Don Norman, pionir gerakan User Experience Design, definisi UX adalah:
"User experience" encompasses all aspects of the end-user's interaction with the company, its services, and its products. ~ Don Norman, Nielsen Norman Group
Jika diterjemahkan,
"User Experience (pengalaman pengguna) mencakup semua aspek dari interaksi pengguna akhir dengan perusahaan, layanan-layanannya, dan produk-produknya."
Atau disederhanakan menjadi,
"User experience adalah keseluruhan aspek interaksi antara pelanggan dengan suatu perusahaan, layanan, dan produk nya."
Alhasil, UX bukanlah proses penciptaan wireframe, atau “tahapan sebelum UI”, tapi UX adalah keseluruhan proses desain itu sendiri, yang salahsatunya termasuk perancangan UI.
UX adalah “umbrella term” dari beragam aktivitas terkait penciptaan pengalaman pengguna yang menyenangkan.
Rata-rata ajang dan konferensi internasional pun mengusung judul “UX”, misalnya:
Lantas yang biasa dimaksud “UX” dalam konteks “UI/UX” itu apa?
Istilah yang dipakai di banyak perusahaan dan organisasi profesi adalah “Interaction Design (IxD)”, salahsatu disiplin di bawah payung istilah User Experience Design.
UX hanya mencakup desain?
Dalam praktiknya UX bahkan melibatkan juga divisi dan role lain di suatu perusahaan karena interaksi antara pelanggan dan suatu perusahaan terjadi sejak sebelum ia menggunakan aplikasi yang perusahaan buat.
Misalnya dengan team Marketing, saat menonton iklan TV yang menginformasikan produk dan layanan yang perusahaan tawarkan, lalu dengan team Sales, saat mempertimbangkan paket langganan mana yang akan dipilih. Atau, dengan team Customer Service saat harus meminta kejelasan terkait produk, layanan, dan lainnya.
Alhasil, untuk aktivitas UX design yang khusus terkait perancangan aplikasi saja, istilah yang lebih tepat adalah Digital Product Designer, atau “Product Designer” saja.
Ada berapa banyak jenis UI?
Secara definisi, UI (User Interface) adalah fasilitas interaksi antara pengguna dengan aplikasi. Walaupun istilah UI identik dengan tampilan visual, namun kenyataannya ada banyak ragam UI, misalnya Voice UI, Haptic UI, Gesture UI, tapi yang paling umum memang Graphical User Interface (GUI).
Jika diibaratkan restoran, maka UI adalah piring, sendok, garpu, pisau, dan gelas, yang kita gunakan untuk mengkonsumsi makanan dan minuman yang dijual restoran tersebut, sedangkan UX adalah gabungan dari pemilihan alat makan, desain interior, musik, dan layanan reservasi yang membantu terciptanya pengalaman makan yang berkesan.
Selain UI, ada banyak bagian lain dari UX, misalnya: Interaction Design, UX Writing, UX Illustration, Animasi, Sound effect, dan Information Architecture, yang akan kita bahas di artikel lain. (byms)
The project was unique as it poses an interesting question: what product will become our future-proof solution? Think within the context of work productivity, collaboration, project management, activities that we already have a ground on, but think outside of the box.
As an example, look into MS Excel, surveys shows that it’s the No.1 Project Management tool in the world despite the success of Trello, Asana, and the likes. Why? Because people find it easy to use and good enough to cater to most of their project management needs.
Its “open-scenario” style also makes it a very versatile tool, therefore despite its branding as a spreadsheet solution, people use it for many things beyond a spreadsheet. Product Owners use it for Roadmap and Backlog, programmers use it as a database, some could even program their software using Macros in Excel!
What would be something that we can create to match Excel’s versatility?
To answer this question I look into the tools I’ve already use, to look for inspirations. What project management tools do I use? What are the other tools that I find very useful in my day to day work? Then I asked my colleagues the same questions to ensure minimum bias. After that research, the answer converged into three tools: Google Keep, Apple Note, and sticky notes!
Why sticky notes?
I love sticky notes! It’s a multi-purpose tool that you can use to taking notes, creating reminders, sending a message for others, insight generation in card-sorting activity, and many things. You can even create artwork from it! In fact, even in our office we quickly realized we used sticky notes a lot. It’s on the walls, the windows, monitors, tables, refrigerator, everywhere!
My concern with sticky notes is its very silo-ed and analog nature, meaning its content can not be seamlessly integrated into other media, rather permanent, space is very limited, and not easily duplicable. The available digital version back then, even from its originator 3M, was leaning towards creating a virtual board for you to play around with digital sticky notes, yet weirdly, copying their limitation as well. Among those that pushed for innovation, Miro was the one that proposes interesting value as a digital whiteboard, but it still doesn’t answer the needs we identified.
On the other hand, we have Keep/Note that is also used in a similar fashion: you can use it for almost everything! What’s good about those is that they’re digital, so it carries the awesomeness of digital products like the ability to edit, copy and paste, search contents, and adds multiple properties like adding date, sharing, color, links.
So I was wondering if we could somehow create something that represents these two marvels.
Turned out we could.
The Concept
The converged idea comes in one afternoon and I quickly sketched it on a piece of paper to show to the CEO/Head of Product, the CTO, and my Product Owner counterpart. After a quick discussion and add on notes, this is what we got:
The concept that we agreed upon is a “note”, an entity that can be made to support different purposes through properties, e.g. date, people, response, comment, and can be linked to other cards to form a cluster of cards. This way, you can even do project management using cards! Simple, versatile, powerful.
The next step is to decide on the look, and how it works. For these goals, our team did a lot of case studies collecting to identify common use-cases, a co-creation workshop to tap into our colleague’s rich knowledge, as well as doing benchmarking.
By running tests with our current users, and speaking into potential users, we also got good feedback into how they would use the product, which helps in setting the product direction, features to be included, what should be in our MVP, and what is our roadmap.
At the end of the project, our UI Designers reviewed at least 40 different products to decide on the visualization!
Naming wise, after consulting with other stakeholders, including our VP of Marketing, eventually, we settled on “Eko Cards” or just “Cards”.
Challenges
What I found as a very interesting challenge from this project, aside from the innovation challenge was the importance of having a thorough use-cases examination. Why?
As a German proverb says, “Der liebe Gott steckt im detail”, which translates as ‘God is in the detail’, popularized in the Modern Design movement by Mies Van Der Rohe, the use-cases really helped us in identifying challenges and how to solve it.
For example:
Which feature(s) shall we put on the top menu? How should it look on the empty state, upon filled, how to best save the precious screen estate but kept the function recognizable?
As Cards support realtime collaboration, what would happen if two or more people are editing the same card at the same moment? Which input shall we prioritize?
Should there be a save button? What about autosave? How often should we autosave it without putting too much burden on the server? Can we create a local buffer?
What would happen if the internet connection was lost, and other contributors are unknowingly making changes to the same section the user is editing? Whose edit shall be prioritized? What should happen to the other edits?
What would happen if a user edits a section, which practically locks it, but then going idle? Shall the system keep locking the section? For how long? Should there be a way to inform the user?
How should we add the feature to transform Card into a task? What should happen if a task is done, should we “close” or deactivate the card? What should be shown on other card(s) linked to that card?
How to effectively inform the card viewer that there are other card(s) attached?
To what extent should we display the card’s History? What considered as an edit? What are the events the system needs to track?
How should it behave on a desktop web view? How to best taking advantage of the bigger screen estate on the desktop? Should we completely mimic the mobile version’s behavior, or should they complement each other?
And so on.
Those are dizzying questions but necessary to ensure the creation of intuitive experience. Hours of discussion spent, and on many occasions we simply need to be content with having an educated guess, to be iterated later on after we can gather real user feedback. Else it will be an endless loop.
After the tough discussions, several iterations of creating and testing, including grabbing strangers in public places for guerrilla testing whenever we can, finally we launched the product and I was so happy to see it taking center stage in our app.
For more reference about Eko’s Virtual Workspace, visit the company page here: https://www.ekoapp.com/
One of the most tedious, demanding task for any designer looking for career opportunities, admit it, is updating our portfolio! It’s almost impossible to do while we’re working full-time, (unless you’re already thinking ahead of switching job), yet when we finally have time, without a proper evidence gathering rigorously practised during we’re still employed, it means going back and forth through the whatever archive we can get our hands upon.
I’m glad I did some evidence gathering once in a while which help to give structure to my storytelling, so my current design portfolio update wasn’t that painful.
Still in it’s first draft stage, almost 40 pages long! Yes I will trim it down but that’s stage two, for now this is it, a work in progress:
