My favourite OS X Yosemite feature… yet to be

Posted by William Gallagher

It’s not fair to say this to you yet because I’m only tried it exactly once and exactly one minute ago. But it didn’t entirely work and I can’t see why, so I want to explore it. And also, frankly, tease you.

This is the feature and this is the bit that is working: I can now make phone calls from my Mac. It uses my iPhone but that’s the thing, it uses it, I don’t. Scroll through my Contacts list and click or right click on any phone number anywhere – in an email, on a website, in an OmniFocus task – and I can dial it from there. It may ring using my phone but you don’t care and I don’t notice: the sound comes out of my Mac’s speakers and my voice is sent via the Mac’s microphone.

I found the call quality to be a bit crackly and the person I called – okay, it was my mother – had trouble hearing me but it did work and it was useful.

Except.

I realise now that I will use this for all my calls when I’m in my office because it’s just so handy but I did originally want to use it for recording interviews. And that’s the bit I can’t get to work yet. I use Rogue Amoeba’s Audio Hijack Pro a lot and it’s the obvious choice for this kind of thing but it isn’t working for me yet. I tried grabbing the audio from FaceTime, the application that the Mac uses to do these calls and got exactly nothing recorded. I tried switching to have Audio Hijack Pro grab my system audio – so every little bleep and whistle my Mac makes – and that did work except it audibly dropped the volume on the call so that now I was having trouble hearing my mother.

I wonder what we’ve both just agreed to.

So let’s consider the interview-recording to be a work in progress but, blimey, calling from your Mac. As with so many things, this is the way it should always have been – and so this is the way it will be. If you’re on a PC then thank you for reading this far but you’re going to get this Mac feature as soon as Microsoft finishes its cycle. That would be stage 1) deriding Apple, stage 2) claiming you could always do that anyway with a PC, stage 3) announcing it as a new feature and hoping you don’t notice Apple’s already done it, stage 4) eventually shipping the new feature and stage 5) eventually shipping a version that works.

Dip into the original Getting Things Done

Posted by William Gallagher

David Allen’s book Getting Things Done spawned an industry which has taken to doing podcasts. Allen’s own site hasn’t quite got in on the act yet, perhaps it’s on his Someday/Maybe list, but it has collated some audio interviews.

They’re all Allen talking on various radio and podcast shows so there tends to be a lot of overlap of topics as GTD is introduced each time. And I’ve had some problems getting the audio to play reliably so that’s two things against it but have a go with one and see what you think.

David Allen podcast interviews on Getting Things Done

It’s not who you know, it’s how they trick you

Posted by William Gallagher

Earlier this week I was advising some schoolkids on their pitch to a TV company. Last weekend I was directing a group of kids for a show. And in both places, I had the same advice for them:

You are on until it is done

In the case of the show I directed, the group of kids had to act as if they were on stage from the moment the first of their parents arrived. Perfect behaviour, everybody with a job to do, the show has already started. They did it and they were ace.

With the pitching, each group had up to six people all contributing and it’s so hard: once you’ve said your bit and the next person has taken over, you automatically feel relieved that it’s all done. But it isn’t. It is on from the moment you step onto the stage and it is on until the moment you reach the bar. (An age-appropriate bar, obviously.)

I treat interviews the same way. And this week learn the following that makes me glad I do:

When David Cancel interviews potential candidates for engineering jobs at HubSpot, he brings a cup of water into the interview with him. At the end of the meeting, the chief product officer leaves the cup on the table and waits to see what the interviewee does with the garbage. If the person picks up the trash, he is probably a good fit for the job. If he doesn’t, that signals he probably wouldn’t work well on the team.

It might sound like an unfair trick or gimmick, but Cancel insists that it works. “I’ve tested it over 100 times at this point, and it has always turned out to be pretty accurate for me,” Cancel told Fast Company. “The people who didn’t go and reach to take the cup were always the people who weren’t a great cultural fit.” Since starting at HubSpot in 2011 when HubSpot acquired his startup Performable, he has hired more than 100 of the company’s almost 700 employees.

HubSpot Reveals the Mind Tricks It Uses to See if You’re Right for a Job – Rebecca Greenfield, Fast Company (15 May 2014)

That is the only trick this fella reveals but others in this company-I’ve-never-heard-of-before use and you will quickly glance at the ceiling at some of them. But you’ll also readily understand why they do it and what benefit it gives them. Read the whole piece.

More advice on how to get hired at a job

Posted by William Gallagher

There’s this firm, right, and it’s looking to hire various people but one particular group is proving a problem because they write rubbish applications. Apparently Project Managers are so bad at managing to project an image of themselves that the person hiring them was driven to write an article about how they should do it. Remarkably, just as with so very many other pieces of advice for job applicants, the answer is to write better.

You can do that. You’re a writer. We forget sometimes that what we do is hard and that many, many or even most people just can’t do it. So use your skill, use your talent, write your way into a job interview.

I also think that Product Managers need to write better resumes. Designers have, for the most part, figured out that it’s more about showing than telling. It’s easy to go to someone’s sites and portfolio to get a sense of what they’re about. Product Managers still appear to be stuck in the “Let me tell you how awesome I am” rut, though. This is a generalization, of course, but what I’m mostly seeing right now is resumes that excel at vagueness. It’s not uncommon to see a sentence like “Applied world-class methodologies to create a successful customer-centric product”, or some variation of that. What does that mean?

It’s great to see proof of success, yes — stats about conversion improvements, etc. are extremely useful. But hiring managers need more than that to assess Product Managers. We need to know how you think. We need to know how you approach problems, how you work, what methods you like and don’t like, and why. And for some reason most PMs I speak to seem surprised by those questions and have trouble answering them.

