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.

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. 

Workshop sobre "Indicadores de Monitorização de Processos" (parte II)

Parte I.
.
Datas:

• 20 de Janeiro em Lisboa
• 27 de Janeiro em Aveiro
• 10 de Fevereiro no Porto
• 17 de Fevereiro em Bragança

Recentemente realizei uma auditoria interna ao sistema de gestão da qualidade. Durante a preparação da auditoria, deparei-me com um problema clássico. A empresa tinha definido um processo chamado "Gestão Comercial" (BTW, não vou levantar ondas aqui mas tenho "issues" com este tipo de designação que confunde processos com departamentos. Recordar isto, isto e, sobretudo, isto) com este objectivo:

"Este documento descreve o modo como a AAAA procede perante consultas ou encomendas dos seus clientes..."

Repararam?

.

O objectivo descrito é o objectivo do documento, é o objectivo do papel!

.

Prefiro que se comece pelo carácter teleológico de um processo, em que é que ele se projecta, para definir o seu objectivo, a sua finalidade. Por exemplo, transformaria o processo Gestão Comercial em dois processos:

• Ganhar peça nova (trata da parte das consultas)
• Tratar encomenda (trata da parte das encomendas)

Para que é que existe o processo Tratar encomenda? 

.

Reparar como esta abordagem pode ser feita com a folha em branco, não precisamos de saber o que se faz dentro do processo. Qual é a razão de ser do processo, para que é que ele existe?

.

A resposta pode ser, por exemplo:

• Responder rapidamente às encomendas, sem erros e indo ao encontro do prometido

Quando se procede desta forma, acontece magia. Que indicadores escolheriam para monitorizar a eficácia deste processo?

• Tempo médio de resposta a uma encomenda;
• Taxa de erros por encomenda;
• Taxa de cumprimento do prazo de entrega;
• Taxa de reclamações e devoluções.

Desta forma evitam-se os indicadores da treta.

.

Venha fazer-nos companhia no Workshop.

.

Objectivos e programa aqui.

.

Valor do investimento: 70 €

.

Inscrições em metanoia@metanoia.pt com a referência IMP01

Workshop sobre "Indicadores de Monitorização de Processos" em Lisboa (parte I)

Na sequência deste texto, "Medição e risco (ISO 9001:2015) (parte II)", sobre a importância da monitorização e medição, recebi uma provocação para retomar um Workshop que animei durante os anos de 2012/13 na APQ.
.
Assim, aceitando o desafio, propomos a realização de um Workshop sobre "Indicadores de Monitorização de Processos"  em Lisboa a 20 de Janeiro. Entretanto, procuraremos agendar uma data para o Porto em Fevereiro.

Um Workshop de 7 horas:

Objectivos:

• Relacionar os processos com a estratégia de uma organização; (recordar o recente "Alinhamento estratégico")
• Formular o propósito de um processo;
• Desdobrar indicadores de eficácia a partir do propósito de um processo;
• Desdobrar indicadores de eficiência a partir do fluxograma de um processo;
• Identificar indicadores de quantidade relevantes para um processo;
• Construir um circuito de monitorização de processos;
• Construir um painel de bordo para monitorização dos processos.

Programa:

1. Indicadores e processos – indicadores ajudam a responder a perguntas
2. Tipos de indicadores – eficiência, quantidade e eficácia; finalidade de um processo
3. Fluxograma de um processo – indicadores de eficiência
4. Identificação e designação de um processo
5. Abordagem por processos e modelação do funcionamento das organizações
6. Relacionar estratégia, processos e indicadores
7. Monitorização de indicadores – drill-down; erros mais comuns; plano de monitorização, painel de indicadores, controlo estatístico do processo

Destinatários:
Directores, Gestores de Processos, Líderes de Projectos de Melhoria, Gestores da Qualidade, Ambiente e Segurança e outros Gestores interessados na implementação de Metodologias/Ferramentas/Filosofias ligadas a estas temáticas

Investimento:
70€

"Perdi a Carteira"

Quando facilito sessões de criação, de representação, de desenho de modelos do funcionamento de uma organização, com base na abordagem por processos, uma das regras que proponho é

"Esqueçam os nomes dos departamentos, dos gabinetes, das direcções, das áreas. Concentrem-se no que se faz, nas actividades, nas tarefas!"

Isto para que as esquipas não designem os processos com nomes facilmente associados a uma caixa do organigrama. Assim, nomes como:

• Comercial;
• Recursos humanos;
• Compras;

São substituídos por nomes como:

• Ganhar clientes;
• Recrutar e integrar colaboradores;
• Adquirir matérias-primas;

Um processo é acção, movimento, fluxo - uma sequência organizada de tarefas ou actividades, que transformam entradas em saídas.

Um departamento faz-me lembrar aquelas imagens sobre as propriedades tensoactivas, e sobre a acção dos agentes de suspensão, numa mistura entre água e uma gordura:

Quando se menciona o nome de um departamento, não se menciona acção, transformação. Quando se menciona o nome de um departamento sistematizam-se tarefas, não em sequência, mas por categorias, por tipos, por ordens. Por exemplo; Departamento de Recursos Humanos permite equacionar os seguintes tópicos, não directamente relacionados entre si numa sequência directa:

• recrutamento;
• despedimento;
• assiduidade;
• formação contínua;
• avaliação de desempenho;
• remuneração;
• legislação laboral;
• ...

Assim, não deixa de ser interessante a designação dada a este novo balcão de serviços públicos:

"Foi inaugurado ontem na Loja do Cidadão das Laranjeiras o novo balcão "Perdi a Carteira". O objectivo desta nova funcionalidade é o de atender os cidadãos que, em caso de perda ou roubo, necessitem de segundas vias dos seus documentos ou de alterar quaisquer dados." *

A designação é feliz porque retrata a conclusão mental pessoal que identifica imediatamente o cliente-alvo deste serviço.

* trecho retirado do Público de hoje, artigo de Joana Palminha, intitulado "Balcão "Perdi a Carteira" inaugurado para combater inferno da renovação de cartões"