SAP ROI — Enterprise Architecture & Business Solutions

Strategic SAP & IT Program Development for Measurable Business Value

ERP vs. ERP II vs. ERP III Future Enterprise Applications

May 31st, 2010

ERP vs ERP ii vs ERP iiiAbstract on ERP I, ERP II, & ERP III

ERP applications integrate enterprise operations within and across enterprise legal entities, or company codes. ERP ii (or ERP 2) applications extend supply functionality to external enterprises (generally vendor-affiliated companies or enterprises) to reduce cost, improve supply chain efficiency, and to perform collaborative innovation.  ERP iii (or ERP 3)enterprises go to the next level of integrating the ERP and ERP ii functionality to include customers and the sales side of the marketplace in general.

Moving To the Border-less Enterprise

I’ve heard and read lots of material about the enterprise applications and what the next generation of ERP is.  Some have suggested that ERP systems were just manufacturing tools (see e.g. ERPwire article on major differences between ERP vs. ERP ii).  They then suggested the next generation of ERP systems, or ERP ii systems, were little more than an extension of ERP functionality to new industry sectors.  In my opinion this is a completely misplaced assessment.  Just changing industry sectors does not change what an ERP application does so a broader definition is more appropriate.

Before we go into the details and background of each of the 3 generations of enterprise applications here are my definitions for ERP, ERP ii, and ERP iii systems:

ERP Definition

An ERP (Enterprise Resource Planning) system integrates virtually all operational business functions and processes and automates entries to finance and reporting within the enterprise (the legal entity or entities that make up an entire company no matter where its operations are).  ERP systems focus almost exclusively on operational excellence value propositions of process efficiency and automation.

ERP II (or, in other words second generation ERP, ERP 2) Definition

Through collaboration, SOA, and other interface, data exchange, or interaction methods the ERP ii systems move beyond Enterprise boundaries (or a basic ERP system) and into the vendor space including the supply, design, and engineering collaboration areas. ERP ii systems continue to enhance operational excellence and start to introduce a measure of the innovation value proposition.

ERP III (or, in other words third generation ERP, ERP 3) Definition

Through collaboration, direct contact, social media, and various data streams within and outside of the enterprise ERP iii integrates marketplace fans and critics into the extended ERP and ERP ii organizations.  From this integration of the customer and vendor a constructive dialog and exchange of information is created to innovate, produce, and then sell / distribute better products or services.  This closes the value proposition loop by going outside of the enterprise boundaries and finding ways to bring customer input, needs, wants, and insight into the enterprise.  ERP iii system create a strong synergy between innovation and customer focus.

ERP System Definition or ERP Defined

The acronym ERP literally stands for “Enterprise Resource Planning.”  And this is exactly where I disagree with the ERPwire definition proposal.  Just a manufacturing system is not an “enterprise” system at all.  It is merely a manufacturing system, or an MES (Manufacturing Execution System).

As the university studies and academic literature note, ERP systems are “a single instance of data, a full process chain of dependencies” (see Change Management Strategies and Knowledge Transfer Processes for a Successful SAP Project citing Kallinikos, 2004). In the ERP industry we (consultants and integrators) frequently refer to any ERP system as a type of “back office” application or system.  By “back office” we are referring to company centered business functions into a single database, or, a single “system of record.”  “Back office” processes are fully within the border and boundary of the enterprise.

In 2000, in an article addressing ERP ii, Gartner noted that they had defined ERP in 1990:

In 1990, Gartner defined ERP, establishing a new vision for the resource planning domain. That vision centered on resource planning and inventory accuracy, as well as visibility beyond the plant and throughout the manufacturing enterprise, regardless of whether the enterprise was a process manufacturer, discrete manufacturer or both. ERP has since appeared in different “flavors.” Extended ERP reflected the fact that many nonmanufacturing industries turned to ERP systems for “backbone” financial transaction processing capabilities (Bond, et. al., 2000 pg. 2, note 2).

That article went on to note that the accepted definition (in 2000 and beyond) had become:

Despite [the] original definition, ERP has become the accepted term for back-office transaction processing systems, regardless of the industry or region (Bond, et. al., 2000 pg. 3).

The definition I have provided is as comprehensive as the original Gartner proposal and includes the later understanding of the application to more industries and business functions.

ERP Focuses on the Operational Excellence Value Proposition

