One thing that drives me bonkers about tech culture is teaching designers that the bureaucracy is more important than the output — journey maps, documentation, multiple iterations, user research etc etc. All of these are fine tools but the goal is a good product and you can spend months producing mountains of all these design artifacts and still end up with junk.
=> More informations about this toot | More toots from fonts@sfba.social
@fonts Certainly, designprocesses in tech have very much adapted to the corporate way to do things, incorporating the dynamics and operations of those companies. Products in this context are (99%?) not the goal, but means to increase revenue for investors and shareholders. Thus design has to follow “their mode” of operation.
Designgoal=working product is one common perspective – but it can and should also serve as a tool for better investigating relationships within complexity.
=> More informations about this toot | More toots from kainiephaus@mastodon.social
text/geminiThis content has been proxied by September (3851b).