Category Archives: Technology

Let the Bloodbath Continue!

In a recent LinkedIn post, THE PROPHET tells us there is a Consulting Bloodbath starting, especially in the Big 5 (and their strategy firms). All the doctor can say to this is Good Riddance! and It would be even better if they battled it out Gladiator style! (After all, it’s been 28 years since American Gladiators ended, time for a rebrand and a relaunch with a little bit of MXC, which ended 17 years ago.) But we’re getting ahead of ourselves here …

Basically, according to THE PROPHET, firms are worried about the economy and growth headwinds ahead (this is also why investors have yanked money from equities and lessor-rated debt in recent weeks), and this includes tech/dev teams within consulting firms. In some cases lucky consultants are put on the bench and told they have six or nine months to find their next gig, and in others (and maybe the doctor is reading a bit between the lines here) they received their pink slips faster than they could say please Jack Robinson.

The bit about tech/dev teams makes the doctor happy because,

  • these are not tech firms, and they are selling modern analytics/automation/AI solutions they have no business selling (and no real capability to deliver at even an average level, as discussed in our recent post on why if if you want to get analytics and AI right? Don’t hire a F6ckW@d from a Big X!)
  • they are not structured for proper SaaS development and deployment and are NOT SaaS enterprises
  • most of the “talent” they are using are not “top” talent, and if if they are “top” of their class when they are hired, they still need mentorship and experience to become “top” talent, mentorship and experience they are NOT going to get at a Big X
  • the Big X cost structures are too high for mass market penetration; only the F500 / G3000 can afford them, but they still shouldn’t because overpaying doesn’t deliver the value they need in inflationary times where supply chains are breaking daily

And before you chastise me from apparently taking pleasure in people getting fired, think it through! If you do you will realize

  • the true “top” talent is going to end up at appropriate SaaS/Tech companies (or SaaS+IP powered niche automated services consultancies where their true talent/drive really is) where they can get the mentorship they need to grow and reach their full potential because
  • Big X being forced to pull out of (chasing) inappropriate custom SaaS/tech deals/engagements will open up the market back up for those companies that are well positioned, who can start growing and pick up this top talent
  • the “talent” that is not ready for the tech market will either go back to school or find their true calling (before going down a path where they will eventually get overwhelmed, be unhappy, or both; we can’t have the next generation burn-out in first world countries where a very significant portion of the aging population will not be of working age in the very near future)

Plus, shift happens! (How many of us have been restructured, rightsized, or outsized from a job by financiers and lawyers who think they can run a complex enterprise from a balance sheet or understand advanced technology and engineering when they can barely gas up the Jaguars and Mercedes they drive to work everyday?*) Furthermore, given that the average life expectancy at a job these days is 4 years, this talent might as well learn about, and get used to it, now when parts of the economy will be rebounding (and they have opportunity ahead of them), versus getting their @ss3s unceremoniously throw to the curb next time the market drops.

And if, for some reason, a Big 5 Consultancy (which did not start in tech but in accounting/tax, operations, strategy, etc.) is where they belong, then let them prove it in a battle royale! Forget about sitting on the bench waiting and hoping to get invited to a sales call where they can sell a project to work on, put them in the Arena! When a Fortune 500/Global 3000 needs a consultancy, force them to make their selection in the arena where the consultant leads will battle it out modern gladiator style! Not just a Dragon’s Den pitch, they have to battle it out to even get the opportunity to pitch — prove they’ll do whatever it takes to deliver value at the hourly rates their employer is charging!

Thoughts?

 

* If the apocalypse is nigh it is largely because these idiots forced the engineers who actually know how to build things out of the C-suite, allow Gen-AI to tell them how to do technical jobs, and then elect populist pinheads as Prime Ministers and Presidents to tell them it’s okay. And let’s not forget that, as per the OECD PISA data, most of them can’t even do high school math competently!

Firms that Rely on Logo Maps and Analyst 2*2s for Tech Selection are NOT Appropriate for Tech Selection!

In our last article, where we described in detail the many, many reasons why logo maps (including the Sourcing Innovation Mega Map on Source to Pay+ with 666 Unique Clickable Vendor Logos which were verified to be valid as of 2024 April 13), we not only reiterated how these maps are mostly useless but explained that your mileage will vary widely between a map created by an analyst who’s likely seen 1/3 to 1/2 of the vendors in depth and a(n) (former) implementation consultant or (want-to-be) influencer from a CPO background who has no in-depth technology education or experience (beyond the systems he used).

Those who read between the lines would have seen this post coming — not only are they not appropriate for tech selection, any firm that relies solely on them or analyst firm 2*2s (which are great if you are searching for some holy smoke to keep the beast of procurement technology at bay) is also inappropriate for tech selection projects.

Your results with such firms will be about the same as the bigger firms with “consulting partner” status with all the (same) big players, as they will ultimately just recommend the same ten firms for your Tech RFP over and over again, whether or not they are the right firms (and solutions) to meet your needs.

In order to effectively select a set of potential solutions for a client, you need to, at the very least:

  • understand the processes the client needs to support and the gaps they have
  • understand the solution types needed to support the processes, and the client’s gaps in particular
  • understand the client’s current technology landscape and Technology IQ, including what is replaceable and what is not (since, gosh darn it, some clients are going to hold onto that ERP they overpaid for until you dodge their six-gun pistols and pry the contract from their cold, dead hands)
  • understand the client’s unique situation based on vertical/industry, market size, and geography/culture
  • understand what global vendors support the processes, fill the gaps, synch with the tech stack, and can, possibly through third party integrations/partners, address the client’s unique requirements

This is a tall order. So tall in fact that, despite the growing demand for technology transformation and digitization across the Procurement landscape, outside of a few niche vendors that primarily focus on specific industries and specific solution types, the vast majority of procurement transformation shops aren’t able to fulfill it. Most will

  • have the processes down pat, they are consultants after all!
  • have a decent understanding of the common/core solution types, as they smart ones will actually read the expository articles written by the analysts (that they have access to anyway*)

Some, who employ technology and industry-specific professionals, will be able to build a decent understanding of

  • the client’s technology landscape and technology quotient
  • the unique requirements to look for/enable based on vertical/industry, organizational size, and geography

But few, if any will be able to:

  • identify even a handful of relevant global vendors that take into account the first four requirements

This is because, as pointed out in our last few articles:

  • the space is much bigger than they think, with
    • more types of product offerings,
    • considerably more vendors then they think exist, and
    • considerably more than they can process
  • they don’t have the deep technical background or technical understanding to differentiate between two vendors that speak the same and present applications that look the same in a 60 minute demo, but differ greatly in underlying power, extensibility, integration capability, etc. where you need a deep technical background and/or competitor understanding to tease it out (as well as a deep understanding of Procurement and the competitive [solution] market place)
  • they don’t have a process to do a proper technical assessment, diligence, or tech analysis …
  • and they certainly don’t know how to do a deep assessment by module/area to truly differentiate two solutions to qualify them as suitable for selection if they submit the best RFP

As a result, many consultancies will just do their in-depth process analysis, write up functional requirements based on that, and toss it over the wall to the solution providers to figure out, selecting from their partners if they feel there is enough overlap, then from the upper right in the analyst maps they paid for, and, finally, from the logo maps from their most trusted source. And, as we’ve explained, this doesn’t cut it and is why many sourcing / procurement software selection projects fail to live up to client expectations. Because, and we can’t say this enough, the most you can use logo maps / analyst 2*2s for is vendor discovery. Not validation for your projects!

Now, while the doctor has yet to receive an answer to his transformation process inquiries from any consultancy/service provider that fully satisfies him (he is demanding, after all), he is happy to say that, recently, a few# providers have acknowledged that transformation is going to require getting a lot more intelligent in tech and updating their processes and methodologies to recognize that, while it’s still The Wild West, it won’t be tamed by hope and grit alone — you’ll need the right tools to conquer it (and, FYI, those tools aren’t Gen-AI, they are good old-fashioned predictable, dependable steam- and gunpowder-powered tech solutions in the hands of us old and busted masters; the new hotness has nothing on us).

Secure Download the PDF!  (or, use HTTP) [HTML]
(5.3M; Note that the Free Adobe Reader might choke on it; Preview on Mac or a Pro PDF application on Windows will work just fine)

 

* this is your regular reminder that Sourcing Innovation has never had a paywall and never will for baseline vendor coverage or expository posts; should SI choose to offer books, in-depth [comparative/market] intelligence, or similar IP services, for example, it may in the future sell this non-blog content, but every blog post will remain paywall free — almost 6,000 and counting …

# and we mean few, he can currently count them on his fingers on one hand, thumb not required

Digitalization alone is NOT a cure all to our problems!

A recent post on LinkedIn said digitalization is an emergency because:

  • Health workers are feeling squeezed
  • People can’t find the housing they need
  • Farmers can’t find enough hours int he day
  • Manufacturing firms can’t find the workers they need

