Showing posts with label Michael Dodd. Show all posts
Showing posts with label Michael Dodd. Show all posts

Wednesday, September 30, 2009

To Tweet or not to Tweet: Can Social Networking Channels Enhance or Hinder you CRM Initiative?

 

By Michael Dodd, BroadPoint Consultant

At first I was skeptical of Twitter. From what I read, the term “micro-blogging” seemed to me to be a fancy word for SMS message (even less so, seeing as you cannot exceed 140 characters). When I first started reading about Twitter in the New York Times, the thought of “Tweeting” seemed rather silly and solipsistic, not to mention somewhat unprofessional. However, 5 years ago I felt the same way about the blogging and Instant Messaging. But once these 2 social fads matured, they became an invaluable tool for professional internet communities.

Discussions about integrating Social Networks in Dynamics CRM is not a new concept. If you Wikipedia Social Media, you’ll find that almost anything in an online, user created context can be considered “Social Media” which can be used in a networking context.

And as history will show, it’s the simplest uses of web-based media that makes it into long lasting, mainstream networking channels (Newsgroups, IM, blogs).

So it came as no shock when I discovered that the new addition to the Dynamics CRM Accelerator for Social Networking’s primary focus was on Twitter. My skepticism in the use of Twitter as a CRM worthy social networking tool revolves around the fact that is has a distinct lack of structure. Yet it’s simplicity is undeniably its biggest asset.

So, despite my skepticism (and due in no small part to a recent update to my iPhone’s IM+ application which now includes Twitter integration) I decided to kick the tires. After all, how can I criticize that which I have not yet tried? It seems I have a duty to embrace all new forms of web based media.

Well, it’s been 2 months since I started using Twitter and I’m still skeptical.

How do you begin to use that information effectively?

Organizations that fit the B2C model probably have the most to benefit.

When used properly, social media can be a targeted approach to getting instant feedback from your clients.

First and foremost, anecdotal data (narrative text), it is subject to interpretation, bias, and inconsistencies. But the nature of Social Media anecdotes presents a number of potential pitfalls when used in the context of CRM:

1.) Visibility and transparency: Your are just as transparent as your clients. Transparency allows for more agile communications, but may also expose aspects of your business that are better handled 1 on 1.

2.) Anecdotal data from a social media source can prove difficult to compile/analyze: Whether verbose or succinct, it is difficult to aggregate Text data and even more difficult to report on it. How would you filter this data and under which CRM entity would it be stored? How will the user be able to relate this data to a pertinent CRM record? How will you organize the wealth of data that comes from LinkedIn discussions or Facebook status updates? Who will maintain this data?

3.) Reliability: Anecdotal data can be skewed by your own personal interpretation. So the key questions when it comes to integrating this data into Dynamics CRM is who will have access to this data and how will it be used? As a business process, who will be responsible for making decisions on such matters?

4.) Inconsistent Updates: Obviously, people using social media feel different things at different times. What they expose in a tweet one day may be recanted the next. Moreover, the nature of social media does not require one to be vigilant in their documentation. I may hate the service at XYZ restaurant and then Tweet about it. But the next day, I may have a splendid experience with XYZ Restaurant, but I have no obligation to update my view point the next time I tweet. How can such "Mood Ring" data prove a reliable source of personal information?

5.) One’s Social Persona is not their Professional Persona: People behave differently in their social life. Some tend to be bolder in what they Tweet than what they would say in person. And they don’t always think in a professional manner when they post on social media site the way they do when they write an email (or a blog article). It’s nice to know the social demeanor of your customer, but is this really going to be useful in a professional setting? Moreover, Is the information divulged in a social context appropriate for your next conversation? Finally, albeit public, would you customer feel comfortable that you’re monitoring their social (internet) life?

6.) Finally, will your company is your engagement in your client’s social media going to be a two-way street? If so, how do you present yourself in such a forum, knowing that you’re also speaking for your company when you speak with your client.

