Don't shoot the messenger
The biggest problem is nobody wants to spend the money up front during the design phase and get all of the "relvant" subject matter experts in to do the design.
Just because I'm an Application specific technical architect with a bit of HW knowledge it does not mean I can architect and entire landscape, from storage, servers, networks to resliant DR fabric.
I can scream all I like "I need a storage Architect so work on the Array architecture", all you get is.
Sorry no budget. So out comes the "white paper" and if you can find it the latest manual.
Can I try things out whilst I'm designing.
"No you're an Architect, you're not allowed to actually touch anything, only the engineers"
Alas the Engineers are all stuck in the far east and have never seen the latest and greatest piece of kit that was ordered. They also want step by step instructions on how to configure the beast, just giving them a rule on what needs to be configured is not enough. If they had their way they'd have the architect writing every single command step by step so if it goes wrong it's not their fault.