I believe fun is found, not waited for. Whatever the work or tool, I dive in hands-on and dig the fun out of it. Lodging, apartment management, VAN agencies, e-contracts, and small-business services were all different domains, but structuring repetitive work into products and systems has always pulled me in. Companies and roles changed many times; what stays constant is the thrill of spotting a problem the moment I stop taking the obvious for granted, then solving it.
2022.10–present
Designed scope, structure, and operational flows for Channel Manager and Vendit Concierge products so hospitality operators could manage OTA/PMS, inventory, rates, and reservations more reliably.
2021.10–2022.08
In apartment rental management, structured the manual work and mismatched metrics between HQ, sites, and operations into a daily-report dashboard and a chatbot.
2019.12–2021.10
Structured work scattered across chats, spreadsheets, and manual handling into web application and back-office workflows.
2019.04–2019.12
Automated revenue-database management and data aggregation and consolidated them into dashboards, simplifying repetitive operational workflows.
2014.12–2019.03
Turned repeated support-side customer complaints, installation bottlenecks, and operating expectations into experiments, data, product proposals, and standardized processes.
follow-up redesign, OTA/PMS integration structure
Based on the demand validated and the stability limits exposed in the MVP, I benchmarked leading global channel managers. I redesigned official OTA/PMS integrations, channel-specific flows, rate sync, self-onboarding, and internal/external notifications into our own structure fit for the Korean market.
Result. Setting release criteria on consistency and stability, it launched as a live service, and the reservation/inventory/rate sync structure was improved into an integrated structure.
scope-reduction decision, resource reallocation
I cut more than half of the overgrown scope of a concierge product already in development, analyzed market size and structural risks, and kept only the core features.
Result. I stopped further development and reallocated resources to a larger opportunity. A case of choosing to build less rather than more.
merchant application, back-office automation
I structured merchant applications, document checks, and owner assignment that had been scattered across KakaoTalk conversations into a web application flow connected to the internal back-office database.
Result. Application completion time was reduced from 3–5 days to 1–2 days, reducing document-missing bottlenecks and support fatigue.
operations experiment, installation process transition
When on-site installation was treated as the default, I hypothesized that resistance to remote installation came more from customer expectations and internal assumptions than actual necessity, then ran a four-week experiment.
Result. Per-person installation throughput increased from 2–5 stores per day to as many as 20, and remote installation became the standard process.