Several years ago SCN superhero Marilyn Pratt conceived of a working group of community members who had a formal consultation role with the SCN program. Thus was formed the original Strategic Advisory Council (SAC), community members who committed to work closely with SAP to shape the direction of SCN. The SAC remains in place today, but to be frank, we haven’t done a good enough job listening to the members or building clear processes to enable them to more closely drive our priorities and deliverables.
At the last SAC call in mid-October (we meet with the SAC monthly) we presented a plan to work even more closely with the SAC on prioritization decisions for the SAP Community platform, and that effort is taking shape quickly. We plan to build clearer processes for testing as well: While we invite SAC members to help test and give input on significant new features, and SAC members were also invited recently to participate in formal testing of a new prototype design for the community for instance, we need to do more to formalize our testing processes with the SAC. (I’ll provide some more details about that aforementioned prototype testing and our testing efforts overall in another blog post coming soon.)
Who belongs to the Strategic Advisory Council? Today the SAC represents a variety of very experienced community member roles and constituents. Some are SAP employees who use the community regularly to share insight and answer community member questions, but most are external to SAP, working for customers, partners or independently in the SAP ecosystem. Many are Mentors; most are also moderators in the community.
Here is the current list of SAC members so you know who is representing you in these conversations.