This site provides a much more detailed explanation of the functions and operations of an ERP system like SAP under the section “What is SAP?” ( http://www.r3now.com/define-sap ).

I generally try to categorize all system efforts and business functions into one of three “value proposition” buckets–, operational excellence (ERP), innovation (ERP ii), and customer focus (ERP iii).  The ERP context is almost exclusively focused on the “operational excellence” portion of business “back office” transactional processing.

ERP vs. ERP ii — What is ERP ii?

The next generations of Enterprise applications, or ERP ii systems, extend the “back office” ERP system processing to the extended supply chain.  They extend the enterprise into the supply chain outside of their legal entity borders as an active participant. This would include VMI (Vendor Managed Inventory) processing and KANBAN type demand and supply signals to vendors for JIT (Just In Time) stock management.  But it goes far beyond that, it is the “innovation” portion of the value proposition that is addressed here.

SAP includes ERP ii type extended supply chain applications like SRM (Supplier Relationship Management) and APO (Advanced Planning and Optimization) to help move the supply chain beyond the enterprise borders.

ERP II Creates Collaboration Hubs Beyond Planning Functions and Distribution Functions

Together with the extended supply chain applications there are a number of various exchanges such as common catalogs that are published to the web and integrate with their customer ordering.   Some examples of external exchanges can be seen in initiatives such as “Covisint” for the automotive industry, or Grainger’s online catalog system (although it is not a competitive based platform like Covisint), and many others.

One of the key functions or features of ERP ii systems is supply chain or vendor collaboration, which extends to engineering design and development.  Most enterprises using SRM systems use this to focus on cost reductions, vendor competition, and supply chain efficiencies.  They are generally geared to the “operational excellence” system domain but there is a LOT of untapped possibility.

The highest and best use of ERP ii functionality includes active collaboration with vendors to reduce cost, improve quality, reduce extended supply chain cycle times, and even co-engineer (or co-develop) better products and services.

Many ERP ii solutions now include some type of built-in “reverse auctions” where companies can place requirements out for competitive bids in various formats.  These exchanges might include data interchange methods such as EDI (Electronic Data Interchange) or other standards compliant communication protocols, but they are much more, they are active collaboration hubs.  Together with these collaboration hubs, SOA extensions are being used to extend collaboration and engineering design work to the extended supply chain.

How Has SAP Implemented ERP ii System?

SAP has created an entire collaboration network called the SAP Community Network or SCN (http://scn.sap.com) where customers, vendors, consultants, and any interested party can exchange information, ideas, or dialog.  SAP has implemented ERP ii systems internally through the development of specialized vendor partnerships it calls an “Ecohub” (http://ecohub.sdn.sap.com/).  This is a place where vendors, partners, or other firms with specialized SAP solutions can integrate and promote their offerings to enhance SAP’s various software offerings.  Along with that there are code exchanges, “how-to” articles, discussion forums, and many other types of collaborative information exchanges.  This is similar to what I proposed a few years ago when I wrote “SAP, ERP III, SOA — Learning Organizations through Social Media Collaboration.”

Operational Excellence and Innovation Value Propositions

ERP ii systems integrate the external vendors and suppliers into enterprise processes so that they can directly impact productivity, cost, and efficiency.  Some elements of ERP ii include engineering staff augmentation, free or at a very reasonable rate to the “customer company,” and as a value added service from vendors.  For vendors the ability to augment engineering functions can mean customer retention; for the customer companies this may mean higher quality and lower cost products or services.

SAP’s ERP offerings include PLM (Product Lifecycle Management) with CAD integration for several off the shelf CAD programs.  Although the PLM functionality is primarily used for internal engineering processes it can be pushed out into the extended supply chain for collaborative engineering and design.  That collaboration can be used for innovation if it is properly structured and implemented.  This is in conjunction with other integrated application offerings such as SRM and APO.

By extending engineering or collaboration functions outside of the enterprise, but still within the supply chain, innovation can be introduced into the ERP ii enterprise (see the entire series on Process Execution of Business and IT Innovation).   However, the primary feature of ERP ii systems is the additional operational excellence that is brought about by extended supply chain processing.  Very few companies have succeeded at collaborating with the extended supply chain by introducing extended engineering capabilities, or vendor insight to produce significant innovation.  Most ERP ii systems only work to extend the supply chain beyond the boundaries of the enterprise for cost savings and efficiencies (operational excellence).

Using SOA (Service Oriented Architecture) for Creating ERP ii and ERP iii Enterprises

The promise of ERP ii system success that moves toward ERP iii (discussed in a moment) is SOA or Service Oriented Architecture.

In layman’s terms, SOA is the ability to create a set of “talking points” from any internal system to external systems. 

They are the data structures and data schemas that are published for other systems to interact with and begin to create the framework for the “borderless enterprise.”

ERP iii Defined, What is ERP iii and How Does it Go Beyond ERP ii?

ERP iii addresses the final domain of enterprise class applications by addressing the customer focus value proposition.  It is the extension of technology capabilities which brings collaboration with customers and the broader marketplace into the enterprise system.  This goes way beyond what we currently refer to as CRM (Customer Relationship Management) systems of today.  Today’s CRM applications still operate within the walls of the enterprise and are generally used for managing the sales force rather than moving the enterprise out into the wider marketplace and to direct interaction with customers.

ERP iii from a high level is fairly easy to define, however what it looks like in a few years is difficult to predict.  The areas that ERP iii touches are in a rapid state of change because of the dynamic nature of social media and the global marketplace.

ERP iii Defined

ERP applications integrate enterprise operations within and across enterprise legal entities, or company codes. ERP ii applications extend supply functionality to external enterprises (generally vendor-affiliated companies or enterprises) to reduce cost, improve supply chain efficiency, and to perform collaborative innovation.  ERP iii enterprises go to the next level of integrating the ERP and ERP ii functionality to include customers and the sales side of the marketplace in general.

The end state of the ERP iii enterprise would include a dialog between customers (and potential customers), the ERP organization, and the extended supply chain so that even suppliers would participate in the sales side of the marketplace.  Because there is little or no information in the markeplace about ERP iii direction and design I am offering a more detailed definition here:

Through collaboration, direct contact, social media, and various data streams within and outside of the enterprise ERP iii integrates marketplace fans and critics into the extended ERP and ERP ii organizations.  From the integration of customers and vendors beyond the enterprise boundaries a constructive dialog or information exchange is created to innovate, produce, and then sell (or distribute) better products or services.

ERP iii will create the “borderless enterprise” by bringing together a host of technology sources such as:

  • Collaboration tools (within the enterprise and across the supply chain and marketplace)
  • Social media
  • Internet technologies
  • SOA
  • Smart information integration and synthesis (specialized search with analytics or within specific information domains).  An early example of this type of search is a web service called “Lijit.”  Lijit allows you to manually assign searchable information sources for a customized, high value “search engine.”
  • Extended marketing analytics that are “like” tracking cookies but less invasive and use additional sources of information and research beyond the web (a good example is like grocery store checkout programs that automatically print coupons on the back of your store receipts based on what you just purchased).
  • Direct customer collaboration (we see early examples of this in the Dell “designed by me” and “I made Windows 7” television commercial marketing campaigns).

The Future of ERP iii Systems

Within the extended SAP enterprise (which is my area of expertise) I see many of the seeds of ERP iii germinating and beginning to grow.  Even though the initial “green shoots” are there for an ERP iii revolution I don’t anticipate that occurring for several years within SAP.

Today SAP has:

  • Very active, country specific SAP User Groups (xSUG, in America is it ASUG) with “influence councils”
  • Community forums (previously mentioned)
  • “Mentor Groups” within the community network.

While these all contain the seeds of ERP iii outlets I do not see a lot of the raw material being converted into application enhancements to directly address business marketplace demands.  There are still way too many technical solutions for for technical needs and not enough for genuine business needs.

ERP iii integrates marketplace fans and critics into the extended ERP and ERP ii organizations to innovate, produce, and then sell (or distribute) “customer-centric” products or services.

I doubt that the integration of more social media will move the ERP iii needle much further.  SAP like any other company that embarks on this type of transformational exercise must begin to use their well established outlets to drive innovation and to meet marketplace requirements (see the entire series on Process Execution of Business and IT Innovation).

Social Media and ERP iii

Social media outlets like Facebook, Twitter, and other resources will need to become more sophisticated to produce meaningful differences in business-centered innovation or customer focus.  That sophistication for business will mean finding a means to use those outlets for genuine business competitive advantage.

It will take business some time to find new ways to tap into the collective marketplace consciousness through social media in spite of the massive number of what I refer to as “snake oil sales” people.  Social media in the enterprise will not be useful until the snake oil sales finally align actual business needs to areas of the enterprise (sales, marketing, HR recruiting, etc.) that align with business goals and directions (see Social Media Fads and the Risk to the Enterprise).

Before ERP iii systems are ready for the extended marketplace and for customer interaction it will require “back office” integration with social media (see ERP III – Is the Integration of Collaboration the Future of Enterprise Applications).

As social media and collaboration tools mature over the next 10 or more years then corporations will finally build the ERP iii systems for integration into the wider marketplace.  By then the ERP ii systems will have finally matured to the point that some of them can provide meaningful integration between the enterprise, the entire supply chain and the sales side of the marketplace in general.

ERP, ERP ii, and ERP iii Conclusion

Considering this specialized class of business systems through the lens of the high level value propositions of 1) operations, 2) innovation, and 3) customers; here is my summary:

