Email or username:

Password:

Forgot your password?
Top-level
Jens

@hbuchel
I was gonna argue back as a "designer" but the way I see it the core issue with why software projects tend to become lack-lustre is the fictitious bridge between developers and designers (and users) where all involved tries to find a difference between all three so hard they miss that they are constructing it.

A designer who isn't sitting next to the developer is as bad as a developer who isn't sitting next to the designer and both are crap if users aren't sitting at the same table.

3 comments
Jens

@hbuchel Now I lack a formal education as a designer, and maybe somewhere there is a course why designers should alienate developers at some Uni that I missed - but it seems so absurd that designers position is between marketing and developers instead of cooperating between all three.
Its like someone took communication out of design.

(will shut up now but I have SO many opinions on the issues with modern design work flow)

Jens

@hbuchel I lied... I need to keep talking here:
Design is currently seen as a way to create where developers are the lowly mechanics. This is to me the big problem for us designers. We are told that developers are gatekeepers and if they actually just did what we said, things would be grand.
Its total nonsense. A developer and a designer cooperating can make gold out of straw, a siloed modern work flow that we have now makes straw out of gold and tries to find who's to blame.

Jens

@hbuchel Design is at its best finding a way to present a solution to a complex problem to anyone who needs it. The key takeaway isn't to find a situation and design a problem to overcome by creating technical debt for devs to fix so it can be sold as a solution to users.
Its to be part of the innovative chain, not above or below it, but as someone who can be enthused and amazed and enthralled by the shared goal. And be able to communicate it to anyone further down the line. Not with words but--

Go Up