And while digitalization is an emergency for some businesses, DIGITALIZATION WON’T SOLVE ANY OF THESE PROBLEMS, because lack of is not the core issue. Since the poster is living in Montreal and the doctor is living in Halifax, we’ll focus on the source of the problem from a Canadian perspective, but the reality is that the majority of countries with these issues has the same source problems:

1) Today, 20% of Canadians don’t have a family doctor, compared to 2001 when it was only 13%. This is because, from 2001 to 2021 we saw a 23% population increase. In the same time, we saw a 12% decrease in health workers. (And things have only gotten worse since COVID, but StatsCan is always a couple of years behind. The Nurses association says we are short 60,000 nurses alone!)

2) The national vacancy rate is 1.5%! Year-over-year rent increases are 8%! One bedrooms in downtown Halifax are going for 2K a month! Pre COVID, they were 1K. Pricing is out of control across all major Canadian cities.

3) The days are the same length they’ve always been. What farmers can’t find is enough seasonal workers, despite the unemployment rate, because they can’t afford to pay seasonal workers a living wage. (And that’s why our migrant farm workers in the bigger provinces are essentially facing modern slavery conditions, as per a UN report.)

4) Manufacturers can’t find the workers they need because of a lack of SKILLED workers. Everything is going tech, but yet our STEM graduate rates in Canada hover around 22%! That’s 1 in 5. But if you don’t have decent math, computer, and electronic equipment skills, you don’t have the skills a manufacturer needs.

Thus, it doesn’t matter how much digitization you apply or how good the systems are, we still have the fundamental problems that:

1) it takes a doctor a certain amount of time to properly diagnose a patient, a surgeon a certain amount of time to do a surgery, a nurse time to put in the IV, check the vitals, talk to the patient to do a cognitive assessment, etc. THOSE TIMES CAN NOT BE SHORTENED.

2) We need to BUILD more housing. We need to at least DOUBLE the vacancy rate so that the housing is WHERE it is needed in a market that is COMPETITIVE and REMAINS AFFORDABLE.

3) We need to HALT INFLATION, reduce farm taxes, bring back critical subsidies (and not invent new “grocery taxes” to halt greed mongering, the CEOs will just hike prices for consumers in the end), and make farm work a living wage again.

4) We need to promote and train for STEM.

Only then will digitization help because all it can do is

1) minimize the downtime between seeing patients

2) help people find those affordable units faster and submit applications faster and do the background checks faster

3) help farmers minimize their planning and “back office” operational time

4) help manufacturers get the most from the skilled employees they hire (but there IS a limit on productivity increases)

This is because, as the doctor has said time and time again, all computers are good for is thunking, not thinking, and all Gen-AI does is exacerbate problems because you don’t know if the sh!t it is making up (that’s what generative means — make stuff up) is correct or not! As a result, they can be great at automating tactical data processing and bring the following benefits:

1) centralized country-universal health records, integrated systems, and remote home/self care support — if a nurse or doctor can instantly get all the data on your history they need, they can review it all before seeing you, assess with knowledge, and get to a likely correct diagnosis, and treatment faster; also, if they never have to rekey existing data and just add to the record, it’s less time between patients

2) better three-way support for landlords to find tenants and comply with legislation, tenants to find properties that meet their needs and keep landlords honest (with reviews and instant reports to), regulators who can ensure everyone is using the system properly and fairly

3) easy planning, monitoring, management, and farm-tech selection best suited to the needs of the farm workers based on farm size, location, produce/livestock, and workforce

4) better procurement, production planning, (up)skill(ing) maintenance, design, testing, etc. — maximize every hour on engineering stuff, not back-office paper pushing

But none of this solves the core problems we have or helps if the workers aren’t there to begin with!

Like Analyst Firm 2*2s, Random Logo Maps are NOT Appropriate for Tech Selection!

In our last article, we explained why the doctor created the The Sourcing Innovation Source-to-Pay+ Mega Map, even though he despises logo maps. It was literally the only way he could expose how every one of logo maps released to date was completely useless (and some to the point that they were harmful, but that’s another rant for a later time).

In a nutshell, all of these maps had the following problems, which were correctable (and corrected in the Sourcing Innovation Mega-Map):

  • vendors / solutions no longer existed as of release date
  • categories were meaningless and not actual solution modules
  • vendor logos were not clickable or even footnoted (so you had no clue what that ruin actually represented — a new age vendor or a demonic symbol from a long lost hieroglyphic or symbolic language)

