The Brexit FMEA


The Brexit pre-mortem: BFMEA


Of all the engineering tools that I have encountered, the one that spans the widest spectrum of respect and scorn, hope and despair is the FMEA, the Failure Mode and Effects Analysis.


Developed by the US military and NASA and gradually adopted by the automotive industry from the 1970s onwards, it is intended to highlight things that could go wrong before they do; it's also a way of collecting and tracking the evidence (models, test reports, etc) that shows that the nuts and bolts have been proven before putting them on a rocket - or, indeed, jettisoning a country out of the European Union.


At its heart, the FMEA is a "what if?" analysis. Other methods are available, like the Potential Problem Analysis from Kepner-Tregoe. But I'm automotive, and the FMEA is a requirement in our field, so I've sketched up how a BFMEA (Brexit Failure Mode and Effects Analysis) might have been constructed and eventually look like. Why? Because I simply don't get the impression that the British government perceived the need for any such thinking before diving in to the apparently urgent political necessity that was the Brexit referendum result. And also, because sketching one up isn't all that hard - with practice.

Building the structure


First of all, you need to define what your product or system is, perhaps by following what was defined in the project scope (ABQP). The FMEA might be for a full system, or it might be for an individual component that fits into that system: For our purposes now, it's Brexit. Brexit has a few functions and requirements that I cobbled together in five minutes (naturally with no little help from hindsight):

What could possibly go wrong (failures)?


With an FMEA, you focus on failures first and foremost (it can be a depressing trudge, initially, which is why engineers are always so miserable. Are we? We must be). Put yourself in Law-maker Murphy's shoes, maybe even his socks and underwear, too. The fresh ones.






Then "all" you need to do is to go through each of your functions, wishes, desires, needs, etc: and define all the ways they can fail (one more example here):


How could it come to this (causes)?


If failures are the symptoms, then causes are the bugs that deserve our attention. 

Again, with every failure having its very own potential cause, or causes, we need to repeat the trudge around the houses. I've kept it relatively simple here:

Somebody will have to do something about this (actions)!


The whole point of the FMEA is to discover potential failures and to cut them off at the source: we don't want those bugs getting in that resulted in us hollering into the toilet bowl. So the positive aspect of the FMEA is assigning to-dos to each cause, like "make sure you wash your hands before eating", with the intention of preventing those causes from occurring in the first place (absent a time machine):


So much to do! Where to start (Effects)?


There's one letter we haven't touched in the FMEA yet: the E. Effects. Determining what happens as a result of the failures can be useful in figuring out what actions should be prioritised. You might for example preferentially allocate work on avoiding failures that would otherwise result in conflict on the Irish border over events that would lead to slightly less curved cucumbers still landing on British shores.


But understanding where to prioritise political effects (disgruntlement amongst 48% of voters, for example) is beyond my realm of experience, and represents a clear disconnect between the "plodding reality" of engineering and the human rationality (in all its technical irrationality) that defines politics. Some things might not be "prioritisable" at all. At least until someone works out an official Happiness scale that would be able to balance lots of low-level general contentment (hey, being in the EU isn't actually all that bad most of the time) against intense doses of uproar (they're defining cucumbers again!). Do I digress? I believe I do.

Presenting the BFMEA


Typically, FMEAs aren't presented in the network style that I employed to build mine: the traditional method is the worksheet, which typically leads teams to try and build them in Excel or similar. This is what mine would look like in that format.



It's OK, but a bit sterile. Which is I suppose how it should be. Right? "Real" FMEAs have ratings numbers that help in the prioritisation of tasks, which I have omitted here.

Build and forget?


The FMEA is intended to be a so-called "living document". As new events occur and lessons are (ha!) learned; as new and fantastical failure modes with subtle, complex, causes are discovered, the FMEA grows: often becoming unmanageable, or at least rather unwelcoming in the process. Unless someone or some team is really "living" complex FMEAs as a role, they will bulk up, dry out and fossilise.


