PC-5
Richard Holmes
PC-5InstructionsandChecklist-1-11.docxRunning Header: PC-5 Instructions & Checklist
Process Change (PC) Project
PC-5: Process Improvement Executive Brief
Instructions
Due: 11/28/21, 11:59pm
Individual Assignment
Overview: Advisorpedia
You are part of the Advising Process Improvement Team, which has completed its analysis of the process and identified multiple areas for improvement. You are responsible for implementing “Advisorpedia” – a Self-Help e-advisor modeled after Wikipedia. This will be a system “for students, by students” where students (and related others) can contribute knowledge relevant to the advising process.
Advisorpedia has 7 knowledge areas as described in the table below.
|
Knowledge Area |
Description |
|
Who Directory |
· Listing of advisors, department contacts, and Advisorpedia volunteers · Contact info, specialty, availability · Link to their calendar/booking system |
|
Academic Plans |
· Examples of academic plans for different combinations of majors and minors · Templates for standard majors & minors |
|
How to’s |
· Official description of advising processes · Access to required forms · Form Tracker template (showing steps your form takes to get approved) |
|
How I Did It’s |
· Informal “process” descriptions for how individual students accomplished specific advising goals · Especially helpful when not in CCB |
|
Triage/Escalation |
· How to tell if you are a special case vs. can use a standard process · How to escalate your case when necessary |
|
FAQs |
· Answers to common whats, whys, and other non-How To questions |
|
Change Alerts |
· Breaking news about new/proposed changes that may impact the advising process |
The purpose of Advisorpedia is to collect and share reliable information about the advising process. Its goals are to (1) increase the ability of advisors to handle larger caseloads by reducing the time needed to address simple/routine advising needs, (2) decrease time and frustration for students seeking information on the advising process.
To gain support for your project, you need to prepare an Executive Brief – a short (3 page) document that describes Advisorpedia, presents the rationale for implementing it, and gives examples of the type of content you expect users to contribute.
PC-5 Instructions
Create a 3-page document (extra pages allowed for diagrams or figures), in business format, that addresses the following:
1.0 Introduction
· Provide an overview of the problem
2.0 Advisorpedia (Product Description)
· Overview of what Advisorpedia is
· Description of what it does
· Description of how it will work
3.0 Rationale
· Why/how Advisorpedia will improve the advising process (connect Advisorpedia to the problems discussed in the intro)
4.0 Sample User-Provided Content
· Select two knowledge areas
· one from How to’s or How I did it’s
· one from any of the other 5 areas
· For each selected area, provide sample content.
5.0 Conclusion
· Describe what the future state will look like if Advisorpedia is a complete success
Business Formatting:
Use a business format for your submission. The paragraphs should be in block form (don’t indent the start of the paragraph) with line breaks between paragraphs. You can use the format of these instructions as an example.
The goal is to present the information clearly and concisely, and to make it easy to see important points, so use headers, bullets, bolding, numbers and tables as appropriate to convey your information. (Note: you do NOT have to use all of these).
Structure your report with headers corresponding to the major areas listed above (titles are bolded). The use of these headers means that you don’t need to worry about abrupt transitions between sections – the headers take care of that for you. Remember – the goal of the report is to share information. Professional writing and a good structure will help you do that. Also, remember to cite your sources in text, and include references. Additional formatting & submission requirements are in the checklist on the following page. Use this checklist to ensure you are meeting requirements. This same checklist will be used for peer review and TA grading.
|
Points |
Criteria |
Missing |
Partial |
Good |
Excellent |
|
|
1.0 Introduction |
||||
|
|
a. Describe problem from student perspective |
(0) No reference to student perspective |
(1-3) Minimal or incomplete reference to student perspective |
(4) Correctly identifies and provides some discussion of student perspective |
(5) Offers unique or especially relevant insight and discusses implications for students beyond what was discussed in class |
|
|
b. Describe problem from advisor perspective |
(0) No reference to advisor perspective |
(1-3) Minimal or incomplete reference to advisor perspective |
(4) Correctly identifies and provides some discussion of advisor perspective |
(5) Offers unique or especially relevant insight and discusses implications for advisors. Addresses potential differences in skill levels and knowledge. |
|
|
c. Describe problem from organizational perspective |
(0) No reference to organizational perspective |
(1-3) Minimal or incomplete reference to organizational perspective |
(4) Correctly identifies and provides some discussion of organizational perspective |
(5) Offers unique or especially relevant insight and discusses implications for CCB |
|
|
d. Incorporates quantified data from 11/16 or 11/18 classes or from personal research |
(0) None given |
(1-3) Minimal or incomplete reference to data presented in class |
(4) Uses data from classes to illustrate meaningful points |
(5) Applies data from personal experience or research, beyond what was presented in class, to make meaningful points |
|
|
e. Factually accurate |
(0) Contains numerous errors or questionable claims |
(1-3) Contains a small number of minor errors or unsubstantiated claims |
(4) No obvious errors and all claims are substantiated |
(5) Provides citations/sources for any facts not based on class materials |
|
|
2.0 Product Description of Advisorpedia (A-Pedia) |
||||
|
|
a. Describes Advisorpedia from a Big Picture perspective: “A-Pedia is a ____ that does ____” |
(0) No description of big picture |
(1-7) Basic description that is correct but incomplete |
(8-9) Description that effectively captures “for students, by students” big picture in a clear and concise single statement. |
(10) Offers unique or especially relevant insight from the “big picture” perspective. Goes beyond single statement to provide additional insights. |
|
|
b. Describes A-Pedia from a system perspective. What are major functions the system needs to perform, what components are needed to perform those functions, and how do the elements relate to one another. |
(0) No description of the parts or components of the system |
(1-7) Basic description that is correct but incomplete. Includes, for example, Verifying submitter identity, inputting content via forms for each type of knowledge, search, storing information. |
(8-9) Description that effectively captures the key components of the system. Goes beyond example functions listed in previous column. |
(10) Offers unique or especially relevant insight from a systems perspective. Differentiates between “functions” (what the system does) and the system elements needed to implement those functions. |
|
|
c. Bonus: System-level diagram |
(0) No diagram included |
|
|
(up to +2) Incorporates a block diagram that illustrates the key elements of the system and how they relate. Uses blocks and lines/arrows to show connections. |
|
|
d. Describes A-Pedia from a process perspective (its concept of operations). Explicitly addresses high level view of how information gets into A-Pedia and how users access that information |
(0) No description of the high level process for how A-Pedia will operate |
(1-7) Basic description that is correct but incomplete or uneven in the amount of detail provided. |
(8-9) Description that effectively captures the key steps in the high level process, at an appropriate level of detail. |
(10) Offers unique or especially relevant insight from a process perspective. Process is described at appropriate level of detail with no extraneous information. |
|
|
e. Bonus: High Level process diagram (how the concept will work) |
(0) No diagram included |
|
|
(up to +2) Incorporates diagram that illustrates the highest level “for students, by students” process |
|
|
3.0 Rationale |
||||
|
|
a. Reason(s) why A-Pedia will improve the advising process from the student perspective |
(0) No reasons given |
(1-7) 1-2 Reasons are provided but are incomplete or have some logic issues |
(8-9) 1-2 Reasons provided that are relevant, clear, and supported by discussion |
(10) Offers unique or especially relevant insight based on personal experience or thinking beyond what was discussed in class |
|
|
b. Reason(s) why A-Pedia will improve the advising process from the advisor perspective |
(0) No reasons given |
(1-7) 1-2 Reasons are provided but are incomplete or have some logic issues |
(8-9) 1-2 Reasons provided that are relevant, clear, and supported by discussion |
(10) Offers unique or especially relevant insight. Displays understanding of the challenges faced by advisors. |
|
|
c. Reason(s) why A-Pedia will benefit Carson College at the organizational level |
(0) No reasons given |
(1-7) 1-2 Reasons are provided but are incomplete or have some logic issues |
(8-9) 1-2 Reasons provided that are relevant, clear, and supported by discussion |
(10) Offers unique or especially relevant insight. Connects what is being proposed to issues at the college – and University levels. |
|
|
d. Connects rationale to problems identified in Section 1.0 Introduction |
(0) No connection |
(1-3) Refers to problem but doesn’t provide strong connection |
(4) Connects problem to proposed solution |
(5) Offers unique or especially relevant insight in how the proposed A-Pedia can impact the problems discussed in class and raised in Section 1.0. |
|
|
4.0 Sample User-Provided Content |
||||
|
|
a. Introduction to samples |
(0) No introductory statement provided |
(1-3) Introductory sentence exists but doesn’t provide context for examples |
(4) Introductory statement(s) identify samples and why each was chosen |
(5) Introductory statement(s) provide context (e.g., personal connection, problem encountered) as to why each was chosen |
|
|
b. Present one example of a “How to” or a “How I did it” content |
(0) No example provided for this category |
(1-12) Example is incomplete or misrepresents the category |
(13-14) Example provides information relevant to the category |
(15) Example provides high-value, relevant information, in clear/understandable way. |
|
|
c. Present one example of a “Who” “Academic Plans” “Triage/Escalation” “FAQ”or a “Change Alert” content |
(0) No example provided |
(1-12) Example is incomplete or misrepresents the category |
(13-14) Example provides information relevant to the category |
(15) Example provides high-value, relevant information, in clear/understandable way |
|
|
d. Information accuracy |
(0) Contains numerous errors or questionable claims |
(1-3) Contains a small number of errors or unsubstantiated claims |
(4) No major errors and all claims are substantiated |
(5) Error free, all claims substantiated, and provides citations and sources for any facts not based on class materials |
|
|
5.0 Conclusion |
||||
|
|
a. Describe the future if A-Pedia is successfully implemented |
(0) No future state given |
(1-7) Simply repeats material from elsewhere |
(8-9) Creates clear vision of how the advising process would change for the better if A-Pedia is implemented. |
(10) Synthesizes information from rest of report to create a vision of a desired state that integrates student, advisor, and CCB concerns. |
|
|
b. Wrap-up |
(0) Report cuts off without any ending |
(1-7) Ends abruptly, but intentionally |
(8-9) Smoothly transitions into the end of report. Makes clear statement that project is valuable. |
(10) Strong, clear ending that pulls together whole report. Makes convincing statement that project is valuable. |
|
|
Formatting & Submission |
||||
|
|
Title Block with “PC-5”, Student Name, “class” and due date |
(-1) Missing |
(0) Done correctly |
|
|
|
|
Page numbers – lower left; within page limit |
(-1) Missing |
(0) Done correctly |
|
|
|
|
Running header with student name |
(-1) Missing |
(0) Done correctly |
|
|
|
|
12 pt font/1 inch margins all around |
(-1) Missing |
(0) Done correctly |
|
|
|
|
Filename: “PC-5_studentname |
(-1) Missing |
(0) Done correctly |
|
|
|
|
Word, rtf, or pdf format |
(-1) Missing |
(0) Done correctly |
|
|
|
|
Section headers, as listed above |
(-1) Missing |
(0) Done correctly |
|
|
|
|
References cited in text, listed with enough info to verify source |
(-1) Missing |
(0) Done correctly |
|
|
|
|
Due: 11/28, 11:59pm |
-10% per day applied directly by Canvas |
|
1
