# data[].attributes.headline
Need right and Consistent Client Contact/team engaged from start to finish of a project.

# data[].attributes.subject
Need right and Consistent Client Contact/team engaged from start to finish of a project.

# data[].attributes.body
At XYZ client, XYZ partner had insufficient MB resources - they were too junior

# data[].attributes.headline
Back to Basics on Implementation/Follow already developed process (Anaplan Way) 

# data[].attributes.subject
Back to Basics on Implementation/Follow already developed process (Anaplan Way) 

# data[].attributes.headline
Lack of roles & responsibilities and who owns the success of an implementation

# data[].attributes.subject
Lack of roles & responsibilities and who owns the success of an implementation

# data[].attributes.headline
Documentation for non-English speaking customers

# data[].attributes.subject
Documentation for non-English speaking customers

# data[].attributes.body
The people I spoke to in Japan/France, both stated that they spend a lot of time translating documentation, trainings and support emails for their customers. This effects implementation and adoption.

# data[].attributes.headline
Insufficient bandwidth for BPs and CSDs to monitor implementations effectively

# data[].attributes.subject
Insufficient bandwidth for BPs and CSDs to monitor implementations effectively

# data[].attributes.body
User stories are rush to development or client unwilling to complete user stories. If these are written correctly, could contribute to project creep

# data[].attributes.body
Partners are not incentivized to enable Customers. They may want services revenue or they are against a tight deadline

# data[].attributes.headline
Partners not consistently following the Anaplan Way

# data[].attributes.subject
Partners not consistently following the Anaplan Way

# data[].attributes.headline
Lean too heavily on Agile. Allowing project creep/many changes, having clients add things that a likely not in scope and then expected.

# data[].attributes.subject
Lean too heavily on Agile. Allowing project creep/many changes, having clients add things that a likely not in scope and then expected.

# data[].attributes.headline
Partners are not effectively keeping Anaplan in the loop during implementations

# data[].attributes.subject
Partners are not effectively keeping Anaplan in the loop during implementations

# data[].attributes.body
Several people mentioned that there is not enough emphasis put on making sure a customer in enabled prior to the partner stepping back after implementation.

# data[].attributes.headline
Issues when customers have little bandwidth and only 1 or 2 model builders - - or lack of executive sponsorship. 

# data[].attributes.subject
Issues when customers have little bandwidth and only 1 or 2 model builders - - or lack of executive sponsorship. 

# data[].attributes.body
Sales does not loop in CS early enough. Often sales does not manage Customer expectations and bad-fit partners are selected before CS even gets involved

# data[].attributes.headline
Lack of process around which partners get assigned to deals

# data[].attributes.subject
Lack of process around which partners get assigned to deals

# data[].attributes.headline
Lack of trust or confidence in current adoption score

# data[].attributes.subject
Lack of trust or confidence in current adoption score

# data[].attributes.headline
Partners don't have adequate SIM type resources (just MB or SA)

# data[].attributes.subject
Partners don't have adequate SIM type resources (just MB or SA)

# data[].attributes.headline
Partners are disincentivized to enable customers to drive value on their own

# data[].attributes.subject
Partners are disincentivized to enable customers to drive value on their own

# data[].attributes.body
Can we tie using correct process to bonus/compensation/mbos, etc?

# data[].attributes.headline
Partners may not report issues until late in the implementation phase

# data[].attributes.subject
Partners may not report issues until late in the implementation phase

# data[].attributes.headline
Partners should do a better job of designing a solution, rather than recreating Excel

# data[].attributes.subject
Partners should do a better job of designing a solution, rather than recreating Excel

# data[].attributes.headline
Tools/Templates to get Customer up and running fast

# data[].attributes.subject
Tools/Templates to get Customer up and running fast

# data[].attributes.body
User story templates
Checklists,
Other, etc

# data[].attributes.headline
Internal Staffing to support Implementations

# data[].attributes.subject
Internal Staffing to support Implementations

# data[].attributes.body
Specific to PS org, some think that PS (SA or SIMs) should be involved in all projects, for a min of 5 days for example.

# data[].attributes.headline
Partners not tasked with driving adoption

# data[].attributes.subject
Partners not tasked with driving adoption

# data[].attributes.body
Timing to get project up an running discuss during sales process and CS needs to accommodate.

# data[].attributes.body
BPs feel they are having to go to too many places between Gainsight, Splunk, CPH model in order to track data and its not always aligned.

# data[].attributes.headline
Anaplan Way --- scalable for # account + adapt for Larger Org

# data[].attributes.subject
Anaplan Way --- scalable for # account + adapt for Larger Org

# data[].attributes.body
Current process is geared towards departmental projects, rather than larger strategy of using Anaplan.

# data[].attributes.headline
Better enablement for UX training for Partners

# data[].attributes.subject
Better enablement for UX training for Partners

# data[].attributes.headline
No effective partner performance feedback management platform

# data[].attributes.subject
No effective partner performance feedback management platform

# data[].attributes.body
Each team uses something different depending on the client.

# data[].attributes.headline
No technical documentation left over to support customer technical resources

# data[].attributes.subject
No technical documentation left over to support customer technical resources

# data[].attributes.body
How Partners/CSD's are compensated, take away focus from adoption

# data[].attributes.headline
The art of translating a business requirement to an Anaplan requirement

# data[].attributes.subject
The art of translating a business requirement to an Anaplan requirement

# data[].attributes.headline
Customer success plan - 3 elements (Enablement, Adoption, Enhancements) - quarterly goal setting

# data[].attributes.subject
Customer success plan - 3 elements (Enablement, Adoption, Enhancements) - quarterly goal setting

# data[].attributes.headline
Growth of Ecosystem Can't Keep Up With Demand

# data[].attributes.subject
Growth of Ecosystem Can't Keep Up With Demand

# data[].attributes.body
MB Adoption vs. End User Adoption

# data[].attributes.body
Robert Heintz (CSD)
Traci Gerhart (CSD)
Jean Louise Manalo (BP)
Sree Kanth (PBP)
Dilip Nair (CSD)
Jonathan Pechrus
Ron Woodlock (CSD)
Brad Sisson (PSD)
Kyoko Tadano
Sharon Prior (End User Training, Coaching, Mentoring)
Matt Brady (CSD)
Julian Small
Laurence Di Sotto
Patrick Thomson