# data[].attributes.headline
Separate Course Shell Requests and mods  from Customization

# data[].attributes.subject
Separate Course Shell Requests and mods  from Customization

# data[].attributes.body
Dedicate resources (similar to small win) to complete the "easy" course shell requests and changes. Asking 18 months for 30 min work that we collectively believe should be done is not reasonable from a customer experience standpoint

# data[].attributes.body
A school has requests that cross 6 grade levels of science courses. The request as a whole is so big that it's a no, but if we broke the work into several years of small wins, we could keep them happy and make a big difference at the end of that time. Right now, requests aren't linked to my understanding

# data[].attributes.headline
Too many cooks in the kitchen - not to be confused with a need/desire for collaboration.  Ex. - The school comes to CSP with a question.  CSP goes to curriculum who provides the info to the IP who provides to CSP and then CSP has to relay that to the school with little to no additional context.  

# data[].attributes.subject
Too many cooks in the kitchen - not to be confused with a need/desire for collaboration.  Ex. - The school comes to CSP with a question.  CSP goes to curriculum who provides the info to the IP who provides to CSP and then CSP has to relay that to the school with little to no additional context.  

# data[].attributes.body
Yes, we acknowledge this is a good idea and we will get to it when we can, but we can't right now.

Yes, can do this in the next year

Yes, we can do this in the next 18 months

...

# data[].attributes.body
Guidelines for what is reasonable to expect teachers to do through customization tools vs being done in courseware

# data[].attributes.body
Differentiating between no-never because it violates our core values/brand identity/etc..., no-not in the next year based on what we see on the horizon, no-check in in three years, no-but this may be a good small win, no-the school needs to solve this locally with IP and CSP support, etc...

# data[].attributes.body
Ability to provide schools a clear understanding of which requests will be completed for the next school year - and provide this information as early as possible, at least before teachers leave for the summer.

# data[].attributes.body
Roadmap - What is the roadmap at any given time and where are we on it? What are our major priorities that determine what capacity we have to provide customization.

# data[].attributes.body
More and better collaboration on the front end to get to a better outcome without wasted duplication of effort

# data[].attributes.body
ADO access (read only) to CSP team to see status of items when schools ask.

# data[].attributes.body
more people or hours in the day to vet requests, ask clarifying questions, queue up the work to be done

# data[].attributes.body
Schools submit requests with a delivery date they need. "Approved" means their request is approved as submitted - including the delivery date. Revisiting the approval at the 11th hour to say it cannot be done by the requested date, or cannot be delivered as outlined in the request is a poor experience for customers.

# data[].attributes.body
Better understanding of what we can give on the front end to allow a proper prioritization decision without having to do more work than necessary, or have to redo the same work as multiple people enter the process after submission

# data[].attributes.body
Automation in the Smartsheet that communicates when a request is complete

# data[].attributes.body
PVS has more than 1 school year lead time for state initiated standards changes and we don't deliver updated courses with instructional planning time for teachers.

# data[].attributes.body
IAs are updated with language that is vague or unclear and isn't helpful for schools trying to understand status of a request.

# data[].attributes.headline
- for course mods in particular - someone who really understands the curriculum and can drill down on teacher requests

# data[].attributes.subject
- for course mods in particular - someone who really understands the curriculum and can drill down on teacher requests

# data[].attributes.body
When it feels like the goal post has moved when the ball is in the air. When we have something we've gotten written approval for and hear something like "Yeah, but it was approved but not committed."

# data[].attributes.body
I think an example of what a "good" request looks like (in each instance) could be helpful to ensure each aspect of what is needed by the teams doing the work is captured to reduce additional questions to schools.

# data[].attributes.body
Schools have a voice in what they need in their courses by being able to request how they want them modified.

# data[].attributes.body
Fewer people and places to communicate

# data[].attributes.headline
For the most part, schools are getting the re-rankings and shells that are being requested. 

# data[].attributes.subject
For the most part, schools are getting the re-rankings and shells that are being requested. 

# data[].attributes.body
The front end of the process is better defined than it has been in the past. There are standard forms for submission.

# data[].attributes.body
Johnica is super responsive and helpful with all my questions.