Category Archives: Technology

Procurement Trend #18. Improved Supply Management Skill Set

Fifteen anti-trends still remain but today we can take solace in the fact that we have finally finished with the “old news” anti-trends and have reached the “ongoing” blues anti-trends. While these anti-trends are still “old news”, most are only a few decades old, as opposed to some of the earlier trends we debunked which described situations encountered by many business centuries ago (which is when globalization really began).

So why do the modern historians continue to peg an improved supply management skill set as a future trend? Maybe it’s because they’ve only recently been expelled from an old-school Procurement organization into this brave new world, and this is as far as they’ve made it in their readings, but three likely reasons are:

  • technology is progressing rapidly

    and much faster than the average person can be reasonably expected to keep up with

  • the breadth of supply management continues to expand

    and new categories and responsibilities are often added to Supply Management’s (shared) purview on a regular basis

  • processes aren’t keeping up

    and Supply Managers are getting buried under an avalanche of tactical demands

So what does this mean?

Rapid Technology Progression

Your organization, and in particular, your talent, needs to keep up. Regular training is going to be required for your talent, and thus your organization to keep up. You will have to fight for this though, because despite the fact that it has been among the top three or top five concerns of most CPOs and CXOs for the past five years, the training budget is always the first budget to get cut.

Expanding Supply Management Breadth

This is a good thing, but you your Supply Management organization needs to keep up, not fall behind. The tech progression is a good starting point, the training is a good continuation, but you need to also learn other areas of the business – their language, processes, and goals so that you can collaborate with them, learn their wisdom, and, if possible, share the workload.

Processes Need to Move Out of the Past

Processes need to continually progress forward — that’s why SI is all about Transition management and not just focussed on the classic people-product-technology triangle (as it’s actually talent-technology-transition management). You will have to conduct process reviews not only on all Procurement processes, but on all related operational processes to determine if they can be made more efficient, reliable, or better, identify what new processes would look like, determine if the current technology platforms can support these new processes or if new platforms are needed, and create, and then execute on, appropriate transition plans.

Procurement Trend #19. Service Providers Excel

Sixteen anti-trends still remain but we again assure you that we are getting to the end of the series and all is ok as LOLCat is still dreaming of his grandfather’s adventures as an archaeologist cat uncovering lost tombs, and waiting for this series that is regurgitating topics of his past lives to fade into history. We will continue to lay bare each and every one of the futurists’ lies, and when we’re done, you’ll be in a better position to learn the truth and seize upon the real trends that lie ahead and the opportunities they contain.

So why do the historians keep pegging service providers excelling as a future trend? Have they spent too much time in the janitors’ closets breathing paint fumes from improperly sealed paint cans while practicing their speeches that no one really wants to hear? Hard to say, but some of the reasons probably include:

  • Outsourced Services are still improving

    in both traditional Business Processing Outsourcing (BPO) and non-traditional service sectors.

  • Service Providers are mastering tech faster than their clients

    and often get a lot more experience with a platform in a shorter time frame as they are running projects for multiple clients on that platform.

  • Everything is going out

    because overpriced overly-optimistic consultants have strapped themselves to the outsourcing bandwagon in an effort to make sure that they never fall off.

So what does this mean?

Outsourced Services

Service Providers can often do things better than you, but if they do, you need to adapt or lose control. You don’t want to lose control, because one of your jobs is Supplier Relationship Management. However, at some point during the adaptation, you will, if you are doing it right, become better at managing the process than the outsourced provider, but you will still be locked into a multi-year service agreement. So you will have to transition from learning through managing through teaching. And once the service providers masters your teachings, as they will have more opportunity to practice and perfect, they will again get better than you and the cycle of the student becoming the master and the master becoming the student will continue.

Technology Progression in the Outside World

While this is one of the reasons that service providers outpace you, this is a great learning opportunity for you. Most companies don’t pick the right technology the first time around — and instead implement expensive systems in even more expensive projects that turn out to be massive failures. Then they learn from their mistakes, implement the right technology, and provide you a free lesson on what works if your processes match theirs if you choose to seek it out and learn from it.

Out, Out, and Away

Because your managers are still living two decades in the past where cost reduction was defined as outsourcing, you can, unfortunately, expect more pressure in the organization to not only outsource your tactical work, but to outsource as much tactical work for other departments in the organization as can possibly be outsourced. So you need to either prepare for this, or build the business case as to why the work should stay in and how keeping it in house will either deliver savings or add value.

It’s Faster PussyCat; not Faster Idiot!

Fashion. Mobile Devices. Software. Everything is moving faster and faster. Maybe LOLCats need to move faster because their expected lifespan is one sixth of ours. But we don’t. We’re moving so fast that we’re bringing back infinite scroll and software mystery meat. We’re building mobile devices so thin that they bend, sewing new clothes after they are already out of fashion, and re-launching movies from the 80s because no one has time to even think of an original idea (so forget about taking one to completion).

