Skip to main content

Futurist: Evaluating Enterprise Solutions

I am a long-time Futurist, and technologist. In my career, I have spanned the birth of personal computers, to the rise of Cloud Computing.

What about applications we already have?

What about applications we already have?

Organizations that view their networks as dumb pipes, are going to miss the evolution!

One of the things that I consider in evaluating current and future state solutions is the environment. Does the environment of the organization support the required applications? For example, can people do their job without considerable effort or searching? Also, does the infrastructure truly support the requirements of the applications, including security, bandwidth, and compute assets? First, let me give you the basics of this question. Ultimately, the basis does the environment in which you're putting this application to support what you are trying to do with the application. For example, if this application involves complex data entry, and you intend to deploy it into an organization that no longer has laptops and only carries cell phones, the application has to have many shortcuts. An application designed for cell phone users would, by default, have more shortcuts so that the user can enter the data quickly. The productivity of on-the-spot data entry is lost if it takes the cell phone user 10 to 12 times longer than someone with a keyboard to enter the data. There are speed gains from on-the-spot or mobile data entry. But if it takes forever to enter the data, you lose that technology advantage of being connected. So we must ensure the application balances remote users' value and data entry's reality.

Second, we need to ask, is this the network designed to support the distribution of the information. If a cell phone user has to wait an hour to download data, that isn't a good distribution of data sources. There needs to be a system that supports the device but also the requirements of the organization? It is not a good idea to share data that compromise organizational security. But making it incredibly hard for people to get data increases the likelihood that they'll try to find a way around that security to get the data they need to do their jobs. You can go to secure, and you can't go to insincere. Although technically, I don't think insecure is the right word there, it is more about you can apply security partially, and you can't apply security too lightly. The concept of security is a part of that original question I often ask. What is the end device in question? If it's a mobile device, you must build different apps. What is the network scenario that you are looking to support? Is it a fixed traditional network, or is it an AI-based solution that requires users to connect to the data? Those two are critical questions; of course, the last question we just asked is, do you have the security capabilities that allow the data to flow properly.

That I asked the questions the way I asked them, there is no answer to everything. You can't simply say yes. You can't have our security, and you can have like security in the same sentence, so in that scenario, you say yes to harsh and no delight. You say yes to mobile devices, and you say yes to other devices, but the focus is mobile. So his nose and their nose are critical in building a network and an organizational structure that will support your business, not now because now is transient. An organizational structure and network that will support what you need today but also support the long-term network needs of the organization.

This framework is after the ERT is considered.

This framework is after the ERT is considered.

A Just-in-Time sales application that empowers your sales professionals!

All that preamble to apply machine intelligence to how you offer services to your organization's end users. The concept of intelligent, aware automated applications. So let's break that down into its three component pieces. Intelligence means that the application has the capacity for every user touching it to complete the jobs and functions they need. As I mentioned, if you're building a mobile application that requires a significant amount of data input, you have to make it easy for the user to input data. They have to be able to click the microphone button on their mobile phone and dictate information. Or they need to have multiple drop-down boxes that do not require the input of information. Where applications take into account the concept of state, in other words, if the user for whatever reason loses cellular conductivity during the submission of the form, when the user regains conductivity, they are returned to where they left off, not to a blank document—maintaining the state of the user and the application. The last piece of the puzzle is automation. Now automation is an interesting reality. Many applications, and I watch mobile applications go out the door all the time, are not written to be automated. They claim to be automated before they leave the shop, but 9/10 times, they are automated. Automation is taking repeated tasks and having the system perform those tasks the second or third time.

{Author's note: This framework fits after my Enterprise Resource Triangle (ERT) as ERT focuses on developing new applications in the IT world. This framework focuses on when evaluating applications in the enterprise}

Scroll to Continue

Let's give the example of a sales application to end this discussion today. We decide to build a just-in-time sales application. Just-in-time is an interesting conversation starter. Plus, it has cool initials, JIT! Now I am a salesperson working for a company. I have an inside salesperson I work with, and that person organizes my sales day. My job is to see as many customers and hold as many intelligent conversations with them as I can in a day. The more people I see, the better the day. However, I am on a mobile device and never go to the office. An intelligent automated system would go and read my calendar. Noting that I had five customer calls that day. The plan would then preload all the information for those five customers to my device. That allows me to know what the customer has ordered recently immediately. Additionally, I would know what orders are pending, what orders are back-ordered, and so on. It also allows the system to integrate with traffic and weather to notify me of changes or modifications to my route. So I can be talking to customer "B," leaving customer B's office, and going to customer "C," the system will intelligently route me. The overall integration of the JIT sales application is pretty significant. But by automating certain components, such as calendar-based routing, you can reduce the impact on the salesperson. You can even push calls during customer visits directly to voice mail or route that call to the inside sales representative. Real-time adjustments to schedules and real-time information allows the salesperson to speak to their customers successfully.

This article is accurate and true to the best of the author’s knowledge. Content is for informational or entertainment purposes only and does not substitute for personal counsel or professional advice in business, financial, legal, or technical matters.

© 2022 DocAndersen

Related Articles