- programmers and managers need to fully embrace design — without "buy-in", designing is futile (as it'll never get implemented properly — or, in many cases, implemented at all)
- design is an iterative process where everyone is involved — not just a designer
- design needs to be present at all stages of the project cycle: before, during, and after
- design isn't just eyecandy; functionality is even more important (text/content is part of design too)
- designers should be treated as full team members, not some add-on
- design issues should have high priority too (if something is unusable or even sometimes looks unusable, then people can't use the software)
- designers are developers too (in fact, anyone who contributes to making software is a developer — not just programmers)
- good software requires design, documentation, project management, community engagement, marketing, etc. — in addition to programming
- a lot of designers are quite tech-savvy, but many aren't — regardless, it's okay to not know everything (especially about programming corner-cases or project-related esoterica)
- think about the people using the software as people using the software, not as "users" (using the term "users" is degrading (similar to "drug 'users'") and sets up an "us-versus-them" mentality)
Last active
August 29, 2015 14:14
-
-
Save garrett/2b92a6a2a894b4ff9b9b to your computer and use it in GitHub Desktop.
what software development teams should know about design
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment