Category Archives: Best Practices

Sourcing the Day After Tomorrow Part XV

In this series we are doing a deep dive into the sourcing process today, and, in particular discussing what is involved, what is typically done (manually), and whether or not it should be that way. We have already completed our initial discussion of the initial project request review phase, the follow up needs assessment, the strategy selection phase, the communication phase, the analysis phase, and the negotiations phase. Now we are in the final contracting phase. At first glance, it looks like this is the second most strategic and human-driven phase there is, second only to negotiation, as it is humans (and lawyers in particular) who typically define standard terms and conditions, humans who identify risk and mitigation strategies, humans who define obligations, and humans who analyze the contract for compliance to goals. But is this the case?

So in this final step, the contract step, we have these final sub-steps:

  • Standard Terms and Conditions
  • Modification & Risk Mitigation to Supplier & Country
  • Key Metadata definition and obligation specification
  • Contract Analytics

If all of the standard terms and conditions are in existing contracts and the contract clause / template repository, there’s no reason that a system cannot automatically scan the contracts and repositories, identify the standard organizational terms in every contract, identify the standard terms for the category, and identify any terms, often not included, that would be relevant to the category. Probabilities can be applied and contract terms organized by weight. The buyer can then just bulk select or bulk reject the relevant clauses.

In the modification and risk mitigation step, a contract analytics engine can be applied to determine how well a particular clause addresses a certain risk of relevance to the organization based on context models and differentials. It can then compare that clause to the clauses that best address the risk and identify the necessary modifications, and do so specifically from a supplier or geographic context.

In the key metadata definition and obligation specification step, the goal is to identify the right metadata that needs to be tracked against the contract. This will be dependent on the terms and conditions, the goals, the obligations, and other key information that will be specific to the contract. However, contract analytics can identify, or at least suggest, much of this as well automatically based upon similar contracts, similar terms, similar goals, and similar obligations. This can greatly reduce the effort required by a buyer.

In the final step, the contract analytics step, the identification of risks, variances from a norm, and non-standard clauses can often be better identified by a contracts analytics engine that can cross-compare potentially risky clauses and variant clauses across hundreds, if not thousands, of contracts and identify deviations from the norm. A user just has to decide whether the variance is enough to be of interest to them, and properly setting a threshold can eliminate the majority of those variances that are not.

In other words, at the end of the day, contract analytics identifies the majority of standard terms and conditions that are of interest, the majority of standard clauses that will need modifications to address supplier and country risk, the relevant metadata and obligations associated with the contract, and any clauses that can be considered variant enough to warrant special consideration.

The majority of the work can be automated with a good contract analytics engine — the role of the buyer is to apply their intelligence to determine how accurate and effective it is. As the buyer trains the engine, it will become more and more accurate over time and the strategic work will be reduced to hours, sometimes minutes for simple contracts, compared to days or weeks.

In other words, the more we explore the sourcing process, the more we find out how truly tactical, or at least automatable, the majority of it is.

Sourcing the Day After Tomorrow Part XIV

In our series to date we have recapped Sourcing today and taken a deep dive into the key requirements of the review, needs assessment, strategy selection, communication, analysis, and negotiation phases. In each of these six steps to date, we found that while some steps were critical for a sourcing professional to undertake, others, while necessary, were a complete waste of skilled talent time as the majority of the tasks could be automated. And while we’re still at the point where some tasks have to be done by humans whereas no matter what, we’re almost certain that this is true across the entire sourcing cycle, but until we complete our analysis, we can’t be 100%, so that is what we’re going to do today and tomorrow.

So in this final step, the contract step, we have these final sub-steps:

  • Standard Terms and Conditions
  • Modification & Risk Mitigation to Supplier & Country
  • Key Metadata definition and obligation specification
  • Contract Analytics

In the standard terms and conditions step, the buyer identifies all of the organizational standard terms and conditions that are relevant to the product and services in question. This involves reviewing the standard conditions proffered by legal, previous contracts, and standard contracts put forward by competitors and selecting those that are relevant.

