← Back to Innovator Stories
ProductDesignLeadership

The Shift From Building Features to Shaping Experience

It wasn’t a big release. But it changed how the product feels.

4 min read11 Apr 2026, Sat

The Moment

Today felt different. Not because I built something large or complex, but because I started working on features that changed how the product behaves in real use. This release was focused on things like pulling APIs for recommendations, improving preview layers, fixing how flags and locations are displayed, and introducing a proper “Today” view. I also started mapping the entire day’s route - connecting one activity to the next in a way that actually reflects how a day unfolds. Individually, none of these felt like “big features.” But together, they started to change something.

The Tension

The challenge was that these features are subtle. They don’t announce themselves. They don’t feel like major milestones. But they sit right at the point where the product either: - feels static, or - feels alive Pulling in recommendations through APIs was one example. It’s easy to add more data. But the real question is whether those recommendations actually help, or just add noise. The same goes for the Today page. It’s not just another screen. It becomes the moment where the user stops planning and starts experiencing the trip. And mapping the day’s route - it sounds straightforward, but it changes how people perceive time, distance, and effort across the day. These are not hard technical problems. But they are hard decisions.

What I Did and Changed

I shifted how I approached these features. Instead of asking: “Can I build this?” I started asking: “Does this make the experience better?” For recommendations, I focused on making them contextual - tied to what the user is already doing, rather than just showing more options. For the Today page, I treated it as a live layer - something that reflects where the user is in their journey, not just what they planned earlier. For mapping, I ensured that each activity connects meaningfully to the next, so the day feels coherent, not fragmented. And for smaller details - previews, flags, visual cues - I made sure they support understanding quickly, without adding friction.

The Insight

These are not headline features. But they are the ones that change how a product feels. It’s not the big features that make a product feel premium. It’s the small ones - connected together, thoughtfully.

Broad Reflection

There is a shift that happens at some point in building. You move from: - solving problems To: - shaping experiences The difference is subtle, but important. Because once the fundamentals are in place, what matters is no longer whether the system works. It’s whether it feels right to use. And that is where the real work begins.

Related Stories

LeadershipProduct

The Builder’s Shift: When Thinking Turns Into Doing

I thought I was just trying something small. I didn’t expect it to change how I think about building.

4 min read05 Apr 2026, Sun
Read Story →
EngineeringLeadership

Alignment Over Complexity: Why Systems Fail Quietly

Everything was working. Until I realised I couldn’t trust what I was seeing.

4 min read05 Apr 2026, Sun
Read Story →
ProductDesignLeadership

Why Good Products Feel Simple (Even When They’re Not)

We had everything built. And yet, something still felt wrong.

4 min read05 Apr 2026, Sun
Read Story →