lucaluk uiux designer header

Do not listen with the intent to reply,
but with the intent to understand.

~ Stephen R .Covey

Hello I am Luca Luk!

# Proactive pessimist

As an INFJ @16personality, I see problems everywhere, yet I enjoy imagining new flows and solutions for day-to-day processes.

# Curious enthusiast

Always excited to learn new things and understand how things work, like taking up jobs in different sectors to observe different work flows.

# Listener

Rather than judging right away, I tend to observe, listen, and figure out why.

Nothing lights me up as creating a solution that changes people's lives.

About

Skills

Research

#User interview
#User shadowing
#User journey
#Personas
#User testing

Presentation

#IA system
#Sitemap
#Wireframe
#Design system
#Mockup
#Prototype
About

Tools

  • Slack
  • Slack
  • Slack
  • Slack
  • Slack
  • Slack
  • Slack
  • Slack
  • Slack
  • Slack
  • Slack
  • Slack
  • Slack
  • Slack
  • Slack
Projects

Highlights

Android Concept app

Note Management App

Focus on the research in the market and competitors, discovering a group of users market not taken care of, who prefer taking notes on a simple yet organized platform.

  • # User Research
  • # Personas
  • # User Journey
The Woods
Cinque Terre
Mountains and fjords

IOS Concept app

Finance Tracking App

Put huge effort on IA System, went through 6 versions to gather complicated financial information and present them in a simple way. Another highlight is the utilization of transaction efficiency.

  • # IA System
  • # Product Features decisions
  • # Efficient Transactions
Projects

Side Projects

Testimonials

Hear what they say...

Andrea Soverini

IDF Bootcamp mentor

Luca has been a phenomenal student and her passion for design and problem solving came out since our first session together. Her work has always been very thorough and she's not shy in going the extra mile. Her enthusiasm for learning and improving both her skills and the product she's working on, make her a great candidate for a dynamic team able to keep helping her grow and become an amazing designer. She learns fast and gets stuff done at high standards.

Joyce Lau

Senior customer manager

Luca came as a shy person, but she is willing to listen and accept opinions and feedbacks . She experienced a huge improvement in speaking to clients, being ease yet persuasive . She likes exploring creative flows to simplify processes , and she provides tons of constructive suggestions regarding the UI of our new database system

Jasmine Wong

Managing director

Luca is sincere, enthusiastic, and hard-working. During her service at our company, she proved herself to be a reliable, responsible, and efficient person. She is able to complete all the work assigned to her and she performed her duties to our complete satisfaction.

Android Concept app

Note management app

I am personally using Onenote, I like how it organizes my notes, but the navigation seems a bit clumsy. I searched for different apps in the market, but not an ideal one I want. Is it possible to create an organized yet simple note app?

Market Research

  • According to Verified Market Research, the Global Note-Taking Management Software Market was valued at USD 897.7 Million in 2018 and is projected to reach USD 1.35 Billion by 2026, growing at a CAGR of 5.32% from 2019 to 2026.
  • There are a large number of note-taking apps in the market, including those by huge companies like Google and Microsoft. Is it possible to compete against them? Why users would choose our app over the others? Which kind of users will do so?

Competitors Research

  • #Explore apps in the market

    #Read through the comments in the app store

    #Interview users around

    #Role playing

    #What? How? Why?

  • Simple apps can hardly organize and lack compatibility when coming to sharing and syncing.
  • Comprehensive apps are sometimes too complicated to understand nor troublesome to explore, at the same time making the app bulky.

User Research

  • Favored a simple yet organized platform, allowing them to take notes without confusion and distractions with notes grouped and sorted in an organized way.
  • Hate a steep learning curve or being confused and overwhelmed by complicated functions. Another interesting finding is that these users are often in high education and low-tech group.

How might we create an organized yet simple note-taking platform, so users can easily keep and access to important things in life?

Product Features Research

I had a deep dive into both simple and comprehensive apps, exploring from interface arrangements to input features, examing whether they would be suitable and welcomed by our target users?

Solutions

Pre-organized system

Templates are made to note specific items like amount, phone numbers, and travel routes. The system saves users time to organize little things in life.

Quick navigation

Save users time from traveling layer by layer to reach a note in a specific folder.

Input features

I focus on how to simplify the formatting process, like adding formats without selecting and applying multiple formats at once.

User testing

My approach is to test almost every button and wording. I asked testers to do basic tasks like adding a new note with my prototype.

And they are asked about the first impression of the app, like “What do you think this app does?” “How do you interpret these six categories?”

