OK, the call is over but the recordings are available here:
English version: https://sap.emea.pgiconnect.com/p9ej5um4nih/
German version: https://sap.emea.pgiconnect.com/p1zm6gbdym8/
Agenda:
- Influencing via Customer Connection
- Focus Topic project timeline & scope
- Process & Tools
And the link to the presentations slide deck: https://cw.sdn.sap.com/cw/docs/DOC-153538
Next step: Collect Requirements
We will be collecting requirements here https://cw.sdn.sap.com/cw/community/influence/cc/nwbc : till 28th March.
Final call (more details nearer the time): 21st March.
After that, we will select the most popular, and most feasible, requirements for implementation.
We hope to offer some form of test or evaluation of the next major release before the final release to customers - also, more details on that later, if it proves feasible. However, this is some months in future.
Submitting / subscribing to proposals: DOs and DON'Ts
Several of you have submitted and subscribed already - this is great for us. A few hints to optimize the process, and make sure the most popular requests make it to the selection stage:
1. DO SUBSCRIBE, DON'T VOTE
Sorry about the garish fonts, but "Vote" is obsolete - it will be removed as soon as possible. The only thing that counts is the number of subscriptions.
Your proposal must collect 5 subscriptions to be considered for selection.
2. DO SUBSCRIBE TO YOUR OWN SUBMISSION.
This is standard practice, is not frowned upon at all, and it increases the probability that your proposal is considered for selection.
3. DO SEARCH FIRST, *THEN* POST 😉
It is great to see so many proposals so quickly after the call. And it's probably good (for you and us) that many of you are fairly closely aligned. However, it would be a shame to split the vote for a potentially popular proposal.
As damean-bf.chenhas pointed out, customers cannot delete proposals. Sorry about that. However, if you (the proposer) let me know that you want your own proposal deleted (because you are subscribing to / commenting on a similar request above), I will delete it.
Conversely, if I see two similar-looking proposals , I will add "Flagged for Deletion" or similar in the Comments, and add a link to the alternative.
IMPORTANT: If it is your proposal - PLEASE - let me know as soon as possible that you accept the deletion. I do not want to delete proposals against the owner's wishes.
4. DO CREATE ONE PROPOSAL FOR EACH FEATURE
I can see why it is appealing to bundle similar features together. However, we don't then know who exactly is subscribing to what. So please keep each improvement proposal separate. Thanks.
Background Information
To structure the feedback we get from customers, we at SAP run the Customer Connection program. Customer Connection is directed at incrementally enhancing and improving products in mainstream maintenance. It offers you as customers the opportunity to suggest small enhancements and improvements to those products (“Improvement Requests”). The Improvement Requests selected for development will be delivered as part of our next major release (provisionally for Q4, 2014). This quarter, NWBC has been selected as a focus topic for Customer Connection.
See here for our page for Customer Connection: NWBC.
If you are interested in getting to know more details about the program in general, please visit our collaboration site: Customer Influence. Here you will find presentations and videos explaining the goals and process in detail.
For a list of user groups, please see SAP Service Marketplace - Regional Information and user groups.
AND FINALLY...
Thanks a lot to all of you who took part and/or submitted to the page. You have vindicated our decision already.
Best wishes,
Julie.