As well as the following problems, which still exist in the Sourcing Innovation Mega-Map (SIMM) because some of them are just not (fully) addressable:

  • nowhere near complete (the further you get away from the Source-to-Pay core, the less complete the SIMM likely is
  • no indication that the landscape changes DAILY (vendors come, get acquired/merge, go out of business, add new capabilities and modules, drop existing modules, etc.)
  • the vendors aren’t always comparable even at a functionality baseline
  • not all vendors with a comparable solution are relevant to the same (type of) company

We ended our last article noting that the right vendor for you was dependent not just on the module(s) you needed to address the process gaps the transformation consultants defined, but the industry/vertical you are in, the size of your organization, the cross-organization user base you need to support, and their technical intelligence (TQ).

The logo maps don’t capture that. (But, to be fair, the vast majority of the analyst market maps don’t either.)

But more importantly, they don’t always (accurately) capture what solution(s) a vendor accurately captures. The reason for this is that, to be completely accurate, the creator would have to be fully aware of, and have seen, the current full end-to-end solution as of the day the map was released and then accurately map the providers’ solutions to each of their logo map categories.

the doctor has likely reviewed more Source-to-Pay solutions over the past 19 years as an analyst than almost any other analyst except for Mickey North Rizza (15 years at AMR / Gartner / IDC), Duncan Jones (who was Forrester Vice President and Principal S2P analyst for 16 years straight), and Pierre Mitchell (25 years at AMR / Hackett / Spend Matters). (Just about every other technology analyst still active in our space has only been a full time market analyst for a decade or less.) Even though he has reviewed, in depth, over 500 hundred solutions (and written about 350+ in detail on Sourcing Innovation and Spend Matters [but good luck finding at least 1/3 of the Spend Matters coverage since, as previously mentioned, the site refresh dropped co-authors on many articles, many of his articles were co-authored, and he was always second billing], he hasn’t even seen half the solutions on the map in depth (but still believes the ratio of in-depth vendor knowledge that went into this map is still greater than every other logo map produced). As a result, his classifications, like any other analyst, are based on, in order:

  • in depth demos, diligence or evaluation projects
  • detailed vendor communications (beyond just what’s on the website)
  • website / third party summaries (looking at the functionality where possible, not just the language)

Which means that, if the website/materials were out of date when reviewed (and it’s been a few years since the last review), the classification could now be highly inaccurate. The eProcurement vendor could have shifted mostly to I2P/AP. The supplier management vendor found a niche in risk management or category sourcing and dropped most SXM capabilities. The contract management solution, interchangeable with forty others, didn’t get traction and was dropped. And so on.

So if your mileage varies in this map, put together by someone who has consistently been at least a part time (if not full time) analyst since Sourcing Innovation was started in 2006, imagine how much it will vary in a map put together by a former consultant, who might have only seen the same ten solutions he was always implementing in depth, or a former product manager who doesn’t have a solid technical background and can’t accurately judge the true capabilities and potential of the solution he’s looking at. (the doctor has an earned PhD in computer science and has been a software architect / research scientist / CTO, compared to the average analyst who, in the early days, came from an operations / logistics / management background if you were lucky and a journalism,
English, or history background [because they could actually write] if you weren’t.)

In other words, no matter how cool these (logo) maps look, at best they will be mostly useless (if they give you clickable logos so you can begin your own research effort), or completely useless otherwise.

Secure Download the PDF!  (or, use HTTP) [HTML]
(5.3M; Note that the Free Adobe Reader might choke on it; Preview on Mac or a Pro PDF application on Windows will work just fine)

the doctor dislikes logo maps! So why did he create one?

To demonstrate how, to date, they have all been completely useless, with some to the point of being actually harmful, but now that the gauntlet has been cast, he expects the next version of at least one of these maps to only be mostly useless (and maybe even only moderately useless) and mostly harmless. It’s the same reason he developed the initial versions of Solution Map*, because he found all of the big analyst firm maps mostly useless, and completely useless for tech selection.

(On the tech map front, how can you compare the technical capabilities of a solution where the axis are each on subjective classifications such as “strength and “strategy” or “execution” and “vision”, and, furthermore, where each of these nebulous concepts is made up of half a dozen subjective ratings meshed into one. While not perfect, at least Solution Map gave you an apples-to-apples pure objective technology rating (as each question had a defined rating scale based on technical maturity) against an unbiased pure customer opinion. So you at least knew whether or not

  1. the vendor actually offers a readily available solution of that type
  2. how it compares to the market average of vendors with actual available solutions of that type)

Thus, if you insisted on using logo maps, he at least wanted to make sure there was at least some redeeming qualities.  However, as he has already stated, his map is mostly useless and while a few flaws were corrected on release, some are inherently not addressable.  The problem with these maps in general is that, in addition to all the weaknesses the doctor addressed in his release post, namely:

  • Some vendors/solutions no longer existed as of release date (which was addressed)
  • Many of the categories are meaningless and not actual solution modules (which he corrected, but this means the fit varies across vendors in a category)
  • Vendor logos were not clickable, and not even footnoted when all you got was some strange symbol that looks like it should be carved on a 3000 year old ruin (which is the primary improvement, all logos are clickable and take you to the vendor site as of the release date).

4. They are nowhere near complete.
Most of these maps are in the 100 to 150 logo range. As the doctor has clearly demonstrated that’s only 1/7 to 1/10 of the number of vendors in the core space. Furthermore, even though the doctor does a full database update at least annually, he will guarantee that not even his map is close to complete. While he’d wager he has 90% of the vendors actively selling in North America and Western Europe in the core Source-to-Pay buckets, that percentage goes down as you venture out into the periphery. Plus, in some areas, like ESG/Carbon, he tracks only those focussed on carbon/scope 3 accounting with supplier management / sourcing integration capability, and ignores the remaining ESG/Sustainability/Climate vendors, of which there is likely 10 times as many right now (although we’ll see a lot get swallowed up or die off as the space matures). Most of the supply chain risk vendors are missing unless they offer core supplier management capabilities, or integrate with supplier management modules, as well. And so on.

5. The landscape changes daily.
the doctor did a full database review last year when he did his 39 steps … err … 39 clues … err … 39 part Source-to-Pay+ series, and since then, over half a dozen vendors/offerings are completely gone and over a dozen acquired and swallowed into larger vendors. One, acquired in 2022 that was still offered as a standalone solution late March disappeared by the final link checks that began on April 13. So, while these maps are distributed by their creators for months, and sometimes a year, they are only valid as of the last date where the creator actually re-verified every single vendor.

6. The vendors are only comparable at the baseline, IF they are comparable at all.
If no two (2) vendors are created equal, imagine how different twenty (20) are, or one hundred (100)! If you refer back to our previously referenced 39 part Source-to-Pay+ series,

  • sourcing vendors break down into RFX, Auction, optimization and may/not contain (best-practice) templates or category expertise
  • contract management generally breaks down into negotiation support, (post-signing) lifecycle (execution) management and tracking, and analytics
  • spend analysis is similar, but differs on DIY vs. services led, load/classification support vs. self load/(re)class, out of the box report templates, autonomous analysis and opportunity identification, etc.
  • supplier management was broken down into the 10-segment CORNED QUIP mash, which expressly excluded DEI, because most application thereof is definitely NOT equitable (as the biggest promoters clearly never looked up what the words actually mean in a dictionary)
  • eProcurement, while it revolves around a PO (and, hopefully, a no PO, no pay policy), may or may not have punchout/internal/managed catalog support, may or may not support receiving, may or may not support price tiers and discounts, etc.
  • I2P, while it revolves around the invoice, it may or may not support anything beyond internal PO flip or XML, may or may not support m-way match, may or may not integrate with a payment system, etc.
  • and the same variation exists across every other category

This is assuming that the creator actually understood what every vendor offered and classified according to what the vendor’s product actually did vs. what language the vendor chose to use to describe their product.

7. Even all the vendors with comparable solutions are NOT relevant for you.

When you are considering a vendor, at the very least you have to consider

  • the verticals/industries their solution was designed on, and designed for
  • the organizational size they were developed for

and a host of other considerations based on your industry, your organizational size, and the hole you are trying to fill.

This is why so many Source-to-Pay+ selection projects end up not (fully) delivering and why most big consultancies just keep recommending the same-old same-old five (5) (big) vendors regardless of what your needs are, because they don’t know any different and at least those vendors will be around tomorrow. And this leads into a bigger discussion of why these logo maps, like most analyst maps, are NOT appropriate for transformation projects. Which we’ll take up in our next article / rant.

Secure Download the PDF!  (or, use HTTP) [HTML]
(5.3M; Note that the Free Adobe Reader might choke on it; Preview on Mac or a Pro PDF application on Windows will work just fine)

* and the doctor would like to make it very clear he had NOTHING to do with the current interface and presentation of Solution Map; it’s likely many of the questions are still his, but to be valuable, SolutionMap has to be properly scored and the ratings properly compared and applied relative to a number of factors not explicitly captured in the map