Discussion: View Thread

  • 1.  Selecting Projects

    Posted 10-13-2001 18:24
    Jay,

    Suggest you look at www.robustdecisions.com.

    Dr. Ullman was motivated to develop this decision aid to help designers
    make choices but it is sufficiently general to address your needs.

    The software only does the math, of course, so Dr. Ullman provides a
    "Twelve Steps to Better Decisions" the first half of which tells how to
    discover the important attributes of the issue under decision.

    Interestingly, when several people participate in the decision process
    the inter-group variances that arise illuminate the issue even more.

    If you are looking for a pre-canned checklist of factors to consider in
    making such product choices, see the client's statement of Strategy,
    Objectives and Initiatives or their Balanced Scorecard items. If the
    client has neither of these then giving them a project selection method
    is a lot like arranging deck chairs on the Titanic.

    But if they are still worth it the general checklist can be extracted
    from "Response Ability" by Rick Dove, Wiley, 2000.

    Jack Ring

    ----- Original Message -----
    >
    > Date: Fri, 12 Oct 2001 15:36:36 -0500
    > From: Jay Warner <quality@a2q.com>
    > Subject: Application Question for Mgt professors
    >
    > Dear MG-ED-DV professors and practioners,
    >
    > A client wants to put some organization into their project selection
    > process - for manufacturing development level projects. They are
    quite
    > sophisticated in terms of technical aspects of execution for each
    project,
    > but true to form, there is a gap between that and the selection of a
    few
    > projects from the raft of potential. I'd like to help them with
    something
    > that will assure they have considered the major issues in a
    > tabular/organized way, but at the same time, will not result in
    'analysis
    > paralysis' at this early point.
    >
    > Once upon a time I watched a Research Director build a matrix of
    issues,
    > estimated probability of technical success, anticipated market payoff,
    > etc. Something like this _might_ work, but I'm sure that better/newer
    > organizational approaches are available today.
    >
    > Can you (plural) point me toward some references to such methods?
    Perhaps
    > something in Research Management has done it already.
    >
    > Jay
    > --
    > Jay Warner
    > Principal Scientist
    > Warner Consulting, Inc.
    > 4444 North Green Bay Road
    > Racine, WI 53404-1216
    > USA
    >
    > Ph: (262) 634-9100
    > FAX: (262) 681-1133
    > email: quality@a2q.com
    > web: http://www.a2q.com
    >
    > The A2Q Method (tm) -- What do you want to improve today?


  • 2.  Selecting projects

    Posted 10-13-2001 18:49
    From: Michael Cook [mailto:michaelscook@hotmail.com]

    Jay Warner asked for some information on project selection processes,
    and
    Fred Nickols added some cogent comments. Fred pointed some of the
    difficulties with cost/benefit and ROI analyses: bogus numbers that
    reflect
    the biases of whomever is defending/attacking the proposed project. To
    round out these rational, economic-based methods, payback (how soon will
    we
    recoup the development costs and begin to make a profit) is another
    analytic
    tool. Presumably, when faced with a choice, you select the project with
    the
    earliest payback. But, what if the alternatives have a higher overall
    ROI,
    or a better cost/benefit ratio? And, of course, payback suffers from
    the
    same problem of bogus numbers as does ROE and cost/benefit.

    I have also seen discussion of the MiniMax theory (minimize the maximum
    loss--never take on a project, that if unsuccessful, would result in
    bankruptcy).

    Having worked at consulting firms for over 15 years in which proposal
    decisions--which projects to bid, and at what price--were a weekly, or
    even
    daily decision, a successful selection process is more of a decision
    tree
    than anything else.

    First, do we have the capability of performing the project--do we have
    the
    people, material, $, etc. to be successful *given what we are already
    doing,
    AND our likelihood of winning other work we've already bid on/selected*?
    If
    we don't have the resources could we get them by the time we would have
    to
    start?

    Second, can we perform the project without destroying the company, or
    the
    staff morale? For example, we might win a project that would require
    everyone to travel all of the time, but would they do that, or would
    they
    quit?

    Third, can we make a profit? If so, is it more profit than something
    else
    we might do? This is the only really rational economic step, and, of
    course
    it can suffer from the bogus numbers problem. But generally, profit is
    pretty simple--will we make money?

    Fourth, is there some other benefit that distinguishes this project from

    others, such as market entry, market share, standing in the community,
    or
    large potential future profits? For some firms, "fun" or professional
    interest might also be included here.

    Finally, is there some special negative/cost that distinguishes this
    project? For example, could it make current clients/customers unhappy
    or
    could it result in conflict with external groups ("Hey kids, lets open a

    hazardous waste landfill in _______")?

    And after all that, you go with the one that the senior vice president
    wanted to do all along....

    Michael S. Cook, Ph.D., PMP
    Colleague Consulting
    8318 Gentle Brook Court
    Laurel, Maryland, USA 20723
    301-498-6719
    Technical and management training and performance improvement