Management
Are you starting something?
Jul 12th
I consider myself to be a chronic procrastinator. Left to my own devices I make “to do” lists, lists of “to do” lists, project plans, plans for project plans, lists of plans for plans of project plans; essentially, I’ll do anything but actually start working. I willfully make my life more difficult than it need be.
If I’d been a waiter in a 1920′s restaurant in Vienna I’m pretty sure I’d have been fired for going on about how there’ll be all sorts of amazing things in the future, but I might also have been observed by a student by the name of Bluma Zeigarnik.
Zeigarnik noticed that the waiters could remember perfectly the orders of their customers until they’d paid their bill, at which point the waiters instantly forgot all about the order. This effect, now known as the “Zeigarnik Effect”, states that we retain information about unfinished tasks far better than we do about completed ones. Further to that though, the paper in which Zeigarnik first wrote about the effect goes on to explain that our brain actively dislikes having unfinished tasks. The response to working on something that drives us to complete the task is all wrapped up in this effect – we try to clear our minds by finishing things so that we can forget about them.
But how does the Zeigarnik Effect apply to my inability to work properly? It’s quite straightforward. According to Professor Richard Wiseman in his book “59 Seconds”, the best way to overcome procrastination is to start a task. That sounds obvious. He goes further though – you don’t need to think that you’re going to sit down and complete the task. You don’t need to think you’ve got to work all day. So long as you can spend a few minutes on it that’ll be enough. Once the ball is rolling the Zeigarnik Effect will be enough to keep your mind on whatever you’re working on and pull you through to the other side.
I discovered the solution to the problem of procrastination in my last year of university. I started working on my final year project at the beginning of the first semester only because I had a free weekend when all my housemates were away. When I’d sat down to start I had no intention of working on the project for several months. The weekend would have been enough. But having that unfinished task drove me on to finish. All the while most of my fellow students were putting off starting theirs. Consequently, by the end of the year, I’d finished with plenty of time to spare while the rest of the group were pulling all-nighters to get their projects done. I realised that starting was the important bit. The rest comes naturally.
It was only very recently I discovered the reasoning behind the phenomenon (hence this blog post). I can heartily recommend it though if you’re like me – don’t sit down to work for hours. You won’t do anything productive. Sit down to work for a few minutes. That’s the way to get things finished.
Looking back.
Mar 30th
First and foremost, welcome to the new blog. Thank you for taking the time to read what I hope will build into a reasonably comprehensive archive of my thoughts about the future of the internet, and more specifically web site development.
I am Chris Neale. I was a web developer for a little over a decade before deciding to stop hacking code for a living and take on some other, more entertaining projects. In the main they’ve been quite successful so far. I’ve had a lot of fun over the past six months and I’ve no intention of heading back to an office any time soon unless the exactly right opportunity arises.
During my 10 and a bit years of developing reasonably advanced internet technologies I came to a number of conclusions about the problems that face clients and developers in the modern internet age. From starting out hand-coding HTML for a large university, through building all the usual guestbooks and contact forms for small business clients, and on to designing and developing online applications for well-funded start-ups dealing with millions of pounds of sales through e-commerce and call centres, I’ve seen the same issues over and over again. Without exception they come down to one of three things;
- A lack of understanding of the online world on the part of the client.
- A lack of understanding of business processes on the part of the web developer.
- A lack of communication between client and developer or client and customer.
They’re all entirely solvable issues. In fact, they’re trivial. With the right application of expertise on both sides, and proper communication between all parties there are no reasons why websites need roll out with the problems that they so often have.
Over the next month I am going to outline what I see as some of the more problematic issues that websites have, what can be done to solve them if they’re already in a website, and what can be done by everyone involved in website development to avoid them happening in the future. I hope you come back to read them.

