Built Sweetspot's design discipline and its first shared design system
- Role
- UX and Product Design Lead
- Team
- A senior and a mid-level designer I led; reported to the CPO; DesignOps with developers and managers: design reviews, UX audits, workshops
- Scope
- B2B and B2C · web, iOS and driving-range hardware · Club Portal, booking, website, design system
- Context
- Booking and business platform for golf clubs, simulators, driving ranges and academies
- 3 teams
used the rebuilt Sweetspot.io for leads: sales, marketing and customer success
- Shipped
Club Portal's new navigation, regrouped around clubs' daily tasks
- v1
ScrambleDS launched, one design system on Tailwind for several products

Golf clubs, simulators, driving ranges and academies use Sweetspot to run bookings, memberships and payments, and their players use it to book and pay. From 2023 to February 2026 I led UX and product design for all of Sweetspot's digital products, with 2 designers.
Several products for golf businesses, and no design discipline yet
Sweetspot runs on web, on iOS and on hardware at driving ranges. Businesses run their day in Club Portal, and players use the consumer products. When I joined, the company had no design discipline of its own. The products looked and behaved differently. Designs reached developers late or incomplete, and decisions were made without talking to clubs or players. Club Portal also ran on legacy code, which limited how far a redesign could go. My job was to build the discipline while I led the design of the products.
ScrambleDS: Tailwind underneath, Sweetspot's own components on top
I built the foundations of ScrambleDS, the design system for Club Portal, the booking web app and the mobile app, and launched its first version. By the time I left, 3 squads used it. Its job was to keep the products consistent and make work between designers and developers simpler. I built it on Tailwind, with Sweetspot's own components and tokens on top: we didn't start from zero, and we still owned the brand and the patterns. A front-end engineer built it with me.

Club Portal's menus, regrouped around the jobs clubs do every day
Club Portal is Sweetspot's flagship for golf businesses. I redesigned its navigation completely. In my first summer at Sweetspot, support tickets, heuristic evaluations and interviews with 6 golf clubs showed what was wrong. Several menu items had the wrong names. Some sub-sections belonged under other sections. Settings were spread across the sections instead of sitting on the main settings page. And no one had decided the order of the items. I weighed a lighter option, renaming and reordering the existing menus, against regrouping them, and chose to regroup: the menus followed the jobs clubs do every day, such as bookings, players, memberships and payments, with sub-pages nested under each. The new navigation shipped and fixed all four problems.

A website that sales, marketing and customer success used as a tool
I redesigned the Sweetspot.io website and rebuilt it in Framer, so people outside design could update pages without developers. Sales, marketing and customer success did, and used the site as a tool for leads and customer experience. The design team kept ownership of the site's structure and most of its pages.

Player products and driving-range hardware shipped too
I designed the consumer products myself: golf packages with resort stays in the iOS app, and passes and memberships on responsive web. The team I led designed pay-and-dispense for driving ranges of all sizes.
This case has no figures: they're confidential. The evidence is what shipped, and what the people I worked with say about it.
“He is hands-on, stays on top of AI trends, and is deeply skilled in technical design. During our time together he delivered top-tier work on our most complex projects.” Alexander Gunnarsson, product manager, Sweetspot



Insights and Project NEXT were still in development when I left
I designed both of these larger pieces myself: Insights, analytics for club owners, and Project NEXT, the next generation of the admin.


Led 2 designers, and brought managers into design reviews
I led a senior and a mid-level designer, and mentored them.
“From day one, he had a strong sense for when and how to support the people around him. He shares the right tools, at the right time, in a way that genuinely helps you grow.” Vemund Due Thorén, designer, Sweetspot
I started DesignOps at Sweetspot: design reviews, UX audits, discovery and ideation workshops, plus fixed rituals such as critiques and handoff check-ins. It included developers and managers as well as designers.
Bringing managers into design reviews was my best call there, but I made it only after the first conflicts. Until then, what we built often strayed far from the design, because developers and other stakeholders changed it to their own taste. In the reviews, managers saw why we had designed the product the way we did.
I stayed hands-on and reported to the Chief Product Officer.
“Together, we built and architected our design system from the ground up — and his deep understanding of the bridge between design and front-end development was key to making it work.” Viktor Pöntinen, front-end engineer, Sweetspot
What I'd do differently
I'd set up Amplitude events for Club Portal's navigation before the redesign, so I could show the change in numbers, not only in feedback. I'd bring managers into design reviews from the first week. And I'd cut Project NEXT into smaller releases, so some of it shipped before I left.
Credits: a senior and a mid-level designer, the front-end engineers who built ScrambleDS and the product and engineering managers who took part in design reviews.