top of page
Search
Writer's pictureNigel Adams

Trial by Kafka

Updated: Jan 17

Why asking a team of subject matter experts to document your processes is unlikely to provide you with much insight.

The Trial by Franz Kafka is one of my favourite books. It’s tells the story of a man who is arrested but not imprisoned. Neither the charges, nor any evidence that might hint at the charges are ever revealed. As with many of Kafka’s works there’s an element of absurdity about it.


Which is where we come to the main point of this blog. The title of the book in German is Der Prozess and Prozess, as well as translating into English as the word for trial also translates as the word for process. Over the last few months a number of colleagues in financial services have remarked on their organisation’s efforts being directed towards process governance. This is where the absurdity comes in.


It seems that since the Hayne Royal Commission, many organisations have established process governance forums, licensed some software and then set about documenting their processes. And then given themselves a pat on the back. Job done!


Apart from ticking a compliance box on whether your processes are documented, simply documenting your processes adds little to no value. One of the few things you can say for certain is that the process documented will not be the process that is executed day-to-day. Another is that the majority of these organisations are not measuring this fact. They are not checking whether what the delivery team actually does is what the process documentation says they should be doing. And if you’re not measuring conformance, how do you know whether your process is meeting your regulatory or customer obligations? The answer is you don’t. And if you don’t know the answer to this question, you don’t know where to look to improve. So it’s likely that a lot of the improvement resources you are deploying are being misdirected.

  1. In short process governance really should be about:

  2. Define the services you deliver

  3. Determine the processes required to deliver these services

  4. Set the specifications for the process that will ensure you are meeting your regulatory, customer, shareholder and other stakeholder objectives

  5. Monitor your process to ensure they are performing in line with these specifications

  6. Target your improvement efforts to plug the gaps when they invariably are not.


While the principle is simple, in service businesses execution is challenging due to the many, many variants that tend to exist for each process. You may have defined a “happy path” but it’s likely that there are many more acceptable, alternative paths depending on the specific nature of the service request and the inputs you have to work with. But this is all part of the fun and why process governance can never be treated as a project.

Unlike Kafka’s novel, there is no start and there is no end. Process governance will always be required. You cannot improve effectively and sustainably without it. It’s absurd to think otherwise.

1 view0 comments

Recent Posts

See All

Kantban

Comments


bottom of page