ia play

My basic librarian-ness is always a bit shocked by finding writing in books. But this is a bit different:

At first I suspected a personally prudish but meticulous scribbler. But there’s a more obvious explanation, of course. This book was used to record a Talking Book, a structured audio book that blind and partially sighted readers use.

Talking Books are recorded in DAISY format, a XML based markup language.

“A DAISY book is a digital audio book, designed to allow you to move around the text as efficiently and flexibly as a print user. You can:

• make bookmarks
• pause books
• speed up or slow down
• read or ignore footnotes
• jump easily from chapter to chapter, heading to heading and page to page.”

Daisy 3 Structure Guidelines, for those that like this sort of thing.

I’ve started work on a project for RNIB Rushton School and Children’s Home.

Rushton provides education, residential care, and therapies  for young people with sight loss, multiple disabilities and complex health needs.

I’m capturing requirements for an information system for the school and home.

Some of the constraints (like complying with the Care Act 2000 and OFSTED inspections) are rather less negiotiable than is usual on my typical IT projects.

And for many of the staff, their daily lives do not revolve around a desk and computer.

It’s interesting stuff and I’m looking forward to getting to know more about how Rushton works (even if that does mean a lot more travel to Coventry!)

Right then. Back to the blog.

Since we spoke last,  I have:

Given up my FUMSI editor job. Finished off my Open Uni Certificate in Contemporary Science. Passed the Requirements Engineering exam. Got an allotment and an extra chicken. Made croissants.

I’m particularly pleased with the croissants.

Asking about a typical day is always an interesting question to ask in job interviews. All sorts of stuff gets chucked in job descriptions but there’s often no indication of whether that tasks represents something you’ll need to do every day or once a year.

A fairly typical day for me recently went something like this:

9am

Attend our ‘Knowledge cafe’ . This is an informal weekly meeting in a coffee shop with the project managers, business analysts, and knowledge managers. There’s no agenda, just a chance to recharge, share stresses and pass bits of information around. Nice, social and deeply useful.

10am

The rest of the morning is spent doing research, analytics, thinking etc. I might be buried in Google Analytics, auditing competitors, reading up on the technology or messing around with index cards, big bits of paper and a lot of furious hair twirling.

1pm

Meeting with content owners. Listening to them and their experiences/knowledge. Sharing IA insights. I used to find these depressingly familiar battles but I’ve tried to reposition them in my head. I’m not going to learn about IA in these meetings but that doesn’t mean there’s nothing to learn about. Showing interest in the subject matter has actually helped make these meetings happier places.

3pm

Travelling to suppliers. They’re not too far but other days can involve lengthy treks to other offices.

3.30pm

Developers at the suppliers demo us the last few weeks work. We plan the next two weeks, flesh out user stories. The PM is usually there, often the web manager and accessibility consultant too.

The battle here can be to keep the focus on the important stuff. Making sure we’re working on simple, high value stuff rather than stuffing it full of bells and whistles. Suppliers generally just want to keep client happy, with the least effort. Mostly we have to be the voice of the user here, although occasionally the developers will argue than something isn’t user friendly (especially if it is complicated to develop).

5.30

Go home

The big shock for me, coming from a huge UX team at the BBC is there’s no designers involved, UX or otherwise. Visual design was outsourced, the details will be handled by the client side developer. Functional design and usability is the combined responsibility of me, web editors, business analysts and the accessibility consultants.

I produce very little documentation or deliverables.  Maybe a sitemap and some sketches for the content authors to think about. Some mock-ups to talk around, once we know what the site will look like. Mostly I think then talk.

Sometimes I”ll do whole days of each activity. Sit at home doing in-depth research, have all-day content workshops or be all-day on site with the developers. But more often than not days are mixed up like this. Makes me think of the polar bear venn diagram.

Related posts:

• IA deliverables
• The manager’s schedule and the maker’s schedule

Last week I went to the Search Solutions event, held by BCS in their lovely office in Southampton Street. There were maybe 50 people, 6 or 7 women and seemingly even less laptops (which rather made it stand out from the more web-focused events I usually attend – because of lack of laptops not the male-female ratio).

I didn’t make masses of notes but I did capture a few points and reminders:

Vivian Lin Dufour from Yahoo talked about Search Pad, an attempt to make search more “stateful”.

Richard Russell from Google explained how the auctions for Google Ads work. Always interesting to hear more about the money side of things.

Dave Mountain, a geographer (another example of Nominative Determinism?) talked about geographical aspects of searching. He explained that if the task is “finding the nearest cafe”, then the ‘near’ isn’t a simple statement. There are types of near: as the crow flies, in travel time, in the direction I’m already going. After all you may not be interested in a cafe that’s already 5 miles behind you on the motorway. He had some good slides covering this, so hopefully they’ll be made available.

Tony Russell-Rose discussed Endeca’s impending pattern library. Should be interesting – public version to be available in the new year.

David White of Web Optimiser talked amongst other things about the importance of cross-media optimisation. He asked why don’t more companies, especially b2b ones, have phone numbers in title/description of search results? He also touched on the growth of twitter as a substantial source of referrals (in response to a question about whether Bing was increasing referrals and thus changing optimisation tactics).

Richard Boulton, as well as discussing his efforts with open source search, introduced us to the marvelous concept of dev/fort/.

“Imagine a place of no distractions, no IM, no Twitter — in fact, no internet. Within, a group of a dozen or more developers, designers, thinkers and doers. And a lot of a food.

Now imagine that place is a fort.”

