Mostrar mensagens com a etiqueta abordagem por processos. Mostrar todas as mensagens
Mostrar mensagens com a etiqueta abordagem por processos. Mostrar todas as mensagens

quarta-feira, fevereiro 21, 2024

Primeiro, o que é a abordagem por processos?

Primeiro, o que é a abordagem por processos?

A abordagem por processos consiste em olhar para uma organização como sendo constituída por um conjunto de processos que interagem uns com os outros, porque essa é a forma mais eficaz e eficiente de atingir resultados desejados. Enquanto a abordagem tradicional é a de ver uma organização como um conjunto de departamentos.

Resultados consistentes e previsíveis podem ser mais eficaz e eficientemente atingidos quando as atividades são compreendidas e geridas como processos inter-relacionados que funcionam como um sistema coerente sintonizado num propósito comum.

A reengenharia dos processos nos anos 80 e 90 contribuiu para a popularização da abordagem por processos, que foi depois formalizada nos sistemas de gestão da qualidade pela versão de 2000 da ISO 9001.

Adoptar a abordagem por processos promove uma alteração na forma como se vêem as actividades numa organização. Michael Hammer escreveu:

"First, processes are teleological (from the Greek word telos, meaning "goal' or mission"). That is, they focus on the outcome of work rather than on work as an end in itself. In an organization that pays attention to its processes, everyone in the company understands the why as well as the what of their work. How people are trained and how performance is measured must reinforce the outcome orientation of processes.

Second, processes are customer-focused. Thinking in terms of processes compels a business to see itself and its work from the perspective of the customer, rather than from its own.

...Third, processes are holistic. Process thinking transcends individual activities. It concentrates instead on how activities fit together to produce the best outcome — the results that must be delivered to customers. The key goal - superior value for the customer — is achieved when an assortment of warring departments is replaced with a seamless web of collaborators working together for a unified purpose."

Adoptar a abordagem por processos permite melhorar a eficiência operacional. Quando se traduz o que se faz numa organização num conjunto de processos, facilmente se descobrem os pontos mortos, as etapas que consomem demasiado tempo, os by-pass que normalmente trazem problemas. Um processo é um conjunto de verbos, um processo é acção, um processo é fluxo, um processo é um rio com pressa de chegar à foz. Por isso, uso muitas vezes a imagem da água a jorrar de uma torneira para ilustrar o que para mim é um processo. Quando uma empresa ilustra pela primeira vez como funciona, usando a abordagem por processos, normalmente descobre com horror o lado direito da figura que se segue. Em vez de fluxo livre, temos barreiras a seguir a barreiras, constrangimentos e regras que diminuem o fluxo e levantam problemas.


Enquanto a abordagem por processos promove a satisfação dos clientes do processo e a eficiência do processo, a abordagem tradicional, departamental, promove o cumpriento dos objectivos departamentais, por vezes isoladamente do resto da empresa, levando à clássica visão dos silos. 

Uma analogia clássica para o que acontece numa organização sem a abordagem de processo é ver a organização como um conjunto de departamentos, os silos. Silos porque cada silo só contacta os outros silos através do topo. Silos porque cada silo responde a incentivos diferentes e conflituantes. Silos porque não vêem o panorama geral.

Lembro-me de exemplos de empresas onde o departamento comercial fecha vendas não lucrativas porque as vendas são boas para os bónus, mesmo que sejam não lucrativas. Ou as Compras recebem grandes bónus com as poupanças alcançadas, as famosas "savings" enquanto o resto da empresa é atormentado com problemas de qualidade, atrasos ou erros dos fornecedores, ou a Produção está tão focada no cumprimento dos objetivos de eficiência que não se preocupa com os acordos com os clientes, ou o cliente que negociou uma entrega especial, pagou extra por ela, contratou uma equipa para receber e aplicar o que vai receber, e depois a entrega não é feita porque o departamento de Logística é avaliado e premiado com base na capacidade de minimizar os custos de envio.

Com a abordagem de processo, diferentes pessoas de diferentes departamentos trabalham juntas e coordenam-se para alcançar objectivos comuns.


Há tempos estava numa carruagem de comboio e não pude deixar de ouvir a conversa de duas pessoas que trabalhavam numa empresa de serviços ligada ao mundo da criação artística para o marketing de marcas. Foi impressionante a descrição das actividades que eram realizadas descoordenadmente sem a orientação da abordagem por processos, com o consequente desperdício de recursos, o tempo perdido, a insatisfação dos clientes, a insatisfação dos trabalhadores, a margem perdida, a reputação manchada.

Se desenhassem o processo, se identificassem as caixas de decisão e a frequência de decisões que emperram, que atrasam o processo, se calculassem a diferença entre o tempo de ciclo teórico e o tempo de ciclo real ficariam com os cabelos em pé. Como se trata de um serviço, algo abstracto, é mais difícil de apreender. Contudo, quando se desenha um processo ... o serviço torna-se tão concreto quanto um processo de uma empresa manufactureira.

