The main takeaway from the video below is to solve a problem, create a process that can scale, and then introduce technology.
In this brief video – the second in a series*, I will focus on the following critical points: – Never, ever lead with technology and then look for a problem to solve – Identify and solve a problem – Create a scalable process – Introduce technology.
2025 (TODAY)
1990 to 2025 (WHY DO PROCURETECH INITIATIVES CONTINUE TO FAIL?)
When I collaborated with Eastman Kodak to develop an early digital camera that leveraged the company’s continuous tone printer and what came to be known as the “Kodak Engine” to seamlessly transpose headshots in the jerseys of consumers’ favorite NHL teams, I did not lead with technology! I first understood and solved a problem – it was complex, especially in 1990.
I then created a process to scale understanding of all of the unique operating agents – an early version of agent-based modeling and the identification of what became strand commonality. As a side note, in the late 1990s, the Government of Canada’s Scientific Research & Experimental Development (SR&ED) program funded my research and work that enabled me to create one of the industry’s first web-based self-learning algorithm platforms to enable the Department of National Defence to procure MRO parts to support their national IT infrastructure.
Then, and only then, did I build the technology to scale and extend the core platform to support the NYCTA IT infrastructure.
Unfortunately, through the ERP, SaaS, digital transformation, and now the Agentic AI eras, most solution providers are still developing their solutions in reverse, e.g., building the technology, selling and scaling the technology, and then “hopefully” solving a problem which it fails to do 80% of the time. Let me know if you would like to access my archives of white papers, research articles, and other material dating back to 1990, including extensive case studies of initiative failures and successes.
Procurement Insights
This Is How Technology Is Supposed To Evolve
Posted on January 29, 2025
0
1990 (35 YEARS AGO)
The main takeaway from the video below is to solve a problem, create a process that can scale, and then introduce technology.
In this brief video – the second in a series*, I will focus on the following critical points: – Never, ever lead with technology and then look for a problem to solve – Identify and solve a problem – Create a scalable process – Introduce technology.
2025 (TODAY)
1990 to 2025 (WHY DO PROCURETECH INITIATIVES CONTINUE TO FAIL?)
When I collaborated with Eastman Kodak to develop an early digital camera that leveraged the company’s continuous tone printer and what came to be known as the “Kodak Engine” to seamlessly transpose headshots in the jerseys of consumers’ favorite NHL teams, I did not lead with technology! I first understood and solved a problem – it was complex, especially in 1990.
I then created a process to scale understanding of all of the unique operating agents – an early version of agent-based modeling and the identification of what became strand commonality. As a side note, in the late 1990s, the Government of Canada’s Scientific Research & Experimental Development (SR&ED) program funded my research and work that enabled me to create one of the industry’s first web-based self-learning algorithm platforms to enable the Department of National Defence to procure MRO parts to support their national IT infrastructure.
Then, and only then, did I build the technology to scale and extend the core platform to support the NYCTA IT infrastructure.
Unfortunately, through the ERP, SaaS, digital transformation, and now the Agentic AI eras, most solution providers are still developing their solutions in reverse, e.g., building the technology, selling and scaling the technology, and then “hopefully” solving a problem which it fails to do 80% of the time. Let me know if you would like to access my archives of white papers, research articles, and other material dating back to 1990, including extensive case studies of initiative failures and successes.
30
Share this:
Related