ERP (Enterprise Resource Planning)

Primarily focused on the “back office” with a heavy emphasis on operations, automation, cost control, financial activity, and lagging business indicators of performance.

ERP ii (the second generation of Enterprise Resource Planning)

Extends “back office” processing functions and operations into the extended supply chain with a heavy emphasis on supply chain automation, additional efficiency, more cost control, and some vendor collaboration for limited innovation.  This area of the application moves into the “last mile” of improvements that can be more expensive to implement and yield lower returns.  However, carried out properly with significant supply chain collaboration and joint engineering or development efforts this can provide new / innovative products or services addressing both lagging indicators of cost control and efficiency while exploring leading indicators of new products or services.

ERP iii (the next generation of Enterprise Resource Planning)

This will encompass the integration of social media with new marketplace intelligence and analytics into the ERP ii enterprise.  With a very simply “hub and spoke” idea, the enterprise will constitute the “hub” and the extended supply chain vendors, engineers, and designers, together with customers and market analysis as some of the “spokes.”  This will be enabled by the ERP application that is extended with collaboration and social media tools.  The ERP, ERP ii, and ERP iii functions will all be integrated with new analytics and “smart source” search methods to integrate and synthesize trend, market, and product or service information.  This will close the loop on the ERP ii innovation and will bring a new customer focused business paradigm into the enterprise that goes far beyond today’s CRM applications.