In the modification and risk mitigation phase, the buyer identifies which standard terms and conditions, prior contracts, and suggested terms (defined during the early phases) need to be modified to address risk on a supplier and/or country basis and makes some suggestions as to what needs to be done.

In the key metadata definition and obligation specification phase, the buyer needs to define the metadata that needs to be tracked against the contract, how it needs to be tracked, where it needs to be used, and even how to generate value from the metadata.

Finally, the user needs to analyze the contract for risks, variances, and clauses that are non-standard, identify, catalog, and track them over time. Plus, the user needs to determine the relative risks, variances, and clauses relative to other contracts to determine overall priority.

This sounds pretty buyer intensive and strategic, right? Not much room for automation, right? Well, we’ll find out in our next part!

Sourcing the Day After Tomorrow Part XIII

In this series we are doing a deep dive into the sourcing process today, and, in particular discussing what is involved, what is typically done (manually), and whether or not it should be that way. We have already completed our initial discussion of the initial project request review phase, the follow up needs assessment, the strategy selection phase, the communication phase, and the analysis phase. Now we are in the negotiations phase. At first glance, it looks like this is the most strategic and human-driven phase there is — as it is us who do the negotiations, figure out our BATNA (best alternative to negotiated agreement), and determine what facts we will use in our negotiations, but we have been fooled before.

We are now discussing the negotiations step, which has the following steps that have to be completed every time (and not just sometimes):

  • Format Selection (online, offline, hybrid)
  • Fact Prep
  • BATNA fallback
  • Audit Trails

Let’s start with format selection. Sure, it’s the buyer who selects the format, but, like strategy selection, the selection of negotiation format also depends on should cost analysis, market costs, supply vs. demand market trends, and previous performance of options in similar situations — all of which could have changed since the initial event was kicked-off. Depending on the expected savings or value expected, it may not be worth the in person negotiations. And who’s better at computing the costs, computing the trends, computing the variance of current supply market context against previous contexts, extracting the differential savings between contexts, and generally at doing hundreds, thousands, and millions of calculations. The machine. In this phase, the platform could do all of these calculations, apply a few probabilistic models, and come up with a ranked list of the best options under a well-defined set of assumptions. Most of the time, especially when market costs and trends change slowly, the buyer will be able to review the options, validate the assumptions, and choose one of the best options and have the system automatically generate a report that validates their format selection. It’s a strategic human decision, but one that can often only take a few minutes after the machine takes days (or weeks) of work away.

Now let’s move onto fact prep. In this phase, once the senior buyer has selected the format for the negotiation, and revised their expectations, they need to gather all of the facts in one place that they expect will assist them in their negotiations. Besides deciding what they need, this is a very tactical phase of information gathering and consolidation — which is something the machine is best suited for. In addition, based on all of the decisions made to date, if previous events were captured as well as materials selected and used, the machine can also apply probabilistic models in this step to determine which facts will likely be most useful to the buyer and auto-generate a suggested “fact-book” (outline) that the buyer can update with minimal effort. Then, with one press of the button, all of the information they want in the negotiations is at their fingertips.

