Discussion about this post

User's avatar
Valentin Loew's avatar

Hello Roger,

It is great to have more on this because this question has been extremely helpful to me since I started using it.

I recently had a discussion with a partner following the finalisation of the Strategic Choice Cascade for a client who has a maritime weather consulting firm.

We were discussing how to build the EMS to make the strategy actionable. My partner told me he was working on implementing an IT platform to manage delivery and the consultants billings since they use outside contractors. He suggested that this should be added in the Cascade.

My first reflex was to use the « Is the opposite Stupid question » to try and figure out if this was truly something we should add. The opposite of the choice would be to keep working with bloated excel spreadsheets. It would be stupid on its face. So at first glance this looks like an operational imperative, so there is no place for it on the main corporate cascade.

But it got me thinking further : What he is really doing is functional strategy (Here the IT function, to support our WTP/HTW). My intuition is that what he is doing is truly strategic, but it must be part of a different integrated set of choices. So I reclassified this choice not as an operational imperative, but as a key component of the IT strategy, which must be laid out in a different cascade, with all the proper choices clearly laid out.

It avoided dismissing what he does as « not strategic », while laying the groundwork for proper reflexion on a truly differentiated IT strategy.

The question was helpful here as a classification tool : something can sound as an operational imperative for a corporate strategy, but be a key element of a powerful functional strategy.

The core idea being that the software in itself is not strategic, it's what you do with it that is.

I’d be curious to know your thoughts on this and if this makes sense logically.

Best,

Valentin

Olivier Burnouf's avatar

I've found that sometimes the opposite of a choice appears stupid on its face because that's how the industry has operated for ages and the assumption is not challenged (by incumbents that is).

I'll take 2 examples:

1/ private banking: targeting people under a certain amount of savings/income appears stupid on its face. How could you manage the wealth of customers that are... not wealthy? (and the failures of low-cost offers back in the dot.com era would convince any banker of the stupidity of the choice): you must target wealth investors. Period. Then came the robo-advisors...

2/ Factoring/receivables finance: when I was head of strategy with a leading factoring business, one criterion for the target customers was businesses that sell on credit. Targeting businesses that don't sell on credit - and thus have no receivables on their balance sheet to fund - looked beyond stupid: that was a non-starter. Then I suggested that maybe there were businesses that didn't sell on credit but would like to do it to increase their revenue and/or build loyalty. They'd do it provided they got our expertise in credit risk and our funding. We would fund invoices that would not have been created if we had not offer to fund them in the 1st place. Brits are too polite to say that choice was stupid but since I was not even asked to articulate what would have to be true for my idea to be a valid one, that was the feeling I got (then B2B BNPL became a $200 bn industry)

I'm pretty sure you have encountered such situations (wealth management notably). I'd be curious to know how you managed to convince clients that a choice never pursued (successfully) by the industry is not necessarily stupid on its face (at least maybe it was but it's not anymore)?

14 more comments...

No posts

Ready for more?