A typical user access will be made on the OLTP application, in order to collect some of the user's special, separate needs. At the same time, this access can also analyze some processes or some users know that they can implement these knowledge into IT processes. However, in the data warehouse application, its work is not replacing or modifying a process, it is unveiled user potential knowledge. Ironically, this makes this visit look like a tool.
Difficulties exist, because users don't know what is commercial intelligence in the first time and can't make it clear about what they need. Here are some suggestions about excavating user potential, it allows the process to become simple.
Think about what you need
For you, ask a question what you need to need is very difficult, then you can imagine how embarrassing it is visited. They have some vague views that they can't clearly express what they need, but you can guess. The potential invention-related things is slightly speculative. How do you know the business priority they analyze? Of course, usually you can't, at least in the initial time. By guessing to complete your process, you will find that every job you have finished is very satisfied, but very small. Don't let yourself feel empty, this is normal.
Three better than two
When a user describes what they want some in an analyst, then this proposal usually goes deep into the center of the process and will go deep into some huge sectors, which you may not be familiar with it. So, how do you know what they are talking about? You can do notes, write down the trajectory of your process, and think about the next guiding problem, ask questions right away? You probably not. Because this will not be as simple as you have previously work, it is best to take a colleague, one question, one to do notes. In this way, you can concentrate, and you can create a direct access to the topic in the conversation.
Four more than three
For better questions, you need to have a helper to help you record, but for users, he also needs a person to beside him, which will think more effectively. They can think about potential possibilities, think of things that the other person didn't think of. Let them talk freely for you is a chance, you can understand what you want and let your collaborator record.
Clear new data resources
When analyzing the data source, the development team will naturally rely on physical resources. IT workers tend to believe in these teams; the available data is found on the available media, right? However, the user is not so thinking. For employees who handle decisions all day, the data comes from his computer, magazines, and logs, and the Web is news, satellite TV. For them, the rules listed by IT workers are irrelevant to them. You need to listen to your users. The data they use is what they need, whether it is suitable for IT. If they gain some important industrial information from a received magazine, and this affects the analysis process they need, then your job is to capture this fact and find out what information is included and put it in information. warehouse. This is not a joke, but this is indeed the reason they get information.
Commercial ending
When you need the information and the fact that the process is too far, it is reasonable, you have already made it very well in those processes. Usually, the rush decision is appropriate because some people around you help you keep the app's trajectory, if your idea is not confusing. They will correct your omissions. However, using these analysts, you come out of a class that departures from the safety net. If you don't have a business relationship, you can write an OLAP process, which can provide users, but there are omissions. So, what you need is not only to understand the process of analytical data, and you need to in-depth understanding of these processes. If there is a need, and the progress of others will fill your entire gap, and even you will not meet your specifications. Get more
In the OLTP world, you can do one or more meetings when needed. You are looking forward to it; they endure it. In the OLAP world, there may be multiple meetings, which becomes a gift. Once you have opened the door, they will ask you to interview. Don't be surprised. Trying to enter the process, and if the user doesn't know what to do, please stop them.
