Ep 05 Listener questions: Should designers code? Is platformification killing design?

Show notes

Stephen reflects on the early success of the podcast and introduces a new format—episodes shaped by listener questions. This episode is the first “question show,” featuring two insightful questions from Craig Elimeliah, Director of Creative Technology at VML.

Question 1: Should Designers Understand Technology? Should Engineers Be Creative?

The Case for Designers Learning Technology

Stephen strongly believes designers must understand the medium they design for. Comparing it to a chef who knows ingredients but not how to use a stove, he argues that designers must grasp the limitations and possibilities of the technology they work with. Without this knowledge, designs often suffer during execution, getting lost in translation from vision to experience.

He draws from personal experience—coding since the Apple II days, using AppleSoft BASIC, HTML, ActionScript, and even dabbling in Xcode—to highlight the value of knowing how things are built.

Key takeaway: Designers don’t need to be expert coders, but they must understand the form factors and constraints of digital platforms to create experiences that live up to their vision.

How to Inspire Engineers to Be More Creative

Stephen explores the challenge engineers face in traditional setups: when they do flawless work, they’re often invisible. This “only noticed when something breaks” culture diminishes their creative potential.

He champions inclusive collaboration frameworks—like design thinking—as powerful tools to level the playing field and invite everyone to participate meaningfully from the start. These cross-functional teams—designers, UX, engineers, product owners—work together through ideation, problem-solving, and execution.

Core insight: Engineers can be creative if we shift the structure, expectations, and culture to let them be. Give them a seat at the table and encourage shared accountability.

Create a Culture That Embraces Creative Risk

Stephen warns against siloed teams where everyone documents everything just to avoid blame. He argues this stems from bad communication and a fear of failure. To build something innovative, you must accept uncertainty and failure.

In this culture, every role remains accountable for their core discipline (designers for design, engineers for code), but collaboration and feedback are encouraged—without overstepping into each other’s expertise.

Important balance: Empower participation, but respect discipline-specific ownership to avoid chaos.

Understanding the Tools Divide

Stephen discusses a deeper systemic issue: design and engineering tools are still too disconnected. Designers often lack tools that output clean, usable code, and engineers struggle to interpret complex design files like Photoshop or Sketch. Bridging this technical gap is a crucial next step for the industry.

Beyond Craft: Designers and Engineers Must Learn Business

Stephen takes the conversation further: to lead in today’s landscape, creatives and technologists must also understand business. With design and technology influencing strategy at the highest levels, professionals need to evolve beyond their silos.

Advice: Learn the business side. Read design publications and the Harvard Business Review. Broaden your impact by becoming fluent in both craft and commerce.

Question 2: Is Platformification Killing Design?

Designing for Platforms vs. Designing Systems

Craig’s second question asked whether the dominance of platforms (like Facebook, Snapchat, Instagram) is killing design. Stephen acknowledges that we’ve moved away from building bespoke, pixel-perfect experiences toward designing for existing “cities” and systems.

He argues this shift isn’t the death of design, but rather its evolution.

Perspective: Design is becoming more about storytelling and systems thinking—how to communicate clearly and beautifully within constraints you don’t control.

Content Is King (Again)

As platforms control the visual container, the content inside becomes more important than ever. Designers must focus on brand clarity, content quality, and message consistency, even in environments they don’t fully control.

Stephen likens this moment to post-Gutenberg publishing—when content creation became accessible, but the challenge shifted to standing out.

From Static to Dynamic: Designing with Living Systems

Stephen describes how digital design has evolved into creating responsive, modular systems that adapt to various screens, languages, and data. It’s about building resilient frameworks—not static layouts.

But again, the tools lag behind. Designers must manually create dozens of artboards instead of building living prototypes. Prototyping tools (like Framer) are powerful but not accessible to all because of their steep learning curves.

Industry challenge: Design tools must evolve to support dynamic systems in a user-friendly way to meet the new demands of digital product design.

A Call to Action: Participate in the Future of Tools

Stephen encourages designers to be proactive—not passive—in shaping the tools they use. He shares his experience partnering with companies like Adobe to give feedback and help steer development.

Challenge to listeners: If you want better tools or industry practices, don’t just complain. Engage. Contribute. Shape the future.

Conclusion: The Path Forward Is Shared and Evolving

Stephen closes with a message of hope and shared responsibility. The future of design and technology lies in mutual understanding, respect, and growth. Designers and engineers are increasingly interdependent—and both must expand their skills beyond their traditional lanes to succeed.

Listener Engagement and Credits

• Have a question? Email Stephen at ask@stephengates.com.

• Leave a review to help more creatives discover the show.

• Legal note: All views are Stephen’s own and do not represent current or former employers.

Final message: Time is the ultimate luxury. Thank you for spending yours here. Until next time, stay crazy.

Tagged as:
collaboration creative process design and development design creativity design evolution designers learning to code digital design challenges digital platforms impact on design integrating developers inter skill set enhancement user experience