Sorry about this but I have another WordPress whinge. The trigger was yet another conversation today with someone who hired a web programmer who didn’t deliver. They hadn’t delivered on multiple fronts, the design was not what the client expected. They’ve balked at the change in content. (Okay, I get that. Client directed changes should be extra in most cases.) And it’s really late.
The client, to their credit, was blaming themself for some of the missteps, but then I interrupted and asked, “Did they ask you what you wanted your website to do?” “Did they provide a wireframe so you could mutually discuss where the content emphasis should be?” “Did they talk about creating actionable items that lets the site visitor both see that you understand their pain and provide the solution in one click?” “Did they ask if your site was a Destination site or a Confirmation and Credentials website?”
The answers to the above questions were all no. Okay, well that’s not the fault of the customer. That’s the fault of the developer not guiding the customer. A website is viewed by many people as an intimidating technical exercise. Based on the number of people who come to us each month with similar stories it really shocks me that we seem to be the only ones asking these questions. I know that’s not true, but the evidence is there and it truly bothers me.
Okay, so what does that have to do with WordPress? The revelation I have relates to the creation of the wireframe. High-end custom website design includes them as part of the process, but we do them even for our $1000 websites. Why? Because it eliminates the guesswork from building the site the client truly wants. So, why are many WP developers not providing one? I think it’s because they just want to stuff you into one of the standard design frameworks and move on.
WordPress is only economical for the programmer if the customer does not demand more than what the template framework offers. As soon as they go off-book, it can get very expensive. And suddenly WordPress is no longre a cheap solution?
A wireframe opens up possibilities that the WP programmer does not want to provide you. Your Web Department does not use templates or frameworks. Our no-code system can pretty much give you anything the wireframe describes.
So, there you. That’s my theory. Getting railroaded into a WP framework is a lousy way to build a good website. If you want a website and the website builder does not say the word ‘wireframe’ then you should run away.