Design is often seen as a 'soft skill' that is about an opinion of aesthetics, not hard rules, much less the rigorous logic of code. Yet designers work for years perfecting a craft, not just spouting uninformed ideas. However, being able to explain and articulate the 'method behind the design madness' is not always easy, and rarely quick, which leads to numerous project frustrations. Fortunately, there is usually a way to defuse the tension.

01. I designed it that way for a reason

🧵 2/6 →

The Problem: The designer spends weeks creating meticulously crafted visual comps and spec documents, only to have them seemingly ignored by the developer. Beyond ignoring the specifications, some developers simply allow the browser defaults to stand without change if they are not explicitly stipulated in documentation, not just shown in visual comps.

🧵 3/6 →

The designer assumes that the developer will look closely at the comps and try to make them match 'pixel-perfect'. However, this generally leads to interfaces that feel cramped or poorly organized, despite the best efforts of the designers.

🧵 4/6 →

The Solution: Designers should assume nothing, and know that documentation is never enough. A good design guide is the first step toward eliminating this problem, but designers also need to work side-by-side with the developers, regularly reviewing their work to ensure it's what is intended in a design acceptance review when the developer feels comfortable with what they have done.

🧵 5/6 →