Why is seeing a demo of a platform important?
The answer would seem obvious – but it isn’t.
Far too many people look at technology through the lens of features, functions, and benefits. If all the buttons work as expected and light A goes on when you use switch A instead of light B, the demo is technically considered a success because the tech is doing what the solution provider said it would.
Unfortunately, not enough people look beyond the functional tech to determine whether turning on light A rather than light B is actually good for them.
I know it is an overly simplistic analogy, but you get the point. Instead of looking at features and functions or embracing Magic Quadrant recommendations or solution map logo placement, you should look at the problem-solving process behind the technology. In short, how did the technology evolve from solving a problem, and is it scalable to solve your problem? By the way, just because you are in the same industry as a current user client does not automatically guarantee your success.
Before you go any further, read the following post regarding my work using self-learning algorithms in a nascent AI framework to procure MRO parts to support the Department of National Defence Base IT infrastructure – https://bit.ly/3FBnFRr
Problem-Solving Capability = Supply Chain Resilience
In the Department of National Defence “DND” case overview, at what stage was the technology introduced? No pressure, but your answer to this question will determine whether your ProcureTech initiative will succeed or fail.
Let’s pose the question another way: was the technology developed and introduced before or after the problem was solved?
With the DND, we created a resilient supply chain before introducing the technology. In short, supply chain resilience, in which we “maintained steady operations, protected revenue, and sustained customer trust in an increasingly volatile global environment,” wasn’t established with technology. However, when introduced at the right time, technology did accelerate and expand the capabilities of the procurement team to the point that within 18 months, the FTE requirement was dramatically reduced, while delivery performance improved from a 51% next-day SLA to a contract-compliant 97% next day.
Back To The Demo
While you want to ensure the technology platform works, what good is a light switch if it doesn’t turn on any lights, let alone the right one? However, technology is not, nor will it ever be, the solution to anyone’s problems or challenges. Only after you work with the right solution provider to communicate and collaboratively solve the problem will introducing technology, e.g., a demo, be of value.
30
Procurement Insights
What is the purpose of a ProcureTech AI demo?
Posted on September 30, 2024
0
Why is seeing a demo of a platform important?
The answer would seem obvious – but it isn’t.
Far too many people look at technology through the lens of features, functions, and benefits. If all the buttons work as expected and light A goes on when you use switch A instead of light B, the demo is technically considered a success because the tech is doing what the solution provider said it would.
Unfortunately, not enough people look beyond the functional tech to determine whether turning on light A rather than light B is actually good for them.
I know it is an overly simplistic analogy, but you get the point. Instead of looking at features and functions or embracing Magic Quadrant recommendations or solution map logo placement, you should look at the problem-solving process behind the technology. In short, how did the technology evolve from solving a problem, and is it scalable to solve your problem? By the way, just because you are in the same industry as a current user client does not automatically guarantee your success.
Before you go any further, read the following post regarding my work using self-learning algorithms in a nascent AI framework to procure MRO parts to support the Department of National Defence Base IT infrastructure – https://bit.ly/3FBnFRr
Problem-Solving Capability = Supply Chain Resilience
In the Department of National Defence “DND” case overview, at what stage was the technology introduced? No pressure, but your answer to this question will determine whether your ProcureTech initiative will succeed or fail.
Let’s pose the question another way: was the technology developed and introduced before or after the problem was solved?
With the DND, we created a resilient supply chain before introducing the technology. In short, supply chain resilience, in which we “maintained steady operations, protected revenue, and sustained customer trust in an increasingly volatile global environment,” wasn’t established with technology. However, when introduced at the right time, technology did accelerate and expand the capabilities of the procurement team to the point that within 18 months, the FTE requirement was dramatically reduced, while delivery performance improved from a 51% next-day SLA to a contract-compliant 97% next day.
Back To The Demo
While you want to ensure the technology platform works, what good is a light switch if it doesn’t turn on any lights, let alone the right one? However, technology is not, nor will it ever be, the solution to anyone’s problems or challenges. Only after you work with the right solution provider to communicate and collaboratively solve the problem will introducing technology, e.g., a demo, be of value.
30
Share this:
Related