What To Do When Nothing Has Value

2025-06-28_karma-yogi.png

Saturday, 9.40pm

Sheffield, U.K.

The major value in life is not what you get. The major value in life is what you become. – Jim Rohn

I think we are living through a change in the global system, one that could have profound consequences.

Or it could fizzle out.

But while we’re waiting to see what happens let’s conduct a little thought experiment.

Let’s think about a world where there are fewer jobs to do because of these new technologies that make people with jobs so productive that companies don’t need to hire as many people as before.

New entrants to the labour market find there are fewer jobs to go after.

The well paid ones, the few that lead to money and status, are hoovered up by the rich and connected.

The rest struggle to get anything.

That’s one view.

Or, the technologies allow us to do more than ever before.

Every single person has the tools to create something great – they don’t need the resources of a corporation to create a new product, find a market, delight customers.

So yes, there are no jobs. But instead there is an explosion in businesses – where people create value.

I started this post by suggesting that a world could exist where nothing has value.

Perhaps I should examine my assumptions there.

If a machine can do something in seconds that would take an artist days or weeks, and do so for free – what happens to value?

The value of the machine generated product is nothing.

The value of the artists work is something – to a person that values the artist – and nothing if not.

The art in itself becomes less important than the way in which its produced.

There is a market for free. And there is a market for handcrafted. And each of us needs to decide how we go after the market that works for us.

The drawings I make for this blog are stuck at a 4th or 5th grade level.

Look at the picture above. It’s not art. It’s just someone doodling with a pen. It’s not worth anything.

Except to me.

Because it helps me in my process – in the writing that I do next.

And the writing isn’t brilliant either – it’s rambling, informal, grammatically questionable, unedited.

Nothing that would make it into the New Yorker.

Except, I’m not writing for the New Yorker,

I’m writing to get my thoughts in line, because it helps me in how I live my life.

Culturally, I was brought up in a tradition that values work, not the results of work.

I don’t know how well that translates to you reading this, but it comes down to saying do what you must do, do the thing that you’re working on with no thought of reward, no need for gratification.

Do it because it must be done.

But why, you might ask? What’s the point of that. You may point to Samuel Johnson who said “No man but a blockhead ever wrote, except for money”.

But if you live in a world where you cannot sell your writing, you cannot sell your art – because the machines do it instead – should you stop making art, stop writing?

Or are you now free – to do it because you want to not because you have to.

Because you value doing what you do.

And when that happens it doesn’t matter what happens in the rest of the world.

You just do you.

And figure out some other way to create value for others that brings in money.

Cheers,

Karthik Suresh

The Trough of Despair – Is SSM understandable?

2025-05-17_ssm-issues.png

Shallow understanding from people of good will is more frustrating than absolute misunderstanding from people of ill will. – Martin Luther King, Jr.

Saturday, 9.43pm

Sheffield, UK.

First, apologies if you have received multiple posts today.

That’s because I figured that some of the lighter, more business focused stuff that I’ve been putting on LinkedIn might as well be here as well.

It’s a bit of a break from the heavier stuff on systems thinking, like in this post.

I really wouldn’t blame you if you stopped reading here. In fact I’d advise it…

But, if you’re still here.

Going forward, you might get a mix of the two types depending on what I write and when I post.

With this post I want to close off Holwell (2000) that I’ve been working on the last three or so posts.

And I think I might have bitten off too much with taking on this talk.

The reason is that it’s very hard to explain something to someone that they don’t already know.

This is because most people know something.

When they hear something new they try and fit it into the existing structure of what they know.

This is a bit like fitting a watermelon into a large bucket.

That’s easy you might think – but here’s the problem. The bucket is sealed with a lid fitted with a small straw.

That’s the cognitive opening – the hole in the straw that you’ve got to fit the watermelon through.

And that sort of activity usually ends up making a mess, with most of the watermelon dripping everywhere.

This is a terrible analogy.

The takeaway message is that there is lots of confusion and misunderstanding about soft systems methodology (SSM) and what it is.

So much so, that I’m not sure I can tell you what it is and I’m supposed to be the sort of expert around here.

So, let me just sum up some of the key points that make discussion problematic – the issues, if you will.

First, there’s the history of SSM and how it developed from being an application of systems engineering to a learning system that could be used to engage with and improve problem situations.

Then there is the explanation of what it actually is – from paraphrasing or parroting what the pioneers said, and the philosophy behind it all.

Although, I do remember reading a catty letter that suggested the pioneers disagreed too.

Again – the old thing. Why are academic arguments so vicious? Because the stakes are so small.

Explanation is complicated by what’s said, what’s said later, and what one says about what’s been said.

I don’t want to go into it but it feels a bit zen like – you can only get it with experience not with talk.

But talk is the business of academia so you end up with lots of usage and lots of talk.

This is stuff like the aspects of SSM, definitions, justifications, how it could be used with other approaches, whether it’s grafted on or whether other approaches are embedded in it.

And throughout all this, you’ll note that I haven’t yet said what the thing is – SSM, that is.

Anyway, I’m now in this trough, where it all seems far too hard to explain but I think I know what it is and it works.

Just trust me, will you?

Okay, I wouldn’t either.

So, I think we’ll move on and I’ll climb out of this sometime.

Starting with figuring out how one should approach a history paper in the first place.

Maybe we’ll examine one or two by Kirby, who’s written a few histories of the operational research (OR) society and see if they can give us some guidance.

Cheers,

Karthik Suresh

Well-defined or Ill-defined Problems

2025-05-13_holwell-2.png

Tuesday, 9.06pm

Sheffield, U.K.

There is a lot of stuff we can’t control, but it is completely in our power to decide what the definition of what a good job is. That’s up to us. – Mike Rowe

I’m carrying on with reading Holwell, S., 2000. Soft Systems Methodology: Other Voices. Systemic Practice and Action Research 13, 773–797, and today I am going to focus on a single paragraph.

But first, some background.

I’ve been writing more on LinkedIn recently and I’m finding it tricky to find the right kind of tone.

A writer on LinkedIn is incentivised by the system to chase engagement and likes – it’s the dopamine reward for putting the “right” kind of content on the platform.

That content is designed to stop and engage you, and so it uses certain psychological triggers – clickbait of one kind or another.

With each promise in the headline, there has to be a payoff to keep you from being disappointed; you need a nugget of wisdom in exchange for stopping your scroll.

This is something that’s tricky to deliver if your message is that the world is complicated and when you start trying to make sense of it things usually get more complicated.

And that things are usually harder to do than you think.

But the kind of message that hooks you is look at this thing you need, we’ve got an easy button for it, and if you buy this everything in your life will be better.

In a roundabout way, this is the point of the paragraph that I’m reading – the difference between simple and complex, between well-defined and ill-defined problems.

A well defined problem is what is 2 x 3? You don’t need to worry about what is 2 and what is 3.

I struggled to find a word for this next point and came up with it’s a closed problem – you don’t need to know anything about the properties of graphite to figure out the answer. The pencil you use has no impact on the problem, neither does the room you’re in or the ongoing dispute you have with a neighbour.

It’s a means-ends problem – what means do I need to achieve this end? To solve the problem you must have some knowledge of arithmetic or know someone who does.

And finally, there is a stopping point. There is a solution. You know when you get to the answer that there is an answer, and this is it.

The kinds of problems we face in real life are often not of this sort, they are instead ill-defined.

There isn’t really a “problem” but a problem situation.

Take a look at the news right now.

How would you, if you were the leader of a country, respond to what is going on in politics?

It’s got to be a hard one. You may agree with the policies. You may disagree with them. You might disagree but have to pretend to agree because you haven’t got any cards. You might have to disagree because that’s what your people want you to do, but really you want this whole thing to be over and retire to your country house.

What you’ve got isn’t a problem but a problem-situation.

In such problem-situations the context matters. The way you act will be different if you have power, or if you need support from others, and whether you can count on support or if you have to persuade others.

Such approaches require problem structuring – what are the tradeoffs, what kind of agreements could you reach, what levers do you have?

I imagine the kind of frantic negotiation that happens when a bill needs to be passed and the sponsors need to call all the legislators they know and engage in horse trading to get the task done. You know it’s heading in the right direction when everyone is about the same amount of unhappy.

And then finally, there is no end point, there is no solution.

The best you can hope for is that you’ve made the world a better place – that there has been some improvement.

In the next post, we’ll try and get back on the history track.

Other Voices In The Development Of Soft Systems Methodology

2025-05-11_2000-Holwell.png

Sunday, 8.41pm

Sheffield, U.K.

There are three kinds of men. The one that learns by reading. The few who learn by observation. The rest of them have to pee on the electric fence for themselves. – Will Rogers

This post is a set of reading notes from Holwell, S., 2000. Soft Systems Methodology: Other Voices. Systemic Practice and Action Research 13, 773–797, as I prepare to give a talk on the history of soft systems methodology (SSM).

