Matthew Cook -
Software Money Pit Blog
    Strategy & Management
    Trends & Technologies
    Case Studies
About Matt
Buy Matt's Book
Matthew Cook -
  • Software Money Pit Blog
    • Strategy & Management
    • Trends & Technologies
    • Case Studies
  • About Matt
  • Buy Matt’s Book
Strategy & Management

A Software Vendor Checklist

March 10, 2016 by Matt Cook No Comments

Please choose the door through which your next software vendor will take you.  Image: Doors of Dublin, by Tim Sackton, edited to fit 569 X 368px, CC license.

Selecting a software vendor is difficult at best in the 21st century; here are some must-have criteria, in addition to, but perhaps more important than, cost and time:

Does it solve my problem? Does the software company’s system solve your business problem? Does its existing functionality match the business requirements you drafted?
Does it pay back? Do the financial benefits from the solution pay back the total cost of implementing it in three years or less?
Do I understand all of the solution’s costs? Have you accounted for initial license, recurring support fees, custom development costs for changes you want to make to the software, hardware costs, upgrades to your network bandwidth or operating systems on your current servers or PCs, the cost of the next version upgrade, the cost of consultants, of hiring backup staff for project team members, and travel?
Is the solution in line with my strategy? Does the system match your criteria for what types of information solutions you will invest in, now and in the near future?
Do I understand all of my alternatives, besides this particular vendor? Have you done your homework regarding software options available? Have you constructed an evaluation matrix and compared all the alternatives to one another?
Does my team have the time and skills to implement this solution? Can you secure near full-time people to manage this project? Is the system easy to learn? Is it intuitive? Has your team evaluated it and are they comfortable they can master it?
Do my users have the aptitude to learn it and become proficient? Can you envision your end users quickly learning to use all aspects of the software? Are there enough users who could become proficient enough to serve as key users and help other users with training and troubleshooting?
Does my team fully understand how this solution will integrate with the company’s other systems? Has the vendor demonstrated to your satisfaction the ease with which the system will integrate with your other systems? Are other enterprises already running the software with systems like yours? Try to get at least a conference call with those references to gauge the level of integration complexity.
How risky is this particular software alternative compared to others? Can the software be phased in without interrupting the business? If the solution fails or the team encounters startup problems, how easy will it be to keep mission-critical activities running?
Vendor reputation. How many enterprises are using the vendor’s software, and for how long? Get references and check them.
Can I find programming help in the open market? If you need customizations, can you readily find people to do the work? Or are you locked in to using the vendor to make all your changes?

All of this is of course after you have submitted and reviewed detailed RFPs from the most appropriate vendors.  You can build a grid or a table, with vendors/solutions across the top and your most important criteria down the left hand side, and weight the relative importance of each. The result is an overall score that points you to a solution that best fits your needs.

Share:
Strategy & Management

FUD Still Here 35 Years Later

July 6, 2015 by Matt Cook No Comments

Photo by Jimmy Brown, CC license

 

FUD stands for fear, uncertainty, and doubt, and was a phrase used in the early 1980s to describe the unsettling and confusing atmosphere companies faced as they began investing heavily in software applications.

In 1979 Gideon Gartner, formerly a top technology analyst at Oppenheimer & Co., capitalized on that confusion and formed an advisory firm to help companies with technology decisions. Gartner Inc. now has a market value exceeding $4 billion and customers in 85 countries.

Although we have software tools far superior to what was available in the the 1980s, FUD still exists.

It exists wherever software marketers and commercial enterprises interact.  The dialogue is predictable: “Can your system do this, that, and the other thing.”  “Our system can do that, and much more; it can do X, Y, and Z.”

But the two parties (software, business) are talking past each other.  They aren’t even using the same language.

Software marketing is filled with evocative corporate-speak; it is opaque, conceptual, and general.  Meanwhile, the business person looking for a solution is mired in her own problematic world and knows in general what she needs but doesn’t realize that the software company she is speaking to has no idea of the details of her situation and even more cannot imagine it.

They speak to one another and try to find some common things they both agree on and understand.  The business person is left bewildered.  FUD.

Money pits thrive where FUD exists.  In this situation, bad and costly decisions are highly probable.

  • Take a step back and evaluate your business and technology strategy.  Do you really need this technology or could you outsource the whole business process?  Will the investment in this technology make my customers happier?
  • Before considering any solutions offered by software vendors, take the time to evaluate processes the software will support, document how those processes should flow in the future, and prepare a detailed list of requirements for the future application.  You will use this to evaluate the “fit” of each software solution to your situation.
  • Like anything else, educate yourself before you buy.  Understand the type of technology you need, and the options available in the current market.  An advisory firm is recommended here; it will cost you a fraction of what you intend to spend and save you multiples of that.
  • Change the conversation with the vendor.  Stop talking about the software.  Instead talk about your business context and the goals you have.  Most vendors really do want to understand your needs but they don’t have the advantage of being in your shoes.
  • Take the vendor’s software solution for an imaginary “test drive.”  Spend time with the vendor walking through your future process and the associated technology requirements.  The result will be much more clarity and understanding of the vendor’s potential to meet your needs.

 

 

Share:
Strategy & Management

How to Handle a FUD Experience

November 20, 2014 by Matt Cook No Comments

Two years ago I began exploring “cloud” software for integrating our company with its trading partners. This is how one company explains the benefits of its cloud software solution:

“Cloud supply chain platforms invert the traditional EDI (Electronic Data Interchange) hub equation by moving the data processing and linking logic from the partners at the ends of the spokes to the center hub itself. In this model, the entire value chain community leverages a common core technology utility so that all partners link to a single version of supply chain truth across the entire network.”

Here you have conceptual-speak, what sounds like preamble, and lots of jargon made to sound sensible (who can resist “a single version of supply chain truth across the entire network”?). In the section that is supposed to answer “what is this technology made of?” I come across this explanation:

“First, importantly, it is technology designed for the deep and detailed processes of a specific B2B domain. It is not generic. In this respect it diverges sharply from traditional EDI technologies that were designed for file transport and translation across all processes. Traditional systems take a “one size fits all” to information exchange: EDI file delivery for everyone, but a complete picture for no one.”

There’s more:

“In rich process domains such as supply chain execution, where the processes are long-lived and highly collaborative, what is needed is an information transformation layer that is knitted to the specific business processes at hand. Only by understanding the underlying and highly detailed data models and linkages of the critical business objects themselves can an information exchange platform create tight mappings to process. If an EDI VAN (Value Added Network) transports file packets, but is blind to the contents, the next generation platform interprets at the content level — it applies technology to the inside of the packet, in other words.”

None of this made sense to me, so I met with the firm’s representatives.

What they mean, as it turns out, is that their cloud software acts like a big private Facebook page, where your partners post data and transactions, as compared to traditional EDI, which is like passing a message to your partners in a straw where only you and they can see what’s in the straw.

One of the best ways to start a constructive conversation with a vendor is to say, “Ok I’m stupid. Connect the dots for me. You can link me to my trading partners like we’re all on Facebook. So what? Do I get rid of my EDI? What does that save me? Do I reduce inventories and order lead times? Will my customers and suppliers love me for doing this and will they partner with me on this approach?”

If a software vendor is good, that firm will assess your business situation first – your operation and processes – before trying to sell you anything.

So to handle the FUD experience you have to break the spell.  Be the spoiler in the room who is not going along with the feel-good lingo emanating from the vendor.

Share:

Categories

  • Strategy & Management
  • Trends & Technologies

Archives

© 2017 Copyright Matthew David Cook // All rights reserved