The User’s Goals Should Be Your Design Answers
That new plugin is pretty cool, but no one is going to see it. That CSS3 animation you made is neat, but all your visitors are using IE7. That’s a great responsive design, but you ate up production time with something no one is going to see. Now, I’m not saying there isn’t a place for these things in our projects (especially in regards to responsive development), they are the innovations that keep our designs fresh and fun, but they should always answer the question, “Is this going to solve the problem in the best way?”.
Let’s get back to what our service is really about – being the solution to our customer’s problem. In our case the customer is usually our client’s customers. Our clients specialize in their fields and they want to offer their services as a solution. Our job is to facilitate this.
It’s really a mindset to keep throughout the developmental process from first sketch to production. Making a website design and search engine optimization work should be collected with a client’s goals in mindThe data collected from analytics, heat maps, and market research should be reviewed with the client’s service in mind. You must understand the problem, and once you can break it down into its simplest terms, you can then deliver an answer in the same respect. These answers become your project’s goals and they should be revisited often with the development team to ensure the project stays on task. Without this, projects can suffer from bloated features and scope creep. Terrifying.
Be sure the features you add are there to assist the user in finding their solutions in the most succinct way possible. Let’s make informed, data-driven decisions and make the internet a little better of a place.