[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::digital

Title:The Digital way of working
Moderator:QUARK::LIONELON
Created:Fri Feb 14 1986
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5321
Total number of notes:139771

2357.0. "Revunue Producing vs Non-Revenue Producing Jobs" by GRANMA::MWANNEMACHER (A new day has dawned) Thu Feb 04 1993 09:32

    
    
    Much talk lately of Revenue Generating and Non-Revenue Generating
    positions.  I think this warrants discussion.  What constitutes a 
    revenue generating position and a non revenue generating position?
    
    In my opinion a company should be void of all Non-Revenue Generating
    positions.  The caveat here is that, just because you are directly 
    in the revenue stream (so called overhead) doesn't mean that you are 
    not involved in the revenue process.  If, without your service, the
    function you are performing(billing, software updates shipping, systems 
    development, cleaning the bathrooms) the revenue generating would be
    impeded, then you are part of generating revenue.
    
    In my 7 years at Digital I have seen Non-Revenue generating positions
    and the majority of these positions were in management and management
    support positions.  I know of a system that was developed so as
    managers could have more reports to review, when the information was 
    already available in an existing system.  Not only that, but the
    pre-existing system has to feed the new system which was developed.  
    Point of this last paragraph is to point out that there are Non-Revenue 
    producing things going on.  
    
    Discuss.
T.RTitleUserPersonal
Name
DateLines
2357.1WLDBIL::KILGOREAdiposilly challengedThu Feb 04 1993 11:1259
    
    The concept of revenue-generating vs. non-revenue-generating at most
    levels is a false deliniation. It assumes you can draw a hard
    line, from top to bottom in the company, between those of us who are
    directly responsibile for encouraging customers to give us money, and
    those of us who are not. It induces corporate micromanagement.
    
    Value-added and non-value-added (or perhaps value-added and
    value-subtracted) is a much more useful concept, because it can be
    applied to every business, functional group, cost center, team and
    individual in the company. The key is that you have to be willing to
    delegate the responsibility of making value-added judgements to the
    appropriate level of control.
    
    Stand-by pay is a case in point for the diference between these
    concepts. Recently, a high-level corporate decision was made to change
    the stand-by pay policy, to the effect that people who are directly
    supporting customers receive stand-by pay, while people who are
    supporting internal folks do not. This was a deliniation drawn at the
    corporate level based on revenue generation, and does not reflect any
    judgement of value added. There is no doubt in my mind that having
    people available on demand to customers encourages those customers to
    give DEC more money. But what about the people who used to be available
    on demand to fix network or node problems and thus help speed the
    development and delivery or a product to the market? Does timely
    delivery of products not also encourage customers to give DEC more
    money? And how can the corporate decision makers determine the relative
    value added in these two instances?
    
    My understanding of the New DEC is that business units will sell
    products to customers, and contract engineering groups to build the
    products that they deem sellable. Does that mean that the business
    units are revenue-generating, and the engineering units are
    non-revenue-generating? Does that mean that people in business units
    will be eligible standby-pay, second phone lines to their homes, and
    pencils and Post-Its, and engineering units will not?
    
    In a value-added model, the corporation can decide which business units
    bring in more revenue, and support those business units. Business units
    can decide which products will add more value to their portfolios, and
    contract engineering groups to build those products. An engineering group
    can decide what services it needs to build a product, and contract with
    appropriate service groups. A network service group can decide whether it
    is more useful to use stand-by pay or additiona shifts or other incentives
    to provide the services required by its contract.
    
    I know this is going to sound like heresy, but it is not the ultimate
    responsibility of everyone in this company to generate revenue. The
    business units and up-front sales folks generate reveuue; that is their
    ultimate responsibility, and their value-added work should revolve around
    how best to generate that revenue. The ultimate responsibility of
    everyone else in DEC it to support the front-line revenue generators,
    or the next group up in their particular location in the supply line to
    the front-line revenue generators; their value-added work should be
    tightly focused on meeting the requirements of the next group up the
    line. Forcing revenue-generating deliniations too far down in this
    model (ie, below the first level) tends to remove some of the options and
    resources but none of the responsibilities.
    
2357.2Hmm, micromanagementNEWVAX::MZARUDZKII AXPed it, and it is thinking...Fri Feb 05 1993 07:0910
 >>>The concept of revenue-generating vs. non-revenue-generating at most
 >>>levels is a false deliniation. It assumes you can draw a hard
 >>>line, from top to bottom in the company, between those of us who are
 >>>directly responsibile for encouraging customers to give us money, and
 >>>those of us who are not. It induces corporate micromanagement..
    
    Agree. Some interesting quotes come to mind from a hard-liner
    "if you don't touch the mail, your overhead". Apply that literally
    to a certain entity and see what happens.
    -Mike Z.
2357.3Managers will be managersESGWST::HALEYbecome a wasp and hornetWed Feb 10 1993 15:5721
re: .2 
   
>    My understanding of the New DEC is that business units will sell
>    products to customers, and contract engineering groups to build the
>    products that they deem sellable. Does that mean that the business
>    units are revenue-generating, and the engineering units are
>    non-revenue-generating? Does that mean that people in business units
>    will be eligible standby-pay, second phone lines to their homes, and
>    pencils and Post-Its, and engineering units will not?
    
I think this will free up the engineering managers to do what they think 
best.  If spending money on post-its, WSs for home and phone lines help 
them generate "better" (earlier, higher quality, less expensive) products 
than they would be silly not to approve them.  I think that they will find 
another scape goat, however, as the real blocks are not the "corporate" 
penny pinchers, but the lack of effort on these issues by the very 
engineering managers that are complaining.  I see little effort in 
protecting the individual contributors by most engineering managers and 
consulting engineers.

Matt