# data[].attributes.body
- from customers view
- how to manage detailed expectation from customer perspective (for our products and OBE)
- Reactions times (panic mode)

# data[].attributes.body
- Created manny tracking boards which helped us to see the rollout process
-  Communication in the end of the project was fast and we had a better understanding who does what
-Created a BPO board to react on issues, first time we had a central issue management

# data[].attributes.body
-  Product available mostly on time for key decision mile stones
- Benefits for other countries while working towards the US goal (UK)
- structured issue management

# data[].attributes.body
- Setup of people (ProdOps - PSM - PO) works in general
- Transparent communication from PSM as "customers voice"
- Good prio on bugs and improvements in meetings
- We matched Deadlines

# data[].attributes.body
- High level of product attention
- Fast turnaround for product requests
- Getting closer to true US readiness of product (loyalty, net display)
- Good collaboration among team members
- BPO Board management

# data[].attributes.body
On time delivery
No customer complaints

# data[].attributes.headline
Benedikt   Huge testing and bug fixing phase

# data[].attributes.subject
Benedikt   Huge testing and bug fixing phase

# data[].attributes.body
- Central documentation was missing and it was not allways clear when to do what, timelines often where not communicated early enough
- Documentation for the plattforms where missing and we had a huge effort to create them

# data[].attributes.headline
Communication between PO/PSM and GAM could be more efficient

# data[].attributes.subject
Communication between PO/PSM and GAM could be more efficient

# data[].attributes.body
Beta Testing phase with Client users not well organized
(TripLink)
Client/Customer expectations not set correctly
Team disappointed due to low acceptance on customer side

# data[].attributes.body
- Too much manual testing
- Difficulty/Lack of understanding of issues (e.g. net display, labelling)
- SIngle product deliveries become go-live critical
- Lack of understanding of local requirements
- Overall product development too driven by specific customer requests
- Lack of automated alerts
- Not always speaking with the same voice as the OBE

# data[].attributes.body
- Late hands-on to the product at customer
- Setup and configuration (PSM)
- Late clear final requirement to target setup (e.g. Triplink)
- Rollout date movements
- The reals user is "more far away now"

# data[].attributes.body
- Customer called us out on foreseeable items
- Lack of standardised documentation

# data[].attributes.body
- Internal communication is key for a fast rollout
- The earlier the product team has the requirements the easyer it is to work on topics
- Clear communication if things are possible in time helped us to forward a clear vision to the customer
- Changing the scope is better than changing the release dates, at least for Siemens it seems.
- Central documentation for FAQ's is needed and has to be updated

# data[].attributes.body
- require better roll out management

# data[].attributes.body
- Products and communications need to be plug-and-play
- Need standard format for collaboration
- Transparency re time lines (customer and product)
- Regional collaboration (exchange of materials)

# data[].attributes.body
- We can not make it perfect upfront
- Documentation of decisions and status are important

# data[].attributes.body
Thanks to Christian close alignment with customer and intense testing, with immediate feedback and short reaction time from PD team. "Agile":-)

# data[].attributes.body
- Late OBE testing on test account
- Problems and bugs last minute

# data[].attributes.body
Customer expectation most of the time higher, due to experience with other Apps.
No reporting available yet.

# data[].attributes.body
Be better prepared (e2e) from product via communication to continuous optimization

# data[].attributes.body
Christian und Sebastian haben (mir) den Kunden vom Hals gehalten

# data[].attributes.body
- New features and based on customer feedback
- Product quality checks before go-live
- Keep and improve quality

# data[].attributes.body
rollout and product itself
need for standard process (internal)

# data[].attributes.body
- We finished something but it's not used!?
- Reporting

# data[].attributes.body
- Sales -> Account Management "Framing"
- Mehr Informationen zum richtigen Zeitpunkt
- Vertragsdetails
- Reality check

# data[].attributes.body
- Selbstbewusste Kommunikation und pro aktive Empfehlung von HRS  an den Kunde für unsere Lösungen (verhindern den Kunden nach der Lösung zu fragen) + User Dokumentation proaktiv
@Jochen, Christian

- Sicherstellung der richtigen Prio by BPO customer in PD/IT Portfolio Prozess
@Sebastian, Christian

- Prozess für Produkt Marketing für Fortschritte und neue Features (Kunden und nicht Kundenspezifisch)
@Michael

# data[].attributes.body
- Ensure general service and feature quality in product. Microservice monitoring complete?
@Hendrik

- Dokumentation von "known issues". Generelle Probleme unsere connects und services, die wir aktuell "akzeptieren" mittelfristig aber angehen sollten. Proaktive Kommunikation und Lösungsstrategie in der Kundenkommunikation
@Hendrik

- Product is in charge to test and provide test setup before roll-out (as equal to real production as possible). Ensure all dependencies like test / demo OBE clients are avaialble for pre release testing
@Jochen, Michael

# data[].attributes.body
- PSM testedt(soll?)
- Trend positiv
-  SLAs für spezielle topics

# data[].attributes.body
- Needed call and should be continued.
- After we are trough we directly should plan the next meeting for the first action points!
Thx for your preparation @Michael

# data[].attributes.body
- I think this was very helpful
- Challenge will be to find the resources for the required follow-up
- Maybe we can also talk abouy

# data[].attributes.body
3 Topics -
Activation / roll-out of a service for existing customer

BPO - Rollout complete

Product & Service Scale and roll-out

# data[].attributes.body
-  Product documentation
@Sebastian & Christian
Create high level skeleton / framework of required documentation for customer (General description, FAQ, things you should know)
(Vorbild Sonja?)

# data[].attributes.body
BPO Cockpit is the solution