X

Advice and Information for Finance Professionals

5 Weeds Hiding in Your IT Garden

Rudy Lukez
Director, ERP Product Marketing, Oracle

Gardens and summer are annual partners in many households. Homes around the world grow gardens with dreams of delivering beautiful and bountiful cornucopias of fresh flowers and produce. But gardens have one major downside: weeds.

Controlling and removing weeds is a daily challenge, and if you miss one day of pulling, the next day the weeds seem to have multiplied by a factor of four. Many great garden plans conceived in May have been decimated by weeds in July.

This slippery slide into despair can easily be compared to on-premises projects for finance software. Excitement reigns on kick-off day. Over the next few months, hopes for the original project slip away as cost overruns, schedule delays and scope creep take root.

Weeding the garden is not unlike what IT shops experience when working with on-premises finance systems. Every on-prem ERP project suffers from one or more of the following weeds. Don’t let them go unchecked.

  1. Bug Weed. This weed is insidious—always small but constantly present. IT departments are constantly applying patches and bug fixes to on-premises finance applications, hardware systems, other infrastructure components, and databases. Strategic projects fall behind as IT staff becomes overwhelmed with tactically fixing operational and security issues.
  2. Choke Weed. On-premises ERP systems experience choke weed when requests for custom code, one-off reports and new features strangle IT resources (and budgets) with endless tactical projects. It’s like spending two or three days pulling weeds while more important improvements are postponed indefinitely.
  3. Resource Weed. This is the big tap root that is always larger beneath the ground. Sometimes called “iceberg” or “deep weed,” the tap root plant consumes the lifeblood of any garden: water. The on-premises ERP equivalent is likewise a tap root that extends daily into IT and business budgets—except, instead of water, it sucks dry any source of cash it touches. It continues its bottomless hungry rampage while strategic projects are cancelled and die of thirst.
  4. Flower Weed. At first, this weed seems innocent. It even looks acceptable, maybe even attractive, in the garden. But experienced IT departments running on-premises ERP solutions know better. Flower weed delivers seemingly simple requests unexpectedly—such as, “Please change this report’s header for the CFO.” IT resources are rapidly redirected when the CFO’s name is casually tossed into the conversation. The scope grows with every tug and the overall task becomes harder to complete.
  5. Pain Weed. The weed with very sharp, dagger-shaped spikes. Even with leather gloves made from the thickest bison hide, the thorns penetrate deep into your skin and cause so much pain the subsequent yelp is unprintable. On-premises system managers go through similar pains whenever they need to approach the board for more money—more capital funds to cover more rounds of consulting services, hardware repairs, and software upgrades.

Weeds are a fact of life with gardens. But when your finance department moves from on-premises systems to the cloud, you can greatly reduce the frequency and types of weeds you encounter daily.

In many ways, the cloud is an organic antidote to these leafy pests. With cloud ERP, capital funds are saved as operational expenses are used to cover the monthly subscription fee. Pain weed rapidly becomes a distant memory. IT moves from tactical battles to strategic priorities as resources are no longer choked off.

When you begin moving from on-premises financial systems to cloud solutions, you rapidly notice how all your other IT efforts bear more fruit—especially the green kind. You begin to focus on new, strategic efforts to improve the productivity and diversity of your garden.

See how lovely your finance garden can be. Request a demo of Oracle ERP Cloud.

 

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha