Do you keep developers away from tasks involving design or the overall look and feel?
Updated by Tiago Araújo [SSW] 11 months ago. See history

❌ Figure: Bad design can be dangerous!
While flexibility is important, particularly when dealing with a low designer-to-developer ratio, it's still wise to keep design work primarily in the hands of designers to maintain consistency and quality.
Streamlining design decisions
Design is an inherently subjective field, and even experienced designers don't always agree on every decision.
In addition, effective design demands a holistic approach, where layout, typography, color, UX, and other essential elements work together to create cohesion. When non-designers, especially those without a strong grasp of these principles, get involved, the result is often disjointed and inconsistent, leading to a fragmented user experience.
This situation is analogous to designers writing code. Many designers may know basic HTML or CSS, or use tools like ChatGPT to generate code. However, without a developer to review and refine it, there’s a higher risk of introducing poor-quality code, which can lead to tech debt. This often results in long-term maintenance challenges and system inefficiencies. Even if a developer steps in to review, it adds unnecessary workload and distracts them from their primary responsibilities.
Note: While developers and designers should focus on their expertise, multidisciplinary Scrum teams offer valuable opportunities for collaboration. By working closely together, they can learn from each other, enhancing teamwork and problem-solving. Ideally, developers should only take on design tasks when training to transition into design roles, or vice versa, as part of structured learning. Otherwise, it's best for designers to handle design and developers to focus on development to ensure quality through specialized expertise.
Categories
Need help?
SSW Consulting has over 30 years of experience developing awesome software solutions.