I’m Perfectly Imperfect, Flawlessly Flawed

Following on from yesterday’s post featuring “lowest common denominators,” I was once assigned to a project in which “flawless execution” was a stated requirement.

Not a goal, or a vision, or something to strive for – there it was in black and white, right in the requirements document: Fail to execute flawlessly and we may as well not have bothered even showing up.

If I could have gotten away with just walking out immediately then I would have. Instead I snidely commented that I’ve never done anything flawlessly before, so I was excited to start.

Everyone stared at me blankly for thirty seconds and then we all moved on to the next item on the agenda.


The Two Most Poisonous BPR Dangers

A little while ago when I wrote about The Monkey Parable, I promised that I’d write more about what I see as being the two most poisonous BPR dangers you’ll face when attempting to re-engineer and optimize business process, at least from my experience of attempting to do so.


Well friends, the time has come. Join me, won’t you, after the break.

“This is How We’ve Always Done It”

The first danger I alluded to in a not especially transparent way when I relayed the monkey parable to you all: we do it this way because this is the way we’ve always done it.

This used to be an extremely prevalent problem in my organization. Less so these days thanks to a senior leadership team that specifically calls this thinking out and tackles it head on – but even so this kind of thinking still exists where I work, and I’m 99% confident in saying it exists where you work too.

Essentially the thinking here is that we’ve been doing something the same way for 20 years then there has to be an excellent reason for that, otherwise something would have changed long ago. The fact that nobody knows the excellent reason is seen as largely irrelevant.

So from a Business Process Management / Business Analysis perspective, how do you combat it? It’s all about perspective. It’s unlikely that any of the truly important processes in your organization are completed by a single person, and that makes perfect sense: somebody who shapes sheet metal to create a panel for a vehicle would be an extremely skilled craftsman, but that doesn’t mean they have the expertise to build a gearbox. Too often though we have too narrow a focus when we look at business processes.

Focus is only good if you know you’re focussing on the right thing, and to understand that you need to take a step back and take a more holistic view. It’s in doing this that you can start to break down those “this is how we’ve always done it” misconceptions, because they most commonly arise from a misunderstanding of the up- and down-stream impacts of the work a particular person is doing. If you’re looking for transformative change then my advice every time would be to get subject matter experts from every aspect of a process together to talk the whole thing through – I guarantee you’ll find waste, and probably lots of it. And if your process doesn’t start and end with the customer (in purest sense of the word), you’ve defined it too narrow a way for this phase of your work.

Catering to the Lowest Common Denominator

“Think of the dumbest person you work with, and let’s build a process they can complete with ease.”

I’ve personally uttered those words in the past during sessions I’ve run as part of BPR initiatives, and I suspect I’ll do so again in the future. Getting people to think like this is fine, but it’s a powerful tool and you have to be very careful not to misuse it.

If you’re talking about designing a user-interface perhaps, or discussing building automated error-proofing functionality into a system – absolutely, let’s make that stuff as intuitive (read: idiot-proof) as possible.

All too often, this gets taken too far and results in masses of waste and redundancy being built into business processes. If I complete a task that I then hand off to somebody else only so that they check every aspect of my work, that’s a problem. A big one. The company would be better off taking my paycheque every two weeks and burning it. They could use the fire to help heat the building, and they also wouldn’t have to deal with the massive attitude problem I’d develop through being part of a system that places no trust in the work that I do. The result of which is the problem becoming self-perpetuating: Now I’m not only disengaged, I’m not accountable for my work in any kind of meaningful way – if I do a bad job then the person who’s checking everything I do will fix it anyway, so what does it matter? So of course I do a bad job, why would I bother trying to do anything else? “Ha!” say the powers that be, “told you it was necessary to check over everything. We find errors in 65% of the tasks that Jason completes.”

So how do you tackle this from a BPR perspective? Two ways. Firstly, you have to trust people to do the work they were hired to do. That’s easier said than done sometimes, but as a Business Analyst (probably) dealing with people’s performance issues (whether perceived or real) and coaching is unlikely to be within your remit anyway, so why make it your business? If there’s one thing I’ve learned about people it’s that you get from them what you expect to get from them. If you have low expectations and treat people like idiots, you get back poor performance. If you have high expectations and provide people with autonomy and, most importantly, accountability, then you’ll get back the high performance you’re asking for. Quite aside from all that, if the “lowest common denominator” that you have in mind when you’re designing a process really does require that a second person checks over everything they do then you should fire that person and start over with a new “lowest common denominator” in mind.

Now that we have an accountable, high-performing workforce completing our process the second thing we need to do is allow for some mistakes. If we demand perfection from the output of our process then rework and unnecessary checks will almost inevitably be the price we have to pay within the process. Six sigma (which is what we’re all striving for these days, right?) allows for a defect rate of 3.4 parts per million, and that comes from the world of manufacturing where machines are doing much of the actual work. If your people-based process really expects that level of accuracy then my recommendation would be turn your attention away from increasing the process’ sigma level and figure out a better method of handling expectations and dealing with the inevitable defects instead.


Home Server Setup – Useful Links

I’ve mentioned in a couple of previous posts that I’ve refreshed my home server recently. In setting everything up I spent a lot of time googling around looking for information on how to do things that for the most part I’d done before on my previous server.

To help me avoid future googling if/when I need to go through this process again, I’ve been creating a whole bunch of bookmarks this time around. I thought I’d share them in case they’re useful to anybody else.

oVirt Hypervisor

Linux Server

Windows Server


Late Night Links – Sunday August 24th, 2014

It’s that time of the week again! Late night links! Yay!

And we’re done for another week! See you all next Sunday: same time, same place.


Learn Version Control with Git

Recently I’ve been reading the eBook “Learn Version Control with Git” online, and I’d recommend it.


I’ve been using Git for a while, but certainly not to its full potential, and not even really for its intended purpose. The book is great because it:

“…doesn’t require a master’s degree in computer science to read it. It’s aimed at beginners of programming, at designers, at project managers… It tries not to require too much prior knowledge on the technical side. It tries to go slowly.”

You can read it online for free, or purchase it in PDF, ePub or Mobi format for your device.



Why Great Ideas Always Come In the Shower (and How to Harness Them)

Never in my life have I had a good idea in a meeting.

All my good ideas come at other times. During my commute, when I’m out for a walk, and – of course – when I’m in the shower.

Why Great Ideas Always Come In the Shower (and How to Harness Them)


Late Night Links – Sunday August 17th, 2014

It’s Sunday night again. Where does the time go?

And that’s it for another week! See you all next Sunday, same time, same place.