# data[].attributes.body
Consistency and maintenance of what our offerings are and making sure that it is accurately reflected on our website, in NetSuite, on scheduling forms and to sales/CSM/PDS teams.

# data[].attributes.headline
Teamwork, Support, Communication, Collaboration. Feel the PD Team is responsive, accommodating, supportive and organized. Positive and wonderful workplace. 

# data[].attributes.subject
Teamwork, Support, Communication, Collaboration. Feel the PD Team is responsive, accommodating, supportive and organized. Positive and wonderful workplace. 

# data[].attributes.body
Scheduling - PDRs, Master Calendar, District Spreadsheet

# data[].attributes.headline
Having more lead time on the ILC BTS Features. 

# data[].attributes.subject
Having more lead time on the ILC BTS Features. 

# data[].attributes.headline
•	Shared resources, demo accounts, easy coverage process. Using follow up email templates from other PDS's, having demo accounts (and/or Figma), and easily finding coverage through the PDOP's team helped a lot this BTS!

# data[].attributes.subject
•	Shared resources, demo accounts, easy coverage process. Using follow up email templates from other PDS's, having demo accounts (and/or Figma), and easily finding coverage through the PDOP's team helped a lot this BTS!

# data[].attributes.headline
Everything is working. Things just need some retrospective tweaking. 

# data[].attributes.subject
Everything is working. Things just need some retrospective tweaking. 

# data[].attributes.headline
•	I have so many that where accounts were not ready, demos really saved the day.  Although, we prefer a customer account be used, most are OK with the demo. Having the Mentimeter Accounts and Increased Demo Accounts have been amazing this BTS season! 

# data[].attributes.subject
•	I have so many that where accounts were not ready, demos really saved the day.  Although, we prefer a customer account be used, most are OK with the demo. Having the Mentimeter Accounts and Increased Demo Accounts have been amazing this BTS season! 

# data[].attributes.headline
I credit the triad teams for the relative ease of this BTS. We definitely want to keep encouraging these relationships and processes! I agree that the PowerBI Onboarding Tracker was also a good addition, but we got it a little late in the game and there were a few things that could be improved on it. (Specifically adding next PD date to the tracker since that info is in the OBR.) I'd love to see it right next to the Target Launch Date. 

# data[].attributes.subject
I credit the triad teams for the relative ease of this BTS. We definitely want to keep encouraging these relationships and processes! I agree that the PowerBI Onboarding Tracker was also a good addition, but we got it a little late in the game and there were a few things that could be improved on it. (Specifically adding next PD date to the tracker since that info is in the OBR.) I'd love to see it right next to the Target Launch Date. 

# data[].attributes.headline
Finally, digging for details about implementation is still so challenging, especially when providing coverage for a session. I would love to see a new tab in NS maybe that was called "Success Plan" that contained at a minimum information about the intended use of the program, grade-levels/populations, etc. I know we talked about a Box folder for Success Plans and that has not been where CSMs can focus right now, but I'm thinking about the info that goes on a quote that populates in the onboarding record (rostering method, login type, contacts, etc.) Could there be a few more fields added that gather the info we need presales? (This is just my Christmas wish.)

# data[].attributes.subject
Finally, digging for details about implementation is still so challenging, especially when providing coverage for a session. I would love to see a new tab in NS maybe that was called "Success Plan" that contained at a minimum information about the intended use of the program, grade-levels/populations, etc. I know we talked about a Box folder for Success Plans and that has not been where CSMs can focus right now, but I'm thinking about the info that goes on a quote that populates in the onboarding record (rostering method, login type, contacts, etc.) Could there be a few more fields added that gather the info we need presales? (This is just my Christmas wish.)

# data[].attributes.body
Having enough PD Specialists to deliver and knowing concretely what they were able to deliver in. Having a built in content expert/support group in PD Operations to support when PD Specialists needed assistance or we needed someone to jump in on a session.

# data[].attributes.headline
Not sure what the wording is on the survey, but could something be added about 1 being the lowest and 5 the highest, etc.?  Many times there are really positive comments, yet the person chose a 1 - and they may be confusing the scale thinking 1 is the highest.                                            

