001
Discover
Problem Framing & Research
Vehicle owners had questions but nowhere built for them — generic forums, scattered reviews, and no direct line to the garages and vendors who could actually help. On the other side, garages and vendors had service quality and trust to prove, but no platform built around their expertise instead of generic listings. Discovery centered on a three-sided problem: owners needed answers and trust signals, garages and vendors needed visibility and credibility, and neither side had a shared space designed for both.
002
Define
Strategy & Roadmap
The core strategic decision was treating Vehiculr as a social platform first, marketplace second — a feed where users post moto-related questions, photos, and problems, with garages and vendors able to respond directly as verified participants, not just as ad listings. I prioritized the posting and engagement layer as the foundation, then layered vendor/garage profiles and a review system on top, so trust could be built through visible interaction before it was built through star ratings alone.
003
Design
UX & System Design
Designed the core feed experience where users post automotive questions and content, and vendors/garages engage directly — answering, commenting, and posting their own listings and ads within the same social space. Built the review system so ratings reflect real service outcomes, giving owners a reliable signal before choosing a garage or vendor, and giving good garages and vendors a way to stand out on reputation rather than ad spend alone. Every flow was designed to keep the platform feeling like a community first — a place people would actually check for moto questions — rather than a directory with a comments section bolted on.
004
Deliver
Sprint Execution & Launch
Managed iterative, sprint-based delivery starting with the core feed and posting experience, then expanding into vendor/garage profiles, listings, and the review system as validated additions. Prioritized keeping the three-sided experience (owners, garages, vendors) balanced at every release — making sure new features served the community layer and the commercial layer together, not one at the expense of the other.
004
(03)
(Portfolio)
© 2026