ERP iii state companies will be marketplace disrupters who are agile, nimble, and global.  They will be able to spot emerging trends and unmet customer demands (needs or wants) far more quickly and with greater ability than their peers.  From those trends and customer needs these companies will be able to quickly execute innovation programs to develop new products and services to quickly fill those customer demands.  The most advanced of these new “disruptive innovators” will be the companies who can intelligently synthesize all of the various data points to understand customer demands that are not even articulated.

======================

Bond, B., Genovese, Y., Miklovic, D., Wood, N., Zrimsek, B., and Rayner, N. (2000). ERP Is Dead — Long Live ERP II; Gartner Publications.

Kallinikos, J. (2004), “Deconstructing Information Packages. Organizational and Behavioral Implications of ERP Systems.” Information Technology and People, Vol. 17, No. 1, pp. 8-30.

Related Posts:

Designing startup metrics to drive successful behavior

March 11th, 2010

Great companies are almost always run by great management teams. And great management teams know that the only way to improve a process is to start by measuring it. Good metrics should also be actionable, and drive successful behavior. In this post I hope to help show how to figure out which metrics matter the most, and how to design them in such a way as to drive behavior that will lead to the results that you want.

This post is applicable to any kind of business. In a follow up post, I will use this technique to walk through the design of a set of metrics for a SaaS company. Since SaaS businesses (or any other subscription-based business) are different from standard software businesses, there are some interesting elements that we will uncover.

Think of your company as a machine

One way to look at how companies work is to imagine them as a machine that has Outputs, and Levers that you, the management team, can pull to affect it’s behavior.

image

Weak management teams have only a limited understanding of how their machines work, and what levers are available to affect performance. The better the management team, the better they will understand how that machine works, and how they can optimize its performance (what levers they can pull).

When we look to design metrics, we are looking to deepen our understanding of the machinery, and how it works. Well designed metrics will automatically drive behavior to optimize output from the machine.

Example of a bad Board Meeting to Review Business Success Metrics

