What's the point of 2 web design routes?
Out of context: Reply #12
- Started
- Last post
- 17 Responses
- kelpie0
in my experience this is just a default requirement of new business. Clients expect the options and a designer's dreams of The One True Route are fantasy. Functionality and structure wise, (again in my exp) this is set in the functional specification, so the routes are aesthetic alternatives only. Although this is essentially daft from our point of view, I can't help thinking that the ego issue I described above is utterly matched by any designer who believes they are able to provide the perfect look for their client in a single shot in normal circumstances. Clients are humans and like choice and options, and sometimes simply aren't into the same stuff as you. Good on ye if you have the resource to have separate teams working on concepts for a single job too. That sounds nice, like.
- I think that you can argue that functionality needs to align with user requirement - but you can also argue the same about aesthetics. Any design choice should be able to be backed up with a rationale.********
- aesthetics. Any design choice should be able to be backed up with a rationale.********
- clearly, which leaves you the routes that adhere to all possible rationale to choose from.kelpie
- I think that you can argue that functionality needs to align with user requirement - but you can also argue the same about aesthetics. Any design choice should be able to be backed up with a rationale.