Breadcrumbs
Home / Blog / Divestiture / What Would Happen if You Sold Part of Your Business?Written by Helene Abrams Sunday, November 18 2007
Deciding what information to share and what information to keep private is one of the most critical decisions companies face when they decide to sell part of the company. Sharing too much information allows competitors to identify advantages to use against the parent company. Keep irrelevant information may result in unnecessary costs, such as excess storage, maintenance, and disaster-recovery charge.
A growing number of boardrooms are facing the problematic question of what information to share.
By September 2007, global divestitures had reached a record-setting $1.64 billion for the year in almost 10,000 deals, up 25 percent for the same period in 2006, according to Dealogic, a software developer for the investment-banking industry. Divestiture, or selling off a part of the company, can be a healthy strategy for pruning under-performing divisions, responding to changes in the marketplace, allowing a company to focus on different markets, or just because cash is needed for new initiatives. Some of corporate America’s most well known names are in the midst of divestitures, getting rid of assets that are considered “noncore” and refocusing their resources. While divestitures can provide many benefits, executives must plan what information to share under stressful conditions. They are expected to sustain growth and retain existing customers while reducing the impact of organizational change.
Disposing of unwanted divisions or products is complicated. Deciding how to handle information during a divestiture is not unlike splitting the assets of a marriage during a divorce. Not only is the parent company affected, but acquiring companies are as well. Very often the divested company is sold to a competitor. Providing historical information for the part of the company to be divested may increase the selling price, but may provide information that you don’t want your competitors to have. Some information, such as customer lists, is considered low risk. Competitors likely know already whom major customers patronize. And realistically, by the time a divestiture is announced, it’s likely that some key data may already be in the hands of departing employees, or already part of the buyer’s information. Of greater concern are trade secrets, trend analyses, prices, discounts, cost of goods sold and contract terms with suppliers. If exposed, this information could give competitors an advantage and should be kept private, if possible. Public and private companies have different obligation.
Due to the complexity of accurately managing changes to such large relational databases, technology has entered the picture as a substitute for a large piece of the painful consulting work and is playing an increasingly larger role by helping to automate the process, reducing time and expense. Planning ahead is essential; experts recommend starting at least three to four months prior to the separation and regularly communicating the impact of changes to all business units. With so much at stake, wise executives will take careful steps to decide what information to disclose and what to keep private, and then use technology to automate the separation once the decision is made.
| < Prev |
|---|
Related Articles
Enter your email address to sign up for our Newsletter
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?
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."
Popular Articles
- Organization Setup in R12
- If IFRS...Then, Part 2: 5 Best Practices in Designing a Chart of Accounts in Oracle E-Business Suite
- 11i to R12 Decision: Upgrade or Reimplement?
- Designing a Global Chart of Accounts and Taking Advantage of Oracle® E-Business Suite Release 12
- Moving from GAAP to IFRS with Oracle EBS