I was going to carry on from my last post which was working through the summary in Systems Thinking Systems Practice (STSP) but then I felt I would just be repeating what Checkland had already said.

I stopped, thinking I should look more widely first and searched my collection of papers and came across Holwell (2000).

She makes the following observations:

  1. Many people simply repeat Checkland’s work, more sophisticated approaches focus on specific aspects of the work;
  2. A lot of people just don’t get it;
  3. Early work in Lancaster was based on systems engineering – how do we approach that and is it dated?
  4. The secondary literature is starting to impact the way people think about SSM.

From positivist thinking to interpretivist thinking

Brace yourselves. This is going to be heavy going. I find it tricky.

Checkland’s defining contribution is bringing “the concepts and philosophy of interpretive social science into systems thinking” (Flood and Ulrich, 1991, p.186).

Let’s unpack this.

First, interpretive rather than positivist refers to two ways of looking at the world. Positivism says that the world is real and all that matters can be observed and measured. Interpretivism says that you create the world along with others in your mind.

The systems concept is about wholes and the properties of wholes.

The application of systems thinking in the social sciences is usually under the heading of functionalism. This is Emile Durkheim’s theory that socity is similar to a biological organism. There are parts to it, and there are structures that connect these parts and that the workings of these parts within the whole enables a successful society.

A functionalist model “sees” society as parts and connections and can therefore accept that these parts can be designed, constructed and managed.

Society is a machine that can be controlled.

Now, you can see that this line of thinking leads to possibly problematic outcomes, such as dictatorships.

SSM has a model of social reality that is derived instead from Husserl’s philosophy of phenomenology.

Husserl’s approach says something like rather than going with the traditional Western rationalist bias, pay attention to your real lived experience – it’s sometimes called the science of experience.

I think this must be similar to the Japanese concept of going to gemba – the place where the work is actually happening.

So I think what this is saying is that rather than starting with a framework that says this is how societies work and this is how we should organize things, go and look and see for yourself and rely on an intuitive approach, without assumptions or intellectualizing to “get” what is going on.

Which is a lot of big words to say something like just open your eyes and see what is in front of you rather than what you believe is in front of you.

The other connection SSM has is with Weber’s interpretive sociology, which combines a social group’s needs to have a coherent world view, but also what the power relationships are in their environments.

Again in simple terms – this is about why are we where we are, and how can we hold on to, or gain more power.

Think about this like a manager – why are you in your job, and how do you keep your position and get ahead?

Let’s stop here and carry on in the next post.

Cheers,

Karthik Suresh

From Science To SSM – A Summary

2025-05-07_ssm-history.png

Wednesday, 9.39pm

Sheffield, U.K.

History never looks like history when you are living through it. – John W. Gardner

In Peter Checkland’s 1981 book “Systems Thinking, Systems Practice” (STSP), there is a helpful summary of the arguments developed in the book.

The scope, however, is vast.

Let me try and make sense of the summary, by in turn summarizing it.

In the beginning, there was magic and mystery and then science came along.

As an aside, I’m currently watching the BBC series Merlin, for no defensible reason.

The legends of King Arthur are set in a post-Roman time around the 5th and 6th centuries.

In the reimagined series, there is quite a lot about the methods of science.

The scientific method and modern science are really associated, however, with the scientific revolution in the 16th and 17th century.

The three Rs made it clear what was science and what was not.

Reductionism, repeatability and refutation made it possible to build a reliable and continuously refined account of what went on in the world.

This worked very well in the restricted sciences like physics, and pretty well in the unrestricted sciences like biology.

But the methods of natural science start to break down when they are applied to complex and social situations.

In particular, they struggle with questions of ends and means – of “managing” activities.

While science is concerned with bits it’s less worried about wholes – and that’s where the systems concept entered the picture.

The systems concept is concerned with wholes and characteristics that emerge at different levels – characteristics that do not arise from lower levels.

For example, in biology, the science of cells does not explain why a particular arrangement of cells makes up a human body that sings.

The systems concept was seen as a useful way to address management problems associated with human activity.

But then we came up against different types of problems.

The techniques of analysis and engineering being used worked well on certain kinds of problems – hard ones – where there was a well defined problem that needed to be solved.

How do we bridge that large gap so a train can get from here to there, for example.

But the systems concept struggled with ill-structured problems.

How do you start to fix something that you know is broken but you’re not sure how to express the problem in the first place?

That issue led to the development of a new methodology from 1969 to 1972 in 9 studies.

We’ll dig into this in the next post.

Cheers,

Karthik Suresh

What Is Soft Systems Methodology (SSM)?

2025-04-24_ssm-definitive.png

Thursday, 9.12pm

Sheffield, U.K.

Every company has two organizational structures: The formal one is written on the charts; the other is the everyday relationship of the men and women in the organization. – Harold S. Geneen

I write a lot in this blog about soft systems methodology (SSM).

But what is that, exactly?

To find out, you might want to read Peter Checkland and John Poulter’s “A short definitive account of soft systems methodology and its use for practitioners, teachers and students”, published in 2006.

It’s the definitive account, the final say, so perhaps that’s a good place to start.

A few of Checkland’s papers complain that people don’t understand SSM and they miss the point of it in how they use it – or claim to use it.

It’s easy to get lost in the academic discussion – but I am going to make things worse by attempting my own interpretation of what’s going on with SSM.

Here’s my version of the brief version.

Let’s start with life itself – the everyday. Today, tomorrow, yesterday. All the days that we live through.

We live in a flux of interwoven events and ideas. Ideas lead to events, events spark ideas and life goes on.

Everyday life produces situations.

These situations have people in them. It’s the presence of people that make it possible for situations to exist – because they come into existence in the minds of people. A problem only bursts into existence when someone believes it does.

Let’s not worry about this too much, but the key point is that you need people to make a situation – and what those people think about the situation is what we’re focused on.

Sometimes, they think a situation is problematical. That something is wrong. That things could be better.

Why do they do that? Why look for problems, or think at all?

It’s because we can’t help but be purposeful – we act with purpose. Human beings have a brain that allows them to act intentionally – rather than randomly.

But, we usually only see situations from our point of view. We may exist in a complex, multifaceted reality that some people insist is very simple because they see it one way, and others disagree because they see it another way.

It’s the same thing – we just have different perceptions of the thing we’re in.

Wars have been fought over these different perceptions of the same thing.

But, we’re learning over time – and the thing that could help is to learn more about the situation.

We go out and intentionally learn more about the situation as perceived by the people affected by it and affecting it.

We talk to them, we ask questions, we listen to them, we build a rich picture of what’s going on.

All this learning helps us build models of purposeful activity.

This is a new bit – it’s not something most people do.

A model helps us capture that learning and put it into a form that we can look at and understand – it’s like a theory, an operating manual – something we can use.

And we use it to help us as questions about the situation, to take this model or models with multiple viewpoints and have a structured debate – a good conversation about what’s going on and what we could possibly do.

This kind of discussion helps us to decide what action to take – and to take that action.

The action, we hope, is going to improve the situation.

It’s going to affect it in some way, anyway.

And now the situation has changed – hopefully for the better, sometimes for the worse, and we now have a new situation.

If all is good, great.

If it’s still problematic, then we continue our cycle of learning, modelling, questioning, and taking action.

All this may seem simple. Perhaps even obvious. But it’s the result of decades of thinking and action research.

In my next post I think I need to go back to where it all started to show the gap between where things were and where things are, and then build a bridge between the two.

Cheers,

Karthik Suresh

Beginning At The End for SSM

2025-04-23_parthian-shot.png

Wednesday, 9.29pm

Sheffield, U.K.

God cannot alter the past, though historians can. – Samuel Butler

I talked in my last post about having to work on a talk about the history of SSM.

For the next several posts I’m going to work on this project – so you may ending up learning more about SSM than you might consider necessary.

Here goes.

I could look at this history chronologically or thematically.

Let’s start at the end.

Peter Checkland, the name most associated with Soft Systems Methodology or SSM, delivered a keynote at OR 60, the Operations Research conference.

The paper that followed was called Reflections on 40 years in the management field: A Parthian shot (friendly).

A Parthian shot is a hit-and-run battle tactic used by the Parthians, an Iranian people.

Their cavalry would attack the enemy, then turn tail and run. The enemy would chase them believing they were fleeing. When the pursuers were close the Parthians would swing around in their saddles and fire their arrows into the chasing army.

This is where the term “parting shot” comes from – delivered by the person who has to have the last word as he or she leaves the room.

The talk and paper mark the end of Checkland’s professional career and so are perhaps the right place to start from to understand the journey that led to SSM.

They are reflections on the years “spent trying to understand the everyday real world in order to bring about positive changes in real-world situations which are taken to be problematical”.

Let’s unpack some of these elements – what are real-world situations that are taken to be problematical?

