Project Overview

My first move wasn’t a redesign — it was rebuilding the sitemap and user flow against what actually existed, so any decision after that was grounded in the real product, not the documentation of it.

Team & My Role

I was the lead product designer working closely with product managers and engineering leads across two product tracks simultaneously.

Target Audience

The platform served two distinct user types with very different needs and technical literacy levels.

Business Goals

• Reduce onboarding friction for new enterprise clients adopting FCI cloud services
• Create a consistent product experience that could scale across new features without design debt accumulating further
• Expand reach to mobile users by shipping the product’s first native mobile app
• Win the FPT Hackathon to demonstrate innovation and team capability
• Enable the design system to be inherited and improved by future designers without rework

The business needed the product to feel enterprise-grade. The users needed it to feel usable. Those two goals were more aligned than the existing product suggested.

Design Context

User Pain Points

Key Metrics

User Research

I conducted interviews with 8 internal users (IT admins, developers, and one business manager) and reviewed support tickets to identify recurring friction patterns.

Key Insights

Scope & User Stories

The project was scoped into two phases: foundation (design system + IA) and expansion (mobile app + new features).

Logic & Business Rules

Service provisioning flow

Key business rules

• Users cannot provision services exceeding their account quota — the system must surface remaining quota before step 2, not at confirmation
• Deletion of active services requires a typed confirmation (service name) to prevent accidental loss
• Error states must include a plain-language explanation + recommended action for non-technical users, in addition to error codes for developers
• Mobile app read access only — provisioning remains desktop-only in v1 to reduce complexity and risk

UI Screens

Selected screens from the redesigned platform.

The full set of screens lives in the Figma prototype.

Attachments & Documents

Outcome

The redesign delivered a unified product experience across web and mobile — the first time SmartCloud felt like a single platform rather than a collection of features.

• Rebuilt the sitemap and navigation around how users actually think about cloud services, not how the product was built
• Established a design system with shared tokens, components, and documentation — inheritable by future team members
• Shipped the product’s first mobile app (iOS + Android), covering monitoring and alert management
• Won the FPT Corporation Hackathon, demonstrating the team’s ability to ship innovative work under pressure
• Error states rewritten in plain language, reducing support ticket volume for UI-related issues

The work that mattered most wasn’t the final screens — it was the system underneath them. Every feature after this point had a foundation to build on.

Overview

FPT Cloud Server provides a secure and reliable virtual server system, designed centrally for easy scalability. Users can create and configure compute instances with minimal operations, and control the system through the web, CLI and API. Each compute component can be configured separately: processor, storage, networking, operating system and charging method.

Product advantages

My Role

I was the only designer on the product, working closely with the Product Owner team in an Agile process (Jira and Microsoft 365).

• Collaborating with the PO team
• Sitemaps, wireframing and prototyping
• Design iteration and high-fidelity UI mockups
• Building the design system
• Marketing assets

Design Process

Research

We analysed user feedback collected by the sales teams and ran internal surveys to find the critical pain points and the areas to improve. From there, the Product Owner and I agreed on three key insights:

Ideation

With the research done, we built new wireframes and user flows for the web and mobile app, focusing on navigation, resource management and data visualisation.

Iterative design

Building on the research, the competitive analysis and the user flows, I created the design system and style guide that keep every product module consistent.

• Design System, version 2.0
• Style Guideline, version 1.0
• Product design for desktop, mobile and tablet (UI version 2.0.0, 2024)

Problem-Solving

User-Centered Design

I focused on intuitive interfaces for complex cloud management tasks, serving both technical IT staff and upper management. The mobile app is built for quick notifications, easy monitoring of virtual machines and a simple billing overview.

Technical Considerations

I worked with the development teams to make sure every design improvement was feasible within the existing system architecture, and designed with scalability in mind so new features can be added without hurting the experience.

Outcome and Impact

The project is in the planning and bug-fixing stage, with a roadmap for gradual UX/UI improvements. I created a full plan for rebuilding the design system and component library, to keep the product consistent and reduce hardcoded elements.

Lessons Learned

This project shows how I approach complex design challenges in enterprise cloud services: building a design system, balancing technical requirements with user needs, and improving a live product without disrupting the people who use it every day.

• A solid foundation (the design system) has to come before rapid feature development
• Redesigning an active product takes careful planning and prioritisation
• Continuous user feedback is what guides good decisions on complex technical products

Overview

My team’s goal was a complete data visualisation solution, comparable to Power BI, to support financial and accounting work across FPT Corporation and eventually replace Power BI. The need sounded simple, but meeting it meant the PO and BA team kept reviewing Power BI’s features, picking the ones that truly mattered to the business and its subsidiaries, and researching how competitors handle big data and data security.

• Web application: data visualisation, reports and dashboards, data modelling, account management, workspace and organisation management
• Native mobile app: viewing reports and dashboards

My Role

I was the only designer on the product, working with the PO team in an Agile process (Jira and Microsoft 365).

• Collaborating with the PO team
• Sitemaps, wireframing and prototyping
• Design iteration and high-fidelity UI mockups
• Building the design system
• Marketing assets

Design Process

Research

