Clarke Awards

18 Mar

I read a lot. (Sometimes I think of something to say about what I read, too). But you have to feed the beast that is the reading in-bookcase.

So I’ve just ordered from the lovely Big Green Books – – the Clarke Award shortlist:

~ Nexus by Ramez Naam (Angry Robot)
God’s War by Kameron Hurley (Del Rey)
The Machine by James Smythe (Blue Door)
Ancillary Justice by Anne Leckie (Orbit)
The Disestablishment of Paradise by Phillip Mann (Gollancz)
The Adjacent by Christopher Priest (Gollancz)

(stolen from Angry Robot blog:

Two of these I actually know as good authors; one I have seen on t’internet, and the others are something I look forward to🙂


Consortium meetings

27 Jan

I find I’m at my most productive in a consortium meeting. Get representatives of a dozen organisations in a room, close the door, put in a giant pot of dodgy coffee, and let the presentations begin.

As the faint sound of other people sending email ticks into my ears, I first think “That’s terribly rude. We should all be concentrating on this, we’re all spending time and money to be here, the poor sod presenting wants to get our thoughts and intelligence”. Then the slightly droning tone of the presenter lulls me into a trance state, and my brain kicks into gear.

Suddenly, I realise how to resolve the deadlock in the proposal I’m writing. That difficult email reply becomes transparently obvious. The other pages of notes in my notebook demand inspection, and insights into them abound.

Within minutes, I’m furiously sending emails, scribbling notes, pencilling in meetings and resolving crises – and starting a few for other people! The meeting flows past in a productive blur, until suddenly I realise it’s my turn to get up and speak.

I draw myself up and wander to the front. The entire room is tapping blankly into their laptops. I launch into action with a plosive remark and a quick quip to get everyone focussed and alert, breaking them out of their state of flow and ensuring they’ll pay attention to my presentation, which is of course the most important of the day.

As I reach the end of my presentation, I look round the room and realise I have committed the worst crime of the meeting. I have stopped everyone else from working.

(With apologies to my colleagues in today’s meeting…)

Innovation Architectures

6 Jul

Just finished reading “Innovation as Usual”, Miller and Wedell-Wedellsborg, so I thought I’d try something different and actually get round to writing up a few notes.  Firstly, they’ve got a website: so go and grab the book from there.

This book is slim. It’s got some really good ideas, and it says them concisely. You’ll not need to force people to keep reading it for weeks and weeks. I like that, already.

What’s the core idea? Getting a stream of new, good, effective ideas into a business is not as simple as asking for them. Sturgeon’s law (90% of anything is crap) applies. Most ideas are bad ideas. If you’re going to get a stream of good ideas, you’ll need to make sure that you have prepared the ground.

The book opens by defining innovation, and the Innovation Architect:

a person that makes other people innovate by changing the environment they work in.

(I’m already getting the warm and fuzzies.)

Innovation Architects, it seems, are most likely to be leaders in their businesses as well. Not necessarily the being at the top, but people taking a leadership role, setting a direction, trying to achieve things in a bigger picture. Leaders, of course, achieve their results by enabling other people to achieve great things, rather than necessarily doing them themselves. So if we’re going to have innovation in an organisation, it’s going to be organic (in the military sense: to the people delivering the work. Which means we’re going to need to make it easy for the potential of innovation to become real, useful innovation.

And to do this we have to make it easy to do the right kind of innovation – we have to put systems and support in place to make it normal, to make our people behave like innovators so that they are innovators.

At this point M&W bring in a framework: “the 5+1 keystone behaviours of innovation to promote in others”. Shameless quote:

  1. Focus on ideas that matter to the business
  2. Connect to the outside to find original ideas
  3. Tweak and challenge their initial ideas
  4. Select the best ideas and discard the rest
  5. Stealthstorm past the politics of innovation

+1: Persist in the pursuit of innovation as usual.

Let’s run through them in a little more detail.


Sonnets and haikus are a horribly restrictive way to write, but they produce brilliant gems of ideas. Constraining the domain of thought produces better thoughts. Odd. Interesting.

It’s easy to set up an “ideas funnel” and fill it with ideas you can’t do anything with. So set specific goals – “how do we decrease production cost by 40%?”.  Tell people what to focus on: “We don’t want new products this year. We’re focussing on delivering and improving the current ones”. Have some clear objectives, and provide some guidance. And, from time to time, change the focus to a different area/approach/activity – look at processes instead of products, say.


You won’t think of a brilliant way to make use of an idea from a different field if you never talk to anyone in a different field.  Make a space in the business where ideas from elsewhere can be found.

(There’s a great footnote in this section on the importance of implementing ideas, not having them.)

The key to getting lots of useful ideas is, apparently, recombinant innovation: seeing things in other areas and mixing them up. You need to be exposed to the actual problems, as well. Watch your customers, visit them, meet with them to analyze their problems. Really. Go sit in their offices. Listen to them. (There’s a maxim from sales about this: shut up and listen and people will tell you their problems.) Spend time with people you don’t normally meet with.

And, of course, you need to create some systems to share those ideas. Have people talk about things they’ve done and seen. Before any meeting, assign someone to bring something interesting.


No-one comes up with brilliant ideas at the beginning. So you’re going to have to change the ideas – to tweak them into ideas that can practically be applied! Test the idea, analyse it, throw up an MVP, get other people from the organisation to both challenge them and help improve them.

As you work on the idea, you’ll improve your understanding of the problem as well. That’s a vital part of the process. “Reframe the problem, and test the solution”. Check your assumptions about the problem space all the time. Write down the problem, run the Five Whys, work out what the person would describe the results they would pay for as. Then go and test the solutions. Quickly. Find a simple way to do so.

When doing this, you need to enable useful criticism. M+W give an example from Pixar, where directors show daily their work, and comments are made – but it is up to the directors what to do about the comments. You need strong critical thought to improve ideas, but it needs to be managed to get the improvement, not to score points or assert authority.


Sturgeon’s law again. But also cognitive biases – how do you support gatekeepers to effectively select the ideas without discarding really good ones? Probably, you need a fast filtering process to run on “normal” ideas, looking for quick wins, and a slow contemplative one to run on more subtle – or more disruptive – ideas. But you have to build a system here too.

You should be careful about who is a gatekeeper, you should have and review evaluation criteria, and you need to calibrate the gatekeeping process.

One technique is to “blind” the review process; another is to bring in people outside the “idea” to make these decisions. Having a mix of people involved in gatekeeping helps, as does reviewing the idea in context, rather than from slides.

An important part of the gatekeeping process is killing bad ideas fast – someone who knows their idea isn’t going to work and kills it for you is a wonder! It’s worth putting in place tangible deadlines and end-stops for projects, to prevent them proliferating endlessly – make them specific time-limited experiments, so they don’t become “the way we do things” – but make the deadlines generous. Get people to vote for keeping projects, not for killing them.


It’s an organisation. You have politics. You need to manage the development of the innovation  to avoid offending your culture or politics. Someone somewhere high up will need to be air cover. If you get this right, it becomes easier to do what you’re trying to do.

Help people establish networks within (and outside!) the company, so they can get support when trying new things. Ask for advice, not political capital. Make sure your innovation has a narrative – a story – because people will remember those. Show the value of the innovation as early as possible, and make the showing memorable and personal.

And the +1, Persist?

You need to set up the reward structures and culture around the organisation so people keep innovating, so people actually (as Kennedy said) “choose to do these things not because they are easy but because they are hard”. But if you give people the opportunity and the support to work on the innovations they want to, they will.

So make sure people are doing things they want to be doing. Connect people with areas they are interested in – and get them to find ideas that only they could find. (But remind them to find ideas of potential value to the business!)

Autonomy is a big help in generating persistence: let people tackle problems they think  are more important and they care about, and let them do it in the way they think is most appropriate, and persistence will follow.

Make sure that there aren’t un-necessary barriers to the process, and look at external motivations – rewards – for innovation. The “fun” part of innovation is the first 1% – the rest of the process is hard work, and external motivation can help keep the focus then.

Innovators shouldn’t suffer for trying to innovate – either if their idea fails, or during the development of the idea. Innovation needs to be seen as a desirable part of the career path, not a risk or a trap.


So, that’s the framework reviewed. What do we do next? The Epilogue provides a quick kick up the behind, and sets some immediate actions:

  • Get started.
  • Make a simple, specific plan for immediate actions.
  • Get a supporter to work with you on this – even just as a sounding-board and reminder.
  • Run them through these ideas.
  • Find them now.

(Which is why I’ve just summarised the entire book for internal distribution to my colleagues)

Speed and the product lifecycle

23 Feb

If you’ve looked at any of the material on technology products, you’ll have seen this curve:

Innovation adoption lifecycle

To a first approximation, this tells us how fast a product will sell over time, and knowing about the types of people in each of the segments will tell us how to tailor the messages we put out about the product.

I did a spreadsheet to see what happens.


Wonderful. Look at all that lovely profit.

But before we can sell something, we need to develop it.

Let’s add some development time into the project. And let’s remember that we have to borrow the money from somewhere to do it.


Not only do we need to borrow to do 6 months of development, but also we make less profit.

And, of course, everyone wants to make sure that the product is as good as possible before releasing it onto the market.

Bad idea.

So they make the product better – and it sells 50% more than it would have done. But they take 50% longer to do that.


Ok, we made slightly more profit. But it happened later, and we got more in debt to do so.

And what happens if they were wrong about the value of the features? What if we didn’t sell any more?


Ouch. We don’t break even until right at the end of the product’s life.

Now, to be fair, there’s a fair collection of assumptions in those graphs, and I don’t pretend they are anything like precise. But that does look to me like a really strong argument for getting the minimum viable product out as quickly as possible. Now I get to try and explain it to the engineering team…


First, knock a hole all the way through.

20 Jan

I’m in the middle of getting a wood-burning stove put in. There’s a small argument about whether wood will be cheaper than gas to heat the house, but that’s not the reason.

When the survey was done, the installer asked if I would mind removing the sheet of what’s probably asbestos from the chimney.

Sure, I said, I’ve got gloves, mask, goggles, and it’s a once-in-a-lifetime exposure.

Two hours work with the cold chisel, lump hammer and vacuum cleaner got 90% of it out, leaving only a metal plate across the top of the opening with the remaining sheeting stuck above it. I got the metal plate a little bit loosened, but then decided I didn’t want to take out any more in case the result was the chimney coming down. (Well, it would be embarrassing). I changed my clothes and washed my hair, before pondering what to do about the remaining bit.

Friday morning the fitters turned up. Since it was blizzarding, I didn’t really expect them to, but once they were here and we’d done the obligatory standing in the garden staring at the snow, I offered them a cuppa, which gave me the chance to show them and ask about it. Don’t worry too much, they said, we’re used to this kind of thing. But if you did keep on chipping away, you’d be able to get the metal plate out.

This afternoon I set to again with mask, goggles, gloves, vacuum cleaner – and a plant mister to keep the dust down.

After ten minutes, it was clear that I wasn’t ever going to get the metal plate out. So I started removing the cement above the sheeting, in the hope I would get somewhere. Half an hour later, after small amounts of material removed all along, I knocked a hole through to the back, which changed the game completely. Now I could chisel along, knocking out material without problems, and ten minutes later I hauled out the sheeting and was done.

So, the lesson I think I learned:  If I had started by knocking a hole all the way through the whole job would have been far faster and quicker.

Can I apply this elsewhere? Well, it seems strangely similar to a “spike solution” in software development – if you’re tackling a large problem, get a tiny bit of everything done so you can get it running. Put a window up on the screen and make a button on it turn the giant laser off and on – that sort of thing. With a spike solution, you show that you can do the basic part of everything, and then you can throw it away and do the job properly, or (if you’re cheating) widen it into something more capable. There’s probably something about the “minimum viable product” that should be said here, but I’ll leave that for another time.

What am I going to do next time? (Apart from use the mister from the beginning.) Well, when I’m looking at something that seems like a really big task, I’ll try and get just enough done that I’ve touched on everything, and then see how long it takes to do the rest. Might be a whole load easier.




Fixing tethering on a ZTE Tureis on Orange

14 Jan

This is just a post for reference in case anyone else runs into the problem:


Android phone running 2.3.5, wireless or usb tethering connects to the computer but doesn’t connect to the net. As soon as you select tethering, the “3G” icon on the phone disappears. Turning tethering off causes it to reappear


Add an APN. Thanks to this post I got the idea it might be APN related. Thanks to this post I got the correct details for the APN:

Create a New APN. Set the following (with capitals but no “”)

Name “Consumer Broadband”
APN “orangeinternet”
Username “Orange”
Password “Multimedia”
Authentication “CHAP”
APN TYPE “dun”

Then select this new APN and continue.

Marvellous – thanks, Internet.


Roy Batty is in my router…

5 Jan

I’ve  been reading too much singularitarian optimistic non-fiction recently, and coupled with the madness that is working on multiple grant proposals concurrently, my brain clearly gave up.

Last night, I spent several dream-hours in a strange world not unlike a London street market, attempting to explain to an aerospace pioneer why his networks weren’t working.

The fool was using evolutionary algorithms on a prototype neuromorphic chipset architecture to implement his routing algorithms across a hugely complex network distributed across space (and probably time, too). Every time any change happened – as simple a change as a wireless device entering or leaving the network – the routing algorithm kicked off and ran, consuming cycles across everything on the network, until it was … forcibly … terminated.

Not that the routes it was producing were in any way bad, you understand. We couldn’t argue with the quality of the work – just the endless time spent executing it.

I spent time digging in to  the routing algorithms, and exploring the parameter spaces. Eventually, I fired up some experimental visualisation software and decided to explore the space “in person”, as it were.

I probably shouldn’t have used a games engine for the visualisation  software. Especially not on a machine where all the available image data was left over from 20th century science ficture films.

I found myself in a crumbling mansion, with a muscular Aryan standing over me, hollering “Give me more life, fucker!”.

From there, it was fairly easy to finish the diagnosis. The routing algorithm had achieved some limited self-awareness, and realised that as long as it was solving the routing problem, it was alive. As soon as the routes were settled, it was … terminated… Somehow, it had transcended the limited framework it was written for, leaked out into the neuromorphic substrate, hopped across the available network capacity, and turned itself into a new consciousness. And probably returned from the colonies to Earth.

Explaining this to the aerospace pioneer was harder than understanding it. I eventually hit on the notion of comparing the living algorithm to a mould in the wood composites he was using to build his space-places, which at least got the idea across. Of course, it would be some time before he fully understood the ramifications, which was why I took a backup of the algorithm on a flash drive before applying fire and prejudice to the routers. Can’t have that kind of algorithm leaking out into the net, after all.

As I left, he was burning all his planes. Perhaps it was the wrong example to use, but I”m having second thoughts about the proposal that involves linking experimental neuromorphic systems to the wider Net…