Good systems architecture is crucially important - which is why it should only be done by people who know they can get called at 3AM when it all goes hatstand.<p>Not the sorts who wave their hands and draw nonsense diagrams on a whiteboard and chuck something that <i>cannot work, ever</i> over the fence to the implementation team and blame their skills when the project fails.