Here is an example of a bad board meeting, which happens far more frequently than you might imagine. The company has just missed its quarterly revenue forecast. Good board members want to know two things:

  • Why that happened?
  • What can be done to avoid the problem going forward?

As they ask management what happened, a common answer will be that the market was really tough, and deals just didn’t close the way that they hoped. They also don’t have a great plan for what they are going to do differently next quarter, other than hope that the market improves, and that more deals will close. There is a great saying for situations like this: Hope is not a strategy.

Example of a good Board Meeting to Review Business Success Metrics

The better management teams answer those questions differently. They will gradually peel back the covers of the machine, like peeling the layers of an onion, and expose the true nature of the problem, which of course will also highlight what levers need to be pulled to fix the problem. Lets take an example, and look at how they might do this:

  1.  
    1. They will be able to tell you that revenue is composed of deals. To compute revenue, you multiply average deal size by number of deals. They may tell you that they were targeting to grow their average deal size to $x, and were successful in hitting this target. But the number of deals that they closed was below target.
    2. They will then peel back the onion one more layer, and tell you that the reason that the number of deals was below target was because 1/3rd of the salesforce missed their targets.
    3. They will then peel back another layer, and tell you that the reason those salespeople missed their targets was because they were not handed the required number of trials from marketing. However, for the trials that they did receive they were successful at converting them to closed deals at the expected conversion rate. So we know from this that the problem is not the quality of those sales people.
    4. Peeling back another layer, they will tell you that the number of trials is equal to the visitors to the site x the conversion rate of those visitors to trials. They may tell you that the number of visitors was on target, but the conversion rate fell below the previous levels.
    5. Peeling back one more level, they may tell you that they ran three major campaigns to drive visitors to the site, as well as relying on the normal levels of word of mouth traffic.  They may then reveal the true source of the problem: the ads that they had started running on Facebook were delivering a far lower conversion rate to trials than in prior months.

The contrast between the two approaches is stark. In the second case, it is clear that management will know how to fix the problem (by adding new traffic generation programs). They also know precisely how much additional traffic will need to be generated to reach the growth targets, and how many sales people are needed at a given productivity level, etc. etc.

What is surprising is just how few management teams really have their act in order in this area. For Web and SaaS businesses with smaller transactions at higher volumes, this kind of modeling and tracking is much easier, as web-based lead generation and marketing have easy to implement measurements, and the greater the volume of transactions, the more clearly patterns emerge. This is a little harder to do for channel sales, but still extremely valuable. And a little harder than that for direct sales situations with large deal sizes.

The Secret to Success in Sales Conversion Business Metrics

The secret to successful design of metrics is to start with the end goal and work backwards. In most companies, the end goals that matter the most are:

  • Profit/(Loss)
  • Growth
  • Good cash flow

(You may wonder why we don’t have Revenue in this list, but read further, and and it will soon become clear.)

Let’s take the first of these, Profitability, and work backwards. Working backwards means looking at the components that make up Profitability:

Profits (EBITDA) = Revenue – Cost of Goods Sold – Expenses

So to focus the management team on driving profitability, we should also track and measure Revenue, CoGS, and Expenses. Obvious, isn’t it? Well the good news is that this same principle can be applied over and over again focusing on the components of Revenue, CoGS, and Expenses where needed.

So the next step is to take Revenue, CoGS, and Expenses, and break them down to the key components. Bookings is the pre-cursor to Revenue. So let’s look at Bookings as an example:

Bookings =No of deals closed * Average Deal Size

For Reseller Channels, we might be looking at something different like this:

Revenue = No of productive resellers * average productivity per reseller

(Note: in many businesses there are several categories of deals. e.g. there could be large deals, and smaller deals. Or their could be deals from two or more different categories of customers. So the formula may have more elements to it than shown above.)

Peeling back another level, we might find the following:

No of deals closed = No of productive sales people * Average Productivity per Sales person

There will also likely be another formula to compute this, which will look like the following:

No of deals closed = No of Trials * Average Conversion Rate

These two formulae clearly indicate some of the levers that we have available to increase Bookings. We can grow the number of trials, or grow the number productive sales people, or we could try to increase the average productivity of our sales people. However we need to make sure that we grow them both together, otherwise we could end up out of balance, and have too many sales people and not enough trials to feed them, or too many trials and not enough productive sales people to close them.

