Showing posts with label Design Thinking. Show all posts
Showing posts with label Design Thinking. Show all posts

Monday, September 07, 2020

The power of asking the wrong question

 Sometimes the problem isn't the problem. The problem is the question.

And that, in itself, is a problem for...er problem solving.

Let me explain. Imagine you have a client has asked you to build a better mousetrap.

You may spend many a fruitless hour seeking incremental improvements. You set off a stream of work on spring mechanics. Another on bait testing. Still another expends effort on reducing the number and cost of moving parts. After much effort you present you MVP. It ain't going to remake the market.

But what if we reframe the problem - by asking a different question?

How do I rid buildings of mice?

Now we have a world of new possibilities to explore - sonic and scent deterrents, scare cats, etc.

Sometimes the problem isn't the problem. The problem is the question. It introduces constraints that need not be applied.

Photo by Ricky Kharawala on Unsplash

Friday, February 01, 2019

Minimum Learning Vehicles

https://medium.com/@NeotericEU/lean-start-ups-by-example-5aea8091c07b
One of the many problems with making stuff fast in organisations is the varying forms of language used to describe the same thing.
Park for a moment the regular confusion between efficiency and effectiveness, the one that can create mindblocks in rapid iteration is the Minimum Viable Product.
I have heard this used interchangeably for paper sketches in Design Thinking creative sessions, all the way through to the first product being taken to the actual market at production scale.
Mindblocks - well not having a clear view of this makes it very difficult to understand what each rapid iteration cycle is trying to achieve.
I have become used to using MVP as something that may better be called the Minimum Learning Vehicle (MLV). I say it may better be called that because I think it better reflects the learning discipline of the MVP:
1. Identify what it is you want to learn from this iteration.
2. Draw/make/build only that which will give you that learning.
3. Test with the end user.
By its nature, the use of MLVs keeps things lean - avoiding scope creep and maintaining focus on the value proposition (the value to the end user).
It's a critical thing for all parties to agree when they set out to iterate to value at speed.
What do you call your MLV?

Monday, January 21, 2019

Creating new value - or simply keeping up?

Photo by Fancycrave on Unsplash

Demand for digital transformation is at an all time high - according to a survey of 600 leading execs for a DXC report: 2019: The year of digital decisions. It provides timely evidence that supports my mapping of the situation facing industry right now - referred to in detail here.

Referencing that article (The Job Of Digital Strategy Consulting): Companies are testing the water, feeling their way with agile here, lean there, new-tools-but-same-ways -of-working almost everywhere... There is no certain way of doing or being digital yet. Not by some distance. But we must expect that there will be movement in that direction.

What the increased demand/desire tells us is that digital transformation is headed toward ubiquity and with it standarisation and the need for interoperability. There's an increasing realisation that companies must build themselves a new future and this is at such scale that trying to do this with hand wrought nuts and bolts is too bespoke - too slow and too expensive.

What this also reminds us is that digital transformation is not the end product. It is a process of creating the nuts and bolts on which higher-order complexity - the novel stuff that creates greatest value - gets built.

When you have all the nuts and bolts, and power supplies and gears and pulleys and all those things you need to make stuff, it doesn't magically self-assemble. into things of value.

How you are able to use what you have brought together - the pile of 'what's' your grand 'why' of digital transformation may have provided you - that is where the magic happens.

The insight, the imagination, the ideation, the design, the rapid iteration, the testing and scaling - without these your digital investments are simply 'efficiency' spends. They won't even reduce your IT budgett. When we make stuff more efficiently we tend to use more of it (as Simon Wardley points out. Think how many more nuts and bolts got used as a result of standardising them.

What is needed is a way in which you can standardise and make repeatable the insight, the imagination, the ideation, the design, the rapid iteration, the testing and scaling. What is needed is a new way of working.

This is the 'How' of digital transformation and it is where the fight for market mastery gets won and lost.

In 2019 this is the most pressing challenge for creating new value vs simply keeping up.

Friday, November 16, 2018

Building in organisational adaptability

The way in which most businesses organise for value has a fundamental 20th century mass production design flaw. It constrains them from reaching both the capacity and capability to respond to the market at the speed our digital world demands.

It is specialisation.

Specialisation made a great deal of sense in a mass production world - enshrined in Adam Smith's pin factory, through Henry Ford's Model T and beyond.
But it presents a problem of friction for the modern, responsive organisation.

For example - if you have wonderful developers in one silo, and wonderful business leaders in another, you introduce a brake on responsiveness.
While you may have optimised your tech teams to develop, and your business teams to come up with ideas to value, in order to accelerate the generation of value these 'roles' should be more closely connected (as we see in Agile, Design Thinking, Lean Start-up, Holocracy and combinations thereof).
Specialisation made sense when neither party could easily access the skills of the other.

