Archive for the ‘Doing Business in Public’ Category

Lessons from Toyota

Andy Parkhouse - February 10th, 2010

Toyota has problems. Eight Million problems. It’s interesting that this has attracted so much attention from mainstream quality media such as the Today programme. My own interest in Toyota – of which some of you are well aware – is driven by their principles and product development techniques, which are fascinating, and provide some of the foundations for currently ‘buzzy’ things like agile software development.

For those who not excited by Toyota, product development or agile software techniques, here’s a cookie for reading this far! Meanwhile, for those who like products, principles, and how the mighty fall, more after this graphical interlude…

Toyota Land Cruiser

So this post offers thumbnails on two topics: (1) why look at Toyota if you’re running an ad agency, digital agency or web app company. (2) what went wrong.

Why Toyota?

I became aware of Toyota principles when we started developing the Viral Ad Network. One of Toyota’s key principles is to control inventory – whatever that inventory might be, you don’t want too much of it piling up around you, the aim is to have just enough while never running out.

‘Inventory’ is a key feature of the Ad Network – in this case ‘inventory’ means space on publisher websites where ads can be displayed. Managing inventory is right at the heart of the network. Too much and space goes unsold (bad for publishers and us), too little and we can’t meet the promises we’ve made to clients. More on how we do this another time.

Way beyond inventory

A little light reading gave me a much more in depth understanding of what Toyota and similar Japanese companies have been doing, where their techniques came from (common sense, rigourously applied), and how they’ve surfaced in lean techniques and agile software development methods. Given that we’re advocates of agile techniques like Scrum and Kanban, it’s seems that we’d have run across the Toyota methods eventually somehow.

…but for agencies and web app startups?

Toyota – and similar lean companies have a bunch of stuff you can use:

  • Principles to run a business by – that put people first
  • Build in quality, don’t rely on fixing it later (film knows this – bad shots *cannot* be “fixed in post”)
  • Get stuff done

There’s way more, but this story about Amazon’s Jeff Bezos sums it up: “stop cleaning and spend your time eliminating the source of dirt”.

So how do the mighty fall?

Toyota’s aim was to be the biggest carmaker in the world. They achieved that a couple of years ago. They got there with a fearsome reputation for quality, customer service, and a certain kind of innovation (excellent engineering, but rarely exciting).

Problems at Toyota have been kicking around for some time. Last year, Toyota’s president went public on his concerns for the company.

Four connected pitfalls (I’m guessing!)

I think Toyota got smacked down by these four nasties. They’re all connected:

  • Infallible fallacy
  • Engineering is difficult
  • Success can kill
  • Dissipation

When you believe that you have the best quality, it’s hard to accept you don’t. You know that you have a system for quality, so there can’t be a problem, right? “We’re infallible” <- Fallacy.

Meanwhile, engineering is difficult. Toyota initially traced many of the accelerator problems to slipping floor mats. With this pegged as ‘the problem’, it takes time to identify that there’s actually a secondary problem with the accelerator pedal. So engineering is difficult. Anyone think a similar thing might apply with clients and customers for agencies and web apps?

Success can kill. Nothing or more less than hubris – a fine dramatic staple. Toyota achieved their goal. Hubris makes you think you’re invincible, infallible, it makes you over-expand, and bank on a certain future, but the future is not certain, and you’re not in control of it. Lean attitudes are born in the cash-strapped start up, or the nation desperately trying to win a war. Hubris is the antithesis of this, it makes you fat, arrogant and lazy, and expectant of easy success. It’s a short step from there to…”you’re dead”.

People love a goal. They like a win, an achievement. Toyota hit their goal – become the biggest – and despite being renowned planners (do you have a one hundred year plan? I don’t – they do) – they don’t seem to have lined up much else in the way of goals. They’ve expanded globally and stretched their capability dangerously. Meanwhile the car market has moved on around them. Most carmakers ‘do quality’ now. Toyotas are not appealing beyond their loyal audience. Suddenly everyone wants their lunch, they are in ten places at once, and they have no clear win in mind. Dissipation.

I don’t need to draw a diagram: there are lessons above for any of us.

Say “sorry”

Toyota: say sorry. You probably will. You should. Not just because it’s in ‘your’ character, but because it’s the right thing to do.

Too many brands aren’t brave enough to say sorry. They should get braver.

If you want to talk about lean, agile, or how brands can ’sorry’ (or ‘thanks’, or ‘how nice to meet you’): andy@teamrubber.com or 0845 680 0575. Meanwhile, it’s nice to finish on a picture :)
Toyota Land Cruiser

Andy joined Twitter

Andy Parkhouse - February 4th, 2010

Short and sweet: http://twitter.com/andyfacts

We’re making Opinion Suite join up with Linked Data (through RDFa)

Andy Parkhouse - January 29th, 2010

With so much chat and buzz at the moment (and rightly so) about Tim Berners-Lee et al’s data.gov.uk, I thought it’d be timely to say a bit about how we’ll be doing our bit towards publishing online consultation information as Linked Data (Steph Gray has recently blogged on a similar subject).

We’ve built (and are continuing to iteratively improve) Opinion Suite, an open-source online consultation management and creation system designed primarily for local authorities and other governing bodies.  It’s currently being used by Bristol City Council, Sutton Borough Council and a large partnership led by Cumbria County Council, with more rollouts hopefully coming soon.

Through Opinion Suite, organisations can store, organise and publish details of all their consultations – hopefully, exactly the kind of information that it’d be really useful to be able to access from a variety of sources, to include in apps and to run analyses/queries on.

As you probably know, that’s what Linked Data is designed to facilitate; it’s a way of marking up web pages semantically so that software (like browsers, search spiders etc) can understand more about the content and so that it’s easier for citizens to ‘cut and combine’ the information in ways that are relevant to them.  The Government’s into it in a big way: all central government consultations need to include this markup as of the start of 2010 and DirectGov already uses it to pull consultation details into its listings.

We’re currently making a few changes to the code of Opinion Suite so that all consultation details entered using the system are marked up as Linked Data – using RDFa, to be precise.  This means that all consultations inputted into Opinion Suite will include this additional metadata, making the information therein more readily and widely available.  So, for example, DirectGov could pick up all of a local authority’s consultation details and pull them directly into the ‘local consultations’ part of their site, or someone could make an app to compare consultation activity with other data, such as population or earnings surveys.  That’s a lot of potential added value for something that’s really not that hard to do – and it won’t affect the appearance or user experience of Opinion Suite for end users or administrators as the data will be taken from existing fields.

It might also be worth mentioning that this is in addition to the existing RSS functionality built into Opinion Suite – for example, you can create an RSS feed from any search query in Consultation Finder, meaning you can take the content and embed it into a blog or community website.

Basically, we like sharing and we like making the most of data – so we reckon RDFa’s a good thing all round and an easy win in many ways.

Why do people completely ignore Security?

Tim Wintle - January 27th, 2010

When it comes to security, I’m often shocked by how much people are won over by a little social engineering – but I was even more shocked this morning.

Here are some regular examples of things we routinely see people do – all of which are potentially highly dangerous, and could easily lead to an attacker stealing your bank details, work information, or your entire computer:

  • Open files attached to emails (.swf, .pdf, .doc, .wmv, .sh to name a few) We all know never to open a file we’ve been sent unless the email has been digitally signed right? But how many people actually sign their emails?
  • Embedding content from another domain into your website (pulling a .swf, .js, .class, or even .gif file from another domain can give the other website owner control over what happens on your site)
  • Emailing log-in details. (emails are sent as plain text – if either of you are on wireless, then anyone within 100 meters or so of you can see exactly what’s been sent with some very basic tools)

But what I saw today was even more shocking (to me) – I was invited to join a facebook group, ostensibly to help find a couple who lost thier camera (there’s no reason to suppose that’s not actually what the group is doing, so feel free to go ahead and join).

When I looked at the page, it has this message:

TO MASS INVITE
1)Click "Invite people to join"
2)Delete all the text in your address bar and replace it with the following
javascript:elms=document.getElementById('friends').getElementsByTagName('li');
for(var fid in elms){if(typeof elms[fid] === 'object'){fs.click(elms[fid]);}}
Then hit enter

In fact, looking at the code, that does look like it does what it says on the tin, so nothing dangerous – “what’s the big deal” you might ask?

Well that message is asking you to paste executable source code into your browser, which will run the code as if it was code trusted by facebook

i.e. whatever code you paste into your browser window, can do whatever it wants to do with your facebook account – and I suspect very very few of the people who followed the instructions actually understood exactly what the code was going to do – although I know for a fact that a lot of people did follow the instructions.

So that’s another one to add to the list – Never copy and paste anything into your browser that doesn’t begin with http: or https:

Team Rubber defeats the (mostly) undefeatable

Alex Pitkin - December 18th, 2009

