当前位置:网站首页>How to understand the difference between technical thinking and business thinking in Bi?
How to understand the difference between technical thinking and business thinking in Bi?
2022-07-06 13:59:00 【Passerby a Java】
Pick a point from this article to talk about BI Technical thinking and business thinking in .
article : Look at a picture BI Thinking framework and several problems
one can't make bricks without straw
A friend said such a thing : It's all said and done BI Be business minded , We can't always think about problems from the perspective of technical thinking , From a business perspective ...balabala... Listen to too much truth , Can you give an example to illustrate .
Let's talk about the difference between technical thinking and business thinking through demand analysis .
stay BI A common situation in projects is , The business department, especially the senior management, raised several analysis requirements during the demand research , I'm done IT The team is worried , The first reaction in my heart :WTF, The data are not analyzed very much .
No data refers to : The system does not have this part of the business module , No data accumulation ; The system has business modules of this part , But the quality of data accumulation is very poor .
All in all , There are no numbers available , It's hard to deal with !
So I quickly came to the conclusion , This is not a technical problem , It can't be realized , Because the system is short of numbers .BI What you can do is : What kind of data , What kind of analysis can we do , No data , Can't do analysis .
Is there anything wrong with this sentence ? There is nothing wrong with it .
Sometimes I complain , How can this demand be raised , The business system is so bad 、 Don't everyone know that the data is so bad ? Finally, with everyone's full cooperation , Perfectly kill this demand .
The above reaction is a kind of technical thinking .
Of course , If it is a business that makes random demands , Or add additional requirements on the premise that the requirements have been confirmed , There are many interest factors to consider when this demand is killed , Put aside these factors , Let's take a look at the comparison between the two .
The entry points of technical thinking and business thinking are different
The first consideration of technical thinking is always from the perspective of Technology , Can I realize this problem , How should we achieve . Obviously , The system is missing 、 Low data quality cannot be solved , Or it can't be disposed of in a short time , So it doesn't work .
There is nothing wrong with thinking about problems in technical thinking , But it will limit the comprehensiveness of our consideration , Many opportunities to think deeply and solve complex problems will be lost , Also lost the opportunity to improve themselves .
First of all, I want to make some corrections and explanations to the above cognition , Why do people who need data often feel that they don't understand the current situation of data , It feels like they are always making for the project " trouble ":
First of all , The top management will not pay attention to the micro level of information construction . The top management is basically not the user of the business system , They are not used to opening every business system to see the data inside , So I don't notice these micro level things at all .
second ,BI Differences between users of system and business system . The users of business system are usually called front-line business execution layer , They operate these business systems more to solve their daily business processes 、 Business data processing . but BI In most cases, users of the system are basically cross department 、 Cross business 、 Cross organizational , Their ideas are nonlinear , Requirements themselves are different from those expressed by business systems .
Why do we have different perceptions of the same thing , At a deeper level is the difference in the way of thinking , Here we use the example of opening a restaurant to illustrate how different perspectives think :
Technical thinking —— " What kind of data do I have , What kind of analysis can I do ", Which translates as :" What kind of raw materials do I have , I can fry this A few dishes ".
Business thinking —— " What kind of analysis should I do , So what kind of data I'm looking for ", Which translates as :" What kind of dishes should I cook when I open a restaurant , So what kind of raw materials should be prepared ", When you are a boss, you must think so , Isn't it ?
Do you understand ? The comparison between technical thinking and business thinking is obvious from this small example .
Landing of business thinking
In the process of thinking, we also need to understand these problems :
First of all , Why should users raise these requirements . Like the simplest one , The management proposed to look at the industry benchmarking data , These data are definitely not available in the enterprise's internal business system , Usually we need to climb the data of Listed Companies in the industry .
Why look at these data ? The data comparison of enterprises is often divided into these kinds :
1) Compare yourself to yourself —— Compare yourself to yourself , It depends on whether you have made progress for several consecutive years , Why there is no progress ? It's the whole industry , Or something ?
2) Compare yourself with the industry —— It depends on your position in the industry , If the industry growth rate is high , Your growth rate has not increased , The market share is small , What's the cause of the ? What factors drive the rapid growth of the industry , Whether this driving factor matches your competitive advantage , There is no match , The competitive advantage in the past has become a disadvantage .
3) Compare yourself with your peers in the industry —— Match the overall trend of industry growth , But there are stronger players , What do they rely on to drive business growth , Their gross profit level 、 What is the turnover rate , What other improvements and efforts can we make .
Behind many seemingly inadvertent needs of the management, there is actually a very deep thinking background , So when looking at problems, you can't just look at the surface , Make clear the thinking point behind the problem, which is the core . Improvement of personal ability , The gap between people is also opened from these details , We should see the essence of the problem .
Those with this ability are often more likely to be favored by leaders in enterprises , The depth and height of thinking may not reach the level considered by senior management , Because the contact surface is different after all . But the thinking consciousness is in place , That's enough .
therefore , experienced BI Consultants will pay special attention to why users ask these questions , What is the logic behind their thinking ? Accumulate these problems bit by bit , Will become very strong .
second , The system has no corresponding business module , There is no relevant data support . This part may be of particular concern to the management , And I really need . But because the construction of business system is gradual , It's hard to get there in one step , So the system is missing , This is also very normal . But now leaders are paying attention , And through in-depth communication , It is really important to find this point , What do I do ?
What problems should be solved by informatization every year , Where is the investment point of informatization ? Isn't it very clear , The next stage of informatization planning is to check and fill these omissions , These points should be included . Therefore, these needs of the management point out the direction for the key construction of informatization in the next stage , It's OK to implement them later .
But for the immediate management, we need to see how to solve these data ? It's good to supplement the data , Manual processing is also good , Also try to make up , After all, this is the focus of end users . They don't care how these processes are handled , What we want is the result . First fill in the data 、 Manual supplementary recording solves this problem , After the follow-up information system is improved , Just switch over one after another .
Of course , If you fill in according to this 、 Data supplement 、 Manual processing , The corresponding project cost investment has also increased . This matter requires the management to decide whether to invest in this way at this stage , If you want to , It shows that this matter is really important . If not , On the contrary, it shows that this matter may not be so important , Naturally, this demand may not be a really important demand , It can be eliminated at this stage .
Third , The system has corresponding business modules , There are also corresponding data , But the data quality is not good enough . This problem is more complicated , Because there are many reasons for data quality , Let me just give you a few examples .
1) The system has BUG. We have encountered this situation in the project before , There is no problem in the business system , One pull BI There are problems. . Inexplicably, there are many more pieces of data , And some data logic is seriously problematic .
If this situation is found , It's the system developer's problem , The first BUG Solve the problem of processing data again .
2) There is a system , Business users don't use it well , It is easy to find excuses that the system is not easy to use . On the one hand, the system may really be too bad , All kinds of inconveniences , Various complex operations , Various deficiencies . This situation , We still need to find the business system supplier to solve , This can also reflect Party A's informatization management IT Weak ability . On the other hand , System available , Lack of necessary training means to guide users to make good use of the system , This situation IT Departments should strengthen training . Some problems are really caused by poor system experience , But through the necessary training, it can still be done without adding additional investment costs , Maximize the avoidance of data quality problems caused by operational reasons .
There are too many cases of data quality problems , Think about it , There are more than ten situations , In the future, I will open a separate article to talk about .
What only talks about thinking but not landing is pit
From a technical perspective, problems are always limited , In turn, from a business perspective, think about how to find a suitable path through technical means or in what way of thinking 、 The way to solve the problem in stages , I think this is the most important .
After all, all problems can be digested by time , But once limits are set , You can only stagnate .
Just to finish up , Business thinking clearly , It still depends on the final landing , Only landing will encounter various problems , Only by solving all kinds of problems , This is our methodology 、 Our thinking fell to the ground . It sounds a little windy, doesn't it , Because I have seen some tall consulting projects , The plan is complete 、 Various new concepts are flying all over the sky , Customers also like to listen 、 Willing to listen , I still feel very happy after listening to it . But no one will tell customers in advance what risks there are , What kind of problems will you encounter , How to solve these problems .
Unexpected risk is the biggest risk , Can't see the problem in advance and put forward the solution to the problem , The final landing is a bunch of people trampling on the pot .
Consulting 、 There are many people who preach, teach and dispel doubts , Choose to be a master or a teacher , The master is flying high above your head , The teacher is holding you higher .
Recent original articles :
Look at a picture BI Thinking framework and several problems
CIO and CTO The difference between 、CEO From the perspective of CIO And informatization
How to interact : Follow the video Number , Private message communication
边栏推荐
- 扑克牌游戏程序——人机对抗
- Get started with typescript
- .Xmind文件如何上传金山文档共享在线编辑?
- Implementation of count (*) in MySQL
- 7-15 h0161. 求最大公约数和最小公倍数(PTA程序设计)
- Reinforcement learning series (I): basic principles and concepts
- 中间件漏洞复现—apache
- Record a penetration of the cat shed from outside to inside. Library operation extraction flag
- 7-15 h0161. Find the greatest common divisor and the least common multiple (PTA program design)
- 7-7 7003 组合锁(PTA程序设计)
猜你喜欢
1. First knowledge of C language (1)
MATLAB打开.m文件乱码解决办法
QT meta object qmetaobject indexofslot and other functions to obtain class methods attention
MySQL lock summary (comprehensive and concise + graphic explanation)
Renforcer les dossiers de base de l'apprentissage
MySQL事务及实现原理全面总结,再也不用担心面试
Mode 1 two-way serial communication is adopted between machine a and machine B, and the specific requirements are as follows: (1) the K1 key of machine a can control the ledi of machine B to turn on a
Difference and understanding between detected and non detected anomalies
Have you encountered ABA problems? Let's talk about the following in detail, how to avoid ABA problems
1. Preliminary exercises of C language (1)
随机推荐
. Net6: develop modern 3D industrial software based on WPF (2)
【MySQL数据库的学习】
Hackmyvm target series (6) -videoclub
Experiment 9 input and output stream (excerpt)
Strengthen basic learning records
.Xmind文件如何上传金山文档共享在线编辑?
MATLAB打开.m文件乱码解决办法
搭建域环境(win)
Analysis of penetration test learning and actual combat stage
Poker game program - man machine confrontation
Zatan 0516
Renforcer les dossiers de base de l'apprentissage
[during the interview] - how can I explain the mechanism of TCP to achieve reliable transmission
强化学习基础记录
Thoroughly understand LRU algorithm - explain 146 questions in detail and eliminate LRU cache in redis
HackMyvm靶机系列(7)-Tron
Experiment 7 use of common classes (correction post)
Inaki Ading
[experiment index of educator database]
Programme de jeu de cartes - confrontation homme - machine