Surprises and Shocks

  • A testers thought it is a music app. I think the reason is that I put my favorite song’s lyrics as the content of note in the prototype.
  • Another user asked, “Is this a draft version?” This is another hard-hit and got me to research more on the UI trends and made a complete redesign of the UI.

Reflection

UX writings

I designed the full app, including every screen and pop-ups like the settings, and found much more to consider than expected, especially the UX writings. A slight change in wording can make a huge difference.

Test in low fidelity first

My approach this time focuses too much on particular functionality and wording, somehow lose the sight of the big picture. And it took me long to build a very high fidelity prototype. Next time I will try testing with low-fidelity prototypes until the tone and approach are confirmed before moving on to detailed mockups.

IOS Concept app

Finance Tracking App

Frustrated by apps in the market

I am a heavy user of expense tracking apps but usually frustrated using those in the market, like the time-consuming process and confusing report. Is it possible to have a better solution?

How do others think?

  • Other than interviewing people around, I also browsed the app store for comments and reviews of expenses tracking apps.
  • Lots of interesting and meaningful critics and suggestions are found, which is very helpful for accessing users’ pain points.

Think Process

Why people track their expenses?

Tracking expenses itself is not the goal, but just a means to save, to achieve their financial goals.

Why do people fail to save?

According to Financial quotient (FQ), people's financial well beings are the consequences of large and small financial decisions.

This means those who fail to save are likely those cannot notice the consequence when they make financial decisions.

How might we let people notice the consequence of spending, so they become more willing to save, and eventually achieve their financial goals?

Product Features Decisions

I brainstormed freely and then examine the ideas with the action priority matrix, based on their impact and cost.

Spending Consequence

  • Always show the remaining budget
  • Animation to show amount decrease
  • Positive feedback when closer to goals
  • Stars and prizes in every benchmark

Habits analysis

  • List of expensive expenses
  • Tags
  • Daily and monthly report
  • Saving suggestion
  • Investment mode

Efficient bookkeeping

  • Recent transaction
  • Typing suggestion
  • Auto search information of shops
  • Swipe instead of tap to input transactions
  • Photo widget

Connect and safety

    Share and connect with others
  • Trip mode
  • Fingerprint privacy lock
  • Hide specific info

User testings

I applied the agile methodology, creating designs, and let them tested over and over again. I focus on testing the visibility and usability of the app with a prototype.

  • Questions how do you interpret this section/button?
  • Tasks ask to do basic actions like adding a transaction

Surprises and Shocks

  • Surprised to find those “obvious” features are not understood, like the part of the template.
  • Some “brilliant” features are not appreciated, like forcing users to decide an expense is needed or wanted. The IA system is another huge problem.

Reflection

Best takeaway: Organize data

I realized I might be too ambitious to start by building such a complicated app. There is a huge amount of information to handle, and why to present them in a simple and clear IA system is a big challenge. Even I sometimes misunderstood the flow, it took me six versions to this final product. And I found mapping the flow out is very effective.

UI decisions

In the past when I did graphic design, I generally just put things where they look good. But once I start creating a user interface, I found there is a lot more to consider. I need to know exactly why a button is positioned here and why I chose this icon, what I want to achieve by that and what impact it brings.

Desktop Redesign

Google Drive Redesign

Note: I am not part of the Google company, this case study is only a product based on my observation. I do not have access to the user data nor visions of the company. This redesign is the best I can do for education, not to trample over the work of Google in any sense.

Very First Project

The first case study I did after start learning UX. To start, I decided to research on a well-established app that I am familiar with. My goal is to apply what I learned like user research, user testing, and problem-solving in this project.

Design Process

1Product Research

I spent a weekend exploring the app’s every button and functionality, making sure I have an in-depth understanding of its capabilities.

2Qualitative Tests

  • Try to observe them doing simple daily tasks.
  • Talk with google drive users of varied tech backgrounds, using “whys” to explore pain points .
  • Pain points: Not enough storage | tedious organization process | lack functionalities
  • Check whether the existing functionalities are effective to solve their problems
  • Discover a lot of useful yet unpopular features, like the draggable menu bar.
  • Carry out online survey to collect data from a wider group.
  • Interesting to find that most users are not using the cloud storage app to store files, but to share between users and devices.

3Quantitative Test

  • Pain points: Not enough storage | tedious organization process | lack functionalities
  • Check whether the existing functionalities are effective to solve their problems
  • Discover a lot of useful yet unpopular features, like the draggable menu bar.

4Assumption validation

