I've been doing a lot of research on the Web Design Process and finding out how I should implement it properly.
I'm really curious to know what your process is from start to finish.
If anyone is generous enough to share their process can you please include detailed explanation of each step.
I hope to hear from you all.
I just got an email saying someone replied to this thread, why isn't there a reply lol.
For efficient web design first of all to know the what are the requirements for designing the web and structure of the web, then we have to design the web based on our requirements, then implementing the code then testing will be performed on that web if any errors are exist in our project. If any errors are exist then it will be redesigned if not it will be launched in the market. If we are designing the web in this process, it will be finished successfully without any bugs.
That can happen when either someone changes their mind and deletes their own post (which you can do within 30 minutes of posting) or when a moderator decides that a post is spam, irrelevant, meaningless, repeats what has already been said or is in some other way a violation of our policies, and so deletes the post ... but the system can't undo the email that you've already been sent.[/ot]
Different approaches suit different people. But this is my preferred scenario:
- talk with client extensively about what the site requires (content, functionality, aims and goals etc...)
- establish content—text, images etc.
- organize content in an intuitive and logical way
- bases on the content structure, establish a wireframe for the design
- using the wireframe as a guide, establish a design for the site (colors, fonts etc.)
A lot of people come up with a pretty design and then force the content into that, which is not a good way to go, IMHO.
This is my process:
- Get client to send me content, images and any other usefull resources they already have.
- Create a mockup of the website in photoshop
- Get feedback from the client
- If they like the look of the mockup It gets coded up.
- Then we link it to our Content Management System
- Then we work with client to get content and pages done.
Here is our process, it appears to be quite different to replies so far so I'll outline it.
Discuss requirements and goals extensively with client; for us the most important thing is what they are selling and what they want to achieve. By selling this can be a single product, range of products, type of product that they sell; or a service they offer or anything else - not necessarily a tangible product (basically what it is they are doing). Also learn about their company, background and so on.
Perform audience research to get an insight into their customers (or users) common needs, desires and interests. Discover who they are, where they are, what touchpoints they use, what online services (and if relevant offline services) they use.
Using the above, investigate different solutions; leading to the design of a strategy to achieve their goals and a design for any solutions that will be used to achieve the strategy.
Product Development; basically building and testing the solution
If the client pays for it, audience testing to gain pre-release insights which we can use to make changes (this can be during or immediately after development)
We then do performance monitoring, analysis and optimization. By performance meaning penetrative performance.
Obviously in the design stage itself (points 1, 2 and 3), these points are broken down into their own process. Point 3 probably being most relevant to this thread, so I'll break that down a bit; though it varies from project to project as they are all different.
Basically it includes two primary processes; a strategy and then a product design based on the strategy.
This is where we use pre-design investigation to outline the different ways in which we can deliver on their goals, the types of solutions, relevant platforms and so on; and of course the types of results they could expect from such solutions.
Here we perform a process that looks something like this for each solution (though the process can vary depending on what the solution is; so my example is for a website):
Wireframes, flow diagrams and other structural and process designs as appropriate
- Sketches of UI and UX concepts
- Artistic direction (so themes, messages, colors etc.)
- Digital concepts created in say Photoshop, Fireworks and Illustrator
There will be a number of different designs, which we run by the client and advise the client on. There are other things like content design, copyrighting and a host of other things too, but those aspects are all solution dependent.
Then onto production.
I would recommend to think as much as possible and note down all the needs & features then show a wireframe to the client after agreement start the design so if they try to add features afterward you can charge extra otherwise they always change ideas and want what they see from other website
- Meet client and get a full list of requirements including functionality for each page and proposed content (usually they dont have much at this point) - this should include colours they like, the kind of theme they are going for, what pages they want/need/you suggest
- Agree a scope and a timescale, write contracts, set the amount of revisions they can have on designs, get initial payment to ensure their "lock in"
- Generate wireframes based on ideas discussed and proposed content.
- Meet with client to collect content and discuss wireframes
- Design pages
- Sign off/revision process
- Start build
- Sign off/tweak/revision process
- Final payment
This topic is now closed. New replies are no longer allowed.