One tiny megaphone
The scenario: You’ve been hired to do some design work, you’ve submitted the deliverables, and they were accepted. You maybe even got paid. The client later comes back and asks you to change something in a way that you think breaks the design in an unacceptable way. What do you do?
Continue reading “Design bind: Can you make the logo bigger?”
I had a discussion recently with someone about a not entirely uncommon situation consultants can find themselves in. You get hired to solve a problem, but the reason they have hired the work out rather than do it internally is because they aren’t really committed to making the project a success. What do you need to know to best deal with this situation?
Continue reading “Designed to fail: An absence of commitment”
It happens sooner or later to all consulting designers: your client decides not to use your work or — if it’s what they hired you for — take your advice.
Now what?
It’s common in the web and app development industry for stakeholders to make a distinction between “designers” and “developers”. One of the things I’ve noted about this distinction is that it opens the door to antagonistic perceptions and even behaviors between the two camps. At a conference a few years ago, in the presence of developers expressing disparaging views regarding designers, I suggested that, “Designers are developers.” The deafening silence suggested I had to explain what I meant: