Why Workarounds Won't

PDFPrintE-mail

Every quarter, every year, and every month, financial organizations work hard to close their books and prepare financial statements in accordance with countless rules and regulations. And when their ERP systems, designed at great expense and some point in the distant past, can’t keep up with their ever changing needs, they resort to creative workarounds, relying on spreadsheets, diagrams, or other documents jut to get through another reporting period.

As time passes, documenting the period-end process becomes more complex, and maintaining the process documents takes more and more time. But the collective memory of the finance team hasn’t forgotten what it was like to get through that first ERP implementation project – not to mention its enormous expense – and any hopes of improving the situation are abandoned as soon as someone says, “What about the ROI?”

Finance teams would have a better chance of responding to the ROI question if they banded together with their colleagues in purchasing, HR, product management, manufacturing, sales, marketing, and IT as they struggle with the same legacy ERP systems. Ask around and you’ll find that all of them have created their own sets of creative workarounds just to get through another day.

It’s happening everywhere.

HR professionals, for example, have all sorts of ongoing ERP-related headaches to deal with. Employees leave or join the company or move from one business unit to another, possibly in another country. As a result, compensation, bonuses, benefits, commission policies, and structures are a moving target. Layoffs and furloughs have taken their toll, and divestitures and acquisitions mean company reorganizations are seemingly endless. How likely is it that the once elegant workflow designed around an ERP system implemented 5 or 10 years ago hasn’t needed to change?

And with businesses struggling to keep their heads above water during this recession, RIFs and budget cuts only exacerbate the problem. It’s like having your business broadcast on a hi-def TV. Suddenly every innocuous work around looks more like a big ugly wart.

And it’s happening in virtually every business unit and functional area.

Purchasers in recent quarters have been working hard to reduce inventories by renegotiating contracts and payment terms. Manufacturers looking to reduce costs have outsourced, in some cases insourced, and in many cases adopted lean production practices. Product managers have been reducing product lines to those that are most profitable, and IT teams have been investigating cloud computing and other virtualization initiatives to drive out costs. Sales teams have seen dramatic changes in their territories, pipelines, and orders. And marketing teams have been redirecting funds to less costly online venues thanks to Twitter, Facebook, and LinkedIn.

In other words, everyone has been on the same bandwagon for months, driving out costs and looking for efficiencies while hoping to hang on until the economy turns around. And one day it will.

The Next Great Companies

The question is how easily will your organization be able to adapt to a new business environment? Is a hopelessly inefficient ERP system going to cut it? Will you briefly consider doing something about it but abandon any lofty plans because of that killjoy acronym, ROI? How will your organizations respond to an uptick in the economy, effectively and efficiently? Nimbly? Like the contortionists executives want everyone to be?

As if issuing a wake-up call to the business community, Gartner has proposed that organizations should now seek changing patterns in their business environments and formulate strategic plans to address those changes. IT systems will be a key component of this highly competitive new organization, aggregating and analyzing data, synthesizing information, and ultimately discovering patterns that uncover new opportunities or threats.

If Gartner’s vision for the future holds true, organizations that aspire to be market leaders won’t hesitate to update outdated ERP systems and abandon off-line workarounds.

Those who don’t will muddle along. They’ll be the good companies, but never the great ones.

Add comment


Security code
Refresh

Email Newsletter icon, E-mail Newsletter icon, Email List icon, E-mail List icon Enter your email address to sign up for our Newsletter

Sign up now

captcha
TEChanges - Agility by Design

May Puzzle

David is often referred to as Rainman due to his peculiar ability to effortlessly figure out a certain date's day of the week. He recently displayed this talent when I asked him if there was a conflict with the upcoming Fuzzy Dice Conference and our weekly court-ordered community service. He asked the date of the convention. It was April 20th, 2012.

"Oh, that’s a Friday," he said, effortlessly. "And your sentences have you committed for the next few dozen Wednesdays so you'll be able to go." And of course he was right.

One day a few weeks ago I asked out loud in the office about the date June 5th. And of all people, my brother Tommy piped up and said "Oh, that's a Tuesday."

"That's right," said David.

Well how about Otcober 3rd?

"That's a Wednesday," said Tommy. Then I asked about Christmas Day 2012.

"Oh, that's a Tuesday." David nodded in agreement.

Do we now have two rainmen? Or had Tommy figured something out?

Show solution...

Solution

Here's what was going on. Tommy was using something called anchor dates. And these dates apply to each and every year. April 4th, or 4/4 we’ll call it from now on, June 6th or 6/6, 8/8, 10/10, 12/12, are all the same day of the week, each and every year.

So too are 5/9 and 9/5, May 9th and September 5th. So too are 7/11 and 11/7, and all the above dates are the same day of the week, as is the last day in February, Leap Year or not. And they’re all the same day as January 4th, it would otherwise be January 3rd, but this was a leap year, and that’s changes the anchor day from January 3rd to January 4th.

Tommy also knew that New Year's Day was a Sunday. He was sobered up by then. And he knew it was a Sunday because Christmas was a Sunday in 2011, so New Year's Day is a Sunday, so the Anchor Day for 2012, January 4th, has to be a Wednesday!

So if that's a Wednesday, then 4/4, 6/6, 8/8, 10/10, 12/12, 5/9, 9/5, 7/11, 11/7, and February 29th are all the same day of the week, and they're all Wednesdays. So when I ask for example, about October 3rd, he knew October 10th was a Wednesday, 10/10. So 10/3 must also be a Wednesday. 12/12 is a Wednesday in 2012, so it’s 12/26, which is two weeks later. So 12/25, or Christmas Day, must be a Tuesday.

Success Tips for Oracle Project Management

  • Create a standard for documentation at the beginning of your project, and hold team members accountable for completing documentation requirements as well as keeping them at and above the standards required.
  • Before promulgating user documentation or training, it’s also a good idea to choose a representative from the among the business users base to review materials first.
  • If you are not sure about the resources and budget required, obtain several estimates from people that have experience with the same size and scope of your project.
  • Be explicit, before beginning the project, what internal resources are required for execution. This includes people, infrastructure, hardware, and software.
  • Help the project champion understand the impact your project will have on the organization and how its successful completion will make him or her an internal hero or heroine for supporting it.
  • Break up your project into smaller projects (try for projects that can be completed in 4-6 months, especially early on) to get success and demonstrate momentum.
  • Make sure that your testing includes reports, upstream and downstream interfaces, customizations, enhancements, and workflows.
  • Ensure that comprehensive transition reports and meetings between departing and incoming personnel are completed.
  • Instead of spending time and resources implementing third-party reporting, consider consolidating multiple instances, moving to a global chart of accounts (CoA), and/or standardizing on a consistent calendar.
  • Include governance, risk, and compliance management as part of the project plan.
  • Finally, celebrate the successes. Too many projects focus on defects, failures, or small cost over-runs without looking at the big picture and what was accomplished.

The Analyst Corner

John Van Decker, Research VP of Gartner, states:

"A single chart of accounts allows consistency in financial reporting across the enterprise by standardizing on common metrics and reporting structures, reduces dependencies on a separate financial consolidation system, and significantly reduces the costs incurred with ongoing, complex conversions and translations."