There’s a place for speed — and it’s on the racetrack. And while first to market is nice, in the long run, it’s usually best to market that wins. The same goes for organizational technology. It’s not about being the first to have the shiny new toy, it’s about identifying and implementing the right technology the first time. A shiny new toy always looks good, but what good is a toy that sits on the shelf? And that’s exactly what happens when you buy a piece of software that looks good but doesn’t support organizational processes and do what needs to be done.

Slowing down isn’t just for buddhists and chess masters, it’s for anyone who wants to get ahead in business and Supply Management. While it’s important to be efficient and effective when doing non-value added tactical tasks, when it comes to important, strategic, activities that, if done right, can generate an ROI that is effectively multiples of the resources invested in the activity (but, if done wrong, can cost the company millions), speed is not of the essence. Getting it right is. If it takes an extra hour, an extra day, an extra week, or even an extra month to get it right, sometimes that’s the right thing to do.

And in each of the examples given above, the extra time would make a big difference. With enough time, developers would be able to research, understand, and build software that did what people want the way they wanted the software to do it — there’d be no mystery meat. And while the mobile iPhone version of your site might need to be infinite scroll because, let’s face it, you can’t click a button the size of a flea on a 4″ screen, no one wants that garbage on a regular 13″ laptop screen and they definitely don’t want it on a 27″ desktop monitor! You could take the time to research exactly how thin and light you could make a phone that was still resilient enough for everyday use and you could design practical, fashionable clothes that people actually wanted to wear, and not just wear the day a model walks them down the runway.

There’s nothing wrong with wanting to go as fast as you can, but going fast just for the sake of going fast doesn’t help anyone. It just makes your organization look stupid. So slow down once in a while, figure out where you are, figure out where you want to be, and work out a detailed plan to get there. The results might surprise you.

And now, to (software) developers everywhere who bring us infinite scroll and mystery meat on a regular basis, LOLCat has a special message just for you!


LOLCat says you're stupid!

BYODD is the Norm, But What Should This Tell Us?

According to a recent post on Spend Matters, BYODD (Bring Your Own Damaged Device) is Now the Norm, and the doctor has to agree. Not only are mobile devices ubiquitous in today’s workplace and home-life, but so are damaged ones. With essentially one in two mobile devices in use being damaged in some way, this means that at least one in two employees are using a damaged mobile device.

According to the author, the solution is to follow the advice in the referenced 2014 ZAGG Device Damage Study. Specifically, if companies are encouraging employees to bring their own devices to work, then those companies should be buying screen protectors, cases, and other damage defense products for their employees to make sure that these employees not only have damage free products to work on but to represent the company.

That is sound advice, and a precaution that should be taken, but that’s not the solution. That’s a fix. The solution to the problem is to address the root cause, and the cause is the proliferation of devices that are, simply put, way too brittle. While the doctor is not suggesting that we all need to be carrying around military-grade tech that can withstand blows, high-impact falls, and desert terrain, we should not be carrying around phones that bend in our pockets.

In other words, the real problem is the proliferation of devices that are being made flimsier and flimsier in a ridiculous effort to make a device that is not only lighter than the predecessor, but, as far as the doctor can tell, lighter than (compressed) air. And while 23.6 pounds (which was the weight of the first portable computer) is a bit heavy for a laptop, we can easily lug around a laptop that weighs 10 pounds considering we used to carry around textbooks that weighed 5 to 7 pounds each. We don’t need a 3 pound laptop (which is the rounded weight of a Macbook air), especially when a gust of wind can shred it! The same goes for phones. We used to lug around cell phones that weighed almost 2 pounds. We can certainly handle a pound if that’s what it takes to make it resilient and reliable. At 4 ounces, it can blow away with the wind!

So just like we need to avoid developers who insist on putting look before feel and functionality, we need to avoid manufacturers who focus more on making devices featherweight then on making devices resilient and support those manufacturers who take a more balanced approach to device production. When the money stops rolling in, this will quickly convince all manufacturers to kick their obsession with making featherweight devices and get back to reality.

Twenty Five Years Ago Berners-Lee Proposed the WorldWideWeb Project and Web Software Still Sucks. Why?

Because too many software designers and project managers think “Look and Feel” stands for make it look awesome because then you’ll feel good when you look at it. They don’t realize that “look and feel” refers to the “feeling” you get from using it, not just from looking at it.

And that’s why software still sucks. When it comes to software, looking good is important, but not more important than being usable. If, as Thomas points out in this post over on Spend Matters on why you should “Understand Your Use Case First — Develop Later!”, it’s impossible to find the button or menu item you need, or determine if it even exists in the first place, as good as the software looks, it still sucks, at best.

Software has to support whatever process it was designed for, and it has to make it easy for the user to accomplish that process — if it doesn’t do that, then it fails — spectacularly! It might look damn good when it fails, but it still fails.

And as long as developers continue on this ridiculous hidden-menu, infinite scroll, more features than you need but none you actually use kick, software will continue to suck and keep us in the technological dark ages.

So what can you do? Shun software that puts look first and functionality second. Developers will get the message, and eventually so will their managers. Then software can continue to progress forward.