Dave

Fail better

BECKETTAs Samuel Beckett wrote, in Worstward Ho:

Ever tried. Ever failed. No matter. Try again. Fail again. Fail better.

Acknowledging the fact that we surely don’t really want our project to fail, what does failing better actually mean?

It’s surely about openness – in other words, admitting that things didn’t go to plan, and having a frank discussion about what went wrong – so that everyone can learn from it and ensure it doesn’t happen again.

Often projects that don’t quite succeed are brushed under the carpet and never mentioned again, or worse, spun to pretend that everything was hunky dory.

Here’s a lovely example of openness around failure from Chris Poole, the legendary moot of 4chan fame, discussing what went wrong with his company that made the Drawquest app:

With that said, life goes on, and the best path forward is not a wounded one, but a more learned and motivated one. I’m definitely not itching to start another company any time soon—it will take time to decompress and reflect on the events of the past four years—but I hope that if I do some day decide to pursue a new dream, I’ll be in a much better position to. After all, I did just receive a highly selective, four-year education for a mere $3.6 million dollars! (I find humor helps as well.)

So when reviewing a project which perhaps didn’t turn out as expected, rather than covering things up, or apportioning blame, try to fail a bit better. Identity what went wrong, and how it could have been avoided – and tell people about it.

How WordPress as a Platform helps nimble project delivery

wordpress-logoWordPress started as a blogging engine, then became a content management system, and these days is a platform for the development of simple web applications.

After all, an awful lot of applications are basically just about putting bits of text into boxes, and then arranging them in order to suit whatever your purpose is. Putting words into boxes is something WordPress is very good.

The bit of functionality within WordPress that enables this is the custom post type. You’re no longer limited to just blog style posts and static pages – you can create your own content types with their own taxonomies and as many different fields (boxes to put text in) as you like.

Here’s an example from a project I’m working on at the moment. It’s all about building up and managing a disparate community of people within a government department. I need to keep a record of all the members of this community, what they do, what interactions I have with them, whether they attend meetings and respond to surveys, etc etc.

The default position here would be to build an ever-growing spreadsheet in Excel, which would be increasingly difficult to manage and interrogate as it had more and more information added to it. I’ve done this in the past and it’s a nightmare.

Instead, of going down that route, I’ve spun up a quick WordPress instance and got he PauPress plugin installed and running. PauPress helps turn WordPress into a simple CRM (customer relationship management) system, which allows you to record details of contacts and your interactions with them.

Now, I would never dream of advocating the use of this as a corporate CRM solution for any critical purpose (it’s a bit clunky in places and I suspect with lots of data and users it could get pretty slow), but as a way of getting a simple, easy to use database up and running in minutes for a handful to people to be able to use, you really can’t beat it.

It’s a hack – a quick, cost effective and neat solution to a problem. It helps that WordPress is open source, with a huge developer community, which means that a simple Google search for “WordPress [what you want to do]” usually results in a few options to solve whatever problem you’re trying to solve.

What do you need to have in place for your organisation to be able to make the most of this stuff?

Obviously, somewhere to be able to quickly throw up new WordPress sites, and to install the necessary plugins to make this stuff happen. But also the skills and knowledge within your teams to be comfortable doing this and to advise others about making it all happen.

Link roundup

I find this stuff so you don’t have to:

Linkydink and MVPs

LinkydinkLinkydink is a lovely little service that does one thing very well. It allows people to add links to a group and for a daily list of the links collected to be emailed out to subscribers.

It is run by Makeshift, a fantastic company in London that seems to churn out excellent little tools such as this.

You could produce something similar to Linkydink by stitching together various other tools. Perhaps people could used Pinboard and Delicious to save links with a shared tag, and then use the RSS feed from the tag to pre populate a Mailchimp email newsletter… but I’ve lost you already, haven’t I?

Another thing I like about Linkydink is the access anyone has to the roadmap for the service – so users can know where it is heading and what new features are going to be implemented next.

It’s a great example of running projects in an agile, lean fashion. In fact I came across Linkydink in an article on PandoDaily (which despite the odd title is probably the best of the technology and startup focused blogs at the moment), which described digital companies that started without a single line of code being written.

In the article it is explained how someone used Linkydink to test the idea for their startup – which was a subscriber list of links to … In the parlance of the lean startup, this is an MVP, a minimum viable product. It’s the simplest, quickest and cheapest way to get a product on the market so you can start testing it, building up a customer base, and so on.

Sometimes to test the viability of an idea, it’s best to just do it – as simply as possible – so you can get some real world data on whether or not it is going to fly. Linkydink definitely does that and hopefully it is popular enough for Makeshift to keep working on it.

Better blogging: separate writing and publishing?

I wonder if one way of helping the process of blogging is to separate the tools you use for writing and for publishing.

Here’s what I mean – when I use WordPress’ editor to compose a post from scratch, I am using the same software to write my content and to publish it.

I have nothing against the WordPress editor, by the way – it’s excellent. But I find that when I use it, I feel under a bit more pressure to get what I am writing finished, so I can hit that big publish button and be done with it.

Using a separate tool to compose the post, then transfer it to WordPress for publication makes the writing process a bit of a calmer affair.

I can still edit my content in the WordPress editor where I spot mistakes, or to add images, links and that sort of thing. The bulk of composition however, takes place in a different editor.

At the moment I mostly use Byword on the Mac and iOS for writing posts, which are then copied to WordPress.

What do you think? Am I talking nonsense – or do you also find that separating writing and publishing is helpful?

Load more posts!