There is nothing more sad to see than a frustrated, misunderstood designer.
One common source of frustration is the “they didn’t build it like this” syndrome, which underlies the basic point I am trying to make in this post.
That is that often design is seen (by designers) as divorced from the build, a deliverable that is separate to the actual production product. A deliverable expressed in the “Design Specification” My point is that the design spec is worthless if it does not get implemented, so your job is not to design things… its to influence and support the process for developing “what gets built” (and in the process make sure what gets built is well designed) Thankfully for me this means I don’t have to spec as much as I once did – great ! But it also means you are often a design facilitator, rather than a design dictator. It means you collaborate with all the stakeholders to define a clear and considered path for delivery, a process that last the duration of the project. The old waterfall “spec and forget” days are dead.
So as the title suggests : the design IS what gets built (not your spec).if your spec is not built its your failure at engaging, communicating & understanding the job.
p.s. – for a guy who is eternally content and happy, I sure sound angry in this blog. Promise to be upbeat soon