Quando se usa a abordagem por processos é mais fácil:

  • trabalhar na determinação dos riscos e oportunidades. Olhando para um fluxograma perguntamos: O que pode correr mal? O que nos pode levar a resultados indesejados?
  • determinar as competências necessárias para o desempenho eficaz. Olhando para um fluxograma, identificamos as funções intervenientes, e olhando para cada etapa do processo podemos responder de forma clara às perguntas sobre que conhecimentos, que experiências alguém precisa de ter para realizar autónoma e correctamente uma dada tarefa, parte de uma actividade, parte do processo?
  • desenvolver acções de melhoria. Olhando para um ou mais fluxogramas dos processos que contribuem para um resultado a melhorar, podemos localizar onde, em que partes dos processos, ocorrem eventos que prejudicam o desempenho do processo. Ou seja, balizamos a área a investigar e a melhorar. 

Um dos principais problemas que vejo na aplicação da abordagem por processos passa pela deficiente determinação dos processos. E o erro mais comum é confundir processo com departamento. Assim, o que em muitas empresas se chama de processo, é na realidade a descrição de uma série de actividades desempenhadas num departamento. O exemplo clássico é um suposto processo dos Recursos Humanos que lista como se faz:

  • a admissão de novos trabalhadores:
  • a avaliação do desempenho dos trabalhadores;
  • a formação dos trabalhadores;
  • as promoções;
  • o pagamento de salários;
  • a marcação de férias;
  • os processos disciplinares;
  • faltas e assiduidade;
  • demissões;
  • legislação laboral;
  • despedimentos;
  • ...
Qual a relação entre o pagamento de salários e a formação, ou os processos disciplinares?

Por isso, uma das minhas regras é fugir de atribuir nomes aos processos que se relacionem com os nomes de departamentos.

Continua.

segunda-feira, janeiro 15, 2024

"who thinks about the entire company”

"In a recent CEO research study we conducted, we interviewed a dozen CEOs of mid- to large-size companies. There was one key challenge every CEO mentioned: their frustration at not being able to get their executive teams to work together. “I’m the only one who thinks about the entire company,” one CEO lamented, “and despite my best efforts, each of my executives is only concerned with their own function or team.”

It's long been recognized that cross-functional collaboration is essential. Still, stubborn silos that bog down execution, hamper innovation, and slow decision-making are still a common and persistent challenge. In our work with company leaders, we've found that without leaders working together at the top, silos and dysfunction are inevitable. The onus is therefore on senior leaders to knock down these silos — moving beyond their ability to lead their own teams to also prioritize leading across the organization."

É por isto que a abordagem por processos: ver uma organização como um conjunto de processos teleologicamente focados na sua razão de ser, no seu propósito. Um fluxo a caminho dos entregáveis ao cliente do processo e indiferente a barreiras e "alfândegas" departamentais.

Quanto maior uma organização, maiores os benefícios da adopção da abordagem por processos. Porque:

  • facilita a coordenação entre diferentes departamentos, garantindo que todos estão alinhados com os objectivos da organização;
  • ajuda a identificar redundâncias e gargalos, permitindo que a organização optimiza as suas operações. Quanto maior uma organização, maior o impacte das ineficiências;
  • incentiva a análise e revisão contínua dos processos. Quanto maior uma organização, maior o efeito multiplicador.
Infelizmente, a maioria das empresas que pensa estar a usar a abordagem por processos em boa verdade não o está.

sábado, julho 08, 2023

Trabalhar o denominador ou o numerador

A continuar a minha leitura de "Flawless consulting: a guide to getting your expertise used" de Peter Block encontrei este trecho:

"In the second edition of this book at the turn of the century, what was new in the discovery phase were the whole-system methodologies described in Chapter Eleven. Since then, probably the most interesting new development in discovery is the growing interest in looking at a system's gifts, capacities, and possibilities. This approach is used in addition to, or sometimes in contrast to, looking at problems - their causes and their solutions.

This approach goes under many names: asset-based community development, positive deviance, positive psychology, appreciative inquiry, future search, and more. Each of these is based on the premise that looking at what in our history we want to preserve, or what is working in a system now, or what a system longs to create in the future is a powerful way to build commitment and sustainability into any consultative or change process."

A abordagem tradicional a que o autor se refere é a de melhorar o que existe através do ataque às causas das falhas, a abordagem nova referida neste trecho é a de procurar os "system's gifts, capacities, and possibilities".

Entretanto, passei parte da semana a preparar uma acção de formação para introduzir um conjunto de pessoas à abordagem por processos para que participem num esforço de melhoria na senda da abordagem tradicional. 

A abordagem tradicional tem o seu lugar. No entanto, em algumas circunstâncias não é a mais adequada. Por isso, ao pensar no país escrevi em 2013: Redsigma - O fim da linha

