Category: site goals

It’s end of Week 3 and some more homework submitted. Yesterday in class, we discussed previous homework’s and the importance of quantitative data the will you, as a web designer/developer would use to measure your progress toward the “Smart” goal. As Adam pointed, it may not matter that much if  it’s your own website, but it does with a client. Where I am concerned, I always presumed this would be a definite time-line. You I did put some thought in it and yes quantitative goals such as”40 people to fill request form” or say, “A certain now of hits or views on a specific page in the website” could classify as quantitative data and you would need to define or help the client focus on these quantitative goals rather than just time-line.

This week was drawing some navigational site diagrams and charting out the functional requirements of the website work flow. A navigational site-map outlines the flow that a user might take in navigating through your website. I had fun playing with the newest trial version of Microsoft Visio. I have used it before but the current version always makes it easier and I figured there’s no better time to try it than now 🙂 I looked up for more information – a helpful article.

The other document was the Functional Requirements/Feature Plan document. The idea of developing this one is that another web professional who could understand the needs well enough to build the functionality with almost no additional information. I did get down to some detail on this one and yes, took a lot of my time. On the positive side, it resolved a few issues. It gave me an idea how the site map and requirements go hand in hand. Also I now knew how many pages I really had in the website and how the web pages linked to one another. I also chalked out some wireframe diagrams  on what I really needed constant on the template,  in terms of content on each page.

Here are a few other links I have been reading: ( Craigslist CEO blog….interesting!) (An interesting approach on social media)

I created  a separate post for these two topics as I intend to elaborate even further. The first few stages  (if you adhere to the six stage process) are a little tedious, you find yourself generating a lot of information wondering whether it will ever come to good use. I did it anyway.

Adam did pass on a sample website time-line but since I am reading Web Redesign 2.0/Workflow that works I really enjoyed the section, “Creating Schedules”. Interestingly, they made an overview schedule as well as a detailed one. I now understand why. The overview helps you to break the schedule into months (if longer) or weeks. The detailed one becomes a concise day-to day list of action items — as quoted in the book. Here it becomes important to keep track of scheduled date and the actual date when it was completed.

The other topic – Why goals now? Did we not just complete a preliminary questionnaire where most things come out clear? What if goals change?
Defining your goals is important. One of the reasons is you as a web designer/developer could have a different goal than your client and you may not even know it. Putting your goals and getting client feedback on these goal definitions will give you a clear blueprint on feasible and valid goals. How you can help the client facilitate and support the goal (or to what extent) is important and the link gives  a good idea what these  smart goals have to be:

The acronym S.M.A.R.T. outlines the set of criteria that your goal must follow in order for it to be a well-focused and achievable goal. That set of criteria is:

Specific: Do you know exactly what you want to accomplish with all the details?

Measurable: Are you able to assess your progress?

Attainable: Is your goal within your reach given your current situation?

Relevant: Is your goal relevant towards your purpose in life?

Time-Sensitive: What is the deadline for completing your goal?

It also is a good idea to create a priority list for which goals you want to achieve.