That has changed. Technology now enables business ideation. Technologies that enable one-to-one marketing, for example, can inspire businesses to ideate on the new models this supports. But the friction comes when tech delivery capacity and capability remain a bottleneck.

Those choke-points all too often force businesses back to 'as usual' when striving for new.
What is required is a way of giving business people technology skills and technology people business skills. In this way the organisation becomes more responsive to upturns and dips in  the requirement for both. It becomes built to adapt.

Pipe dream? Hardly - there are already many no-to-low code platforms and technologies which enable pretty much anyone with a laptop to develop their own applications and business process automation with nothing more than the lightest layer of additional coding*.
Business folk can be technology folk, too. At low cost. Minimum Viable Products can be crafted by the people with the vision and the insight - closing the strategy gap through direct and hands-on involvement.

And this cuts both ways. By applying managed innovation as a way of working (Agile, Design Thinking et al) Technology folk can become as enabled to access insight, set vision
and focus on value as their business colleagues.

Bringing both no-to-low code platforms and insight-led, human-centred managed innovation into your org, is a huge leap toward becoming a truly responsive organisation.

*I do not dismiss the importance of technologists. Even the best of these platforms 1. Had to be coded in the first place 2. Create their biggest bang for buck when some customisation is applied.

Thursday, July 13, 2017

Six months of innovation in one week

Under starters orders for blue sky thinking
My first day (and a night) at Northumbrian Water Group's Innovation Festival has been both inspiring and informative. Critically, it is turning creative inspiration into tangible plans.

On arrival last night I was treated to traditional northern hospitality. Pie & Peas no less. And a series of bands, primarily made up of NWG employees, showcasing creativity of their own.

In the light of day today the range and scope of activity became apparent. From a full-on hackathon ,where available data is being interrogated to try to solve the problem of water leakage, to VR demonstrations, through the teenagers' bedroom of the future, everywhere there is a spirit of collaboration and creative building.
Where stickies go ideas must follow

This is the first NWG Innovation Festival. It's been sponsored to the tune of £250,000. NWG's commitment has been in bringing the event and the people together and committing as many as 180 of their own people to the full five days of the event (400 plus partners, academics, schools and customers are attending in total each day).

CIO and Innovation lead Nigel Watson is sure it's worth it and is already commited to delivering NWG Innovation Festival II next year.
Design Thinking is being applied to six sprints:

  1. How do we reduce flooding?
  2. How do we know about leakage from water pipes and how can we fix it?
  3. How do we upgrade our infrastructure effectively and affordably?
  4. What will living and working look like in 2030?
  5. What can businesses do to improve the environment of the North East of England
  6. How do we optimise a mobile workforce for a complex network business

Defining solutions
Design Thinking is far from brand new at NWG. It has been in practice for 18 months. Each month a new sprint is embarked on - always off site and always with a suitable and or eccentric mix of people and skills engaged. In one sprint on billing a baker and a gamer were involved, Nigel says.

NWG uses the Double Diamond approach, taking their inspiration for the initial problem from business KPIs - which in their case are focused on delivering improved customer service.

Where they see evidence they are under-performing, that's where they focus the Design Thinking approach, to deliver a step change. This means innovation always delivers against business need.

The first job is to unpack the initial problem and really work to understand what are the true causes of the problem. Using these, they define the area to focus on and reach what Alastair Tawn (who leads Design Thinking at NWG) calls the 'Critical Problem'.

With the critical problem defined, the team can then work up a range of solutions before focusing back in on the solutions that will work.

For Nigel, the Festival delivers six months of innovation in a week.
Each of the problems the sprints are tackling are ones the water industry as whole need solving. Which explains Nigel's other ambitions for the event

  1. To improve the industry 
  2. To give small businesses in the NE exposure
  3. To enhance NWG's own reputation

"And if just one idea come that makes a significant difference to our business we’ll judge this a success," he said.

With programs for dark fibre to monitor for leakage, movement in pipes and changes in temperature;  universal mobile sensors moving above and below ground and new approaches to getting utilities to share both infrastructure and data among those in development on Day 4 of the event, Nigel should be confident.

We'll get a clearer idea tomorrow when the final ideas are presented.
I'm also planning to share a bit more about the culture of innovation at NWG.
Watch this space, as we used to say when space was limited...




FasterFuture.blogspot.com

The rate of change is so rapid it's difficult for one person to keep up to speed. Let's pool our thoughts, share our reactions and, who knows, even reach some shared conclusions worth arriving at?