Thursday, June 12, 2008

WiCamp on June 13, 2008 in Chennai

This Friday the 13th doesn't seem to be that unlucky of a day! 'Cos a WiCamp (pronounced We-Camp) will be held at Wipro Technologies, OMR, Sholinganallur, Chennai.

Themes for the WiCampChennai
Managing innovation as a process
Discipline hindering/ enabling innovation
Practices from start-up to move from creativity to value capture
Role of collaboration in innovation
How firms arrive at value proposition for an innovation
Partnering to take ideas faster to market
Open Innovation Measuring returns on innovation
Shrinking the time to market
Increasing hit-rate of ideas
Managing teams for innovation
Personal creativity to organizational creativity

More details at http://barcamp.pbwiki.com/WiCampChennai

Wednesday, June 11, 2008

How to get to the top


An article in The Economist's website discusses the recent trends in moving up the corporate ladder. It states that while Marketing used to be route to the CEO's chair, these days the Financial wizards are the one who seem to take the top spot quicker. The article also states that sticking to an organization for a longer period of time helps in climbing up the ladder faster than job hopping.
(Image courtesy: Economist.com)

Friday, June 6, 2008

Choosing the right ERP (Enterprise Resource Planning) Software

ERP software integrates the information used by various departments of an organization so that it can be shared, accessed and managed in an efficient manner. However, implementing a well-established ERP software is often a high investment in terms of money, time and resources. This warrants a thorough study on which ERP package is suitable to an organization's needs before the package is purchased.
So, what are those factors that a company needs to consider to select an ERP software? Here are a few -

a) First, decide if you want to go for an ERP implementation.
ERP packages usually come pre-built with business processes that are most widely used in industry. While a good portion of these processes can be configured to suit your organization's needs, they may not always be a perfect fit to what you want. Most ERP implementations require an organization to consider going in for Business Process Reengineering (BPR) prior to the ERP implementation, so that the organization's business processes match or come close to what the ERP delivers! This certainly comes as a shock to many companies that are used to getting software systems built-to-order. If not a BPR, some ERP implementations demand atleast some modifications to certain business processes, and many organizations find it difficult to change the way things have always been done. Since the very purpose of using an ERP is to have various departments integrate and manage data efficiently, it is vital that the decision makers of those departments together arrive at a go/no-go decision for an ERP rollout.

b) Does the product provide most of the features you want?
One ERP package might be excellent for Human Capital Management, while one might be the default to choose for Supply Chain Management, while yet another may be the best fit for Customer Relationship Management. Do an evaluation - which major business function is most relevant in your organization to have an ERP rollout? Choose the package that is believed to be the best for that business function, and evaluate if the package does a fairly good job of addressing the pain points of the other business functions. For example, if your key concern area is Human Capital Management, and say you decide to implement PeopleSoft, check if the SCM and CRM capabilities of PeopleSoft would suffice to cater to those respective functions, or if you would have to go in for some other ERP system for those functions and try to integrate with HCM.

Other features you might want to consider are -
(i) Usability of the ERP over the internet
(ii) Support of data exchange via XML, EDI, flat files etc.
(iii) Availability of business functions as modules (eg. Benefits, Payroll, Accounts Payables, etc).
(iv) Multilingual and multicurrency support
(v) Flexible enough to allow users to create ad-hoc reports
(vi) Ability to run on different operating systems and use different databases.

c) Ask for a demo of the product
The Sales & Marketing team responsible for selling the ERP can be counted upon to present to you the features of the ERP in a stunning Power Point/Flash presentation. That's great! But are you sure that WYSIWYG? Insist on a demo of the product and keep your business users and technical team as part of the audience. Perhaps the business users are looking for a more user-friendly product with a jazzier looking screen, while the technical team wants to evaluate how easy it is to configure or customize the product. A balance usually needs to be struck between what each evaluating party wants. So, go for the demo and try to experience the product first hand.

d) Evaluate the Total Cost of Ownership
Perhaps the ERP being evaluated doesn't cost too much to implement. But what about the costs you would incur AFTER the implementation? How often does the ERP need an upgrade or a patch? What are the support costs? How easily is talent that can support/upgrade/implement the ERP available in the market? How well is the company selling the product doing in its business? If you wish to outsource support, can that be easily accomplished with the product? It is best not to evaluate an ERP product looking only at how well it fits your present requirements, rather keeping in mind its fit for your mid and long term requirements.

There's a good article on CNN.com that gives suggestions on how to choose the right ERP package. While its a somewhat dated article (Feb 1999) and even talks about how the ERP should address the Y2K issue [:-)], many of what the article contains is very much valid in this day.

Happy reading and good luck in choosing an ERP that best matches your needs!

If you liked this article, please Digg it

Applying Supply Chain Management principles to People

Peter Cappelli, a Wharton management professor likens managing an organization's talent to managing the organization's supply chain. He theorizes that the way HR looks at Talent Management is quite different at how the gentleman/lady who handles the organization's finances looks at it. Knowledge @ Wharton has a review of Cappelli's book 'Talent on Demand: Managing Talent in an Age of Uncertainty'. A worthwhile read...

HBR article: The Contradictions that drive Toyota's Success

A judiciously written HBR article on a study done on Toyota over six years, brings to light the contradictions that drive Toyota's success.

The contradictions that are written about are -
a) Moving slowly, yet taking big leaps
b) Growing steadily, yet being paranoid
c) Having efficient operations, but using employees' time in seemingly wasteful ways
d) Being frugal, yet splurging on key areas
e) Keeping internal communications simple, yet building complex social networks
f) Maintaining a strict hierarchy, yet giving employees the freedom to push back

The authors have spent a lot of effort in trying to identify the underlying forces that cause these contradictions, and have identified 3 Forces of Expansion and 3 Forces of Integration. But emulating these to become another Toyota is a whole new ball game!

Clicky Web Analytics