How IT can both deliver business value and 'keep the lights on'
IT teams spend too much time on “daily churn” rather than delivering real value to the organization. Read how Mike Guggemos, CIO at Insight Enterprises tackled the problem.
15 places to use requirements when selecting enterprise software
Not understanding how important requirements are and where they are used is the root cause of most problems with implementing software.
The backward way of gathering enterprise software requirements
Organizations ask users for their requirements, only to find that when enterprise software goes live, it doesn’t meet user expectations. It turns out that we have been doing this backward for years.
The hidden costs of poor software purchasing exposed!
Many companies think they know how to purchase software when they have little idea of the process! This article looks at 3 places where money is squandered
Conflict-of-interest traps ensnare enterprise software implementations
Avoiding these two conflict-of-interest situations helps ensure the software you select meets your needs and the implementation is completed on time and on budget.
Why software implementations are usually late and over budget
Enterprise software implementations usually take substantially longer and cost more than planned. When going live they often cause major business disruption. Here's a look at the root cause of the problem, with suggestions for...
Avoid ambiguity when writing requirements for software purchases
Ambiguous requirements can lead to purchasing software that doesn't meet expectations. Here are some simple techniques for avoiding ambiguities in your requirements.
Law firm uses OKRs to drive astonishing results and get things done
In the corporate world, many decisions are made in meetings, but too often things fall between the cracks. Here's a look at how one law firm used new Workboard OKR (objectives and key results) software to solve the challenge of...
Five ways inadequate requirements wreak havoc with enterprise software purchases
See how poor requirements analysis puts enterprise software purchases at risk of partial to outright failure...and how to fix the problem.
16 difficulties to avoid when purchasing enterprise software
In spite of the time and money spent, few software deployments meet expectations. Why? This article examines the more common reasons why selecting software is so difficult, so these problems can be avoided.
Buying the best BPM for your needs
Business process management software can be thought of as 'the oil that lubricates corporate machinery.' With dozens of competitors on the market, use the reverse-engineering technique to find the BPM software best suited to your...
Use reverse engineering to help users set requirements for big software purchases
Collecting detailed software requirements from users can be painfully difficult. See how rewriting features as requirements helps develop a comprehensive requirements list for selecting enterprise software.
The payoff from a rigorous software selection
With major software purchases, the key to maximizing success is preparation. Even if you already know what software you want, there are still numerous benefits to a rigorous evaluation & selection. And maybe the favored software is...
The enterprise software acquisition funnel
Like sales & marketing, software acquisition has a funnel. See how to use this funnel to reduce the pains so prevalent with major software purchases.
17 painful ways a major software purchase can go wrong
The pain of a major software purchase going wrong can lead to wishing the project had never been started. However, by then contracts are signed and it is too late to do anything about it. Read and be warned!
What not upgrading enterprise software could cost you
Given the rapid rate of innovation in the software field, the costs of obsolete systems are usually much higher than most people realize. The only way to know for sure is to estimate that cost.
Knowing when a full software evaluation project is worthwhile
Based on your software budget, here's how to estimate the resources needed to ensure you select the best-fit enterprise software for your particular needs.
Why software requirements development matters
A thorough requirements analysis takes time and money, but helps an organization to truly understand what they need and want. That understanding is a critical part of the ultimate success of the new software.
Gathering and managing software requirements for buying or building
When developing software requirements it can be helpful to use existing products for inspiration. It is also useful to have several tools that can be used to manage those requirements.
The urgency of recognizing and satisfying unknown software needs
It’s the unknown unknowns that get you! Using marketing technology as an example, we examine ways of exposing unknown software needs and evaluate the urgency of satisfying them.
-
White Paper
-
White Paper
-
White Paper
-
Sponsor Article
Sponsored -
White Paper
Top Blog Posts
