Skip to main content

Online information provided for stakeholders' consumption

It must relay the true meaning and real application necessary in the physical world. We have probably all experience how to learn first thing about our plans before we go ahead and act. Like for instance, when we order something online, attend to some responsibilities for our organizations, communicate with people via video, chat and email including but not limited to asking stakeholders, very politely and sincerely, if there's anything else we can do to help further. This online environment must make us work to facilitate and relay exactly what we expect and do in the physical world. What the online information is telling us should be enough to readily make a decision and act accordingly. This is especially true when people have to do it themselves, read relevant information and will go there, say store, or anywhere else, to perform the chores required.  We cannot provide information online, when customers expect them to be a guideline or instruction to do something, that we know

The how is holistic in technology

Everything that technology does cannot be fathomable, say the entirety of such in an organization's initiative, without the how.

It demonstrates, either technology has a good start, is made effective or bad including the following:
1. Leadership, 
2. Design, 
3. Operation, 
4. Personnel. 

Regardless where the technology is being utilized for the organization and its stakeholders, the how can tell what's going on and may happen. Technology here may include business and industrial applications, security including but not limited to the infrastructure and the data production that are involved. 

The how is not a panacea but it can be used to determine whether or not a certain organization has done and even formalize an acceptable job with its technology to help run various, if not all, business processes. 


Comments

Popular posts from this blog

[TW] IT documents, audit and leaders

IT documents comes with different names such as the following: - Manual or handbook, - Policies and procedures, - Management systems, - Project plans. In the real world we have various names with unique descriptions and purposes when in fact they could be made to do a uniform direction for which actions are based for the entire IT initiatives, probably the longest in IT lifecycle is operation. The problem is our inclination on something else which is wrong. IT remains an IT area. Business remains a business area. The same problem is carried out when we conduct IT audit. Most audit are missing the gists in which IT is being used by businesses. We once said that an effective IT audit is conducted by IT people themselves but there is something wrong with that even. Business and accounting people have been doing it with a different bias and preconceived notions which doesn't make the cut for IT direction and audit respectively. Leaders play the same game and so the problem continues an

[TW] Customers' trust and domains outside of internet's root

We all consider ourselves customers. Those who own businesses are customers even of their own. When we talk about the utility of technology, we often use customers to refer to our colleagues and some stakeholders that were provided access to our enterprise system. In business, customers are those who acquire and engage our products and services, respectively. Customers' trust is achieved and retained when we meet the expectations of our colleagues, stakeholders and the buyer of our products, services and ideas. Not only that we have assured them of those expectations in the contract or terms and conditions including some form of agreement but we attend to them sincerely when they need help. Giving them almost everything they need to form a decision. The experience must not be shallow and pretentious or they would notice whatever motive there is in between. Customers' trust is build not by the customers alone, just because we kept their experience up to their standards or we str