With the Product Owner’s support, I collected Power BI’s functional analytics and user needs, so I could look at the product’s UX objectively. From there, we agreed on three key insights:

Ideation

After working through the needs with the team, we completed the core user flows for the first features, then started wireframes and user flows for web and mobile, with the focus on data modelling, visualisation and account administration.

Iterative design

Finally, we built a complete design system and high-fidelity prototypes, and refined them with stakeholder feedback and A/B testing until the result worked as well as it could for the end user.

Problem-Solving

User-Centered Design

Throughout the roadmap, we aimed for data displays that are easy to understand and pleasant to look at, so people can get insights quickly and make informed decisions. Data Suite is tailored to different roles within FPT, each with its own level of data access and analysis needs.

Technical Considerations

The engineering team made sure the architecture supported many ways of entering data and connecting databases, and worked with us to verify that real-time updates and cross-platform sync were feasible.

Outcome and Impact

When I moved to another project in March 2023, Data Suite was still a proof of concept, with selected FPT member companies trying the platform and running A/B tests to refine the experience. By FPT Techday in November 2024, the product had been released to end users and was in its marketing campaign.

Lessons Learned

This project shows my work on complex data visualisation tools: balancing user needs with strict security requirements, building a full design system and adapting it for web and mobile.

• Simplicity and visual appeal are what turn data into insight
• Multi-level data access is complex to design without making the experience feel heavy
• Complex data tools need continuous testing and iteration

Overview

Pizza Hut Digital Ventures (formerly Pizza Hut Digital & Technology) is a digital brand owned by Pizza Hut, part of Yum! Brands. I’m proud to have been part of PHDV’s work on a world-class digital platform (web, iOS and Android), helping Pizza Hut grow as a digital franchisor through data-driven technology, thought partnership and a people-first culture, and giving the best ordering experience to everyone who enjoys the Pizza Hut menu.

At PHDV, I designed and improved websites and mobile apps, and partnered with other teams to build the core design system. My goal was to grow my product design knowledge across the whole product development cycle.

Team & My Role

• Assisting UX research in Asia
• Sitemaps, user flows, wireframing and prototyping
• Internal testing in Vietnam
• Design iteration and high-fidelity UI mockups
• Assisting the design system
• Marketing assets

The product team had 100–150 people: design, UX research, web and mobile development, product managers and more, working in Agile with Jira and Monday.

In my first month, I spent a lot of time talking with the design team. Before, I had worked with one teammate and handled most of the team’s tasks; here I had international colleagues with many years of experience. I started learning standard product processes and took on specific website and app features under the direction of the Team Leader.

Business Story

Pizza Hut’s sales growth had slowed, while competitors such as Domino’s grew their digital offering. After a $130 million investment from parent company Yum! Brands, Pizza Hut Digital Ventures (now Pizza Hut Digital & Technology) was set up in 2017 to use digital technology to improve the customer experience: online payment, delivery and takeaway ordering, and loyalty programmes.

Our vision

PHDT had a clear mission and a focused product vision: one core, creative e-commerce platform, with websites and native apps for every franchise market, that gives customers an outstanding experience and makes ordering and delivery more efficient and cost-effective.

“Delivering Digital & Technology Excellence for Our Customers, Team Members, and Franchisees.”

Product Features

Personas & Customer Journeys

After discovering and empathising, we moved to defining. The team ran usability tests with two people who matched our core audience segments: we showed them the current Pizza Hut website and asked them to order a pizza with one method, delivery or pickup. The test results showed the main difficulties:

The design team in Vietnam mapped the first customer journey in Q1 2019.

Target Audience

In the second round of research (Q4 2019), the UX researchers at PHDV UK ran user research and a survey with 31 participants across Japan. Synthesising the results with them and with the business strategy, we found three main age groups:

Competitive Research

Competitive research was an essential part of the define stage. By analysing the features and solutions across the market, we saw where Pizza Hut stood, which services were basic and which were complete, and the strengths and weaknesses of our competitors. This helped us define our value proposition and find where the product could stand out.

Sitemap & User Flow

The sitemap and user flow showed the whole journey of a user in the app, from placing an order to checkout. They helped us find opportunities to improve the experience, and gave designers, product managers and developers a shared picture of how the proposed solution was structured.

Hi-fi UI Mockups (Version 2, 2020)

In 2020, as the company grew fast, the design team expanded across the UK, the US and Vietnam. It was an exciting chance to build the second version together with product designers and UX researchers around the world.

Delivery option & order time

The app supports delivery and pickup. Pickup users find nearby stores on a map, by typing a location or using their phone’s location. Delivery users enter their address by postcode or street address, then choose a preferred delivery time.

Menu & item customisation

The menu has six categories: deals, pizzas, sides, dips, desserts and drinks. Users customise a pizza by size, crust, sauce, cheese and toppings: they can create their own pizza, pick any four toppings, or go half and half with different choices on each half before adding it to the cart.

Shopping cart & checkout

In the cart, users manage the order time, delivery address and items, and can add coupons and suggested extras. At checkout, they enter the recipient’s details, choose a payment method, and can register to join the loyalty programme. After the order is placed, a confirmation screen shows order tracking, estimated delivery time, order details, address and payment method.