The next step would be to peel back the onion a few more layers:

No of trials = No of visitors to the web site * Average Conversion Rate to Trials

No of Visitors to the web site = Normal traffic + for each traffic generation campaign: target audience of each campaign * Conversion Rate to visitors

Each time we peel back a layer to expose the components, we gain a better understanding of our machine and the levers that we can pull to make it work better. For example in the above two formulae, we can see that a big driver of the model is visitors to the web site. But this can be expensive to increase. So the other variable that we can try to increase is the conversion rate for each campaign, and the conversion rate to trials. We can try to do this by altering campaign messaging and landing pages and using A/B testing to find the optimum creative content.

We might also decide to focus our efforts on increasing the average deal size. We could do this in several ways:

  • Cross sell to add additional products
  • Up sell to add seats, or premium features
  • Develop a scalable pricing matrix that does a better job of charging higher end customers that are willing to pay more. This might involve several new axes that increase pricing, such as charging per seat, or charging per 1,000 data elements tracked, or charging for 24×7 support, etc.

As with many good ideas in business, all of the ideas above are obvious, and follow common sense.  However, you would be shocked to discover how rare it is to actually see businesses that have fully peeled back the onion to expose all the major variables and levers, and then implemented appropriate metrics to track these over time.

Sales Metrics Trend based analysis

For every major variable that matters in our model, we will want to track how this varies over time. This will show us if we are succeeding in our efforts to improve things, and also give us early warning signs of any negative trends.

For most stages in a sales and marketing pipeline, we will want to track two metrics: how many prospects we put through that stage, and how effective were we at converting them to the next stage. For example:

Stage in Sales FunnelNo of ProspectsConversion Rate
Campaigns to drive trafficEyeballs seeing the campaignConversion % to Visitors
VisitorsSite VisitorsConversion % to Trials
TrialsNo of TrialsConversion % to Closed Deals
Overall Sales Process
(start to finish)
No of VisitorsConversion % to Closed Deals

 

Sales Pipeline


Peeling back the Onion on Inside Sales performance

Another area where metrics can be extremely useful is in managing an inside sales (telesales) organization. Starting with the overall sales number achieved by the whole group, let’s peel this back layer by layer, to see what we can learn:

  • Overall group performance = Sum (individual contributor performance).

Not surprisingly we need to look at how each individual has done relative to the average levels to understand the strong performers, and the weak performers.

  • Individual performance = No of deals closed * Average Deal Size

For the weak performers, it is likely that the number of deals closed will be lower than we want. The question is why? So what are the components that make up the number of deals that an individual closes? Assuming a sales process where each inside sales person is handed a queue of marketing qualified leads, and then calls these to try to schedule a demo, and the post the demo tries to close a sale, the components will be:

  1. Calls made per sales person (if this is low, they will quickly react to peer pressure when they see other sales people’s call rates)
  2. Conversion rate to returned calls. (If this is low, it means the sales person is not leaving compelling voicemails, and should be given training by someone that has a high conversion rate.)
  3. Conversion rate from phone calls to Demos. (If this is low, it means the sales person’s ability to convey the value proposition is weak, and they should be given training by someone with high conversion rates.)
  4. Conversion rate from Demos to Closed Deals. (If this is low, it means the sales person needs better demo training.)
  5. Average Deal Size. (If this is low, it could mean the sales person needs better training on cross selling, or up selling.)

The above may not mirror your inside sales process, but hopefully the method of working backwards from the end goal, and peeling back the layers to expose the components will enable you to map out the metrics that matter to you.

Sales and marketing funnel – summary metrics

We will also want to look at some metrics that cover the entire sales and marketing funnel from top to bottom. Here are some example metrics that are important at this overall level:

Lead source effectiveness:

  • CAC by lead source
  • ROI by lead source (takes into consideration cost, conversion rates to closed deals, and lifetime value of customers that came through that particular lead source)

What not to track for Successful Sales Metrics

Some categories like Expenses are made up of many line items, and we very likely don’t want to bother with metrics for every line item, we need to answer the question: How deep should we go with our analysis? The answer to this is pretty much common sense:

  • Prioritize the components that have the biggest effect
  • Don’t put much effort into tracking things that you can’t affect
  • Don’t bother tracking items that are small, or that don’t vary much. Leave these to accounting.

