Most impactful UX/UI items

36% fewer pages via IA

FIS Global (San Francisco) -- 36% fewer pages from a better information architecture

Before (May 2024)	After (July 2025)
PROBLEM: Short pages were hastily written by engineers who used more pages than needed Total of 50 pages	MY SOLUTION: I revamped and streamlined the information architecture to improve the flow, group related topics, and make finding information more natural. Total of 32 pages -- a reduction of 36%

2x more onboarded

Nium (San Francisco) -- Doubled the onboarding rate due to a new UX/UI steps for onboarding new customers

Before (Oct 2022)	After (Dec 2022)
PROBLEM: New clients were unable to onboard themselves due to the unclear method to them–-and even to Nium. Each region (AU, EU, HK, SG, UK, US) contains five very complex spreadsheets describing various steps of onboarding for various client types and situations:	MY SOLUTION: I created regions of customers with sub-pages for common onboarding steps and for region-specific parameter and example pages. Immediately saw twice as many customers onboarded with 75% fewer Helpdesk requests.

New UX with 2x details

Nium (San Francisco) -- Completely different UX and information architecture with twice as many pages of information

Before (May 2023)	After (July 2023)
PROBLEM: Pages were hastily written by engineers just to have "something" documented, for example: -  1 pg Payins - 14 pg Payouts ====== 15 pages total	MY SOLUTION: I revamped and authored pages with many more details and related concepts, for example: - 12 pg Payins - 19 pg Payouts ====== 31 pages total

25% more players and sales

Mica Games (Seattle) -- 25% more players and revenue from my suggested changes to his games

Before (Mar 1998)	After (Apr 2013)
PROBLEM: Brilliant word games were largely unknown because of clumsy UX/UI: - WordZap - Cricklers	MY SOLUTION: 31 ideas to improve the UX/UI, gameplay, settings, and other aspects.

Saved 85% of translation

Pristine (Taipei) -- Improved readability while saving 85% on translation costs by converting paragraphs to a table

Before (May 2008)	After (May 2008)
I was given text for translation.	I reduced the translation cost by removing the repeated phrases while making it easier-to-read by converting the paragraphs into a table.

20% drop in i18n mistakes

Hewlett-Packard (Singapore) -- 20% drop in internationalization and translation mistakes by PMs

Before (Jan 2007)	After (May 2007)
Hewlett-Packard's translation division used an Excel table to track which languages a project have been translated into and then reviewed for accuracy. I thought it was odd they used the standard ISO 2-letter language code on the X-axis while using their internal 3-letter languge code on the Y-axis.	After changing the 3-letter code to the 2-letter code, I noticed that a language wasn't reviewed yet--a mistake that the responsible project manager didn't notice either!