Como exemplo da abordagem assente em "looking at a system's gifts, capacities, and possibilities" também de 2013: O repovoamento do interior também passa por isto.

De um lado lado temos o trabalhar o denominador (a abordagem tradicional), do outro o trabalhar o numerador (a abordagem dos gifts, capacities, and possibilities).

quarta-feira, maio 03, 2023

Optimizar processos!

Nos últimos meses várias empresas de vários países contactaram-me por causa de projectos na área da optimização de processos. 

Interessante este artigo, "The Boss Wants to Make You More Efficient", publicado no WSJ do passado Sábado:

"For years when AT&T Inc. threw a retirement party, employees had to enter the names of attendees in the telecom company's expense-reporting system. It was the kind of small annoyance that is an accepted part of office life for millions of whitecollar workers.

But a technology team at AT&T figured the requirement, plus a similar one for service-anniversary parties, was costing its workers 28,500 hours a year that they could be spending on more important tasks. So the company scrapped it, and in the past two years has made more than 160 similar moves it estimates are saving employees nearly 3 million hours a vear.

...

The threat of an economic contraction has put companies under growing pressure from investors to reduce waste and boost productivity. That has led to a wave of layoffs and other cost cutting. Many companies are also moving bevond broad austerity measures and homing in on the minutiae of everyday work. They are rethinking processes and how employees do their jobs, with the goal of getting workers to make better use of their time. The efforts are permeating U.S. companies to a degree that executives say they haven't seen in years.

...

Efficiency is about how work is done, and it is closely linked with productivity. If workers are more efficient -reducing the time and resources needed to complete a task-productivity should theoretically improve, too. Productivity, as narrowly defined by macroeconomists, measures the amount of output produced in one hour of labor.

How companies measure productivity varies. Some businesses consider the revenue or profit generated per employee. Others focus on projects delivered or new products shipped. Improved processes could also pave the way for companies to employ fewer people.

At some point, however, shaving time off workers' tasks in microdoses reaches a limit in terms of cost savings. Companies ultimately still need innovation and investment to fuel long-term growth, said Roger Martin, [Moi ici: Nunca esquecer esta achega de Roger Martin, aumentar a produtividade à custa da eficiência tem limites, são "peaners". Aumentar a produtividade a sério tem de passar pelo numerado da equação da produtividade] former dean of the Roman School of Management at the University of Toronto and now an author and adviser to executives.

Labor productivity has largely led by Toyota Motor Corp., which popularized an approach to manufacturing defined by an obsessive commitment to efficiency and constant self-assessment. Elements of that playbook are now being adopted in sectors well beyond manufacturing, from tech to finance to food service. [Moi ici: Costumo dizer isto muitas vezes, a abordagem por processos é muito mais eficaz a nível de serviços do que na fabricação. Na fabricação as coisas vêem-se, as coisas circulam. Nos serviços, é muito mais impactante e revelador transformar as coisas intangíveis em algo palpável. Mapear um processo é como levar uma organização a tomar consciência de como é, de como funciona e esse é o primeiro passo para a batota]"

Imagem retirada deste postal Uma saudade enorme ... 

terça-feira, agosto 30, 2022

Processo versus procedimento

Isto é tão, mas tão verdade:

"If you belong to an organisation that still considers existing documented procedures as quality management processes not only have you not captured the spirit of the new approach but you should be picked up by your customers and other assessment organisations as not meeting the requirements of clause 4.4.1. The fact that more nonconformities haven’t been raised against organisations says a lot about the state of third-party certification and its economic need to survive. Perhaps conformity assessment bodies (CAB) are retaining paying customers who don’t actually deserve to hold the certification."

Recordo:

Trecho inicial retirado de "ISO 9001 Process approach"

quinta-feira, outubro 14, 2021

Conseguir tirar partida da abordagem por processos

Por que é que tantas organizações certificadas pouco ou nenhum valor retiram da abordagem por processos e do seu sistema de gestão?

Da minha experiência de auditor a sistemas de gestão, supostamente maduros, ou seja, com vários anos após a implementação, encontro três causas principais para o pouco valor acrescentado desses sistemas.

Primeiro, objectivos de treta.

As organizações não levam os seus sistemas de gestão a sério, são um sistema paralelo à gestão do negócio. Definem objectivos “infantis”, objectivos pueris que põem logo de sobreaviso quem os encontra. Se os objectivos são de merda não é de esperar grande exigência de melhoria, e num mundo em mudança não melhorar é efectivamente piorar. Acima de tudo é um sistema de gestão que funciona mais como uma carga burocrática mais ou menos pesada

Segundo, considerar que os objectivos do sistema são o somatório dos objectivos de cada processo.