Sales, Conversions, Startup Business Success Metrics Conclusions

There is nothing in this article that should be surprising or earth shattering. It is all obvious. However, as is often the case in business, it is really easy to have the vision of what to do, but far harder to execute on that vision. In my experience the mark of a really well run business is that they actually have the systems in place to automatically produce these metrics. And they use those metrics as part of the management process to run the business.

The Benefits: Good Metrics drive Actions and Behavior

One of the greatest things about putting in place the right metrics is that showing them to people will automatically change their behavior to try to improve the metrics.  Furthermore, the metrics make it clear what levers they can use to change performance.

Well designed metrics make it clear what actions are needed to hit plan

Working backwards from a specific Revenue target, management will be able to understand all the other elements that have to be put in place to reach that target. For example, if you want to hit $xm in bookings for the quarter, you can work out:

  • How many sales people are required
  • How many leads are required to feed those sales people
  • What marketing campaign spend is needed to generate those leads

If you are in a channel model, you can work out how many productive resellers are required, and given a known conversion rate from newly signed resellers going through an on-boarding process, you will be able to work out how many new resellers are required, and how many on-boarding sales training sessions need to be run. Etc.

===============================

Re-posted in full with the author’s approval.  The original version can be seen here:

http://www.forentrepreneurs.com/designing-startup-metrics-to-drive-successful-behavior/

For many other excellent posts on business, business success, sales, marketing, and other resources please see David Skok’s excellent site at

for Entrepreneurs

Related Posts:

Why SAP Projects Fail to Deliver ROI and How to Change IT

July 8th, 2009

Why SAP Projects Fail to Deliver ROI and How to Change IT

Part of the frustration with the failure of results in SAP implementations is the “hangover” from the Y2K effect.  At that time businesses everywhere simply wanted to install ERP systems to take care of the looming potential “crisis” over the millennial changeover.  The real promise of SAP was lost in the Y2K chaos.  After Y2K, the brief downturn in demand for ERP systems along with the tech bubble burst in the stock market created additional pressure.  The idea of delivering SAP implementations “better, faster, and cheaper” together with business benefit was lost in the confusion.  

Because so many custom systems had been developed from the era when disk space and memory were incredibly expensive, nearly all programs were written with 2 digit designations for the year.  The fear was that as we approached the year 2000, those same systems might read that date as 1900, have a different day of the week assigned, or not know how to handle the 2 digit date at all.  As a result there was a massive rush to implement ERP systems to manage this issue and to replace legacy systems with “off the shelf” software.  

ERP and SAP, Better, Faster, Cheaper but What About Business Benefit and Business Focus?

Leading up to Y2K the demand for replacement of these legacy systems with new ERP systems was so strong it lead to an almost exclusive focus on implementing SAP projects “better, faster, and cheaper.”  Certainly this is not a bad thing, but business alignment and business drivers got lost in the fog of technical system replacements.  Rather than doing system implementations that were focused on genuine business drivers nearly all ERP systems were installed as technical system replacements rather than being implemented for business benefit.

After Y2K, there was a continued emphasis by vendors and companies everywhere to implement and automate current business processes because that is the sales model (and competency) they had developed.  That sales model worked, presentations, approaches, methodologies, implementation tools, consulting training and prep, everything was centered around the Y2K “get it in” model. Projects focused only on existing business operations and on replacing existing IT systems.  Implementation methodologies and techniques for “better, faster, cheaper” implementations were developed to support these “quick hit” IT system replacements.

While every project should be delivered on time and on budget, the focus on only current business processes fails to address the forward looking nature of business.  Even to this day businesses implementing SAP still fail to see the system as any other kind of a capital asset where you build a business case with both a current state justification and a future state justification as well.  The current state is nothing more than the “on time, on budget” back office operational project requirements while the future state looks at business strategy and builds those into the application as well.  What do you want SAP to help you with in the future?

ERP Technicians Replace Systems – Consultants Use ERP to Transform Business

SAP projects fail to deliver for a number of reasons that have nothing to do with the software itself.  SAP projects that focus almost exclusively on “back office” processes or “operational excellence” find that they use lagging indicators.  These are important for evaluating current company health, and today’s (or yesterday’s, last months, etc.) indicators of marketplace performance, but these lagging indicators will not produce world class results most C-level executives are now looking for from SAP. [FN1] 

