1) Do bad customer experiences cause people to switch brands? In a 2011 research project conducted by CX application vendor RightNow, 89% of consumers said that yes, a bad experience has spurred them to switch brands. But in the brand-new study of business-executive perceptions that’s the subject of this column, only 49% of the surveyed executives said yes. QUESTION: What steps do you need to take to close this dangerous perception gap?
2) While 97% of executives say CX is critical to the success of their company, and 91% say they’re committed to making their company a CX leader, only 20% would rate their own CX initiatives as “advanced,” with a dedicated CX leader in place, initial projects pushed to the optimization phase, and the overall project extended to new channels and groups . QUESTION: What are the obstacles preventing you from aligning your actions with your words? If you say it’s a “budget” issue, aren’t you really talking about strategic priorities rather than line items?
3) Most companies have a clear and direct understanding of the looming CX challenge and the powerful interaction of social media. The study found that the top two drivers for CX initiatives are (a) rising expectations from customers (59%), and (b) the impact of social media on customers’ ability to broadcast good and bad experiences (37%).
Now, even if you’re able to somehow rationalize those findings, here’s one that not even the most-accommodating executive can dismiss:
10 Reasons Why CEOs Don't Understand Their Customers - Forbes - 0 views
-
-
4) Being a CX laggard can cost those companies many tens of millions or even hundreds of millions of dollars in lost revenue: executives estimated that the lack of positive, consistent, and brand-relevant customer experience can cause them to lose out on a staggering 20% in annual revenue.
-
Worse yet, all that money’s likely to wind up in the pockets of your competitors!
- ...1 more annotation...
Top Mistakes to Avoid in Analytics Implementations | StatSlice Business Intelligence an... - 0 views
-
Mistake 1. Not putting a strong interdisciplinary team together. It is impossible to put together an analytics platform without understanding the needs of the customers who will use it. Sounds simple, right? Who wouldn’t do that? You’d be surprised how many analytics projects are wrapped up by IT because “they think” they know the customer needs. Not assembling the right team is clearly the biggest mistake companies make. Many times what is on your mind (and if you’re an IT person willing to admit it) is that you are considering converting all those favorite company reports. Your goal should not be that. Your goal is to create a system—human engineered with customers, financial people, IT folks, analysts, and others—that give people new and exciting ways to look at information. It should give you new insights. New competitive information. If you don’t get the right team put together, you’ll find someone longing for the good old days and their old dusty reports. Or worse yet, still finding ways to generate those old dusty reports. Mistake 2. Not having the right talent to design, build, run and update your analytics system. It is undeniable that there is now high demand for business analytics specialists. There are not a lot of them out there that really know what to do unless they’ve been burned a few times and have survived and then built successful BA systems. This is reflected by the fact you see so many analytics vendors offer, or often recommend, third-party consulting and training to help the organization develop their business analytic skills. Work hard to build a three-way partnership between the vendor, your own team, and an implementation partner. If you develop those relationships, risk of failure goes way down.
-
Mistake 3. Putting the wrong kind of analyst or designer on the project. This is somewhat related to Mistake 2 but with some subtle differences. People have different skillsets so you need to make sure the person you’re considering to put on the project is the right “kind.” For example, when you put the design together you need both drill-down and summary models. Both have different types of users. Does this person know how to do both? Or, for example, inexperience in an analyst might lead to them believing vendor claims and not be able to verify them as to functionality or time to implement. Mistake 4. Not understanding how clean the data is you are getting and the time frame to get it clean. Profile your data to understand the quality of your source data. This will allow you to adjust your system accordingly to compensate for some of those issues or more importantly push data fixes to your source systems. Ensure high quality data or your risk upsetting your customers. If you don’t have a good understanding of the quality of your data, you could easily find yourself way behind schedule even though the actual analytics and business intelligence framework you are building is coming along fine. Mistake 5. Picking the wrong tools. How often do organizations buy software tools that just sit on the shelve? This often comes from management rushing into a quick decision based on a few demos they have seen. Picking the right analytics tools requires an in-depth understanding of your requirements as well as the strengths and weaknesses of the tools you are evaluating. The best way to achieve this understanding is by getting an unbiased implementation partner to build a proof of concept with a subset of your own data and prove out the functionality of the tools you are considering. Bottom Line. Think things through carefully. Make sure you put the right team together. Have a data cleansing plan. If the hype sounds too good to be true—have someone prove it to you.
Filling a Critical Role in Business Today: The Data Translator - Microsoft Business Int... - 0 views
-
a lot of articles calling data scientists and statisticians the jobs of the future
-
there are more immediate needs that, when addressed, will have a much greater business impact.
-
Right now we have huge opportunities to make the data more accessible, more “joinable” and more consumable. Leaders don’t want more data – they want more information they can use to run their businesses.
- ...5 more annotations...
Moving Sugar to Another Server - SugarCRM Support Site - 0 views
-
-
japtone Senior Member Join Date Nov 2010 Posts 49 Re: Transferring SugarCRM to a new server If you're using Linux try to have the same version of PHP, Apache, and DB (MySQL for instance) in order to avoid compatibility issues. In your production server tar up the sugarcrm root directory, transfer it to the new server and untar wherever your new root directory will be. Next take a db dump of your database, transfer it to the new server and do a restore. Make sure apache is configured on the new server to point to the root of sugarcrm and start it up. Make sure to modify config.php to account for any change in paths and hostname. that's what I've found to be the easiest way to 'clone' sugar.
-
-
mysqldump -h localhost -u [MySQL user, e.g. root] -p[database password] -c --add-drop-table --add-locks --all --quick --lock-tables [name of the database] > sqldump.sql
-
Extract the Database
- ...5 more annotations...
Rittman Mead Consulting » Blog Archive » Using OBIEE against Transactional Sc... - 0 views
-
The best practice in business intelligence delivery is always to build a data warehouse.
-
Pure transactional reporting is problematic. There are, of course, the usual performance issues. Equally troublesome is the difficulty in distilling a physical model down to a format that is easy for business users to understand. Dimensional models are typically the way business users envision their business: simple, inclusive structures for each entity. The standard OLTP data model that takes two of the four walls in the conference room to display will never make sense to your average business user.
On Cursor FOR Loops - 0 views
Browser-Based: Sizing Up Performance - 0 views
1 - 11 of 11
Showing 20▼ items per page