Wars, for starters. The Second World War was decidedly problematical. And it led to the creation of Operations Research as a field.

After the war, however, OR practitioners looked for other fields in which to apply their learnings, such as the management of organisations.

This in turn led to a rich set of techniques that were increasingly reductionist in nature, as benefitted a field that considered itself scientific.

And that led to another issue. A technique that solves a clear problem is great. But what if the problem itself is unclear?

This is something most people never really stop to consider.

Think about the last conversation you had where someone came up with a problem.

Did you feel like you had to offer a solution instantly?

Did you feel like even if you didn’t have one, there was a solution out there that could be found?

Did you ever stop to consider that the problem might be the way you were thinking about problems?

SSM’s origin story is somewhere in this space – in that period between when people believed that science could solve everything, and we learned that people behave in ways that science finds hard to deal with.

That’s a rabbit hole for the next post.

Cheers,

Karthik Suresh

The Road Is Rarely Straight

2025-04-22_bullseye.png

Tuesday, 10.51pm

Sheffield, U.K.

A road’s just an opinion about which way to go. – Rudy Rucker

A few weeks back we went to visit the remains of a Roman fort at Housesteads.

Some unnervingly straight roads take you there.

It’s strange when you travel on a straight road in the UK.

If you do it usually means you’re on a road laid down by the Romans around 2,000 years ago.

I prefer to meander. It seems a more natural way to be. Or, I’m trying to excuse procrastinating.

I’m working on a paper about the history of Soft Systems Methodology (SSM).

I find that when I have a project to work on these days I start by avoiding working on the thing itself.

Instead, I find ways to think about how to work on the thing.

I started by re-reading John McPhee’s essay on Structure.

I go back to this one quite often because he insists that his students start with a structure of some sort. It can be an outline. It can be a diagram. But the starting point is always a structure.

I like to start with a drawing of some kind – like the one that starts each of my posts.

The approach seems straightforward – you start with a structure, with an outline – something that you can build from like a design blueprint.

But, I think that sometimes the structure can only be seen when you aren’t looking for it.

It’s something you spy out of the corner of your eye as you distract yourself with something else.

I’ve read quite a lot about SSM over the years.

If I were following McPhee’s approach I’d first collect all my notes, sweep up all the raw material I have and put it in a pile.

Then, I’d go through this list, making and organising notes chronologically and thematically.

Then I’d look at my collections of notes and start to arrange them in a way that matched the structure I was thinking about.

And then I’d write.

This is the right way. A good way.

So why do I find it so hard to do?

Instead of following this approach I complained a lot in a series of notes.

Then I had something else to do.

When I had a few minutes free again, I tapped out an outline, something that started at the end, worked back to the beginning, and listed a number of themes that need to be put in some kind of order.

I’m finding that this approach seems to be helpful with other kinds of tasks as well.

Want to write some code?

Do your research. Read background information. Take notes.

Then, take a walk. Think about something else. Avoid working on the problem.

Then start work and see how the next stage goes.

This separation between stages, the willingness to give yourself time is hard to do – but it seems to help.

Perhaps it’s about giving your subconscious time to work on something while your conscious mind takes a break.

Still, the work does need to be done.

Perhaps tomorrow I should work on getting the outline finished.

Cheers,

Karthik Suresh

Taking Time To Figure Out What’s Going On

2025-04-21_braindump.png

Monday, 8.14pm

Sheffield, U.K.

I don’t write about good and evil with this enormous dichotomy. I write about people. I write about people doing the kinds of things that people do. – Octavia E. Butler

We live in uncertain times. The S&P500 is down 13% since the start of the year and no one really knows how things will play out.

Is this really something new?

Not really. Since I became aware that such things like markets existed, back at the start of this century, we’ve had a dot com crash, a housing crash, an energy crisis, the start of deglobalisation, a pandemic, a number of big and small wars, and what’s happening whenever you read this.

If you’re interested in making decisions under uncertainty what should you do, are there any models that can help?

I’m starting to think there aren’t.

Everything gets more complex the more you look at it.

Take something simple – the amount of time you spend reading versus the time you spend writing.

What do you read these days?

My list is depressing. I look at the BBC and CNN and get a set of world highlights.

I don’t bother with social media other than taking a brief look at LinkedIn.

I read the Economist when I remember to log into my library app, which suggested in its last issue that LinkedIn is the last space where you get useful information but that’s changing because users don’t spend enough time on it – less than an hour a week versus 35 hours on Tiktok if I remember correctly, although 35 hours – really?

