Skip to main content

It's not about the speed, it's about the skill

Recently, I was regaling my partner with exciting tales of what thrilling things I'd got up to at work that day, while he listened with eager attention. Well, actually, what he was doing was trying to go to sleep, and I was babbling at him about research problems, but...
I was explaining that I was frustrated that I was busy when a research enquiry that had come in, and that when I actually got a chance to do it, I found the answer within a few minutes. "I could have had that result back to the enquirer in minutes, rather than hours, and looked really efficient, since it was so straightforward to find." I was pouting.
"Yes, but your enquirer has no idea of the level of skill it took you to find that answer. They asked you because they didn't know how to find it, and you are the expert. Just because you could find it easily doesn't mean it would be as easy for anyone else. And answering too quickly could make it appear that it was an simpler task than it was. To them, and probably others, it wasn't an easy task: don't make the hard things too simple, because they're not." he mumbled, and rolled over.
You know, he's quite wise sometimes, that boy - the pressure to get things done and passed over to enquirers as soon as possible can make even the person doing the requested research work forget that the job they're doing is more skilled than you might expect. Just because you can do it easily, it doesn't mean others would.
 
And, it's not about how fast you can do it, but the skill you use to do it.

Comments

erin said…
So glad to know I'm not the only one who babbles to my (admittedly less than fascinated) partner about research problems!

Popular posts from this blog

Relaunching a library service

What do you do when you decide to do what is verging on library-based insanity, and basically scrap your current library service, and relaunch everything - physical layout, LMS, and classification system? In my case, spend a year, planning, developing, preparing….and then a frantic few weeks hauling stock!
The background to this apparent madness is this: when I took on this role I inherited a library using a layout that didn’t seem to make sense, a classification system I wasn’t familiar with, and an LMS that had been in place for 20 years but didn’t seem suited to our needs. As I was new to the library, a major part of the time I had available while settling in during my initial few months was dedicated to exploring how well these things were working, both for users, and library staff. I had the benefit of my colleague also being new to the library, only a few months after me, so together we looked at these issues with fresh eyes.We came to the following conclusions: The physical layou…

Too close to the problem to see the achievements

Sometimes, you have so much to do, that you can't see what you've actually done. I'm feeling very much that way at the moment, so I thought I'd make a public list for myself of all the work and professional things I've done since taking up my role in mid January. Then maybe I'll feel less like I'm just not very good at anything. It's worth a try. Although for obvious reasons, I can't publicly say much about the baddest/hardest stuff, but...it's in there. Maybe it's not explicit about how hard it's been, but it's there.

So: what have I done?


Service management and development

Replaced someone who ran the library for 21 years, who retired 3 months before I started, and gave me no handover information.Got 6 weeks of company/training on the library from an assistant, who then retired, leaving me as the only person in the organisation who knew anything about how the library actually worked.Done the assistant librarian and librarian job simu…

Impressive shelving technique

I have a new role model: the shelving technique demonstrated between 12 and 18 seconds by the librarian in this Lucozade video is something to aspire to! :D