Podemos optimizar um processo associado à aquisição de recursos, mas que gera ineficácia na organização. Compramos muito bem, mas os produtos chegam tarde, ou trazem defeitos que só são descobertos durante a produção ou prestação do serviço, a pior altura para isso acontecer. Recordo uma empresa em que o sector das compras todos os anos recebia bónus, à conta dos savings, enquanto semeava o caos nas operações. Ou uma outra empresa onde o departamento Comercial ganhava bónus por ganhar negócios que funcionavam como mais um prego no caixão da empresa.

É claro que os processos devem ter objectivos, devem poder ser monitorizados e medidos, mas estamos a falar de objectivos operacionais. Quando falamos de objectivos do sistema falamos em objectivos da organização como um todo. Quase sempre a optimização de um todo implica a subordinação de alguns processos a um desempenho inferior.

Este é talvez o erro mais comum.

Terceiro, pretender que o mundo é uma realidade simples ou complicada.

Terceiro, pretender que o mundo é uma realidade simples ou complicada e avançar com planos de acção genéricos que são quase sempre uma reformulação frásica das actividades já previstas nos processos.

Pode ser por causa de uma visão infantil do mundo, mundo simples ou complicado com relações de causa efeito simples e evidentes. Pode ser por causa de falta de tempo e a necessidade de picar o relógio de ponto, e há que ter um plano de acção, qualquer plano serve. Ou pode ser por causa de uma metodologia inadequada para a definição das acções como referi neste postal "O que fazer?"


quinta-feira, setembro 09, 2021

Another improvement project


Yesterday, the start of an improvement project.

First step: describe the "as is" process - how do we work? how do we go from inputs to outputs?

Post-its written and posted by the stakeholders.

Step Two: What Can Go Wrong? what usually goes wrong? what do we usually complain to internal suppliers? What complaints do we usually receive from our internal customers?

Post-its written and posted by the stakeholders.

Homework follows.

PS: Paper tablecloths can have very interesting uses!!!


quinta-feira, julho 15, 2021

"Every firm is unique"

"Every firm is unique; it has its own unique history. So we cannot predict the impact or effect of a particular strategy or initiative on your firm, because we know nothing about the specific situation, and no one knows exactly what will be the ultimate impact of any change on the wider system. Your firm has evolved over time to look like it does today. Its value system can be viewed as a set of interconnecting routines. Routines are patterns of action and interaction that are involved in the three value activities of sourcing, operations and selling."

Trechos retirados de: Paul Raspin. “What's Your Competitive Advantage?”

sábado, junho 19, 2021

For ISO 9001 people...

Implementing a management system is like tossing and keeping a series of plates in the air circulating like a jongleur is able to do it.

A dish is, for example, about ordering, receiving, and supplying raw materials to production. Another dish is about sales, another is about production, control, and packaging, another is about...

What often happens is that once the dishes are released... they fall to the ground...

The management system cannot take on a life of its own. Someone has to always be aware that the dishes have fallen and that they have to be thrown into the air again.

This happens when an internal audit approaches, or when a surveillance audit date looms. Then, on the run, corrections are made, figurately “some walls are repaired, some wires are fastened, and a new scenario is set up” so that the next audit will look good in the photograph.

One of the most important mechanisms to keep the management system working, to keep the dishes in the air, involves measuring, analyzing, and making decisions to improve.

Let me show you why.

First, let us consider three levels of monitoring, measuring, and analyzing:

  • The everyday level - everyday people have to act, to react to defects, to complaints, to delays, to orders, to events
  • The process level - periodically, people will collect information about process performance and after analysis will decide if any change, any improvement is needed
  • At the company level - periodically, people will collect information about company-wide performance and after analysis will decide if any change, any improvement is needed
At the everyday level things normally work, the pressure of the moment, the weight of reality make people acting. However, improvement only comes as a consequence of the other two levels. 

Yes, solving "sporadic spikes", controlling is not the same thing as improving. Remember the good old Joseph Juran:
Improvement only happens when you deliberately decide to change the status quo in a positive way. Improvement is not about eliminating sporadic spikes, improving is not about acting around a frame, improving is about connecting the frames and seeing the film, seeing the trend, seeing what is beyond the foam of the days. 
What if there is no discipline to stick with the actions that lead to the analysis at the process and company level?

What kind of improvement, what rate of improvement can we expect from not working at these two levels? I dare to state that without these two levels there is no improvement. And more, these two levels are not event-based, but calendar-based.

Let me show how ISO 9001:2015 clauses are used while we perform the two levels. 

At the company level:
At the process level:

These inputs are used in analysis and evaluation (also inputs from audit results and management review):

Let us see the outputs:
Check out how the outputs of analysis and evaluation can leverage changes in:
  • competency requirements
  • competency gaps
  • risks and opportunities
  • processes
So, if you don't do these two types of analysis and evaluation improvement is only event-based never calendar-based.

Why is that demand for training and webinars on improvement are always not a priority for ISO 9001 people with an implemented quality management system?
  • Do you have the right indicators? (Different organizations in the same economic sector with different strategies may require different indicators due to different priorities)
  • Do you have a dashboard? Is it well designed according to the rules?
  • Do you prepare a report for analysis and evaluation? Do you fall in the three most common mistakes in presenting data?
  • Do you make decisions about improvement?
  • Do you use the project approach to command improvement?
  • Do you use tools and techniques to find the root causes?

domingo, fevereiro 14, 2021

How can we use the process approach (part IVa)


5.Processes and strategy

5.1 Anything about strategy in ISO 9001 and ISO 9000?

ISO 9000:2015 defines strategy as:
plan to achieve a long-term or overall objective
When you remember the old article from Henry Mintzberg, The Strategy Concept I: Five Ps for Strategy, published in October 1987 by California Management Review. 
Summarizing the strategy in a plan is too little, too poor. 

What about ISO 9001:2015, where does the strategy come in? 

Clause 4.1:
The organization shall determine external and internal issues that are relevant to its purpose and its strategic direction
Interestingly, not many people realize that relevant external and internal issues and their classification are a function of strategic orientation.

Clause 5.1.1:
ensuring that the quality policy and quality objectives are established for the quality management system and are compatible with the context and strategic direction of the organization;
OK, alignment of quality policy with context and strategic direction.

Clause 5.2.1:
is appropriate to the purpose and context of the organization and supports its strategic direction;
Again, alignment of quality policy with context and strategic direction. Quality policy should derive from strategic orientation.

Clause 9.3.1:
Top management shall review the organization’s quality management system, at planned intervals, to ensure its continuing suitability, adequacy, effectiveness and alignment with the strategic direction of the organization.
OK, this is understandable, it is peaceful. 

That’s it!!!

Not very useful as a guide to work with strategy.

Let us try another door. One of the quality management principles is customer focus. ISO 9000:2015 states:
The primary focus of quality management is to meet customer requirements and to strive to exceed customer expectations.
One of the things that worries me about ISO 9001 is that it uses the language "customer" instead of "target customer".

Seth Godin in his book “We Are All Weird” writes:
"The mass market — which made average products for average people was invented by organizations that needed to keep their factories and systems running efficiently.
Stop for a second and think about the backwards nature of that sentence.
The factory came first. It led to the mass market. Not the other way around.”
“For a hundred years, industrialists have had a clearly stated goal: standardized workers building standardized parts”, [Another text by Seth Godin, from his blog]. This resulted, as a business model, while demand was bigger than supply. When demand is bigger than supply, the boss, the one calling the shots, is the one who produces. And when that is the case, whoever is more efficient wins. Everyone tries to compete for the lowest cost. 
In this world, the competitive landscape can be compared to a single mountain and all competitors try to climb that mountain, the higher they rise, the higher the yield, but the higher they climb, the fewer the number of companies that survive, because in this landscape of a single mountain, the one that wins is the one that uses the effect of scale, grow in volume to lower unit costs and be more competitive.

As soon as supply started to exceed the level of demand, the economic world began a transformation towards more variety. In terms of the competitive landscape, this translates into many, more and more mountains. And those who climb one do not compete with those who climb the other:
In an economic world full of different peaks in a rugged landscape there are many types of customers. Different customers look and value different things. 

Let us stay away from statistics and look customers in the eye, literally and metaphorically. If we look at customers who value price above all else, what satisfies them? 
Satisfied customers do not happen by chance, they are the normal and natural result of work done upstream to achieve the results they value. 

What do we have to do upstream to produce these results in a perfectly normal, systematic, and sustainable way? 
This market is highly competitive, different competitors seek to improve their efficiency, whoever is more efficient wins, whoever stretches the frontiers of operational excellence wins. 

Amateurs cannot compete with paranoid competitors.

Now, let's look at another type of customer, the one who wants tailor-made service, or a customized product. What do they value? 
What kind of priorities are behind these results?
Finally, let's look at another type of customer, the one who wants innovation, or values design above all. What do they value? 
Again, what kind of priorities are behind these results?
Now imagine an organization that wants to serve the three types of customers at the same time
What a big mess it will be! A typical stuck-in-the-middle situation.
The following figure is taken from an article called “Using Product Profiling to Illustrate Manufacturing-Marketing Misalignment” by Terry Hill, Rafael Menda, and David Dilts and published in July 1998.

One can look into an organization and evaluate its products and markets, its manufacturing structure, and its infrastructure. 
For example, about the products and markets: organizations can have wide or narrow product ranges, high or low rate of new product introductions. High or Low frequency of schedule changes. And different order winners, the most relevant topic at the eyes of certain groups, certain segments of customers.
For example, for manufacturing: organizations can have small or large production run sizes, high or low set-up frequencies, low or high set-up costs.
For example, for infrastructure: organizations may be designed to new product introductions or for process improvements to improve efficiency. Manufacturing Managers’ tasks may be dedicated to schedules or to quantity.

Let us see two examples.
The blue company is a company that bets on innovation, they have a wide range of products, they have a high rate of new product introductions, They are flexible enough to accommodate and thrive in the middle of a high frequency of schedule changes. Customers love the innovative products and the brand. Their manufacturing is aligned by being able to run small production sizes, handle a high frequency of set-ups and their cost is low. Infrastructure is aligned with product introductions and meeting schedules.
On the other side, one can think about a green company. A company that bets on low cost to compete on price, they have a narrow range of products, they have a low rate of new product introductions. A new product introduction is a headache, is more entropy. They try to minimize the frequency of schedule changes, which reduces throughput, that reduces efficiency. Customers love their low prices. Their manufacturing is aligned by being able to run large production sizes without stop, they minimize set-ups, and their cost is high. Infrastructure is aligned with efficiency and process improvements process in and throughput.
Different organizations, different strategies, different processes, different mindsets.

Now consider the example of a third company, a company that has a weak or unclear strategy, a company not aligned.
They have a wide product range, an average rate of new product introductions, an average frequency of schedule changes, and their order winners are based on price. Things don’t fit nicely together
They run small to average production run sizes and average set-up frequency and cost.
Their mind is in searching for efficiency but at the same time, they look to meet schedules to satisfy different customers looking for different products in small quantities.
This company is a mess, is stuck in the middle trying to serve everybody and fighting with conflicting priorities.

Continue.

sábado, fevereiro 06, 2021

How can we use the process approach (part III b)

Part I and part II e part IIIa.

4.2.5 Step 5 – The main processes

We will use the example of a public works company, civil construction, as a basis for modeling an organization. A public works company is an organization that lives based on construction works, each construction works is put out to tender by the owners of the projects, so in an organization of this type the main steps may be:

These main steps represent the core processes of the organization (I call them the Cristiano Ronaldo of the business), those that are triggered by a customer's need and aim to satisfy that need, thus serving the customer. What happens between those two customer states? What actions, what activities do you do when going from one extreme into the other?

In this way, the main processes necessary to complete the change in the status of customers are identified.

4.2.6 Step 6 – The supporting processes

Once the core processes are identified, the support processes that allow the customer service vector to continue to function in the long term must be identified. These are processes that are not directly related to an order, or work, in particular, but necessary to deal with various orders or other types of requests. These are processes normally associated with resources (materials, services, people, machines, financial, ...). 

The process "Supply equipment" ensures that the works have the appropriate equipment to run without equipment shortages, and also ensures preventive and curative maintenance.

The process "Supply material and service" ensures the adequate and timely supply of materials and services essential to the development of the work, it also ensures the qualification, selection, performance evaluation, classification, and re-evaluation of suppliers and subcontractors.

Some organizations linked to construction and public works, with which we have worked in the past, given the particularities of their market, have chosen processes to support financial management (which included credit insurance, collections, payments) we will not do it here to keep the model simple.

The process "Train people" converts potential employees selected from the job market, into employees of the organization. It improves the skills of employees by receiving, analyzing, and closing gaps in the profile of people who occupy the various functions.

4.2.7 Step 7 – The leading process

Finally, the last process, the process "Lead the organization", a process where top management sets direction, sets objectives, and analyzes the performance of the organization, which evaluates the degree of fulfillment of the purpose, its raison d'être, and proposes new performance challenges and proposes changes in processes in order to leverage the organization to higher levels of performance. 


4.3 - Final remarks

Why do I use here these egg fried shapes to represent processes, instead of well-ordered squares like in the figure below?
In doing so, I intend to emphasize and awaken a spirit of humility, our models are not descriptions of reality full of certainties. We look at the world, at reality and we see complexity, mystery, confusion, disorder and problems, challenges of various kinds, and what we do is to organize our exploration of that world based on theories, on simplified approximations of reality, approaches that they make it possible to analyze the world and issue attempts to explain what exists, reality, performance, results and outline plans for the future, in order to influence behavior and induce future results for this part of the reality that interests us.

The amoeba shape, to the detriment of the rectangle, reminds us that our theories are just that, theories, hypotheses, representations, and have no ontological substance of their own, they are not palpable realities, they are nothing but artifices of the human intellect, and as such, they are not definitive can always be improved. Learning takes place through conscious comparison between the organization, as we perceive it, and the organization as we interpret it with theoretical models, our models are like artificial islands that we create, and we have geographically strategically available to cross an ocean of complexity and disorganization. 

The central arrow is the heart of the organization – these are the main processes, everybody should be working to support these processes because they serve clients. That is the job and purpose of the supporting processes, they exist to serve the main processes. You know that winter sport called curling? Like in curling everybody in the organization should be mopping the floor to reduce friction, to easy, to facilitate customer service through the main processes.
The leading process is the brain of the organization, it is here that direction is set, objectives are set, performance is monitored and decisions made.

In the next part, we will relate processes and strategy.

quarta-feira, fevereiro 03, 2021

How can we use the process approach (part III a)

 Part I and part II.

In the last part, I wrote that this part would be about processes and strategy. However, let me make a small change and first address the modeling of an organization, based on the process approach, before relating processes to strategy.

4. Modelling an organization – mapping processes

ISO 9001:2015 clause 4.4.1 states that an:

Organization shall determine the processes needed for a quality management system. 

How can that be done?

We need to develop a model of how the organization works having as its building blocks what we call processes.

4.1 What is a model?

“A model is an external and explicit representation of part of reality, as seen by people who want to use the model to understand, to change, to manage and control that part of reality”

 Michael Pidd in “Tools for thinking - Modeling in Management Science” 

Remember, we don't draw a model to answer ISO 9001:2015 requirements, and please auditors. We draw them because we want to understand, to change, to manage, and control our organization's present and future.

Models are always a simplification and an approximate representation of some aspects of reality, models reduce complexity, simplify the original or the future to be built, to reduce the noise produced by reality, and thus highlight, distinguish the critical factors, for the object of study concerned. The model does not show all the attributes of the original, it only illustrates those attributes that are relevant, or suitable for the observer/creator/user of the model to manipulate. Models do not need to be accurate to be useful, models are simplifications, and their usefulness lies precisely in that approach.

The task of the observer/creator/user of the model is to collect the visions, the perceptions, even if ill-defined and implicit of reality, and to shape them in a sufficiently well-defined way to be understood and discussed by other people. A model is a representation of reality. 

With Deming I learned:

All models are wrong, some are useful!
The reality is composed of a set of objects that constitute a system, at a conceptual level we design a model capable of illustrating the system, the reality. Armed with the model as a work unit, we can perform simulations to perceive reality and influence it, the simulation uses the model to perceive and anticipate the dynamics and behavior of the system.

4.2 Modeling an organization as a set of processes

To build a model of an organization, it is necessary to have a clear definition of its purpose, now an organization exists only because there are customers, they are its raison d'être! 
An organization, the organization object of our study, is an entity, it is a system, which transforms, that converts “potential customers with needs” into “customers served”. 

4.2.1 Step 1 - Identify the different types of customers 

Customers are not all the same, it is possible to identify and isolate different types of customers, this activity is important because different types of customers may require, different processes and may mobilize different actors, may involve different inputs and different outputs. 



4.2.2 Step 2 - List the inputs and outputs of the model

Distinguish the different states of the customers and identify all interactions (inputs and outputs) between the organization and its customers! How do we get in contact with potential customers? How do we collect information to develop new products and services? How do we receive orders or requests for proposals? How do we deliver our products and services? 



4.2.3 Step 3 – Determine the core, the heart of the model

Let us track the route, from inputs into outputs. Let us zoom in on the organization. Let us open the black box! 



For the purposes of this blogpost, we select a certain type of customers and then start to dive inside the organization  (for someone implementing a quality management system for certification, this could be a management system scope option)


I gather a set of people that know the organization, each from a different perspective and give them sticky notes and markers. Then, I post two sticky notes that represent the responsible for major input in the system and the receiver of the major output of the system.

I ask; what actions, what activities do you do when going from one extreme into the other? People use sticky notes to write things that they remember. I set a rule: one sticky note must have one verb and one noun like “Receive Request For Proposal”, like “Write Proposal”, like “Budget Proposal”, like “Present proposal”, like “Negotiate proposal”.

After that kind of brainstorming one can start to aggregate sticky notes that belong to a flow of activities. For example, I can replace these 5 sticky notes above by saying that they belong to the same process called “Win order”. Repeating the technique for other sticky notes we develop the central sequence of processes.

When designing the road from the inputs into the outputs, do not dive into to much detail! 
Let us look at a high level of abstraction and consider 3 to 6 entities (each entity represents a process, a set of activities) And let's number the processes sequentially! 

We can do a mental exercise: "If we were riding an order, what would we see from the reception to its delivery?" Do not register departments or functions, but state changes, the main tasks! ”

4.2.4 Step 4 – Name each process
 
Designate each entity (each process)! Start with a verb that illustrates the transformation that takes place inside! Avoid references to departments, to avoid confusion remember:
  • processes are not departments, 
  • the organization chart is not a process map, 
  • the vertical and horizontal views of an organization are very different.
I like to designate a process by relating its name to the main output of that process. 

While certain processes seem to be clearly determined, based on a physical flow (production, logistics, distribution, transport) or a flow of information (design/development, closing accounts, invoicing, payment), certain activities of an administrative nature seem difficult to integrate into a “process” view. 
There may then be a strong temptation to group them by function analogy and to baptize these groupings as “human resource process” (in which recruitment, training, communication, payment of wages, contract management will be mixed) work, social dialogue, without the slightest logical link or the tangible outputs that characterize such a process appearing), “accounting and financial process”, etc. Performing more or less arbitrary functional groupings is of no interest from the point of view of process management, because it will be difficult to draw interesting conclusions as to the coordination and chaining modes. 

In the next part, we will continue with the modeling of the public works company as a basis for modeling an organization. 

segunda-feira, fevereiro 01, 2021

How can we use the process approach (part II)

Part I.

3. The process approach – a quality management principle

The process approach is one of the seven quality management principles included in ISO 9000:2015. Let us see the statement of that principle:

Consistent and predictable results are achieved more effectively and efficiently when activities are understood and managed as interrelated processes that function as a coherent system.

It is easy to relate those “Consistent and predictable results” with the objectives referred to in the definition of a management system. 

And what does the same ISO 9000: 2015 say about what a process is? 

set of interrelated or interacting activities that use inputs to deliver an intended result

So, we may see an organization as a coherent system made of a set of interrelated or interacting elements called processes, and it is through those processes that an organization achieves its intended results, its objectives.

At a first glance, we have: 

The intended results may be: 

Now, let us zoom the organization to find out which processes are present and how they interrelate.


 For example, the processes may be:

 

When this organization wins a new project, they have to start ordering resources needed to provide the service. At the same time, winning a new project means developing a new service, new resources need will be determined, and service preparation may start. Then, at an agreed date the service provider may start.

Let us go back to the management system definition:

System to establish policies and objectives, and processes to achieve those objectives

Now, our system is our set of interrelated processes, and it through those processes that you try to meet intended results. Processes are like variables in a mathematical equation that we operate in order to meet our intended results: 

Let us go back again to ISO 9000:2015, clause 2.4.1.3, where we can read:

These processes interact to deliver results consistent with the organization’s objectives and cross functional boundaries. Some processes can be critical while others are not.

When we model how an organization works, we include in the model a set of processes. Those processes are needed, but not all processes have the same impact or influence in meeting each objective or intended result.

Just as an example, let us consider this matrix that relates processes and objectives:


 Processes are where the rubber meets the road. Whatever an objective the management wants an organization to achieve, it is only a dream if one or more processes of the organization are not mobilized and changed to that. In the matrix above, meeting objective “Better sales” requires working on the process “Win project”. Meeting objective “Less complaints” requires working on processes “Prepare service” and “Provide the service”. Meeting objective “More satisfied customers” requires working on processes “Develop a new service”, “Prepare service” and “Provide service”. 

Now, look into the process “Maintain equipment”. It must exist but does not contribute directly to any overall objective. These processes are tricky. If you are excellent in these kinds of processes, they will be expensive but will not contribute to customer satisfaction, but if you make a mistake in these processes, they can contribute to customer un-satisfaction. 

No one says: we are very satisfied with our electrical power supplier because at the end of the day there were no power failures. We say, it is the minimum someone can expect, no failures 

Next: Process and strategy

domingo, janeiro 31, 2021

How can we use the process approach (part I)

 1. Management system definition

Let us start with the management system definition.

Do you know what is the ISO 9000:2015 management system definition?

set of interrelated or interacting elements of an organization to establish policies and objectives, and processes to achieve those objectives

Let us substitute “set of interrelated or interacting elements of an organization” with the word “system”. According to ISO 9000:2015, a system is a “set of interrelated or interacting elements”. So, a management system is:

A system to establish policies and objectives, and processes to achieve those objectives

Have you ever looked at this definition of a management system? Seriously, have you ever looked at this definition with eyes to see? I confess, for years and years I looked at it and never gave it importance, until one day I read it again and I was shocked ... I have been working with ISO 9001 since the 1980s. At that time, I was trained in another view on quality systems, very focused on procedures and quality control. 

Now, I was looking at the definition of a management system and saw something I had never seen before. A management system is a system that establishes a policy, that is, a strategic orientation, a set of priorities, translates that policy into a set of objectives aligned with the policy, the objectives are concrete challenges to be achieved, and then, start working systematically to achieve these objectives. 

2. Systemic thinking

An organization is a system. A system generates results and these results do not happen by chance, they are a perfectly normal product resulting from the system, the way people work, their culture. Thus, the current system generates the current results. If an organization wants to achieve different results in the future, it will have to transform, it will have to stop being the current organization to become the organization of the future. 

When we look into the current organization, the one generating the current results, we can discover a network of loops, a network of practices, that reinforce desired or undesired results:
Parts of these loops are intentional design, but others have evolved without a central command. To achieve the desired objectives for the future, it is necessary to act on these loop networks. 

Back to the definition of a management system. In a management system, the focus must be on the work to be carried out systematically to modify an organization, so that it can achieve objectives aligned with strategic priorities. I would almost say that everything else is noise. 

Next: Process approach definition