Building analytics communities across the enterprise

by Alex Pamatat, IT Solutions Manager for Advanced Analytics, NXP Semiconductors

Solving problems with JMP is fun. I still remember the days where I played the role of a data and analytics practitioner in manufacturing, solving highly visible, technical engineering problems with JMP. JMP provided a toolkit which allowed me to “punch up” as an engineer, way beyond my class. I was certain there were others in my company who were also excited about the application of JMP to solve complex technical issues, but who were they? Where were they? And who were the subject matter experts and power users to whom I could turn for mentorship?

My somewhat recent transition into NXP’s IT organization as the Solutions Manager for Advanced Analytics forced me to define the who, what and where of our community of more than 1,600 JMP users. We’ve always maintained strict management of JMP licenses, but we didn’t use the licensee data to the fullest. The data was ripe to be transformed into a JMP Customer Relationship Management (CRM) tool, of sorts. Such a tool enriches a simple end-user licensee list to include the user’s site, city and country work location; their reporting chain all the way to the CEO; their business domain name and function; and how often and when they last used JMP. 

I was certain there were others in my company who were also excited about the application of JMP to solve complex technical issues, but who were they? Where were they? And who were the subject matter experts and power users to whom I could turn for mentorship?

We’re also looking into additional data enrichments from our Learning Management System to provide more insight on training patterns and opportunities. Technical experts at JMP have always enabled our JMP communities, but until recently we’d not personalized the training approach to maximize the total value of our strategic partnership.

By first building a CRM for JMP, we can now turn our focus to building communities of analytic excellence across our large enterprise.

What are the benefits? Here is the short list:

Measuring and identifying JMP user growth: Where are recent pockets of growth by country and work site? Which teams and/or organizations are realizing the growth? Who leads these users, and can I work with that person to navigate the politics of garnering support for training and enablement activities that will grow these distributed communities?

Curating the right audience: There’s no shortage of educational resources from JMP, and I find the online webinars particularly useful. We frequently review the schedule of upcoming JMP webinars, then identify the JMP users by work functions or domains who might be interested in the topics. From there we generate personalized email invitations to the event.

Maximizing investments: Where are JMP licenses going unused? How do we create targeted marketing to help those sites that could be putting JMP licenses to better use? We’ll often collaborate with JMP to deliver a JMP Day event or specialized workshop for these audiencesto demonstrate the value of JMP, and these events always generate an immediate demand for the software.

Speaking the same language: There are always competing resources in a large enterprise, and sooner or later your analytics tools of choice may be cost reduction targets. Help subvert the ugly business of cost reductions by creating a strong common voice for your community to fend off these budget constraints.

You could be the linchpin that connects various JMP communities across your enterprise for the sake of collaboration, professional networking, a strong common voice and technical excellence. Before you leave all that glory on the table, give your JMP community the option to stand upand be counted!

JMP Foreword


Let's stay connected! Opt-in.

You may contact me by email regarding news, events and offers from JMP. I understand I can withdraw my consent at any time.

*
*

JMP is a division of SAS Institute Inc. Your information will be handled in accordance with the SAS Privacy Statement.

 
 

Back to Top