10 ideas – New technologies needed

“Which 10 technologies do we need that haven’t been invented yet?”

In no particular order:

  1. Automated checking and correlation of outside plant (and any other data source that doesn’t have programmable interfaces)
  2. Order to cash tools for customers of CSPs, not just for the CSPs in the usual use of this metric
  3. Knowledge transfer between individuals that is faster than years of training and experience
  4. No-reconciliation data transfer tools (blockchain has great potential in this space to ensure all records are matched on both sides of the transfer ledger)
  5. Scenario recording, playback and forward projections for training, error prevention and planning purposes. Example scenarios include complex incident resolution, optimising network growth, etc
  6. Gamification tools that allow crowd-effort to try thousands of variations to solve complex problems such as root cause or design efficiency
  7. A tool that translates customer requirements to best-fit vendors, fast-tracking vendor selection without months of evaluations involving vast resource pools (my benchmark project is a stepping stone towards this outcome)
  8. Requirement gathering, compilation and analysis that automatically translates to first-draft operational processes in any given OSS
  9. Tools that measure pre-project and post-project to define metrics / learnings that become inputs into future project funding decisions
  10. Efficiency analyser to determine which tools and processes are the 20% that deliver the 80% of value. Conversely identifies what can be culled
  11. Ecosystems that allow customers or third parties to build their own applications on CSP and cloud infrastructure with a focus on productivity and / or revenue generation for those customers
  12. Simplicity robots that can evaluate data and process flows to recommend what is redundant or unviable commercially
  13. Automated forward notifications to guide customers through the complex change management process during project implementation

Okay, so that’s more than 10. πŸ™‚

If this article was helpful, subscribe to the Passionate About OSS Blog to get each new post sent directly to your inbox. 100% free of charge and free of spam.

Our Solutions

Share:

Most Recent Articles

The OSS Golf Analogy

Over the years, I’ve often referred to The Corkscrew Analogy or Momentum Spiral to describe a mindset of incremental improvement that’s needed to keep an

2 Responses

  1. Hi Evan,
    Yes, you got me. I’d already written 14 and 15 before stopping and deciding that 13 was the better number to finish on. πŸ™‚

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.