# data[].attributes.subject
Not sure what the wording is on the survey, but could something be added about 1 being the lowest and 5 the highest, etc.?  Many times there are really positive comments, yet the person chose a 1 - and they may be confusing the scale thinking 1 is the highest.                                            

# data[].attributes.body
Lack of CSM Coverage - 1 CSM starting with Twig mid-July

# data[].attributes.headline
•	The PD Scheduling Form. This is fantastic in concept. It needs to be refined with simpler-LIMITED "available" options once basic selection/product is clicked. There are way too many clicks involved. The critical info needs to be at the TOP: Preferred Date and Start Time and a requirement* to put in 2 Alternatives. Also BOLD TOP that  emphasizes date to be 7 business days from Submission. OR Contact their AE. And a submission receipt should be automatic to the contact/email of person listed on submission. IF they have NO PD, handle at the Pdops stage (or send to AE)(at least during BTS). 

# data[].attributes.subject
•	The PD Scheduling Form. This is fantastic in concept. It needs to be refined with simpler-LIMITED "available" options once basic selection/product is clicked. There are way too many clicks involved. The critical info needs to be at the TOP: Preferred Date and Start Time and a requirement* to put in 2 Alternatives. Also BOLD TOP that  emphasizes date to be 7 business days from Submission. OR Contact their AE. And a submission receipt should be automatic to the contact/email of person listed on submission. IF they have NO PD, handle at the Pdops stage (or send to AE)(at least during BTS). 

# data[].attributes.body
The teams have lots of support built in with our structure from PD Solutions/Certifications to Seniors/Regional Directors to PD Content to PD Operations Specialists. There is always someone to help when they are unsure or confused.

# data[].attributes.body
Move through differentiation in a different way in launching, too much info

# data[].attributes.headline
•	NO DEMO ACCOUNTS FOR ILL LEGACY…There will always be a need for these as new teachers join all throughout the year and may not have access set up yet...they would also avoid any onboarding issues. The Figma are fine but not ideal for a PD session

# data[].attributes.subject
•	NO DEMO ACCOUNTS FOR ILL LEGACY…There will always be a need for these as new teachers join all throughout the year and may not have access set up yet...they would also avoid any onboarding issues. The Figma are fine but not ideal for a PD session

# data[].attributes.body
Consistent and frequent changes in Core PD Scheduling. Not one owner of the PD scheduling process. Use of Google form as an intermediary before PDR. Seems to be a disconnect between CSM/Customer/PDS in regards to scheduling logistics. Does the customer ownership model work for Core? Can we take some of Twig's PD Scheduling routines and utilize them in ILC world?

# data[].attributes.body
Edit assessment section of launching to make shorter, too much too fast

# data[].attributes.headline
•	I covered several sessions with no notes or information on the session.  I had to then track down the assigned PDS/CSM to try and get info and often times there wasn't much.  If you are getting coverage for a session, it should be a requirement to put in the notes the district/school PD contact, CSM and AE, rostering and testing method and any other information even if it's "I have no other information." It helps to have everything in one place instead of having to spend time we don't have getting info or contacting the wrong people (this also happened because NS had the wrong info)

# data[].attributes.subject
•	I covered several sessions with no notes or information on the session.  I had to then track down the assigned PDS/CSM to try and get info and often times there wasn't much.  If you are getting coverage for a session, it should be a requirement to put in the notes the district/school PD contact, CSM and AE, rostering and testing method and any other information even if it's "I have no other information." It helps to have everything in one place instead of having to spend time we don't have getting info or contacting the wrong people (this also happened because NS had the wrong info)

# data[].attributes.body
Rebranding all PD content for all products for a cohesive "brand"; Collaboration with PM to get PM updates b/4 products release; Calibrating with team on a consistent development process, tools, materials, etc.; Training PDSs on product releases/PD content before (almost!) PM releases go live

# data[].attributes.headline
•	The launchpad has been crucial for me this BTS season! I think it is extremely convenient, and I have used the Quotes with PD (by sales rep) option more than anything else! Very helpful!