Assumption: Users fail to notice features they need
  • Followup survey regarding the following features:
    • Permanant deleteA "removed" fispans moved to the bin instead of deleted permanently
    • View storage detailsA page to view and manage storage distributions
    • Draggable menu barAllowing users to drag files into folders
    • Connect appsUseful add-ons like online zip extractor, file converter, and media editor
Results: The majority are not aware of these features

How might we let users notice useful existing features , so they can better manage their storage and organize storage?

5Solutions

  • Put clear indications
  • Revise icons, wordings, and links
  • Unify interactions
  • Simplify user flow
  • Optimize the organization

6Design decisions

  • Not to add
    • Full-function bar excessive information may become noises
    • Full screen feature not useful enough to risk any users' confusion
    • Pop up tutorials may be annoying to those impatient, subtle hints are used instead
  • Not to remove
    • Side panel some other users may be frustrated without it

7A/B test

  • Invited 10 users to the test
  • Finish the same tasks like with the current app and my redesign prototype
    Time used for both designs is recorded and compared

Reflection

Even a frequent user might not be able to utilize an app

It is unfortunate that great features developed remain undiscovered . After doing the user testing, I taught the testers about those useful features, and they are more than happy to know them.

Insights user researches bring

The one on one interview is particularly inspiring. Listening to what users feel and think helps not only to discover various blind spots but also to figure out the underlying problem.

Web-based Hackathon

SME Chatbot

Legal Hackathon 2020

  • Teams all over the world work remotely to solve problems came after coronavirus pandemic
  • Organizations are invited to submit urgent challenges, the one we chose is started by The Hong Kong University, asking to save small businesses, social entrepreneurs, and startups financially.
  • View project on official site

The Team and my Role

We are a team of five, with legal, business, tech, and UX backgrounds working remotely together in a month. I worked closely with another UX designer to provide ideas from UX aspects and create:

  • Sitemap and wireframe
  • User flow
  • Mockup
  • Prototype

Problems

  • Some aids are provided for SMEs, but they lack time or knowledge to find out what aids applies to them.
  • Considering the company’s future, SMEs lack legal knowledge regarding insolvency, like what is it and what will happen to them.

How might we provide instant financial solutions for SMEs under Corona Pandemic, so they can have a clear picture of their situation, and know what works best for them?

# Solution

Web-based chatbot as quick filters for funds they can apply and a quick look at companies financial situation

# Solution

Summary of the funds like criteria, the amount receivable, and ways to apply.

# Solution

Quick insolvency overview allows SMEs to understand what it is and consequences

A toolkit is provided with useful links and documents checklist for the need of visiting a lawyer regarding insolvency.

Challenges

  • Most of the teammates didn't know each other, and working remotely makes it communication less effective. We spent almost half of the time just to decide what challenge to apply.
  • Teammates are very busy, making it difficult to arrange meetings.
  • The majority of the group do not have experience in creating a tech project or involving in a hackathon, everyone’s role is unclear.
  • Need to be very careful with legal information, contents and wordings. This took us a lot of time refining the contents.

Reflection

Better teamwork

It is It is very fulfilling to see a project developed in such a short period. I am glad that our team is very open to opinions and eventually we learned to work together more effectively by defining roles and work in smaller groups.

Insufficient research and testings

It is quite regretful that we did not do user researches with the SMEs shareholders or user testing of the prototype. The schedule is tight but I believe next time we can still do some simple interviews and tests to validate whether the solution is what users need .

Mobile app Volunteer

Medical Bookings App

It is an android and IOS app launched in Jun2020, a platform for hospital patients to book and manage appointments.

Team and Role

  • Brought on board by UX mentors into a team of 3 designers as volunteers to help test the app and provide feedback.
  • Exceeding their expectation, we not just pointing out problems, but also provide visual suggestions, like sitemaps, user flows, and wireframes.

Results

Our passion and insights help us win the company’s trust, bringing us into the company workflow, like inviting us to the company’s meeting. We talked about the importance of user testing and successfullly persuade them to hold on-site user testing, shadowing user flow.

Challenges

  • We joined in the late state when the app is about to launch, meaning that we are not involved in the design of the IA system
  • A tight schedule, limited room for changes
  • No access to vendors and tech team, difficult to understand their concern regarding the suggestions.
  • Cannot access to real users for research, that we may be encountering the wrong problems.

Reflection

See how things works in real world

Involving in a real project is surely a valuable experience, witnessing how they plan out their updates, how different department representatives communicated with each other.

Liaise with company representatives

We persuaded them for different changes, some were accepted, some were not. In the process, we understand more about the constraints of different shareholders, and what they care most. This is extremely helpful regarding idea presentation.