Welcome to Leading by Design!

A blueprint for career strategies in product design leadership

⏰ Today in 5 Minutes or Less

How do you balance high-level design with engineering reality? This week, Ajay Thakur (Chief Information Officer at Movius and former Head of Cognitive Computing and Staff Engineer at Uber) shares a deep dive into bridging the gap between aesthetic vision and technical feasibility.

The Evolution of the Technical Product Designer

As design leaders, we often focus on "user delight" and "user journey." However, in the high-stakes world of global scale, think Uber-level complexity, delight, and a golden path journey without feasibility will stall.

If you’ve ever had a vision stalled because "the API doesn't support it" or "the bandwidth costs are too high," you’ve hit the technical wall. To lead modern product design teams effectively, moving beyond the "design specification handoff" culture is essential.

Empowering creative teams to learn about the technical levers that determine whether a product succeeds or fails in production is a step toward increasing the department’s return on investment (ROI) for the business it serves.

In a featured interview from my book, Leading by Design, Ajay offers an invaluable perspective on the synergy between our disciplines, arguing that the next generation of product designers looks beyond the interface to understand the "machinery" that brings their visions to life.

The Designer’s New Toolkit: Technical Empathy

Ajay’s philosophy is rooted in technical empathy. At Uber, where real-time data is the heartbeat of the app, he views designers as vital partners when they possess a deep understanding of the system's constraints.

For Ajay, the "magic" of a customer experience is actually the result of rigorous negotiation between design ambition and engineering reality. When designers understand the "Why" behind a technical "No," they can pivot to a "How" that actually works.

3 Key Ideas to Mastering Technical Design

Using Ajay’s insights, here are three ways you can lead your team toward technical fluency:

1. Map the "Data Journey" Before the User Journey

Ajay emphasizes data availability. In real-time apps, if data is slow or inaccessible, your design fails.

• The Approach: Don't just design the "happy path." Ask your engineers: "What is the fallback state if this API call takes longer than two seconds?" or "Do we actually have access to this user data in real-time?" Designing for data latency is just as important as creating the user interface (UI).

2. Design for "Minimal-Regret" (The Agile Mindset)

Ajay favors the Agile Manifesto for its speed and "minimal-regret" delivery. He argues that "less is more" often leads to better outcomes and stability.

• The Approach: Challenge your team to identify the "heaviest" part of their design. If a feature requires a custom API or excessive network bandwidth, ask whether there is a way to achieve the same user goal using existing components or proven frameworks. This reduces friction and speeds up velocity.

3. Transition from Mockups to "Technical Logic."

Ajay highlights the importance of interaction flowcharts and documenting the "Why" behind choices. With the rise of AI, the gap between design and code is shrinking.

• The Approach: Encourage your designers to think in logic, not just layouts. As AI-powered interfaces begin to anticipate user needs, designers will be defining the rules and predictions the UI should make. A designer who can write a working prototype or prompt an AI to generate functional code is no longer just a "design" partner; they are a technical design lead.

The Future: Designer-Developer Synergy

When AI can turn a single engineer into a team of hundreds, designers don't become less relevant; their technical literacy becomes the differentiator. By bridging the gap between design and code, we move toward a future where designers aren't just drawing interfaces, but directing AI-driven logic and producing functional prototypes.

But what, if anything, is holding you back? Samira Rahimi, Head of Platform Experiences Design at Uber, hits the nail on the head in her article “The Parts of Your Job AI Should Absolutely Steal.” She asks: “What stops designers—tools, or fear?”

If you’re leading a design team today, the hard part isn’t the tools; it’s the mindset. For years, designers were taught that the "machinery" wasn't their job. That legacy is the real blocker. To move forward, we have to normalize technical experimentation, making it low-risk and, eventually, a core part of the creative process.

Your Challenge: Confront the "Technical Wall"

Overcoming the fear starts with a conversation. Ajay Thakur identified his top three constraints as API limitations, bandwidth, and data availability.

What are yours?

Does your team have a framework for discussing these technical levers, or do you hit a "wall" every time you move from Figma to production? Leave a comment and let me know how you are encouraging your team to move beyond pixels and into the code.

The full interview with Ajay Thakur, along with insights from many other design and tech executives, is available in the book, Leading by Design: The Insider's Handbook for Tech Leadership, on Amazon.

That's it for this week!

PS: Would you like to receive more leadership strategies?

Here are a few ways I can support you:

• Schedule a free coaching strategy call

• Buy or gift my book 

• Subscribe to this Newsletter