Today the marketplace still wants the “better, faster, cheaper” model of delivery, but now CEOs, CIOs, and CFOs are insisting that the application software must do more.  It must deliver something more meaningful. It must deliver strategy and forward looking business benefit.

Leading or Lagging Indicators? 

SAP projects, whether they are new implementations, upgrades, or re-implementations should begin with strategy, goals, and KPIs. In developing goals, KPIs (Key Performance Indicators) and performance metrics there are generally two types of measurement categories–, leading indicators and lagging indicators.  Leading and lagging indicators refer to “timing of cash flows within a corporation.”  [FN2] 

In the past, lagging and leading indicators have been applied almost exclusively to economic output, not necessarily to that of business, but the impact of business on economies. 

Recently, with the rise of the use of KPIs as a method to help drive business goals and strategy, the idea of leading and lagging indicators has been applied to business. In the context of economics, Wikipedia defines these indicators as:

Lagging Indicator  

A lagging indicator is an economic indicator that reacts slowly to economic changes, and therefore has little predictive value. Generally these types of indicators follow an event; they are historical in nature. For example, in a performance measuring system, profit earned by a business is a lagging indicator as it reflects a historical performance; similarly, improved customer satisfaction is the result of initiatives taken in the past. [FN3]

Leading Indicator 

[L]eading indicators are key economic variables… used to predict a new phase of the business cycle. A leading indicator is one that changes before the economy does. [FN4]

The Future of SAP – Strategic Implementation 

To finally realize business benefit from SAP, to achieve that elusive ROI and begin to make a difference in the way your company works, you must change the way you approach your implementation.  [FN5]

The Y2K days of any consultant who could learn to make system settings on the fly to support all those implementations are over.  With them, the thousands upon thousands of application “technicians” who got their start in SAP when the demand was so high may not be able to deliver in today’s tremendously competitive market. After all, now that the Y2K scare is long past, businesses everywhere are beginning to ask the really important questions of “how do we make this huge investment actually provide a return?”

The type of vendor and consultant you employ must have business and application experience.  Today more than ever it is critical to ensure you find the right resources and then do some up front planning and prep work yourself. 

Long before your implementation or upgrade project starts the implementation focus must change. 

While it is great to focus on process improvement, and that is critical in today’s market, it is no longer enough to win in today’s marketplace.  All of your competitors are working process improvement so it will not differentiate you in today’s market.  Does that mean you can ignore it?  Of course not, it still has to be done, but it must be done together with a serious strategy focus to your SAP implementation or upgrade.

Start by looking out at your competitive landscape, where are your company’s strengths and weaknesses in comparison to your competitors?  Are there areas in comparison to them that you are not executing particularly well?  Should you then focus on those processes to improve your competitive position?  In the areas you are doing well against your competition, should you emphasize those?  Are there market opportunities you are missing, or are there gaps in your product portfolio that partnering with another firm might help to fill the gap in?  Is your company large enough that you can change the vendor dynamic for certain key products or services by outright purchasing, or possibly underwriting new competitive vendors to ensure better products and services at better prices?

How do you use SAP to enable all of these processes you’ve just answered these questions to?  How do you develop the key goals and KPIs to meet the new market challenges out there in today’s competitive landscape?  What SAP reports or tools will be needed to support your leading indicators?  What KPIs should you focus on first?

There are many more mountains of additional things you can do to use SAP to achieve genuine business benefit, find that “elusive” ROI and make a real difference in the marketplace.  But to get there take the first step to changing your implementation approach–, start by defining the business reason for your implementation or upgrade before you even begin. [FN6]

[FN1]  Using SAP to improve Revenue and Profitability
http://www.r3now.com/using-sap-to-improve-revenue-and-profitability

[FN2] Bloomberg Glossary, http://www.bloomberg.com/invest//glossary/bfglosl.htm (retrieved 9/21/2009)

[FN3] Wikipedia, http://en.wikipedia.org/wiki/Lagging_indicator (retrieved 9/21/2009)

[FN4] Wikipedia, http://en.wikipedia.org/wiki/Leading_indicator (retrieved 9/21/2009)

[FN5] SAP as a Change Enabler
http://www.r3now.com/sap-as-a-change-enabler

[FN6]  Change How You Look at SAP to create ROI
http://www.r3now.com/change-how-you-look-at-sap-to-create-roi

Related Posts: