Category Archives: Procurement Damnation

Influential Sustentation 97: (Traditional) Analysts

There are a number of influential damnations, but as per our post last yer, analysts are among the worst. Why?

  • Analysts are the Gatekeepers of the Gold Seal of Approval

    Just because you have this great new product that contains at least half a dozen innovative features and functions not (yet) found in the competitors’ products, and just because you built one of the best solutions on the market, that doesn’t mean that you will even get a mention in the back pages of a local business journal until it gets a star of approval as an “emerging” solution.

  • If You’re Not on Their Lists, You’re Not on BigCo’s List

    The best way to get coverage, paid or otherwise, is to get a big win. But a big win won’t happen until a big company adopts your solution and gets a big result it wants to advertise to the world. But the chances of a big company even including you on an RFx are slim to none if you’re not on an analyst’s shortlist.

  • If You Won’t Pay to Play, You Might Never Get on the Analyst Firm’s Shortlist

    Analyst firms have two major client pools: BigCos that want to buy the best (tech) solutions and TechCos that want to supply those solutions. BigCos pay for access to the research library and analyst time and TechCos also pay for access to the research library and analyst time to help them draft an attractive roadmap. As a result, the TechCos that get the bulk of consideration are the TechCos that are (big) customers.

  • If You’re Not a Big Client, Good Luck Making the Perilous Pyramid

    Even if you happen to get the attention of the lead analyst on the research report and even if the lead analyst likes you, if your solution is too much of a threat to the research firm’s big TechCo clients good luck meeting the bulk of criteria for inclusion. Minimum revenue, core modules, absolute feature lists, etc. tend to change year to year in a manner that tends to keep big TechCo clients in and keep their biggest threats out.

So what can you do (especially if you don’t have the ability or inclination to write a cheque with a lot of zeroes)?

Be Open.

Don’t be ultra secretive. Don’t shy away from demos. And definitely don’t ask for an NDA. (Which, by the way, is really, really stupid. How can they write about you if you tie them up in an NDA?) Just like customers like a provider that is open and honest (and focussed on helping them solve their problem, not force-feeding a canned solution down their throat), so do (good) analysts.

Be Educative.

Educate them on what you do, why you do it, and why it’s important. Case studies, calculations, efficiency improvements, cost reductions, ROI(C), impact on WACC, etc. Make sure the analyst understands the value to the customer, how much comes from the uniqueness of your offering, how you will educate the customer to help them do better, and how you will continue to improve the solution.

And Be Prepared to Use the Back Door.

If the analyst in question doesn’t care about openness and education, find an analyst that covers an overlapping area in the same firm who is. Especially one that knows she needs to learn and is willing to listen. They can be your way in, and can often hold more influence over their peers than any pay check you could provide.

Why Good Procurement Goes Bad. Part II.

Most poor-performing Procurement departments don’t start out bad. They start out with the intentions of doing a good job, at least as good as any other department in the organization (although not necessarily a better one), but somewhere along the way, they stumble, and sometimes fall. And since there are not enough best-in-class Procurement organizations, (8% is a small number), and since there are theoretically more good people out there, we have to ask: why does good Procurement go bad?

Yesterday we covered two major reasons good Procurement departments go bad: strategic blinders (like Excel, where nothing good happens) and efficiency over effectiveness (where process is adopted for process sake and no other reason). Today we’re going to cover two additional reasons.

Relationship Blinders

Sometimes a good Procurement department will start by segmenting spend into strategic and non-strategic, do the right thing and start negotiating the strategic, and then treat those suppliers as strategic suppliers. When the suppliers deliver a more consistent, somewhat higher quality product, at a lower price than was delivered before, those suppliers will be looked upon as partners and, as the relationship cements, the relationship will not be questioned over time. Contracts will auto-renew at annual increases to cover “inflation”, but sometimes the “inflation” will also cover “margin inflation” and the quality of the product will not increase.

Even strategic relationships need to be reviewed and the suppliers subjected to a (360-degree) scorecard. The supplier might still be the best choice, but needs to know that the relationship is being monitored and the goal is that both parties continue to benefit, not just the supplier.

Plus, if a customer never goes back to market, it will never know if new suppliers with production capabilities and innovation capacity hit the market and if some of the award should be shifted to a new supplier to help them become a strategic supplier for the organization’s next generation of products down the road.

Values become Dogma

Values are good things. They should be respected, adopted, and implemented. But they should never become dogma. For example:

Relationships first
is a great idea, especially with strategic suppliers. But, as per above

Relationships above all else.
can blind an organization to faltering performance or better alternatives. Similarly:

Value-add
is great to get in every negotiation and can be a differentiator but

Value-over-customer-desire
can simply increase cost. If the customer is buying a “disposable” product that they plan to replace in a year, they may not want a two-year warranty, and focussing on “value” that the customer doesn’t want just increases cost.

There are other examples, but you get the point. Just like an organization can go process-crazy, they can also go dogma-crazy. Too much becomes as ineffective as too little.

For a Procurement organization to get good, and stay good, it has to reevaluate its processes on a regular basis and not get blinded by its own good intentions.

Why Good Procurement Goes Bad. Part I.

Most poor-performing Procurement departments don’t start out bad. They start out with the intentions of doing a good job, at least as good as any other department in the organization (although not necessarily a better one), but somewhere along the way, they stumble, and sometimes fall. And since there are not enough best-in-class Procurement organizations, (8% is a small number), and since there are theoretically more good people out there, we have to ask: why does good Procurement go bad?

Strategic Blinders

The first thing a new(ly formed) or re-staffed Procurement organization does is try to get organized. As they have not yet acquired a Procurement tool, been given budget for a Procurement tool, or even know the right tool exists, they turn to the tool they know — the spreadsheet. Spreadsheets really limit a Procurement professional’s view of what can be done with modern technology — how efficient Procurement can be, how effective they can be in their negotiations with correct and properly weighted bid and survey data, and how complete they can be in their supplier evaluations (as they don’t have to rely on one size tis all surveys for each supplier, which easy supplies different products and services). Spreadsheets are a Technological Damnation, often result in 20 Million in the scrap-heap, and sometimes cost you billions. There’s no such thing as good spreadsheets. The strategic technology choice to get started is often the technology choice that ends it all.

Efficiency over Effectiveness

Process is good, often very good. It increases efficiency, creates operational standards, and provides a repeatable baseline for junior buyers to follow. And no organization should be without processes. But sometimes, in their haste to be the best, Procurement departments wanting to do as much as they can as fast as they can often rush to get as many processes as they can in place to be as efficient as possible. But not all processes, even best-practice processes, are right for the organization. Adopting the wrong process and running with it can hinder Procurement’s effectiveness beyond no process at all. Having a process that all spend between 20K and 200K goes to an auction, while efficient, will be very ineffective if the wrong categories are put to auction.

Another process that blinds Procurement departments trying to get spend under control is the classic 3-bids and a buy. It is better than no bids at all, but there right number of bids is not always 3. For some events it’s 30 — as many supplier who can supply satisfactory non strategic products. For some events it’s two — because the strategic nature of the custom-manufactured nature means that only a couple of suppliers are up to snuff to start producing today.

And even if the process was good in the beginning, a process that goes unchanged for years and becomes an unquestioned routine can miss new opportunities. Gathering the same old, same old intelligence from the same old, same old sources can miss new intelligence from new sources that could identify new, innovative suppliers and products that could be game changers.

These are just a few reasons good Procurement goes bad, but not the only reasons. In Part II, we will explore more.

Societal Sustentation 52: Project Management

Good project management is the key to success. After all, without good management, the chances of a project over-running its resource allocation (of time, people, and money), if not failing, increase significantly. So, despite the fact that project management is a sustentation, it can also be a damnation. Especially if you can not manage the project.

One has to remember that project management has evolved over the last six decades or so to manage traditional types of projects that produce structures and goods against well-understood designs and project plans, starting with the need to effectively manage complex engineering projects in areas that include construction, defence, aviation, and shipbuilding.

When project management was being defined, the ENIAC was still in operation, Procurement was placing an order against a printed catalogue, and a company imported a small number of commodities in which they had contacts and expertise. There were no complex software projects, no complex Just-in-Time supply chain projects, and no automated factory mega-projects (which resulted in some of the biggest supply chain failures in history).

Where software development is concerned, there is a rough definition of what is desired, but the beginning and end is a best estimate that is no more accurate than a wild guess in some cases, the resources required (while defined as software architect, developer, network specialist, etc.) are not well understood (as a non-skilled software architect cannot define what makes, or identifies, a good software architect), and the amount of money required is relatively unknown (due to uncertain work effort requirements, unknown support requirements, etc.).

And that’s just software. When it comes to supply chain, the difficulty is intensified. There’s the management of the sourcing, the management of the negotiation and contracting cycle, and the management of the procurement. But before that, there’s identifying the right supplier, which requires detailed understanding of the product technical requirements and the supplier production capabilities. There’s identifying the expected costs, based upon understanding material costs, labour costs, energy costs, tariffs, and overhead. There’s managing the supplier relationship. There’s dealing with disruptions and disasters. And taking corrective actions.
In other words, supply chain projects don’t have well-defined beginnings. Don’t have well-defined endings. Don’t have well-defined workflows. Aren’t limited to a fix set of resources. Don’t always have a well-defined team. And don’t always have a well-known cost (even if there is a target one).

But that doesn’t mean there is no hope. There are steps you can take to maximize project success.

1. Document all the steps.

For example, if it’s a sourcing project, outline a detailed process from needs identification, through sourcing plan, supplier identification, sourcing, contracting, and supplier management. Each of these steps have been done before, and, on a step-by-step basis, the complexity, necessary timeframes, and risks can be fairly well estimated. If the expected time-frame is more time than you have, then you have to either simplify the project, or increase the risk.

2. Crystallize and clarify all the risks — and mitigations.

What are the risks in the project from a supply disruption point of view? Liability point of view? Supplier point of view? Contract point of view? Make sure the risks are clear, the potential repercussions clearer, and the mitigations the organization can, is, and will take perfectly comprehensible.

3. Implement Effective Change Management

Document all the hiccups that occur (for future learning), and when something happens that requires a change in process or timeline, be sure to document it, the change, and work out the updates to the plan. Don’t play it by ear or wing it, because it’s easy to mis a beat against background noise or get caught on a wire. Make the effort to manage the project, and your project management skills will improve.

4. Get Training

There is a very big Project Management Body of Knowledge (PMBOK) offered, and certified, through PMI and a lot of organizations that are expert in project management, including a few niche consultancies well versed in best practice in best practice supply chain management in the areas of sourcing, procurement, contract management, etc. Engage one and get the knowledge your organization needs to manage better software projects.

5. Use a Tool

Some modern suites offer integrated supply management project management capability and if your suite, or custom assembled best-of-breed platform doesn’t, there are best of breed providers focussed purely on sourcing and procurement project management, like Per Angusta. Get a solution, and use it.

Organizational Sustentation 59: Warehouse Management

This warehouse frightens me … still
Has me tied up in knots …

Dave Matthews Band

And, as per our damnation post, if your warehouse doesn’t frighten you, obviously you haven’t taken a really good look at it. The warehouse is responsible for inventory, and inventory is very costly … even when it is well managed. Many studies of inventory (carrying) costs have estimated inventory costs to be 25% of the value of the average inventory level (or more). That’s huge!

But this is not the only reason the warehouse is a damnation. It is also a damnation because the warehouse controls:

  • product availability

    and can take their time unloading product, packing product, shipping product, etc.

  • the final quality check

    and if they get lax, and don’t independently test the spinach, your company could be blamed for the next salmonella outbreak that is actually the fault of your supplier

  • overhead costs

    inventory, operations, etc.

So what can you do? Let’s start with the obvious:

JiT (Just in Time) Inventory

The less excess inventory on hand, the less inventory carrying cost, the less inventory for the warehouse to lose or damage, and the less overhead cost to consider.

VMI (Vendor Managed Inventory)

Sometimes your vendor can manage inventory better than you can, and if their revenue is dependent on good management, they are very incented to manage it well.

But that’s just the start. You can also:

Get (a) Lean (assessment).

Identify the inefficiencies, and make sure something is done about them to keep efficiency up and overhead costs down. Make sure the organization is focused on lean transformation and continual process improvement.

Get external audits (on operations and inbound product).

Not only to keep the warehouse in check but to help them identify areas for improvement.

Get the Warehouse Training.

It’s not only Procurement that never has enough in the training budget, it’s the warehouse too. Management thinks that because it’s a manual job, it’s a low skill job and little training is required. Maybe, but considering that lean, six sigma, and kanban processes can greatly improve efficiency and minimize costs, it doesn’t hurt to make sure that the processes, and the labour implementing them, have all the knowledge they need to be as efficient and effective as possible.