We use cookies, including third-party cookies from Google to serve personalized ads through AdSense, to operate this site and understand how it is used. By continuing to browse, you accept this use. See our Privacy Policy and Terms of Use for details, including how to opt out of personalized advertising.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    What Kind of Problem-Solving Distinguishes Data Analysts From Software Engineers -- AI-generated illustration
    What Kind of Problem-Solving Distinguishes Data Analysts From Software Engineers
    7 Min Read
    chatgpt image jul 21, 2026, 04 34 30 pm
    4 Core Benefits of Predictive Maintenance after Vibration Analysis
    10 Min Read
    How Does Data Mining Boost Customer Satisfaction in Logistics? Harnessing Analytics for Results -- AI-generated illustration
    How Does Data Mining Boost Customer Satisfaction in Logistics? Harnessing Analytics for Results
    11 Min Read
    chatgpt image jul 13, 2026, 04 23 45 pm
    How Data Analytics Helps Companies Improve User Engagement
    19 Min Read
    chatgpt image jul 13, 2026, 03 59 46 pm
    How Data Analytics Improves Multi-Location Search Strategies
    10 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: Why Add More Features? Because We Can or Because We Should?
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Business Intelligence > Why Add More Features? Because We Can or Because We Should?
Business Intelligence

Why Add More Features? Because We Can or Because We Should?

MIKE20
MIKE20
2 Min Read
Why Add More Features? Because We Can or Because We Should?
Illustration generated with FLUX.2 [klein 4B] via Cloudflare Workers AI.
SHARE

I just read a great post by Daniel Mathai of Infosys, Why Social CRM Can Wait.  He brings an interesting perspective into the decision to add social features to your CRM, which I think is valid for many other business intelligence projects as well.

Why are we adding more features to our applications?  Because the capability is there, or because we need it?

It is easy to make a decision to pursue additional intelligence based on the fact that it will give you a competitive advantage or the ability to learn more about your customer and prospect base.   However, more often than not, managers are quick to jump into the latest functionality without thinking of how it will impact the system as a whole.  From my experience, the system (whether it be CRM or ERP, custom built or software) needs to be audited properly to ensure that it is well managed and integrated before embarking on the latest functionality to enhance it.

It sounds simple: Make sure you can fit the new car in the garage before you bring it home.  But it happens, time and time again.  In your opinion, what are some of the reasons why companies fail to audit and prep their information systems before adding functionality that will significantly alter it?

More Read

How Business Intelligence is Making Real Estate Easier
How Business Intelligence is Making Real Estate Easier
Avoiding Potential Snags in BI Initiatives
Customers and Banks Priorities Collide as AI Jolts Financial Industry
PayPal Winning the Mobile Payments and Mobile Data Race
Can Performance Management Combine the Best of Soviet Planning and Capitalism?

Link to original post.

TAGGED:software
Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

Technical architecture diagram and decision framework for choosing an integration partner for data pipelines: service bus, brokers, and azure-native middleware compared
Choosing an Integration Partner for Data Pipelines: Service Bus, Brokers, and Azure-Native Middleware Compared
Development Exclusive
Technical architecture diagram and decision framework for data engineering for prize draws: building an audit trail
Data Engineering for Prize Draws: Building an Audit Trail
Big Data
Technical architecture diagram and decision framework for the trouble with ai that won’t leave a job unfinished
The Trouble With AI That Won’t Leave a Job Unfinished
Artificial Intelligence News
Technical architecture diagram and decision framework for ai-powered logo generation: design.com vs looka
AI-Powered Logo Generation: Design.com vs Looka
Artificial Intelligence Exclusive

Stay Connected

1.2KFollowersLike
33.7KFollowersFollow
222FollowersPin

You Might also Like

We All Now Work for Software Companies: The Lines Just Keep Blurring
Analytics

We All Now Work for Software Companies: The Lines Just Keep Blurring

4 Min Read
The Dire Consequences of Analytics Gone Wrong: Ruining Kids’ Futures
AnalyticsCommentaryPredictive Analytics

The Dire Consequences of Analytics Gone Wrong: Ruining Kids’ Futures

9 Min Read
5 Questions To Ask Before Embedding Business Intelligence Into Software
Business IntelligenceExclusiveSoftware

5 Questions To Ask Before Embedding Business Intelligence Into Software

7 Min Read
Gamification Must Drive Software Ergonomics
Uncategorized

Gamification Must Drive Software Ergonomics

6 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

AI chatbots
AI Chatbots Can Help Retailers Convert Live Broadcast Viewers into Sales!
Chatbots
From Bolts to Bots: How AI Is Fortifying the Automotive Industry
From Bolts to Bots: How AI Is Fortifying the Automotive Industry
Artificial Intelligence

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-26 SmartData Collective. All Rights Reserved.
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?