Browsed by
Month: February 2019

Revisiting Red Teaming

Revisiting Red Teaming

Reading Time: 3 minutes

Red Teaming: The independent application of a range of structured, creative and critical thinking techniques to assist the end user to make a better-informed decision or create a more robust product.

That’s a kinda academic way to say “having (and welcoming) someone whose job it is to critique you”. 

I originally wrote about this in February 2017, and a lot has changed for me professionally since then. Based on recent experience, I wondered whether I would approach this differently now, has my thinking had evolved? 

recent Twitter exchange gave me a renewed interest in this idea and so picking up on the key aspects of that discussion, I’ve revisited my previous post. 

Is a Red Team a name for something that already exists? 

Yes and no.

Decisions in emergencies (in a UK context at least) are made by consensus. So there is already a structure whereby people with different experience and responsibilities reach decisions jointly. A variety of aspects and implications will have already been considered and extremes moderated or discounted.

However, ‘decisions by committee’ typically take longer to reach and run the risk of ‘group think’ where the desire for harmony in the group results in dysfunctional decisions.

A Red Team is about doing what you normally do, what you have been trained to do; but then taking an equally qualified objective team and seeing if they have any other perspectives you haven’t considered either about the decision you have reached or the way in which you reached it.

UPDATE: A colleague also pointed out that the type of feedback that I would anticipate coming from a Red Team is can also be (although in many cases isn’t) provided in the form of post-exercise reports. However, these are painfully slow to be produced, missing the oportunity to make dynamic change.

What are the barriers to Red Teaming?

There are many, but I think they can be broadly categorised into two groups; culture and resources.

We all like to think that we have the answers, and so accepting that in ambiguous, high risk and complex situations we might always have thought of everything shows self-awareness. Adopting a Red Team approach would signify to me high levels of strategic leadership maturity.

On the resources side, sorry, I think sometimes you have to take a hit. However, this should be balanced against the cost of sub-optimal decisions being made. Arguably that’s much harder to quantify, but having a stab at working out the return on investment would be a better approach than looking at expenditure.

Clearly embedding Red Teams would take time, money and will, but should that be a barrier to doing things better?

A (red) rose by any other name…

I don’t get hung up on what this structure would be called.

I became aware of the concept through a TV drama Newsroom, where it was called a Red Team, and that term has stuck with me as shorthand.

I have mixed feelings about the militarization of civil emergency management. However, there is no escaping that Red Teams have a military connection, where they are used to good effect. Typically, where the military goes, the civil emergency response follows.

The 2010 Ministry of Defence guidance on Red Teaming states it is a “practical response to overcoming the complex problems introduced by our human frailties, helping us to recognise them and correct our thinking and analysis before faulty judgements are cemented in the minds of key decision makers.” I think that’s equally as applicable in a civil context.

Perhaps recognising a militarisation tendency, NATO has opted to call their structure ‘Alternative Analysis’. You could also think about De Bono’s Six Thinking Hats and call it White Hatting, that has a peculiar ring, but might look entertaining in a control room!

What am I doing to implement Red Teaming?

I’m not convinced I’m adding much actual substance to the conversation, other than being an advocate of ‘let’s try it’.

In a lower-key way, I made a recent decision to bring someone in specifically to check my working out on a particularly complex project at work. It was really helpful to have someone force me to reflect on my proposals, and can really see how this could be scaled up. 

I’m interested in views of colleagues on how this could be applicable and how some of the barriers could be addressed.

Ramen Resolution – Ruckus Ramen

Ramen Resolution – Ruckus Ramen

Reading Time: 2 minutes

Finding a ramen place on holiday isn’t difficult, especially in North America. But choosing a ramen place on holiday is a whole ‘nother matter.

I depend heavily on “Top 20 ramen joints in [city]” articles to narrow down the options for me. That’s how I discovered Ruckus Ramen in Boston, which appeared in this Thillist list.

I had arrived just as they were opening, so I was awkwardly the only patron for a little while.

I also missed the instruction to order at the cash register (check me out using Americanisms) so there was a bit of a standoff whilst both sides waited for the other to make a move. Eventually, I placed my order for tempura pickled Padron peppers and the Tori Paitan ramen, mainly beause it was heralded as a ‘crowdpleaser’ in that list I found.

The Padron peppers were delicious, salty, sour, crispy…everything I like!

However, I was disappointed when it came to the noodles. Not because there was anything wrong, but I definitely ordered badly.

I was seduced by what Ruckus call ‘swag’ but everywhere else calls extras. I’d pimped my ramen, with something called an umami bomb, and friends, it bombed.

The crispy chicken skin was not, and it just made the broth gloopy with collagen. Unfortunately, I was unable to finish it because it was just too thick.

That aside, heritage cauliflower was an interesting topping and something that I would try again.

Looking back there are other things on the menu which I should have ordered instead (step forward black garlic mazeman) so, the moral of this story is definitely to take time to read the menu in detail!

It seems unfair to rate Ruckus badly due to inept ordering, but if you’re going to force me I’d give it 2/5.

Ramen Resolution – back to Nanban

Ramen Resolution – back to Nanban

Reading Time: 2 minutes

It’s a rare occasion that I’m early for, well, anything. But a diary misunderstanding today meant that I ended up two hours early for a thing.

After eating, drinking, browsing, reading and general perusing…I even had time to update on some recent ramen adventures! Joy of joys!

My last visit to Nanban was on 31 December 2017. I remember then being intrigued by the idea of curried goat ramen.

After 364 days, I surrendered to the nagging voice in my head and headed back to the Brixton restaurant. I was not disappointed.

I had a cocktail (because; festive), placed my order (because; hungry) and settled back in to my book (because; other resolutions).

Crispy gyoza is a cool idea, but they tasted a bit greasy. The noodles were delicious though. Spicy, slightly sour broth, and meaty hunks of goat dotted through the bowl. It’s not the best egg that I’ve ever had, but hard to really find fault!

I think I’d still prefer soft and juicy pork belly as the meat, but I’m always up for trying new things, and would definitely return to Nanban again to assess the seafood ramen, which isn’t an option you see in a lot of places.

It’s slightly on the expensive side compared to other options in London, but you get what you pay for and so as a ‘last meal of 2018’ I felt it was justified.

I think I’ve given up on my rating system (although it would probably be a solid 4). In hindsight,the system wasn’t well enough developed at the outset, and I’m not sure after so many posts that I can introduce something new. What to do dear reader?!

If in doubt, eat more ramen! Peace.