Before negotiations actually begin, the buyer will finalize their BATNA. While the best buyers will actually start outlining this during the strategy selection phase (as it will need to be executed as soon as the strategy fails, which typically won’t be until negotiations, but if the event tanks in the communication phase (not enough suppliers respond to the RFQ, prices don’t decrease from initial bids in the auction, etc., it may be sooner — and if its sooner, the phases between failure and BATNA get skipped), they won’t finish until just before the first volley of negotiations get underway (as market dynamics can change significantly between the start of a complex project and the negotiations, even with a lot of machine assistance, because the need to involve a lot of stakeholders can draw an event out and the reality that an unexpected mine or factory closure can happen at any time can flip market dynamics on a dime).

So how does one determine a BATNA? One way is to select the next best strategy (extend the current agreement, spot buy — possibly with an auction, use an alternative product design that would allow for a new event, etc.), and as we know from Part VII, the machine can help greatly in this step as it is capturing all the knowledge to run probabilistic models to rank the next-best alternatives under current assumptions.

And last and not least we have unalterable, secure, always queryable audit trails. We all know most modern enterprise systems were made for this. Nuff’ said.

In other words, the more we explore the sourcing process, the more we find out how truly tactical, or at least automatable, the majority of it is. But we’re still not done, so in our next two parts we will explore the last phase — creating and signing the contract.

Sourcing the Day After Tomorrow Part XII

In Part I we recapped Sourcing today, in Part II we did a deep dive into the key requirements of the review step as it is today, and then in Part III we did a deeper dive where we explained that while some steps were critical for a sourcing professional to undertake, others, while necessary, were a complete waste of skilled talent time as the majority of the tasks could be automated. Then in Part IV we began our deep dive into the needs assessment phase which we completed in Part V. This was followed by a deep dive into strategy selection in Parts VI and Part VII, the communication step in Parts VIII and IX, and the the analysis step in Parts X and XI. And upon review of these steps, we’re still at the point where some tasks have to be done by humans whereas others can be mostly automated. We’re becoming fairly confident that this is true across the entire sourcing cycle, but we can’t be completely sure until we complete our analysis, so that is what we are going to do this week.

In the next step, the negotiations step, we have the following primary sub-steps:

  • Format Selection (online, offline, hybrid)
  • Fact Prep
  • BATNA fallback
  • Audit Trails

In the format selection step, the senior buy decides the primary format in which the negotiations will take place. If it’s a low dollar or non-strategic buy, the buyer might conclude that the negotiations can take place entirely on line through offers and counter-offers, through a system that can ensure offers and counter-offers cannot be altered If it’s a high dollar strategic buy, the buyer might decide that all negotiations and communications of any kind must take place in person behind sealed doors. And if’s somewhat important but only mid-price, the buyer might decide that initial communications, offers, and counter-offers can take place on-line through a secure platform with unalterable audit trails and when both parties at least have a solid understanding of the other side, final negotiations will take place in person.

In the fact preparation phase, the buyer undergoes the collection of all information that could be relevant in the negotiation. Market costs, should cost models, supply and demand trends, customer needs, supply alternatives, and so on. This will consist of the relevant information collected in previous steps from the market, the supplier, and the organization’s systems. It will be synthesized into a cohesive set of documents, tables, and facts that can be used in negotiations to the benefit of the buyer so that, at the ver least, the buyer enters negotiations with knowledge.

In the BATNA phase, which stands for Best Alternative To Negotiated Outcome, the buyer determines what the backup plan is if the negotiation does not conclude successfully and lead to an agreement which is captured in a contract (which, even though listed as a separate phase, is a simultaneous phase that occurs during the lsat step of negotiations). Will the buyer take up negotiations with another supplier, temporarily buy on the spot market, or try to extend the current contract? If it’s a spot buy, will it be through a one-time auction or through a catalog from a non-preferred / non-contract vendor? If negotiations fail, especially if time-lines are tight, the buyer needs to be able to put a back-up plan into place quickly. Plus, if the buyer has a back-up, that limits the pressure that the supplier can put on the buyer.

Finally, the audit trail is not so much as a phase as the collection of the output of each step of the back and forth negotiation (which could take anywhere from 1 to n steps, for n quite large) that occurs between both parties. This step tracks who made an offer, who made a counter offer, who commented on the offer or counter-offer, what information was revealed by a party (or counter party), and does so in a secure, unalterable, queryable fashion that can be reported on at any time.

Except for the auditing, which you expect systems can automate, this sounds largely human driven as we choose the negotiation format, we need to get our facts in order, and we need to determine the best alternative to negotiation agreement, but, as we’ve discussed during previous steps, sometimes what sounds human driven isn’t. Sometimes it’s just human verification. But this is a subject we will explore in Part XIII!

Dear Big Co. Here’s Why Your Contracts Suck …

… and why no one wants to sign them, yet alone even read them!

And since all contracts should be written in plain English (or, if between two parties whose native language is Elbonian, in plain Elbonian, for e.g.), at a senior high school reading comprehension level, we are going to write this post in plain English too.

They are too long. No one wants to read 100 pages of your lawyer’s hyperbole rhetoric that is, in common terms, the literary equivalent of a steaming pile of cow dung.

You read that right. No one wants to read 100 pages of your lawyer’s hyperbole rhetoric that is, in common terms, the literary equivalent of a steaming pile of cow dung.

Furthermore, at least 90 pages of this is guaranteed to be completely unnecessary (and you should feel ashamed at the money you wasted paying your high powered corporate lawyer to write it in the first place).

Let’s go back to the purpose of a contract.

To clearly specify

  • the obligations between two parties,
  • the benefits to both parties from meeting their respective obligations, and
  • the recourse available to one party if the party defaults on the obligations of the contract.

In plain English, even English written by the bard himself, how many pages does that take? Even in the most sophisticated of transactions with a list of obligations by both parties, probably not more than a few pages. (Now, if you are contracting for the construction of an office building, you might need hundreds of pages of addendums on architectural, structural, municipal, etc. requirements, but that’s not the heart of the contract. This can be clearly captured in a sentence that states party X agrees to build the structure required by party Y, as clearly detailed in appendices A through T that detail obligations 1 through 20 respectively, do so for a fixed fee of Y M, and delivery by due date, with penalties accruing at the rate of Z00 K per month. Simple, eh?)

After you’ve specified the mutual obligations, there are only three other requirements for a contract:

  1. Requirements of your Insurance Company
    If your insurance requires limitations of liability, certifications, etc. to explicitly be included for it to remain in effect, you include these requirements, and only these requirements, and only to the extent required.
  2. Requirements of the jurisdiction in which you are operating your business
    If you are doing business in the US, and you are buying technology that could possibly fall under ITAR (for example) if certain requirements are not adhered to, then it must be contractually clear that the products will be designed to adhere to those requirements. (Encryption will not exceed a certain level, etc.) Furthermore, if there are regulations against human trafficking in the supply chain, taking measures to insure denied parties do not receive financial payments, etc. that must be adhered to, then these are included as well.
  3. Requirements of any jurisdictions in which you are subject to as part of the transaction
    If the jurisdiction of the other party can imposed requirements on you, or if you plan to sell the products or services bought in a third jurisdiction, you need to include any requirements imposed by those jurisdictions.

However, this does not mean you include pages and pages of detailed requirements and regulations, that are well defined in the appropriate laws and statutes and regulations you are bound to, merely that you reference those regulations and require the other party to adhere to them. This usually requires only a few sentences per regulation, max. Not paragraphs and definitely NOT pages.

That’s it. Nothing else. And I cannot emphasize enough that you don’t include something else just because your lawyer decides there is a minute 1 in 1,000,000 risk that something could go wrong and someone with a better funded legal team could possibly find an innovative way to wiggle out of a contract that didn’t cover the obscure case of a worker tripping and skimming his knee because he stepped on a snail on the way to your worksite. Over funded legal teams under the control of people with more money than brains can always come up with harebrained arguments and ridiculous legal challenges — but how often does it really happen? Especially between two parties who were open and honest in negotiations and go into the contract fully intending to fulfill it? And is it really worth spending tens of thousands (or more) of legal time on an average contract which is usually a small fraction of organizational spend? (If an organization has 10,000 contracts and it’s revenue is less than 10 Billion, the average contract value would appear to be one million, but give that there will be a few large contracts with key suppliers that leverage volume, you’ll have a few dozen contracts in the tens or hundreds of millions and an “average” contract in the tens or hundreds of thousands.)

Remember, your lawyer’s job isn’t to tell you what to do. Your lawyer’s job is to listen to what you want to do, advise you of the risks, and then do whatever you tell him to do, which definitely includes writing short, easy to understand, contracts that people will actually sign. At the end of the day, you need to do your business. Contracts should enable that, not get in the way.