The evaluation section of Project 3 may be a little challenging. You are more used to teachers telling you what you have to do for a grade, and I’m asking you to do something of the opposite. This page explains a little more about setting goals for each level of work that you might complete. Note that if the submission is not a Google Drive document, I cannot provide any feedback.
What Goes in the Evaluation Section
The last section of your proposal is supposed to be the following:
- evaluation techniques (p. 289), which outlines three levels of work for Project 4:
- Average Work ( a C project)
- Above-Average Work (a B project)
- Excellent Work (an A project)
In this section of your proposal, you will tell me how to evaluate the work you are proposing to do (that is, the job application materials you will submit as Project 4).
If I were going to work on my LinkedIn profile for Project 4, I might explain something like this in the evaluation section of my proposal:
- Average Work (a C project): clean up my Facebook and Twitter profiles and set up a LinkedIn profile with basic information.
- Above-Average Work (a B project): complete the C project and fill out the LinkedIn profile completely.
- Excellent work (an A project): complete the B project and add an attention-grabbing summary section to the LinkedIn profile as well as arrange the information on the profile so the most important information is in the first screen or two on the page.
If I were going to work on my an online presence and portfolio for Project 4, I might explain something like this in the evaluation section of my proposal:
- Average work (a C project): create a short video portfolio that employers can use to view my on-camera anchor talent.
- Above-average work (a B project): complete the C project and create a website on which to host the video. Use design elements to organize the website.
- Excellent work (an A project): complete the B project and add a resume to the website. Update the resume so that it is current and accurate.
Extra Background Info
It may help if you understand why I’ve been using these leveled descriptions in your assignments, so here’s a little more info. I’ve worked outside the university, doing software development, web design, and content development.
In all the different jobs, when we faced a new task (e.g., create a new website for a special event, or design and develop a piece of software), we came up with a list of things that MUST go into the project (which I think of as average or C work, the minimum). It was the bare bones version of the project, and in many cases, it ended up going out for testing as the beta version.
We also came up with a list of things we’d like to have (above-average, or B level), and things it would be nice to add if we had time (excellent, or A level). My goal has been to get you all to think about those sorts of levels and how they apply in workplace writing.
At the same time, I’m trying to make the grading expectations more transparent. Using rubrics that describe average, above-average, and excellent writing doesn’t always make sense to students. For instance, you might not understand what I mean when I say something like “above average and excellent work uses design elements to increase readability.” To solve that problem, I have tried to translate that idea into concrete actions, like using the level descriptions to say something like, “B work includes relevant photos and uses headings and layout to make the document easier to read.”