📜 ⬆️ ⬇️

I want to know everything: business analysis. Part 1

How it all began


Staying on “sabbatical”, I have at my disposal a certain amount of free time that I can spend on “socially useful work”. Therefore, if the business analysis is interesting for you, please read the thoughts on this issue:

Reading dog

So, the purpose of the article is to show what users of the results of business analyst work expect and need. In fact, the article was written not only for business analysts, but also for those who are forced to use the results of their work. And not just to “read and use foul language”, but to be able to explain what they missed or did not take into account in their work.

Let's start with the basics: what is “business analysis”? I hope it is not a secret to anyone that “business analysis”, “business analysis” (audit) and “business analytics” are completely different concepts, and, apart from “similar words,” there is not much in common between them.

In order not to obstruct the already voluminous text, I made a “collection of definitions” in a footnote, who are interested, you can read.
')
Business analysis? No, I have not heard
For example, someone Howard Podeswa, in his book "UML for the IT Business Analyst" gives the following definitions (second edition, section 1, page 1):
There are two types of business analysts:
- An ordinary (non-IT) business analyst is one who works in the context of the business as a whole. Such a specialist is involved in process improvement, cost optimization, etc.
- Business analyst in IT: the one whose work takes place within the framework of individual IT projects - procurement, implementation, introduction of changes, etc. Its task is to interact with interested parties on the part of the customer (business users, technical staff, etc.) to collect the requirements emanating from the business.


The International Institute of Business Analysis ( www.iiba.org ) in the BABOK Guide 2.0, defines (Section 1.2, p. 3):
Business analysis is a set of tasks and techniques used as a link between participants and stakeholders to understand the structure, rules and operations within an organization, and to recommend solutions that enable a given organization to achieve its goals.

Business analysis provides an understanding of how organizations operate in order to meet their purpose and identify opportunities that organizations need to provide products and services external (in relation to the organization) to interested parties. It (business analysis) includes an indication of the goals of the organization, links of these goals with individual tasks, determination of the direction of the organization’s actions to achieve the specified goals and objectives, as well as setting methods (processes), as different departments and stakeholders in the organization and for its framework will interact with each other.

A business analyst is one who does all this, regardless of the name of his position. </ Blockquote
The Object Management Group ( www.omg.org ) in the BPMN 2.0 specification gives the following definition (p. 499):
A Business Analyst is a specialist who analyzes the needs and problems of a business, consults with users and stakeholders, to find opportunities to improve the return on business through IT, and also sets, manages and tracks these requirements in business processes.

Traditionally for the West, there is no single definition, but, nevertheless, there are some common features:
beacon of business analysis
  • collecting and documenting the requirements, wishes and goals to which the customer aspires;
  • analysis and documentation of processes;
  • analysis of the collected and systematized information and development of recommendations on the processes and / or their separate stages (here you can already talk about automation and other "buns").

Let's stop at this. And consider the first two of these points in more detail. The first two because with their high-quality implementation, the third part of the work of a business analyst becomes, for the most part, a matter of technology and experience. On the other hand, most of the reports of business analysts always describe the third stage in sufficient detail, with diagrams, recommendations and other things. But to understand how these recommendations are useful, or correct, it is often impossible because of the omissions in the first two stages.

Collection and documentation of requirements, wishes, business goals


So, as they say, it's time to figure out what this was all about. All this, in the sense of "business". And if the managers themselves and / or employees do not know this, “ then we go to you ” (c). In fact, this is a very important stage and there are some very unobvious difficulties.

Traditionally, let's start with definitions. What is business? Business, speaking in Russian, is just some kind of activity or occupation for which we spend our resources (time, money) and our abilities. And any “business” does not exist by itself in a vacuum; it serves to “meet the needs.” All this probably already heard more than once. So, the identification of these very needs and is one of the tasks of a business analyst at the first stage of the study.

Legend
Once upon a time I read that the motto of IBM in ancient times was the statement:
"We sell our customers not what they want, but what they need."
I do not know how true this is, but the statement of the question is very indicative.

And in order for us to have all this praise more understandable, let us digress from the granite of science, to more pliable matters - to examples. Imagine that we are faced with the task of researching the Post of Russia business. This example, I think, will be close to many, because each of us has come across with the mail. So what is the purpose of this organization? What need does it (the organization) satisfy? Many will answer right away that this is “mail delivery”. And it will not be the right answer. Let's ask a little differently, but what reflects the need of customers in “sending letters, parcels and so on”? And then surely everyone guessed it - the transfer of information and values ​​over distances. This is precisely the business need that this organization must meet.

I feel that there will be dissatisfied smirks, saying “you want to twist, turn, you want to fool” the author. But no. Take another look carefully. A person was not born with the knowledge that in order to tell something to another person behind forests and fields (in the sense of being very far away), you must first write it all down on paper, pack it in an envelope and send it by mail. Such were the requirements due to the underdevelopment of communications.