Well marvellous to me but I wanted to get married in a Napoleonic fort so perhaps I’m not typical. He also mentioned searchevent.org, a day dedicated to open source search systems, which will hopefully happen again sometime.

Andrew Maisey talked about a school of thought that search will increasingly become less important on the site. Dynamic user journeys will encourage more browsing.

(Food was pretty good as usual for the venue.  I’m hoping that we’re going back to BCS for our team away-day later in the year and then I can have more of the strawberry tarts.)

I’ve been reading extracts of Shop Class as Soulcraft: An Inquiry Into the Value of Work by Matthew B. Crawford. Crawford has a PhD in Political Philosophy, once worked writing abstracts for an academic journal service and now runs a motorcycle repair shop. His book, which began as an article in the New Atlantis, champions the virtues of using your hands to make and repair things.

He tells some fairly depressing tales of cubicle life:

“The quota demanded, then, not just dumbing down but also a bit of moral re-education, the opposite of the kind that occurs in the heedful absorption of mechanical work. I had to suppress my sense of responsibility to the article itself, and to others — to the author, to begin with, as well as to the hapless users of the database, who might naïvely suppose that my abstract reflected the author’s work. Such detachment was made easy by the fact there was no immediate consequence for me; I could write any nonsense whatever….

A good job requires a field of action where you can put your best capacities to work and see an effect in the world. Academic credentials do not guarantee this…

The good life comes in a variety of forms.”

via The Case for Working With Your Hands – NYTimes.com.

I’m going to “Innovations in Web and Enterprise Search” at BCS next week

Search Solutions is a special one-day event dedicated to the latest innovations in web and enterprise search. In contrast to other major industry events, Search Solutions aims to be highly interactive and collegial, with attendance limited to 60-80 delegates.

Provisional programme

09:30 – 10:00 Registration and coffee

Session 1: (Chair: Tony Russell-Rose)

* 10:00 Introduction – Alan Pollard, BCS President

* 10:10 “Enterprising Search” – Mike Taylor, Microsoft

* 10:35 Accessing Digital Memory: Yahoo! Search Pad – Vivian Lin Dufour, Yahoo

* 11:00 “How Google Ads Work” – Richard Russell, Google

11:25 – 11:45 COFFEE BREAK

Session 2: (Chair: Andy MacFarlane)

* 11:45 “Location-based services: Positioning, Geocontent and Location-aware Applications” – Dave Mountain, Placr

* 12:10 “Librarians, metadata, and search” – Alan Oliver, Ex Libris

* 12:35 “UI Design Patterns for Search & Information Discovery”- Tony Russell-Rose, Endeca

13:00 – 14:15 LUNCH

Session 3: (Chair: Leif Azzopardi)

* 14:15 “Search-Based Applications: the Maturation of Search” – Greg Grefenstette, Exalead

* 14:40 “How and why you need to calculate the true value of page 1 natural search engine positions” – Gary Jennings, WebOptimiser

* 15:05 “Search as a service with Xapian” – Richard Boulton, Lemur Consulting

15:30 – 16:00 TEA BREAK

Session 4: (Chair: Alex Bailey)

* 16:00 “The Benefits of Taxonomy in Content Management”, Andrew Maisey, Unified Solutions

* 16:25 Panel: “Interactive Information Retrieval” – details to follow

17:00 – 19:00 DRINKS RECEPTION

via BCS IRSG – Search Solutions 2009.

As Martin has picked my local The Harrison for the next London IA gathering, and moved it so it doesn’t clash with the Linked Data meeting … I might actually get to an IA in the Pub meeting.

In fact, I’ll probably be the first one there.

London IA in the Pub – London IA.

One of the things about being the only IA/UX/ID type in the building is I tend to work on a lot more things at once than I did at the BBC. As well as the e-commerce project and trying to get the new website live, I’m also working on (to varying extents)

• shared drive folder structure
• replacing various ‘company’ directories
• investigating care management systems
• a new library system
• thinking about the next phase of intranet/teamsite development
• supposedly a reference data management strategy, although I keep having to postpone this

In the old days job titles were created by grabbing a bit of Latin/Greek and adding ‘er’ or ‘or’ to it. The suffix just means “one who does”.

Something of the bits of Latin /Greek are obvious, some not:

Carpenter=wagons, Cooper=vats, Plumber=lead, Lawyer=law, Miner=digging, Baker=roasting, Butcher=slaughtering goats, Doctor=teaching, Teacher=also teaching, Farmer=collecting tax/rent, Soldier=being paid, Tinker=jingles, Tailor=cuts, Dyer= dark/secrets

Vicar interestingly just means substitute or deputy.

And who slaughtered anything that wasn’t a goat? (I’m putting the etymological dictionary away now).

It seems for a modern job title that a single word is not enough. You need a combination of object and activity.

Possible objects in my professional sphere:

project/programme
product
business
content
user experience
customer experience
usability
interaction
systems
software
applications
development
technical
information
accessibility
search
web
digital
online
intranet
e-commerce
sharepoint

Posssible activities:

manager
analyst
architect
designer
producer
engineer

Some people seem to feel hemmed in by the activities bit and choose something vaguer. This usually implies they will only produce opinions not things e.g.

consultant
expert
specialist
professional

In the public and non-profit sector you also get ‘officer’ as in police officer but also projects officer or knowledge officer. This usually just means one who holds an office and seems to be a way of avoiding saying ‘man’. “Head of” is similar but usually at the opposite end of the hierarchy.

All combinations of object and activity are plausible and many are common. Although so far I only know one Usability and experience design oompa-loompa.