One of my main precepts is never to read a book with a colon in the title. They are usually academic or business tracts, too often written in dry language, and tend not to make good bedtime reading, except to fall asleep to. And then you wake up on top of it, pages all creased.
I'll make an exception for England's Historic Waterways: A working heritage. It's a slim, pretty, photo-heavy booklet jointly created by British Waterways and English Heritage, and aimed at people such as property developers eyeing up vacant canalside development sites.
I think the booklet's trying to give them a crash course in why waterside development has a distinctly different set of considerations from your conventional brownfield or inner city site. It particularly stresses the 'heritage' aspect, and how any development needs to fit in with various types of waterways user.
I doubt it'll be bedtime reading for most developers, but you can't say they haven't been told, even though they might not pay attention.
It's not until page 17, in the 'Use and activity' section, that you get the money shot, a paragraph headlined 'Balancing competing needs':
Canals and rivers conjure up images of boats. British Waterways licenses over 32,000 boats across England, Scotland and Wales. Often brightly coloured, these craft differentiate our canals and rivers from other water spaces and are the reason that many towpath visitors come back time and again. The requirements of boaters must therefore be integral to any development proposals.
(The bold above is my emphasis, but I wish BW had emboldened it.)
It was launched at a 'breakfast debate' last Thursday at London Zoo, headlined 'Bricks and water': debating the future of England's waterway past, where they said it was aimed at:
- Architects
- Developers
- Planning authorities
- Urban designers and master planners
- RDAs
- Heritage sector
I didn't know about the debate until I stumbled on it when searching for the download site for the PDF (it might have been buried in an attachment in a press release). I'd be interested to see a summary of the debate, and if any of the attendees came away with the fervour of a new glint in their eye. An edited podcast would be nice to hear.
The booklet's divided into several vaguely titled sections, including: A working heritage, Use and activity, Public realm, Waterspace and A sustainable environment.
Personally, I'd like to have seen a section - much larger than all the others - called 'Who uses the waterways?', defining the activities of each category. And I'd like to have seen it written in a much livelier style, more suited to bedtime reading. But what do I know about property development and developers?
One of my photos is used (with my blessing) in the Public realm section. It's the one that shows Castlefield Basin in Manchester (with a stack of iPhones in the background) taken at midnight on New Year's Eve 2007-8. The caption:
Robust natural stone copings and setts - archetypal 'canalscape' showing rich and appealing patina of age. Castlefield, Manchester.

I suppose we should be grateful that boats got a mention. But I think various 'spokes-stakeholders' - NABO, the Angling Trust, the Cyclists Touring Club, the Ramblers' Association, etc etc, should each have had a page or two to put their case. Developers ought to be reminded of which sort of people are likely to shake their heads in disbelief at any new development as they go past.
Still, BW are making the effort, and good for them. And good for English Heritage too.
The headline of this blog post is a nod to occasions (in the computer world) where Steve Ballmer - Chief Executive of Microsoft - goes wild on stage, shouting to stadiums-ful of programmers that Microsoft's success relies not just on the company itself, but the developers who create the programs that people can use on the those computers.
See some of these extraordinary clips here.
You can laugh at Steve Ballmer, but he's laughing too, and probably harder than you. I think what the waterways really needs is/are are a Chief Executive who can dance and shout DEVELOPERS! DEVELOPERS! DEVELOPERS! in public like Steve Ballmer.
The DEVELOPERS! might or might not do what you want, and of course they aren't the ultimate users, but you've got to inspire their interest in the first place before you can get something the users can actually use.
[PS: Originally in this post I hinted that I was disappointed at not getting a credit. Actually, looking back at my emails, I clearly asked the booklet compilers if they'd NOT give Granny Buttons a credit on the photo, since, as I said at the time, "...don't bother to acknowledge me. I think photos are much classier when they don't have acknowledgement." ]
Recent Comments