GOLFER

End to End Solution for Course Reservation and Management

GOLF IN TAIWAN

We Bring Fresh Air to Golf Environment in Taiwan

Golf reservations in Taiwan haven’t seen much digitalization yet, with only a few major players dominating the market. Golfer was created as a concept to explore the potential of a complete ERP solution—one that not only handles reservations, but also helps manage finances and logistics seamlessly.

Some of the recurring challenges in this space include:

  • too many disconnected systems in a single business due to the need for third-party integrations,

  • overly complex reservation management that general ERP systems struggle to handle, and

  • membership systems tied to banks, which add an extra layer of complexity.

DESIGN PROCESS

Real Design Process in This Company

I won’t sugarcoat the design process by making it sound like a textbook example—because in reality, it wasn’t. With a lean team, efficiency in the design process and handoff became absolutely critical. However, there were several unavoidable variables that were beyond my control as a designer:

  • Vague or unclear requirements, even after multiple rounds of evaluation

  • Sudden changes in requirements driven by user feedback

  • Shared resources—especially on the PM side—meant limited support during product development

Despite these challenges, I remained focused on delivering clarity and direction within the constraints we faced.

Big Issue - Requirement Complexity for SaaS ERP

ERP systems come with a high degree of complexity and unpredictability, often shaped by the specific business model in use. From a product design standpoint, this means deep consideration and time are needed to understand potential negative cases and edge scenarios.

This complexity often led to longer design cycles, as initial requirements were frequently oversimplified and required extensive discussion, research, and validation to mature.

The challenge: tight product timelines with little room for delay.

Problem Started

Solution

To reduce back and forth for requirement, the new flow Design team will request additional time to have deep analysis. It may cost around 2 – 3 day but after the analysis I’m coming with a lot of question, suggestion and ideation.

By find the issue / requirement changer faster then it can be prevent revision coming on developer side

OUTCOME

Below are some of the designs I’ve worked on, though I can’t showcase everything due to a client NDA.

ONBOARDING (LOGIN REGISTER)

BOOKING PROCESS

SCHEDULE

Thank you for visit

The design above was created based on discussions with the product owner and insights from user research. We used an Agile Design methodology, meaning the design process was done iteratively. As a result, there may still be some aspects that are not fully refined yet, with room for further improvement as we progress.

I’m open to presenting this directly if needed. Unfortunately, I can’t share everything here due to an NDA with the involved parties.