And we see that the incorrect definition of business goals leads to its (business, enterprise) dying. After all, cellular communication, fax, e-mail - these means also satisfy the same need - the transfer of information over distances. The fact that the management of Post of Russia did not understand this, it happens, but the fact that business analysts, whom they probably called, did not indicate this - this is already a problem. If we talk about mail, then its task was and remains "the transfer of information and values ​​over distances." Not sending parcels, envelopes, wrappers — namely, “transmitting information and values,” regardless of the way she does it, even let her teleport or produce it on the spot.

With the advent of cell phones, it was obvious that writing letters would be less. Only those who are interested in the transfer of information on physical media remain. That's what prevented the delivery of faxes and the rights of notaries at each post office, so that the person on the other end would receive a certified copy? In the future, you could use the scan and file transfer for printing in the right compartment (the benefit of digital signatures is already in progress). Again, money transfers in Russia with the receipt / departure in each branch. And if we recall the call offices, which were often in the mail, which prevented the organization of VoIP, or its equivalent for cheap calls? It was precisely the lack of understanding of the goals of the organization that prevented it. Now, all the sweet pieces went to courier services, money transfer systems and other VoIP operators. And it was necessary, just to think a little.

I hope that this example clearly showed that the primary goal of a business analyst is to recognize and indicate the business goals of an enterprise, the needs that it satisfies. And how does it (the company) do it (as in our example, sending envelopes, notarizing the fax-mail items, or a video call service) is already a second question. These will be just specific business options for solving the problem. Knowing the business goals, the marketer, sales manager, risk analyst and many others can determine in advance the possibilities and risks of this direction, and offer the customer more interesting options, or point out competitors. Concentration on specific business options, as we clearly see, leads to disastrous results.

The following “artifacts” that a business analyst should work with are tasks, requirements and wishes. And now comes the moment when we (as business analysts) will be very useful in marketing assistance. The need then we identified. But those who will satisfy this need, using the services of a business, must be found by marketers. "Market segment", "target audience", and hence the requirements for the service provided or products produced - must be set by marketing. This is their bread, and they work it out.