In one sense, that's not necessarily a bad thing: if at least in the act of setting it up important considerations were made in that emotionless setting, potentially resulting in actions being taken that avoided some grand faux pas or other, then it will have been useful without too much investment in resources.

Do they? Can they?


It would be fascinating to find out what methods the British Government has at its disposal (and which were used thus far): because, to all appearances, they weren't.


Perhaps they're saving them for the debates surrounding the re-entry into Europe, then.

BFMEA network and other points


Here's the network FMEA that I built up over the weekend. To those engineers reading this who are experienced in FMEA methods: I acknowledge the existence of Occurrence and Detection items. I didn't bother with ratings, as FMEAs can really get bogged down with them - but some sort of prioritisation is required, of course. To those outside of my industry: have you encountered similar "constricted thinking" methods? It would be fascinating to hear from you!




ABQP: Brexit as an automotive project


ABQP: Advanced Brexit Quality Planning


It is surely doing the British Civil Service an injustice to suggest that there was no planning process for Brexit. However, what we see in the media strongly suggests that whatever planning did take place was swiftly overcome by politics: the votes upon votes in Parliament, the pontificating and hardening of views, the dreams shattered and still dearly held. We hear of Papers stating one potential outcome or another, but the feeling remains of a Brexit ship veering ponderously from port to port, turning away from each in disgust without ever reaching one.


I'm an automotive engineer, and could imagine Brexit being an automotive project; there would (in my imaginings, anyway) have been a clear baseline for planning, thinking, moulding, approving or even cancelling the project before it's too late.


