Stop 11 · Collaboration & Developer HandoffTopics · 2/8

Working With Engineers

In short

Engineers turn your frames into a real product. Bring them in early and they'll warn you about hard parts, suggest cheaper ideas and build it closer to your design.

Understanding basic technical constraints (what's easy versus hard to build) and involving engineers early, rather than treating handoff as a one-way delivery of a finished design.

The jaadu in a hard hat looks at a rolled-out blueprint with a builder at a construction site.

Think of it like this

The architect and the mistri

A smart architect walks the site with the mistri before finalising plans. The mistri says 'this beam won't hold that balcony' or 'this tile will crack here'. Fixing it on paper is cheap. Fixing it after construction is not.

Watch it happen

Where engineers should join in

Kickoff

Sketches

Final design

Build

1/5Kickoff: an engineer hears the problem with you. They may already know a data or API limit.

The big ideas

What you need to know

Early and often

Short check-ins at every stage beat one big handoff at the end.

Ask about effort

'Is this hard to build?' is a fair question. A small tweak might save days.

Learn the basics

Knowing a bit of HTML, CSS and how APIs work helps you design things that can be built.

Same team

You both want a great product. Treat technical limits as design constraints, not obstacles.

Save yourself the pain

Common mistakes

Oops

Showing engineers the design for the first time at handoff.

Do this instead

Share rough work early. Their feedback is cheapest before anything is polished.

Oops

Getting annoyed when engineers question a design.

Do this instead

Explain the user reason behind it, and listen to theirs. Often a third option is better than both.

Your mission

Talk to a developer

~30 min

Quick check

When is engineer feedback cheapest to act on?

Go deeper

1Ask an engineer what makes a design easy versus difficult to implement.
2Practice presenting a design's intent and flexibility, not just a rigid final pixel spec.
3Learn to be open to a technical constraint reshaping a design, without losing the core user goal.