6 Enduring Truths About Selecting Enterprise Software - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Software // Enterprise Applications
09:06 AM
Tony Byrne
Tony Byrne
Connect Directly

6 Enduring Truths About Selecting Enterprise Software

Pay attention to these truths and warnings about the tricky business of buying business software.

Editor's note: This is the first of two parts. Read part 2: Six More Enduring Truths About Selecting Enterprise Software

In the 12 years that Real Story Group has been advising enterprise technology selection teams, I've seen customers evolve their approaches to acquiring new software -- mostly for the better.

Real Story Group

In general, customers today have become more savvy, as well as more open to experimentation. Greater attention to enterprise architecture (EA) and user experience (UX) tradeoffs in the buying process has also led to better decision-making.

Nevertheless, many perennial truths about software selection endure. At a time when digital capabilities have become an important competitive differentiator, enterprises seeking to up their digital game need to pay close attention to finding the right fit when investigating new software.

Here are six (sometimes inconvenient) truths that can make you a smarter buyer. At the end of each one, I suggest a short lesson for your team to take away.

1. Software marketplaces are as opaque as ever
Technology buyers have become more sophisticated and have better access to peer networks and advice than ever before. But in fast-changing marketplaces, enterprise buyers still report a lack of transparent, unbiased information about specific technologies and vendors -- as well as insufficient depth. Want to read cursory reviews or simplistic quadrants featuring the largest vendors? Sure, they're available. But what about deeper architectural critiques and contextual evaluations? Not as common.

The rise of cloud-based solutions has to some extent turned opacity into a feature, not a bug. As a buyer, you may not even want to know how a cloud-based service works, just that it addresses an immediate need. For one-dimensional applications, this makes sense: Why waste time investigating closely? For more enterprise-critical applications, you'll want to do the same diligence as you would with on-premises products. Remember, in the cloud, you are still selecting software; you're just not managing it.

[What can agencies learn from IT investments that fail? Read: Lessons For HealthCare.gov: Recovering When Your IT Project Crashes.]

Vendors, too, regularly push boundaries and market themselves to broader use-cases than their technology can handle. You can't blame them. But by the same token, this means that you have more choices than ever, and for important projects, you don't want to rush your decision-making or pursue vendor-of-the-month hype. Having a vendor map or two doesn't hurt.

Lesson: Reach out to trusted advisers to help you navigate.

2. Significant regional and national differences endure
As software marketplaces mature, you begin to see common global trends and products that span geographic boundaries. Some processes are universal; an invoice is still in invoice in Argentina as well as Australia.

Yet, we find that regional differences still matter. Countries like Germany and Japan are resolute in their support for local technology vendors. In Japan, user interfaces often need to feature horizontal scrolling over vertical scrolling -- not an easy change to make if a platform wasn't built that way. Moreover, even mega-vendors like Oracle will distribute resources quite differently in different countries.

Meanwhile, elevated concerns about data location and privacy in the wake of the NSA revelations have only heightened the appeal of local providers.

Lesson: Look beyond brand names and remain open to local suppliers in your market.

3. Interdisciplinary selection teams work best
For important technology decisions, stakeholders can span across HR, legal, marketing and sales, finance, and more. So you want to involve relevant groups in the process. Sometimes business teams hand over responsibility for software selection to IT groups on the grounds that business leaders do not have sufficient time nor expertise. This is a mistake: The wrong tool will eat up much more time and money than a committed presence in the selection process.

And, of course, IT should never, ever pick business technology on their own.

Conversely, we sometimes witness selection teams trying to work around their internal IT resources because they don't like the direction IT is heading, or they simply don't get along. This is almost always a mistake. Even with SaaS products, you will need IT's help for things like data integration.

Lesson: Build a broad selection team that can account for diverse enterprise interests and validate the results with peers.

4. Usability is relative
Everybody wants tools to be "easy to use," but few people can describe what that really means. Beyond basic human factors -- like reducing clicks and pop-up windows, or avoiding horizontal scrolling (except maybe in Japan!) -- you can't make a lot of blanket usability judgments.

The rise of UX and user-centered design principles can help here. UX guru Steve Krug offers a pithy definition of usability: fitness to purpose. Usability therefore becomes dependent on the tasks and personalities involved. What seems too complex to one person can prove richly functional to someone else whose tasks are more complicated.

Although nearly everyone looks to Google as the paragon of simplicity, enterprise software vendors in some segments have headed in the opposite direction, amping up power-user interfaces. This stems from the fact that enterprise technology selection teams are dominated by savvy, feature-driven specialists rather than workaday end-users or real customers.

Lesson: Task analysis is your friend -- you'll need to dig to find out what "easy" and "simple" mean to your customers and colleagues.


We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
1 of 2
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
12/16/2013 | 12:22:55 PM
Great Feedback
Belated thanks, folks, for chiming in.  A few thoughts...

Roadmaps are important for both driving and software, but for the latter, I still think they're overrated.   I prefer to hear and see evidence of broader strategic direction.  How much does a vendor really care about a particular offering?  Will their delivery model change?  Are they keying in on particular verticals?  Have they tended to meander in the past?

Google may not issue detailed roadmap guidance, but more important things enterprise customers might want to know about them is how long they are committed to any given offering before they decide to keep it, and whether they will continue a support and implementation model consisting primarily of smaller integrators who have no closer access to Google's systems than you or me.  Google's approach works for some customers; not others.

Shane M. O'Neill
Shane M. O'Neill,
User Rank: Author
12/10/2013 | 9:34:39 AM
Ease of use
The "usability is relative" point is a good one and the advice here is apt. "Ease of use" can get muddled when those selecting the software are more sophisticated than the employees who will be using it.
User Rank: Author
12/9/2013 | 3:25:33 PM
Re: Aspirational Vendor Roadmaps
Product roadmaps suggest some level of vendor accountability and should instill some sense of urgency, even if the vendors don't always live up to them.
User Rank: Author
12/9/2013 | 10:52:07 AM
Aspirational Vendor Roadmaps
It's interesting that we know these roadmaps are "aspirational" -- yet this is one of the repeated complaints about Google as an enterprise software vendor, that it does not provide enough roadmap guidance.

It's like we want a good story even if experience teaches us not every chapter will come true. Do we put too much value in that storytelling, IT pros?
11 Ways DevOps Is Evolving
Lisa Morgan, Freelance Writer,  2/18/2021
Graph-Based AI Enters the Enterprise Mainstream
James Kobielus, Tech Analyst, Consultant and Author,  2/16/2021
What Comes Next for AWS with Jassy to Become Amazon CEO
Joao-Pierre S. Ruth, Senior Writer,  2/4/2021
White Papers
Register for InformationWeek Newsletters
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you.
Flash Poll