Obviously, the business analyst must understand and document all the requirements and tasks that will be voiced, precisely from a business point of view - satisfying quite specific needs. At the same time, when describing them, it is desirable to avoid all sorts of vague definitions of tasks in the “make Aunt Glasha happy” style, or try to specify them as much as possible (for example, “for the“ assistant ”position, reduce the amount of work performed to 5 operations, total time not more than 6 hours a day "). And most importantly, all asked requirements must have a numerical, absolute value. Suppose we received a requirement: “reduce the cost of delivering items within one area by 5%.” Reduce what? What are the costs: labor, delivery time, delivery costs, or all together in a certain proportion? How to count all this? Ideally, it would be desirable for the requirements to be recorded in a form close to the following examples:
The time spent on delivering shipments weighing up to 1 kg, within 300 km from the place of departure, from the moment of sending the item to the office until it is ready to be issued to the recipient, must be reduced from 24 to 16 working hours.
The cost of delivery of shipments within 300 km from the place of departure, weighing up to 1 kg, taking into account:

  • the cost of processing the shipment;
  • the wages of all those involved in the process of receiving, processing, delivering, issuing and other necessary procedures (including cleaning the premises, servicing vehicles and premises, issuing documents, etc.);
  • equipment depreciation;
  • the cost of consumables;
  • constant quality and speed of delivery.

It should be reduced from 50 to 45 rubles, in terms of one consignment, with a total number of departures of at least 50 per day.

Surely they will immediately argue, “ what about the requirements in the style of“ increase the transparency of the processes? "In fact, there is nothing complicated. First, you need to understand what reasons led the customer to specify such a requirement? In this case, this is a consequence of the fact that it is impossible to control the movement of materials / goods / items in the process of work or other actions. Therefore, such requirements can be written in the style:
The time of providing information on a request to find an arbitrary batch / unit of goods shall not exceed 5 minutes from the moment of its sending / formation.

or
The report on the passage of the stages of shipment / production units / batch of products should be updated at least once per hour.

In this form, the performers will know exactly what is expected of them and will easily be able to confirm to the customer the achievement of the set goals and objectives. On the other hand, the customer will know what he pays for and what to expect.

And finally, I think everyone understands this, it is desirable to set goals and objectives for the process as a whole, and not for its separate stages. Although optimization and / or automation will relate to individual stages of the process, we also understand that improvement in one place often entails deterioration in another. Therefore, only generalized indicators give us an integral assessment of efficiency.

We go further. When we talk about the tasks that the customer sets, the business analyst must make sure that there are real opportunities to accomplish these tasks. Here, for example, the task is to guarantee the maximum delivery time for parcels from Kaliningrad to Petropavlovsk-Kamchatsky in 3 days. Super. Everyone will only be happy. However, analyzing transport opportunities, we see that purely physically, sometimes in the glorious city of volcanoes and “Avachi”, a week can “not be weather.” That is a week planes do not fly there. And in this case, all promises, improvement of processes and anything else will not allow to solve this problem in the current conditions. Therefore, such a task should either be rejected at the earliest stages, or placed under conditions when they can be achieved.

Case study
So, the introduction of a distribution automation system in a branch of a fairly large and well-known international company in one of the republics b. THE USSR. In the course of the analysis, one of the requirements is revealed: “the system should automatically give a discount on the order / invoice, provided that the client includes in the purchase a certain, pre-agreed set of goods that is tied to each specific client. The list of products for different customers is different and must be transferred to the implemented system during the integration process, from the customer’s accounting system. ”

As we can see, the requirement is basically simple. With superficial analysis, everything is fine:

  • Indeed, in the contract (contract) with each client there is an application indicating the item set, the presence of which (item set) ensures the application of a discount on the entire order;
  • moreover, in 1C (with which we will integrate) such a field is also present in the invoice, and it is often filled in in the working invoices;
  • all employees of the branch, from the branch Director, to the project manager on the part of the customer and ordinary employees argue that everything works this way automatically.

But, since I had to prepare not just a “certain document” but a complete and consistent source of information about the project and processes, I had to specify not only the requirements, but also how they (the requirements) should and can be implemented. This nuance is often overlooked, but it is very important.

So, I try to understand how they calculate this discount, and where they keep a list of “recommended for order” products, in the context of customers. Having received the 1C configuration, I see that this field does not automatically fill in at all. Only manual input. The project manager refuses, and claims that everything works fine automatically, and I watched "some kind of ancient unfinished 1C configuration." The sales department furiously supports him in this, indicating that "here, in the invoice, it is filled in." In the end, I ask you to show clearly how it works in reality and where they are and in what form they store these “recommended orders”.

In general, it turned out that the operator at the office "remembers" each client and his recommended set, and sets the discount percentage manually. If “suddenly” he “forgets” what the actual recommended nomenclature of this client is, then “he can find a contract and consult with him”. Nobody could show how this happens in practice.

As a result, the customer began to bring all this disgrace to order, the categorization of customers was introduced, and the “recommended assortments” were introduced for these categories. As for the implementation, these functions were provided with the means of the system being introduced and managed there.

As you can see, ignoring details in requirements and tasks can lead to troubles at further stages of work and this will not add “happiness” to developers, implementers and everyone who will have to use the report and make the “improvements” prescribed by the business analyst, who “forgot to clarify a couple non essential details. ”

I hope everyone imbued and realized that for each requirement and task, you need to make sure that it is possible to implement it and provide explanations with examples and detailed explanations (with restrictions, conditions and details on sources, means, data formats, conditions of their applicability and so on). Looking ahead, the same applies to the found deficiencies, problems, non-standard situations. It is highly desirable to also give the reasons for their appearance.

For example, if “duplicates” are found in the goods directory, then it is necessary to find out and indicate the reason for their appearance. In this case, at least three options are possible:


As we see, there may be situations when either you don’t need to change anything, or there are enough organizational measures, or you have to expand the scope of work by modernizing the used accounting system. In the absence of such details, a simple statement of fact “and in the reference books the duplication of positions” does not mean anything, and even recommendations in the “put the directory in order” or “remove twins” style can be both useless and erroneous.

And at the end of this section, I’ll focus on the fact that business processes have nothing to do with such economic indicators as sales volumes and prices. This is the responsibility of the commercial department in general, and marketing in particular. In other words, marketing is responsible for creating demand, and employees and business processes are responsible for satisfying it. And the only thing how business processes of any enterprise can affect profits is only by reducing costs, including time costs. Pricing, the formation of requirements for products, the volume of production / sales - all this concerns marketing and only marketing.

Byl
At one time I ran into one very competent and professional marketer. Unfortunately, not personally, but found out about him from my colleague. In a free retelling, his position is as follows (if we are talking about distribution, without taking into account the struggle with competitors):
  • in no case should the sales department have the task to ship as many products as possible, its task is to ensure that the product is on the market and available to the buyer everywhere;
  • if the product is commercially available and readily available to the buyer, but they buy little of it, then this is not a problem of the sales department - this is a problem of the marketing department.

So, summarizing this part, we can say that the collection and analysis of requirements should be accompanied by an analysis of the reasons for the appearance of these requirements, the availability of physical capabilities for their implementation, as well as risks, and ways to minimize both the risks and their consequences. At the same time, requirements and tasks should be presented in the form of calculated indicators and set in absolute values. In essence, creating or improving processes is an organizational, or administrative function. And in order to realize it (function) effectively, it is necessary to clearly see why all this “disgrace” is being started, what is expected and what opportunities there are of these expectations to be realized.

→ Continued here

Sources of images:

1. The image of the lighthouse is taken here .
2. Dog from here

Source: https://habr.com/ru/post/327354/


All Articles