Hadoop and SAS?
I recently read short blog post from Mike Ames @ SAS about the possibility of development within SAS to leverage Hadoop.
I can tell you that a number of digital marketing projects we've worked on in the last couple of years have all tackled their version of big, real-time data problems. Hadoop is one of many ways to overcome this hurdle.
SAS has its role to play in the digital marketing world as well. No one is better at batch processing to create personal customer experiences.
However, we get creative with database and custom software to make the two work together. We look forward to SAS pushing into big data and real-time in a big way. Stored proc's in SAS are a good start, but just that.
Here is the blog post mentioned above - http://blogs.sas.com/content/datamanagement/2011/08/29/sas-hadoop-and-big-data/
What does that app do? – Clean Abstraction
Here is the scene. 3 development groups within the company all working on inter-related applications. Each group wants to make a name for themselves and get the cool projects from then on. Each one builds their software with marginal rates of success.
Then something else happens. Each one starts to add 'the grey area' to their app. What is 'the grey area'? It's those features that aren't clearly one apps responsibilities. So in an effort to provide great software, the team adds those features. But so do the other teams.
Additionally, those other features also create new problems. Business users aren't clear where to go to perform those 'grey area' tasks. Each unit is telling them to come to their software to do that. Unexpected results are produced by the software because each is going above and beyond their expected roles.
This scenario gets played out in company after company. This scenario is what makes enterprise architecture so important.
As a solutions designer, it is critical that the roles and responsibilities
for each piece of software be laid out as clearly as possible. Does that
mean 900 pages of requirements? NO!
It's means setting a clear mission for the software with clear integration points. It means collaboration between teams. It means less
competition between teams.
Clean Abstraction is a design goal for marketing systems. It means efficient development (no wasted time on redundant features). It
means clear business value. It means modular software that is
reused and reintegrated instead of rebuilt.
If you are building marketing systems / software from scratch or off the shelf, focus on clean abstraction. Marketing changes too quickly to waste development time on unwanted, or unnecessary features.
4 tips for integrating CRM technology
If you have worked with marketing technologies for any length of time, you've encountered this problem. How can we integrate our CRM with the rest of our organization? How does CRM interact with our call center, website, applications, database, loyalty system, etc., etc.
We've been there.
Throughout our travels, we've picked up a few tips. Hopefully they'll help you.
- Tight integration is dangerous. Just don't do it. - Marketing technology changes faster than fashion. Today's latest and greatest is quickly replaced with tomorrow's new market maker.
- Integrate through marketing concepts not technical application specs. - Abstracting technologies through the use marketing concepts like 'campaign', 'offer', 'contact history', 'registration', 'enrollment', etc. Define what these mean for the organization and build a data structure flexible enough for all applications to contribute to those concepts.
- Databases and services are the lifeline. - Long term success hinges on ease of use and flexibility. Simple services allow for plug and play scenarios. Well designed databases create environments that record interrelated transactions based on their role or concept. This makes business people happy. They can measure, analyze and predict without spending precious hours compiling, cleaning, and organizing data.
- Think replaceable. - Always remember that what you are adding to your technology stack could be replaced in a year and you will need to re-integrate something else. How much of your current work will be thrown away? Minimize the one-time development and maximize your efficiency and cost savings to the organization over the long haul.
We like to think we aren't integrating technology. We are simply making all of our applications play nicely together.
There is much more to this topic, but these 4 tips can minimize your stress for ears to come.