Guest mode and guided first use
Let occasional drivers pay without account friction, while a short tutorial explains the flow for first-time users.

Leading research, product strategy, and visual direction for a parking-payment journey built around clarity and trust.
Research-led product direction
01 / The challenge
Parking payment is time-sensitive. People are often mobile, already in transit, and unwilling to tolerate ambiguous cost, weak feedback, or technical instability.
The work connected two realities: make the current journey easier to trust and complete while defining a scalable foundation for booking, subscriptions, tracking, digital tickets, and smarter parking services.
At Addinn Group, I led the design work from stakeholder discovery and product definition through research, UX/UI direction, testing, presentation, and the visual system used to communicate the service.
02 / Evidence to structure
The program moved through six connected layers: business strategy, value innovation, user research, design goals, usability testing, and a design-system foundation.
Stakeholder interviews, three personas, journey mapping, reaction surveys, competitor review, and a detailed UX audit translated business ambition into priorities for the payment flow and broader service architecture.
03 / Product principles
The research repeatedly pointed to the same requirement: make the next action visible before asking for commitment. That meant less friction at entry, more flexible search, transparent payment, and recovery states designed as part of the core journey.
Let occasional drivers pay without account friction, while a short tutorial explains the flow for first-time users.
Support manual search, map exploration, and location scanning, with availability, price, duration, and reviews organized together.
Show the remaining steps, simplify the summary, support more payment methods, and provide a usable receipt after the transaction.
Design loading, error, success, and retry states deliberately across mobile and desktop instead of treating them as exceptions.
04 / Direction
The resulting direction prioritizes shorter steps, stronger contrast, cleaner summaries, explicit transaction states, and predictable recovery. It also gives the team a stronger story for presenting Smart Web Pay as a service ecosystem across stakeholder, marketing, and communication contexts.
The core lesson is blunt: parking payment is never just a payment screen. Pricing, timing, availability, navigation, and technical reliability have to behave as one experience.
The first gesture
LET'S MAKESOMETHING FELT.