Comparing Brexit with a VW Polo facelift? Ridiculous! Well, yes, but I feel there are some lessons in the processes that we use in industry that might have been better learned before embarking on this huge undertaking. (Otherwise I won't have writting this, I suppose).


Naturally, the advantage that the auto industry has over the Brexit project is that it can produce many models and, with experience, assuming the company survives (which many didn't ), see what sticks. Brexit is a one-shot action that will take decades to mould after the event. But, anyway, here are my thoughts on the Brexit Project from an automotive perspective:

APQP: Advanced Project Quality Planning


Every automotive company has its own flavour of APQP, but the basics are defined and even - of course - available on Wikipedia. Some key aspects that I would highlight here would be:

  • Planning and Defining the Program
  • Product Design and Validation
  • Understanding the needs of the customer
  • Analysing (/predicting) and mitigating failure

It's a plodding, check-box laden process and certainly not in the vogueish agile development process domain - but therein lies its strength as well as tedious weakness: it enforces slow, measured and team-based thinking, rather than snap decision-making.


Irrespective of whether I think Brexit is a good idea or not, the process appears to have been entrained without even a basic level of planning. Was there any sensible product definition of Brexit before kicking off Article 50 and the two-year negotiation period? (Leave Means Leave is not a helpful definition, at least in my book).

Advanced Brexit Quality Planning: A light-gloom-hearted ABQP Statement Of Work


Project Name


The United Kingdom of Great Britain and Northern Ireland to exit the EU.

Project Scope


The United Kingdom of Great Britain and Northern Ireland intends to leave the EU. No other countries will leave the EU. All components of the UK shall leave the EU, including Gibraltar and the Channel Islands. The UK intends not to bow to EU regulations. This normally means not having the same level of access to the European market as available at present. The UK intends to keep the same level of access to the European market. Leaving the EU means developing new alignments with... well, every country in the world, as well as with the EU.

Project Type


APQP: Advanced Product Quality Planning with 5 Phases.

  1. Plan and Define Program
  2. Product Design and Development Verification
  3. Process Design and Development Verification
  4. Product and Process Validation and Production Feedback
  5. Launch, Assessment & Corrective Action

Phase 1: Plan and Define Program


1.1 Identify the needs of the customer


1.1.1 Identify the customer


The customer is all citizens of the UK (including those younger than 25 at the time of voting who, though disproportionately affected, voted at a significantly lower rate their older, perhaps more caring compatriots). Citizens of other EU countries in the UK will... have to lump it. British citizens resident in the EU will... have to lump whatever treatment they are given wherever they are living (they deserve it, the traitors) until such time as they return to the fold.

1.1.2 The needs of said customer


Right. Those needs. Yes. It is absolutely clear that all inhabitants of the UK want the best possible deal. In fact, they want more than the best possible deal, they want the best of everything, which is what was promised.


Also: no more immigrants and no more being told how to run a country by a democratically-challenged council of flouncing Eurocrats.


And: no European Superstate.

1.2 Develop timing plan


Target date: Open-end until Article 50 is invoked, so plenty of time to develop a statement of work, specifications and requirements, a strategy and tactics to achieve an acceptable level of that target.

Article 50 has been invoked


Wha...?

Deadline is now May 2019.


You're kidding... Umm, on what grounds was Article 50 invoked?

None that anyone can discern; negotiations will be the easiest ever anyway. There was something about the EU not showing its hand until Article 50 had been invoked: unhelpful gamesmanship, a trap that the British Government, gleefully bellowing "freedom from!" fell into


1.3 Develop Budget


The EU will be on their knees in a few months. So no real budget is required, no contingency planning, just a few negotiators and the rest is a win for us!

1.4 Assemble Team


See 1.3 above, OK, plus their advisors. No need to listen to the people any more, they've had their vote. And we don't need experts any more, either. We'll ignore the Civil Service, too.

Phase 2: Product Design and Development Verification


2.1 Develop Product requirements


The Brexit product requirement is... Leave! OK, more seriously, there might be some relevant functions of Brexit that we might want to consider:

  • Restore / Increase British national autonomy
  • Restore / Increase national togetherness
  • Significantly reduce immigration
  • Increase internal investment (e.g. NHS)
  • Retain and protect UK integrity (e.g. Northern Ireland)
  • Protect inter-Irish peace
  • Avoid becoming part of the EU Superstate

Are these measurable? Most are. The intangibles (national togetherness) will need more definition as the programme progresses. Can they be modelled? What sort of Brexit would result in maximising the wins across the maximum number of functions?

Predicting and mitigating failures (BFMEA)


The FMEA (Failure Mode and Effects Analysis ) is a key engineering tool, initially developed by NASA with the intention of foreclosing failures before they occur.


NASA was also a specialist in one-shot efforts.


... but that we'll save that for my next post.

Phase 2 (Continued)


Oh never mind: Phase 2,3,4 Finished!


LAUNCH


The unvalidated state

The unvalidated state

Well, that all went somewhat awry, didn’t it?

I must confess that I was prepared neither for the result of the referendum on Thursday 23rd June nor for its impact on my state of mind. I spent most of Friday, 24th June 2016, in a strangely blank pall of frustration, disbelief, even - briefly - anger, plus an element of intrigue at what the future will bring. Such a complex bubbling brew of emotions will take some time to subside as this weekend peters out into another week, the first of a long, long series of weeks, months and years bringing ructions and repercussions in my homeland along with administrative hurdles and considerations of nationality for me personally.

Questioning our sanity

Did 52% of Britons really, actively, vote to exit the EU? It doesn’t seem that way: the EU was never really the point during the less than savoury referendum campaign. Those who voted for Leave were sold a dream of “reclaiming our sovereignty” without being told why the EU was bad for them personally, nor what would be improved for them personally once Britain left the EU. Did 48% really vote for the EU, or were they simply hoping for the relatively quiet life of being able to travel, work, study, buy and sell within what has become a large and appealingly non-homogeneous patchwork of countries whilst tacitly accepting the bewilderingly opaque bureaucratic apparatus that enables it?

Was the referendum correctly set up in the first place? Was 50% the correct limit for such a momentous decision, or should it have been 2/3rds? Should oldies - pensioners - have been allowed to vote at all? Can’t the Queen step in and say: “you bally idiots, it’s our (Queen’s perogative) country and we shall stay in the EU, if only so that one won’t have to produce one’s passport when travelling to one’s castle in Balmoral.”?

Whatever the answers to these questions, we are now left in the precarious position of Britain being a product sold yet never tested or proven out. We don’t even know if it will remain intact over the coming years: in engineering terms, it’s a state that was never validated before it was introduced to the customer.

Trial by error

The Leave campaign was based on disassociated presumptions that were packed into sentences in such a way as to sound like a way for the disaffected English middle to break free of - something - and to arrive at a much better - something else. Unfortunately, the Remain campaign was equally pathetic, having realised fairly early on (presumably in the split second after David Cameron announced the referendum), that the EU is impossible to be passionate about these days.

Neither side made any attempt made to list out the various implications of each necessary step towards leaving the EU, and could therefore make no list of mitigating measures to prevent the worst of those repercussions hitting the UK as hard as it might.

The UK’s relationship with Europe and the rest of the world will have to be hammered out in real-time as uncertainties - and some avoidable certainties - cause unpleasant and unforeseen things to happen.

The future UK will only become what it will be once everything that might happen to it has happened to it. And not much of that will have been properly thought through before the 23rd of June - it certainly won’t adhere to the peddaled flickers of a dream of a greater, better, Britain.

What now? A question to self

There still seems to be a residual hope that the increasingly well-known Article 50 (the procedure for leaving the EU) won’t be triggered: but there’s no great point in holding out for that, especially as I wouldn’t have to act if that turns out to be the case.

If Britain really does start to extricate itself from the EU, I’ll presumably have to start acting - so I should start planning soon or risk falling into the same “dreamland trap” as the politicians. It will most likely involve looking to apply for a European (Irish or German) passport and finding out how my status in Germany will change over time.

But that’s all for the future. For now I need to strip out as much of the first three feelings that I mentioned at the top of this post - frustration, disbelief, anger - and settle to a state of vaguely positive curiosity as to how things will turn out.

This will mean reading as little as possible about the politicians (the Boris Johnsons, Michael Goves, Iain Duncan-Smiths and F*****s of this world), forgetting as much as possible the geographic and demographic divides that this referendum revealed, and hoping that the British “Apparat”, the civil servants, regulators, negotiators and the like, are as good as they might reasonably be expected to be when entering discussions with their European, American, Chinese counterparts…

… or am I selling myself yet another dream?


The Pleasure of Concentration

 
I finally - probably not for the last time - started reading Thinking the Twentieth Century by Tony Judt with Timothy Snyder. That may sound suspicious: admitting two authors is generally a bad sign for a book, but here it was a necessary conceit. Tony Judt was an eminent moral historian who was struck down with ALS (the illness made famous / trivialised by 2014’s ice bucket challenge fad): Snyder is an American historian of Eastern Europe who faded in and out of Judt’s comet trail over the years and who decided that Judt’s own history, views and development over the decades needed to be captured before the inevitable, swift, end.
 
So this is a “spoken book”, a conversation between two colleagues speaking and discussing at eye level, rather than an interview between a professional journalist and a professional of something else entirely. Judt and Snyder by necessity follow in the Eastern European tradition of such transcribed conversations. I’m looking forward to discovering the thoughts and philosophies that they discuss, and to daring to measure their theories and histories against my own reality and recollections: in short, I’m looking forward to the challenge of reading it.
  
As I say, I’ve only started. In fact, I have just finished the introduction - where a single sentence made me sit up straight and realise what I’ve been trying and dismally failing to achieve lately, especially at work. It is a single sentence that could become my standard for the next few years; a sentence that got me blogging again. It comes from Timothy Snyder as he describes how the conversations with Tony Judt came to be and how, in essence, they were. This is it:
 
...the conversation was also a great source of intellectual sustenance, bringing the pleasure of concentration, the harmony of communication and the gratification of good work achieved.
 
Those three points that combined give intellectual sustenance seem so obvious now that they have been written: perhaps they come more clearly from acknowledging something that went right - indeed, I couldn’t crystallise my dissatisfaction - at work, especially - into the negatives of those points. So let’s stick to the positives, and see if we can also achieve…  
  • the pleasure of concentration
  • the harmony of communication
  • the gratification of good work achieved
 …in all of our endeavours.