Yes.
Team Rubber 1, Brucey "win all the time" Boys 0
It did happen.
We won. In the match that I introduced in my last post, we turned up and we scored a goal and didn’t concede any. Now that’s winning. We’re now joint second in the league and on good form so we should win the league, definitely.

Team Rubber in second place, still.

Team Rubber in second place, still.


Ok, so we lost last week but we played well and it was unfair, in a totally-within-all-rules-but-really-annoying way.
A special mention for Tom’s quality left-footed strike should be made, and there it just was.

Multiple python versions – collective.buildbot

Tim Wintle - December 7th, 2009

One of the applications I work on recently dropped support for python 2.4 – and much to my surprise I found out buildbot was failing – despite the instructions to use the 2.5 interpreter.

We had the following code as part of the a collective.buildout:project configuration:


build-sequence =
          python2.5 bootstrap.py
          ./bin/buildout -t 50
test-sequence =
          python2.5 bin/tests -v --v

But looking at the logs, this was being re-written to use “python” (i.e. the version the buildslave was running on) during the buildout.

I guess I could have created separate buildouts for 2.5 /2.6 buildslaves for these projects – but having one buildbot buildout is just simpler.

I found that calling python by it’s full path in the configuration has avoided this issue – although it does mean maintaining different project sections for different python versions.

i.e.


build-sequence =
          /usr/local/bin/python2.5 bootstrap.py
          ./bin/buildout -t 50
test-sequence =
          /usr/local/bin/python2.5 bin/tests -v --v

Teaching people to argue around the world

Chris Quigley - December 5th, 2009

I always find it really fun to watch the new arguments and debates flowing through the aMap website on a daily basis.  Some days we get 1 or 2, and on other days 50+

One of the biggest drivers of traffic at the moment seems to be from schools – and especially schools in the US.  At the same time as people make arguments online, they’re also buying our series of pocket argument guides – with one school in Florida buying 50 the other day!

So to help these teachers, I’m really trying to build up the educational resource section of the aMap site – and have just created a critical thinking exercise for use in Critical thinking a-level classes.

The Critical thinking worksheet is designed to work alongside our aMap argument guide range, so hopefully as well as being useful in the classroom it will also encourage teachers to buy at the same time!

Browser usage stats – Windows 7

Tim Wintle - December 2nd, 2009

I’ve just released our browser statistics for 2009 over on the viral ad network blog – but I thought I’d cross-post this here.

I found this chart quite amazing – it seems that users on Windows 7 have chosen Firefox over Internet Explorer.

Are we only seeing statistics for technical users of Windows 7 (i.e. those who upgraded early)? I don’t know – but here’s the chart:

windows 7 web browser share 2009 Browser usage stats   Windows 7

windows-7-web-browser-share-2009

(more stats are here)

Being Open = Win (Nearly Always)

Andy Parkhouse - November 24th, 2009

I liked this post from Matthias Marschall: Open Communication Stops De-Motivating your Team

We always try to be as open as possible for the reasons outlined in the post, which boil down to “it’s just better”. Hopefully that’s obvious. As Matthias says, if we’re all aware and informed, we trust each other more and we can be braver. If we hide things, the result is unease, rumour and lack of trust.

Much the same applies to our relationships with clients: we’ve seen time and again that clients value and respond to honesty, openness and frank advice. For us this is a default position: it’s in the company’s DNA. Tell a good story: yes; hoodwink and deceive people: no thanks.

Should we be totally open on everything? No. Sometimes we’re dealing with information that an employee or client needs to keep confidential for sound reasons. So we have to make judgement calls, not a blanket rule. Rule of thumb: always be open, except when it will do more harm than good. We’re here to do good :)

More Cycling promotion from the man

Alex Pitkin - October 28th, 2009
Storing, changing, buying, repairing and inspiring

Storing, changing, buying, repairing and inspiring

I just noticed on the Guardian site that the Government has recently launched a new cycling incentive on top of their already successful (at Team Rubber anyway) Cyclescheme tax saving initiative.

What they seem to be doing is not to offer any more savings on buying a bike – this will remain the same – but offering more support and kudos for companies to actually provide the infrastructure required to allows employees to cycle to work everyday. They are segmenting this infrastructure into 5 main areas:

  • Storing
  • Changing
  • Buying
  • Repairing
  • Inspiring

You can read all about all of these on the Cycle to Work Guarantee site.

Now while these are all great words that would make any type of travel a more successful experience, what I am personally interested in is the ‘Inspiring’ bit.

This is the part that I find the most difficult and have put the most effort into in getting people out of cars and onto bikes. You can read what they’re proposing on the site and all I should really say is good luck!