# data[].attributes.subject
•	The launchpad has been crucial for me this BTS season! I think it is extremely convenient, and I have used the Quotes with PD (by sales rep) option more than anything else! Very helpful!

# data[].attributes.body
More time for unstructured exploration of the dashboard

# data[].attributes.body
Twig Purposeful planning website

# data[].attributes.headline
•	Slack is not a great place to share important information. I feel like info gets lost in the threads, and it is too difficult to filter what I need to know RIGHT NOW. Email is far more effective, because I can read/mark unread as needed, and flag for later reading.  Remembering to go back into slack for something is just inefficient.

# data[].attributes.subject
•	Slack is not a great place to share important information. I feel like info gets lost in the threads, and it is too difficult to filter what I need to know RIGHT NOW. Email is far more effective, because I can read/mark unread as needed, and flag for later reading.  Remembering to go back into slack for something is just inefficient.

# data[].attributes.body
Cancelled PD Sessions.

# data[].attributes.body
Issues with scheduling and notifications.

Inconsistencies between the PDOSs and what they are asking for or sending to presenters.

# data[].attributes.headline
•	I would like a place where we can go and get spectacular Follow-up email ideas that then we can tweak for each of our customers. 

# data[].attributes.subject
•	I would like a place where we can go and get spectacular Follow-up email ideas that then we can tweak for each of our customers. 

# data[].attributes.body
Field test PD content early on in development process, release, iterate

# data[].attributes.headline
•	Can we receive PD Form Requests (submission forms) in our Launchpad - perhaps 1 CSV file.  Email gets messy during BTS and would  be so nice to have those form answers in 1 place. FROM INSIDE SALES

# data[].attributes.subject
•	Can we receive PD Form Requests (submission forms) in our Launchpad - perhaps 1 CSV file.  Email gets messy during BTS and would  be so nice to have those form answers in 1 place. FROM INSIDE SALES

# data[].attributes.body
Need more management structure to the Twig PD team

# data[].attributes.body
PM releases all through the BTS season

# data[].attributes.body
Ill-timed.

# data[].attributes.body
Lack of AE involvement, no triad meetings, no information on purchase, hard to get PD quote created - TWIG

# data[].attributes.headline
I know this isn't something we have control over but releasing new features just before/during BTS is a nightmare!  If the content team can budget their time better to get these out between the months of Oct-April it would be smoother for the PDS as well as customers (dawn)

# data[].attributes.subject
I know this isn't something we have control over but releasing new features just before/during BTS is a nightmare!  If the content team can budget their time better to get these out between the months of Oct-April it would be smoother for the PDS as well as customers (dawn)

# data[].attributes.body
Hitting release dates on Twig Middle school

# data[].attributes.body
Accessing staging site for ILC so PDSs & PD Content could dig into releases, so when releases went live , everyone was prepared

# data[].attributes.body
Opportunity to increase collaboration between PD Solutions/Certification and PD Content as well as Seniors.

# data[].attributes.body
Lead PDS Mentor support.

# data[].attributes.body
Fingerpointing instead of problem-solving with the customer as the focus. Often people are too focused on finding out who did something wrong and letting them know.

# data[].attributes.body
The CSMs liked the PD At-A-Glance and 1-pagers in Box. They felt like they were easy to understand and use.

# data[].attributes.body
Susan & Denise bringing Twig into Netsuite

# data[].attributes.headline
Slide Deck Changes (As A Result of Product Changes)

# data[].attributes.subject
Slide Deck Changes (As A Result of Product Changes)

# data[].attributes.body
Difficult for PDS to keep up with most up to date slide decks. How do we avoid having to download daily since it's not sustainable?

# data[].attributes.headline
Gap of knowledge in product implementation

# data[].attributes.subject
Gap of knowledge in product implementation

# data[].attributes.body
PDG Agenda customization
Logistics
Success Plan

Kristen

# data[].attributes.body
Kristen
Better visibility

# data[].attributes.body
Barbara and Kim
field testing

# data[].attributes.body
Barbara and Kristen
Cross-collaboration

# data[].attributes.body
Barbara

# data[].attributes.body
kristin and kim