What I Learned

Pizza Hut Digital & Technology was a great chance to go deep into digital product design, where creative design and technology come together to build products that give customers a seamless experience and keep them engaged. It also let me work cross-functionally and support the whole product development process.

• How digital products are developed in a franchise environment
• Keeping data consistent across the website and mobile app
• Collaborating cross-functionally with Agile teams
• Working in a diverse, multicultural environment

Overview

Customers can easily buy pizza from their phones with this app. Besides earning points and redeeming vouchers, its biggest advantage is letting customers customise their pizza to the flavours they like.

My Role

As UX/UI Designer and Graphic Assistant, I designed 50% of the app’s foundation on my own: login and logout, account, home page and the ordering flow. Later, a second designer joined me for the go-live in Japan, where we added image processing for the menu database and redesigned the menu page for that market.

Design Process

FCDS Branding Guideline & Library

FCD (Fast Casual Delivery & Carry Out) is Pizza Hut’s store format for delivery and carry-out, and the model it uses to enter new markets. It improves the customer experience with technology such as contactless delivery and pick-up.

Our team’s job was to bring this product to market exactly as the FCDS Style Guideline, created by the UK team, describes.

What Did We Build?

The UK team built the web app as a template for other markets. For each market, the Project Manager collected requirements directly from that market and delivered features comparable to the UK site, adapted to local differences, especially in disposition and menu. The mobile app design was rolled out at the same time.

• Product: e-commerce website and mobile app
• Platforms: website, Android and iOS
• Markets: UK, US, Malaysia, Indonesia, Singapore, Japan, the Philippines, Thailand, Kuwait, New Zealand and more

Modules & main flows

• Marketing: landing pages for events and seasons
• Ordering: disposition (delivery, takeaway, dine-in), menu categories, item customisation (pizza, combo), cart, payment, order tracker
• Account: create and manage an account with Facebook, Google or email
• Membership: points, coupons and vouchers per account, order history
• Payment methods

User Flow & Wireframes

The user flow covers the whole journey: splash screen, guest or login, choosing delivery or collection, finding a store, setting the order time, the menu with half-and-half pizzas, the basket with coupons, checkout and order confirmation.

More Screens

Lessons Learned

Even when the product is the same, each country brings differences in UX, language, culture, geography and more. When building an e-commerce product, it is critical to think carefully about how best to reach users and encourage them to interact.

Overview

A complete system that supports the daily operations of a restaurant chain: Kitchen Display System (KDS), POS, Dine-in App and Driver App, for Pizza Hut in Indonesia. It was designed for tablet and mobile, with responsive layouts and touch-friendly interfaces. I worked with the developers to make sure real-time features and communication between the apps were feasible.

I was the UX/UI designer, working with Product Owner Neeraj Kumar.

Design Process

Key Insights

Low-fidelity Wireframes

Wireframes for the Indonesian market, starting with the POS.

Problem-Solving

Personas

More Screens

Lessons Learned

This project tested my ability to build complex, connected systems that balance user needs and business goals. It also showed how much market conditions and company goals shape a product: only the POS and KDS were released. The Driver App and Dine-in App were not built because of budget limits, and another driver app was already launched and more heavily promoted in Indonesia.

• Do thorough market research and business viability checks before full-scale development
• Design systems need to be flexible enough to follow changing business requirements
• Keep talking with stakeholders throughout the design process
• Consider the solutions already on the market, and how to integrate with them

Overview

A small, bright shape can balance a large, dull shape. That one idea, discovered with paper and glue, is the start of every layout decision.

Who it’s for

What they’ll learn

• Name primary and secondary colors and mix one from the other
• Use warm and cool colors to give a picture a feeling
• Make a page feel balanced, with symmetrical and asymmetrical layouts
• Describe color with hue, saturation and value, and pick complementary or analogous schemes
• Use hierarchy and the rule of thirds so the most important thing is seen first

Session plan

Each level is one 2-hour session in three parts. Choose a level to see its plan.

Key vocabulary

What to have at home

Classes are online, so a few simple supplies at home make the activities work.

Overview

Good-looking isn’t the goal. A screen where the palette fits the brand, everything sits on the grid, and the eye lands on the main action — that’s the goal.

Who it’s for

Teenagers from 15 and adults who want the professional side of design — the reasons behind grids, color and contrast — and want to use them on real interfaces.

What you’ll learn

• Read the psychology behind brand colors and choose a palette for an audience
• Tell RGB from CMYK and know which one a job needs
• Check contrast ratios so text stays readable for everyone
• Lay out content on a 12-column grid with consistent gutters
• Group information with proximity, similarity and closure
• Use hierarchy to lead the eye to the main action

Session plan

One 2-hour session in three parts.

Key vocabulary

• RGB
• CMYK
• Color Psychology
• Contrast Ratio
• Grid System
• Column
• Gutter
• Gestalt
• Proximity
• Closure
• Similarity
• Hierarchy

Tools

A computer with Figma (free plan is fine), Sketch or InDesign, an online contrast checker, and graph paper if you like to sketch first.