I would take a step back and think hard about using Social Media in your business endeavors. Twitter may not be the best place to gather insight into your clients. While it seems like an clever method of personal business intelligence, you need to consider:

Is it reliable?

Is it appropriate?

Is their significant ROI over traditional intelligence gather (face to face

Some people will take their clients out to lunch or to dinner and have good time, share personal information. But would they really want you to leverage that information in a professional setting? Moreover, how would that person feel about passing that information along to your entire company in CRM? This information could easily be misused by the wrong person.

Potential Challenges:

1.) Whimsical: Sometimes, it takes me up to a half hour to construct a Tweet. Sometimes less than a minute.

2.) Responses and tweet “chains”

3.) Tweets can be hard to analyze: For eg, “AT&T frustrates me to no end”. How would one respond to this tweet? Can we afford to spend the personnel hours to continue to follow this tweeter for more information? What if the user was simply having a bad day and takes it out on AT&T?

4.) Analysis of “soft” data can be subject to interpretation.

5.) What type of algorithm can dictate a meaningful tweet (eg, data that can be acted upon to increase sales, maintain satisfaction, solve an issue, gain insight, find useful suggestions, etc.

6.) Volume can be distracting.

Wednesday, April 8, 2009

Who's your Source on That? Creating Source Control for CRM Customizations


Please meet Michael Dodd, BroadPoint CRM Consultant, he will be posting often to provide insights into CRM and Tips and Tricks for users.

Part 1 of 2: Suggestions for CRM Customization Versioning in Team Development

By Michael Dodd

One of my newest CRM books is called "CRM as a Rapid Development Platform" by David Yack. The book is probably the first CRM 4.0 book that only covers CRM Development. The book's focus is on using MS CRM 4.0 as a platform for Line of Business applications. In doing so, Mr. Yack touches upon some of the pain points experienced with CRM 4.0 Team Development. The top 2 pain points will be the focus of this 2-part blog post:

  1. No Versioning/Source Control in the CRM Entity Customization UI (10 out of a possible 10)
  2. No Intellisense for Client Side (JScript) Coding (9.5 out of a possible 10).

No Versioning/Source Control

This is most evident in developing client side (JScript) code for a given entity, whereby developers can over-write someone's code with their own revisions and publish these changes without ever knowing they were stepping on the other developer's toes. As you may or may not know, this will all change with CRM 5.0, where they have finally departed with the quick-to-deploy, yet “versionless”, customization UI and added a new "Solution Deployment" UI, which will not only include files for Source Control, but native versioning and roll-back features.

I have created my "Top 5 Ways We Can Improve CRM Team Development" below.

1. Do all CRM Customizations & Development on a Shared Environment - This is possible the most obvious yet most ignored step to improving team development. If the client does not have a development environment, we should create a shared virtual environment that everyone can access (and have local access to via diff disks). This would contain all the necessary development tools (CRM, VS, SQL, SRS, Scribe) as well as an instance of Visual SourceSafe.

2. Treat CRM Customization Files as Source Code - First, all CRM Customization should be done against a Blank Solution in Visual Studio. Next, create separate folders for each Entity being customized. Finally, you must keep each Customization.xml file and all supporting JScript (as .js files) for each CRM Entity being customized (and checked into SourceSafe) in the appropriate entity folder. This will allow for some semblance versioning for each CRM Entities, Workflows, Sitemap and ISV configurations. It will also provide (albeit somewhat flawed) roll-back capability.

3. Standardize Naming Conventions for Customization files

4. Have a Scheduled Deployment of CRM Customizations - Whether it is nightly of weekly, developers must be in sync with the team's changes. one of the biggest reasons we step on each other code is because of a lack of organized deployment of code to the "Master" (or Testing/QA) environment. This will also keep "quick changes" from messing up your code

5. Use Descriptive Comments in your JScript Code

Add this

Bookmark and Share