Archiv der Kategorie: Business modeling

Business modeling consists of topics like business idea, business concept.

Unnecessary loss of friction in the process

Business procedures, such as the development of new services, the procurement of material, the production of goods or the distribution of commodities, are improved through the active Business Process Management (BPM). For this purpose, the procedures are described and weaknesses are visualized in order to optimize the sequence of activities so that only the right thing is done right, e.g.

  • better involved customers,
  • more reliable delivery,
  • accelerated turnaround time,
  • automated tasks
  • minimized time and costs,
  • increased quality,
  • and so on.

The desired effects can not be accomplished, if existing approaches and demands get in the way of real progress. This leads to losses of friction that do not disappear with the designing of processes.

Often these hurdles are homemade. A good example of impeding attitudes is the way of dealing with tasks, authority and responsibility.

  • Tasks without authority and responsibility
    The actual work is performed as a task. Usually something is created, processed, finished or executed – e.g. building a prototype, polishing a surface, assembling a device, washing a car. In order to be able to perform the task, the performers need appropriate knowledge and skills.
    However, if they lack the appropriate authority and responsibility for the results, then the fulfillment will be poor.
  • Authority without tasks and responsibility
    The authority describes the rights that somebody has. This includes the permissions to perform or direct something – e.g. to use a certain machine for manufacturing or to give instructions to the employees. The corresponding permissions must be known by all involved people.
    If someone has sufficient authorities, but no task or responsibility, the competence loses its effect.
  • Responsibility without task and authority
    Responsibility describes the commitments that you make. This can be direct responsibility or shared responsibility – direct responsibility refers to one’s own actions and the activities of directly assigned employees; the shared responsibility arises, if one has indirect influence on occurrences as part of a team (in the sense of cling together, swing together).
    Individuals like to adorn themselves with the glow of responsibility – especially, if it does not result in any consequences, because there are no tasks associated or special permissions required.

In simple words: Tasks, authority and responsibility should ALWAYS be in one hand for the sake of adequate results. It makes no sense to assign someone to a task without the necessary authorities for the fulfillment and without the responsibility for the result. Good examples are the Japanese line workers, who perform subtasks in making a car.  They have the right and duty to immediately stop the line, if they find a mistake. This allows the earliest possible correction of the flaw. That way they avoid the accumulation of unnecessary rework. At the same time, costly decision-making processes are avoided, which would burden the process.

Bottom line: The design of processes often begins with the application of IT, in the hope that this can improve the process. However, often old rules and roles are retained. As a result, for example, task, authority and responsibility remain in different hands. Even, if it is faster and you only have to click once to fulfill your responsibilities or to allow the performers to do their job. The largest effect is achieved by transferring the task, authority and responsibility to the people, who fulfill the task. They know what to do, can decide how to do it, and strive for the required quality of the result. That way, the losses of friction in a process are minimized.

The essential reason for BPM

Time flies and the employees are working step by step until they are finished. Being finished means that the customers, who are willing to spend money for the result, receive the deliverable. Very few, who collaborate on it, are lucky enough to be in direct contact with the paying customer. Mostly they have internal “customers” who contribute their part of the value chain to the deliverable. The entire process is determined by the involved people. Over the past decades, we have learned that deliberately designing these procedures, the business processes, has many benefits for everybody: the employees know what to do and the people in charge can control the process. In some cases, companies are taking care of the processes for the first time. In other cases, the design is done for the umpteenth time. Why do they make this effort for Business Process Management (BPM)?

There are many justifications for the development of business processes.

  • Toppling silos into tunnels
    Overcoming the silo boundaries is a major reason for BPM – double work disappears, delays in crossing the border are eliminated, silo-egoisms will be dissolved. The tunnel also has its boundaries, but they are aligned to the results and the customer. Nevertheless that’s not the main reason for BPM.
  • Letting the data flow
    In the future the floods of information will continuously rising, since more and more processes will be digitally transformed – automation of processes; digitization of deliverables; network-based access to everything, anytime, anywhere. Nevertheless that’s not the main reason for BPM.
  • Getting a neutral rating
    It is hard to estimate how strongly individuals engage into their work. It gets even more difficult when it comes to all employees of a large company. The solution of the past years is the certification by a neutral third-party. The processes are a favorable goal for all people concerned – and as soon as the processes are described, they are also practiced – or not. Nevertheless that’s not the main reason for BPM.
  • Enabling IT solutions
    A specific manifestation of the processes can be found in the IT systems. Since the procedures are encrypted in executable program code, at this point in time clear procedures must be available at latest. Nevertheless that’s not the main reason for BPM.
  • Redistributing resources
    The organizational structure will continue to be the most important tool for distributing means and raw materials. However, the proximity to the value creation suggests assigning employees and resources of the production more likely to the business processes, because they can be better aligned with the results. As long as both approaches are pursued, decision makers have to accept that they will not get consistent figures for their decisions. Nevertheless that’s not the main reason for BPM.
  • Describing processes
    Without the description of the processes, all business players lack an objective basis for discussion, evaluation or changing the processes, to make clear allocations of resources and data, to be certified and to realize the IT. Only something printable is valuable. Nevertheless that’s not the main reason for BPM.

As apt as all these reasons are, they are always only means to an end. Eventually it’s not about the process description, it’s about actual business. The essential reason for BPM is:

Deliver
customers reliably
adequate deliverables
based on applied best practice.

This only works, if the wishes of the customer are known along the value chain and the best practices are consistently applied to deliver the service that customers are willing to pay for. The following aspects support the essential reason for BPM.

  • Only do what is required – not less
    Every process has customers: internally the neighboring department, which benefits from flawless inputs even if it does not pay for it; external institutions that are eligible for reporting; and above all the customers, who finance the whole thing with their payment.
  • Meet the requirements with minimal effort
    In all cases, it is only necessary to do what the recipient of a deliverable actually needs: all employees must do their part to avoid errors, so that there is no need to constantly rework; the tax office and the shareholders are entitled to accurate reporting; Customers determine the required quality with their payment and sustained loyalty.
  • Carpe diem
    Above all, processes are characterized by their speed. It is not about maximum acceleration, as this would lead to situations which would be hard to control. Also, the vanishing flow is not desirable because it makes timely results impossible. The goal is to adjust the gradient so that as many results as possible are delivered quickly and punctually.
  • Being able to recognize what is worth seeing
    As early as possible being able to react to an obstructive incident requires visibility of the current situation. Even the soloistic craftsman has several workpieces in progress at the same time. In business it is an indescribably large number of processes that take place simultaneously. The only chance for an overview is the designed process – together with a contemporary approach of the resulting flood of data.
  • Again and again and again
    Not the number of processes is crucial, but the fact that these processes run repeatedly – preferably always the same way. On the one hand, the effort of designing the processes pays off that way. On the other hand, repeating the same process always creates routine and safety for the employees, what improves the quality of the results.

Bottom line: While in the past the value chain took place predominantly inside the factory fence, today we have an intense, global network of companies of all sizes. The connecting element is the business process that starts and ends with the customer. The process does not become important with the printable description, but with the applied practice that is shared between man and machine. People are the deciding factor because even machines need the human operator. Without involving the employees, only the offices are decorated with A0 plots and the process design happens far from the business in the ivory tower. Do not undermine the essential reason of BPM with the wrong focus: Deliver customers reliably adequate deliverables based on applied best practice.