I find stuff worth reading on Mastadon, where you come across pointers to posts like this one by Kat Hicks.

There’s a section in this post that talks about how you see what’s actually going on, the real rules that people play by when you’re not watching.

It talks about how to understand a thing you must also understand its opposite – things come in pairs.

This is similar to Kelly’s concept of bipolar constructs that underpins Colin Eden’s Strategic options development and analysis (SODA).

I have a lot on my mind right now and Hicks’ post reminded me of the power of pairs and I used them to jot down some of the things I’m thinking about.

Reading, in this case, led to writing.

I used a model to help me get started but, if you remember, I said earlier that I’m not sure models help that much.

So what’s going on?

I’m not going to go through the rest of my list in the image above, but what I think I’m trying to say is that life consists of contradictions.

We spend our days trying to figure out where to position ourselves between these extremes, driven partly by what we want to do and partly by what the environment demands from us.

And that means we have to be comfortable with uncertainty, with complexity, with the unavailability of clear answers and simple solutions.

We have to figure our way through situations that are never as bad as they seem and never as good as we’d like them to be.

We usually find that the future is obscured, that we see dimly, that of the many options that we could pick from none are compelling enough to commit to completely.

It’s when we commit that we take on risk. It’s when we commit that we reap rewards. How can things be both good and bad? And yet they always are.

I therefore reach this unhelpful conclusion.

Keep all your options open for as long as possible.

When given a choice between two things, do both.

Except when you have to make up your mind and commit to one thing.

Then do that.

Cheers,

Karthik Suresh

Why We Need To Try and Improve Rather Than Solve Situations

2025-03-27_improve-not-solve.png

Thursday, 8.57pm

Sheffield, U.K.

In boxing, they say it’s the punch you don’t see coming that knocks you out. In the wider world, the reality we ignore or deny is the one that weakens our most impassioned efforts toward improvement. – Katherine Dunn

Think of a situation, a problematic one.

Struggling to come up with one? Just have a look at the news – perhaps the productivity challenge that seems to afflict so many parts of the economy.

Why don’t things just work?

The larger operations get, the less nimble they are – elephants don’t dance, as the saying goes.

Managers in organisations find themselves in situations that they consider problematic. What tends to happen?

The most common response is increasing paralysis. Things can’t happen because other things need to happen first. And those other things require the first things to happen.

The Economist has an article about the need for countries in Europe to increase defence spending.

The recommended approach is to spend more money on tanks and drones and interceptor missiles.

But that needs more actual money.

Instead, a number of countries are using accounting techniques – reclassifying existing spending as defence spending, such as defence-related pensions.

Which is all very well if you want to hit a target. It’s much less useful if you want to actually defend yourself.

I don’t know if paralysis is the right term, there’s a lot of activity but no actual movement.

It’s the opposite of a duck, all flap but no glide.

At the other end of the scale is demolition, or what is now referred to as “delete” on the other side of the pond.

It’s more common in commercial settings where a new boss comes in and fires lots of people or sells off parts of the company.

It’s a form of surgery – cut off the parts that are diseased and what’s left has a chance to survive.

That assumes that the person in charge knows how to do surgery and isn’t hacking at random.

And, of course, that the patient survives once the surgery is done.

If you speak to insiders you realise that the medical system is not there to help you, it’s there to make money.

Far too many procedures are unnecessary.

We should really try and avoid hospitals altogether – the best defence is to stay healthy.

These first two strategies are the ones managers reach for first.

The third one, which they should reach for, is simple, but not easy.

It’s trying to improve a situation, rather than trying to find a solution.

Let’s take an example that comes up again and again in my experience.

You have a data problem of some kind – you need information to meet some obligation.

The first thing people do is look for a system – is there an app for that?

That’s looking for a solution – a one-stop shop, a magic bullet.

Magic isn’t real.

What’s real is that we do things a certain way right now.

We need to deliver something that we don’t do yet.

How do we improve what we’re doing so that we can deliver this new thing?

Improvement takes time, patience and understanding. You have to go to where the work is being done, see how it’s being done, and learn your way into making improvements.

Some people are too busy to take the time to make things better.

They are also too busy to have the time to learn what’s possible.

And I don’t really know how to address that situation – when people are unwilling or unable we either have to accept a paralysed situation or use coercive power.

And that’s no fun for anyone.

Trying to improve things is hard, unsexy, valuable work.

And, when it works, it can be fun.

Cheers,

Karthik Suresh