How to Get Hired as a Project Manager – Rian van der Merwe, Elezea

Be smarter: don’t apply for jobs when they’re advertised

Posted by William Gallagher

It can’t always be a good idea, but when it’s right, this could work well for you:

Introduce Yourself When They Aren’t Looking

What if you saw an ad for a job where you knew there was a fair amount of turnover. To add to this, let’s assume you are not desperate and unemployed. Wouldn’t it make sense, then, to allow the ad to run its course and send a letter a few weeks later to make it appear your interest in the company was genuine and not an opportunistic spur of the moment decision made because there was an enticing ad that sparked your interest? The point here is to get yourself noticed when they aren’t looking — and when there aren’t a hundred other candidates seeking their attention all at once.

8 Ways to Get Noticed During a Job Search – Wisebread (2 May 2014)

The other seven ways are pretty good too: read the full list. (And a nod of the hat brim to Lifehacker for spotting this.)

Productivity lessons from Blake’s 7

Posted by William Gallagher

In fact this came from Blake himself: Gareth Thomas suggested I do this when I was interviewing him for a forthcoming book about the BBC science fiction series.

Actually, full disclosure, it was more that he couldn’t fathom why I was such an eejit that I wasn’t already doing it.

It’s just this: put your phone calls on speakerphone and tape them.

For all that I said yesterday about finding it hard to make certain types of calls, I have made a fairly constant stream of them throughout my writing and especially journalism careers. With Gareth, I really wanted to phone him over Skype so that I could record the call on my Mac. But he wanted to phone me instead.

I do loathe costing my interviewees any money, I don’t see why they should pay for the call or go out of their way for me, but Gareth couldn’t do anything else. He was on tour in a play and fitting me in on a Saturday morning; he might be able to predict what town he’d be in but there was no way to give me a phone number to ring. I would of course have accepted a mobile number, very happily, but mobile to Skype to Mac has proved tricky before. More than one interviewee has said I sound like I’m in a barrel down a mineshaft.

So I’m genuinely mithered over what to do in order to record the interview. I have to record it. Have to. I’m not going to get a huge amount of time with him and he is somewhat vital to the book, I need to make the most of the chat.

I’ve never actually met Gareth Thomas, I’ve just now done two phoner interviews with him over the years. But even in those short times, I can tell you that he is as charming and funny and interesting as you would expect. Yet I swear I could feel him thinking the word ‘eejit’ before he explained to me that I didn’t need to route the call through my Mac to record it.

Ever get the feeling you’ve been doing something wrong for twenty years? So that happened.

I recorded that man three ways from hell. I rang him on my landline, had my iPhone and my iPad recording the sound from the speaker and I even got my Mac to do it too.

And that’s the productivity lesson: use your Mac or presumably your PC to record calls. You can’t just record anything, it has to be with permission and agreement like I had there with Gareth and a book interview, but you can record anything – in that anything that makes a sound, you can record.

Since that interview, I’ve recorded many calls. Lots of interviews, naturally, but also phone meetings or conversations where I’ve really needed to find out a lot of things and there isn’t much time.

I don’t know how you do this on a PC, though I imagine it’s part of Windows Media Player, but on a Mac you just launch QuickTime Player. Doubtlessly because of its name, few people realise that this Player also records. It can record anything that happens on your screen – so it’s ideal for showing someone how to do something – or it will record your face through your Mac’s camera. Or it will simply record audio.

Choose that, hit the record button. Here’s a second productivity tip, this time discovered by me without the aid of Roj Blake, fictional freedom fighter: identify yourself for the recording. I say my name, the date, the time and who I’ve agreed to record. You don’t think you’ll do this all that often but over the last six months I’ve gathered up a stock of maybe fifteen such calls and being able to identify them in the first few seconds of playback is a godsend.

Especially since QuickTime Player confuses me continually. Once you record something, it is there as an untitled document. Close it and it will ask you for a name to save it under. Or you can just save it and then close it. I say this to you and I cannot see what is so hard. Yet I regularly end up wondering whether I’m going to save or accidentally delete the recording. And I postpone worrying about it by leaving them all there.

So I’ve currently got about seven Untitled phone recordings on my Mac.

I promise to sort through them.

One more productivity tip, this time from my years producing UK DVD Review. That was a podcast from 2005-2010 which I’m proud to say peaked in the top ten of all podcasts, of all genres, across the entire world. I think there were only 11 podcasts then. But I learnt this. If you’re recording a lot, I mean for a long time and maybe just doing a few calls one after another, clap your hands.

I clap three times before the start of a long recording. Interviewees think I am strange. But they suspected that anyway.

This is pointless if it’s just a quick call and even with the much longer one I did with Gareth, it was straightforward: I just transcribed it afterwards from start to finish. Often, though, I will have such a long recording that I need to find parts of it quickly. Usually that’s the start of the next interview. When I was doing this for broadcast, it would be to find the next take or the next section.

These are all things that I would tend to listen to in a proper audio editor instead of just through QuickTime Player. (You don’t have to launch QuickTime Player to listen back to a recording: just find it on your Mac and tap your spacebar. It’s gorgeous how fast that is when you have a lot to look through.) With a proper audio editor, you get wave forms.

And with waveforms, the clap is really distinctive. You get three massive spikes in a row and you can just skip straight to that.

So. With permission, record your interviews or other detailed calls. Do it simply on your computer, label everything, and clap yourself if you’ve done a good job.