Two Simple Things You Can Do As A Freelancer To Increase The Chances You'll Get Work

I had a thought this morning that I thought could fit onto twitter. Ended up being a longer thought than I realized. Here's my Storify attempt to wrap it all up into a neat little package.

  1. As an employer, this works on me. MT @jefftidball: Being a professional gets you quietly noticed by the people you’d want to work with.
  2. There are at least two things -- easy things -- you can do, as a freelancer, to improve the chances you’ll continue to get work.
  3. First is: Answer your emails super-promptly. The gal who returns inquiries quickly is going to stand out. She’s first in line, every time.
  4. The second is: Forecast your trajectory vs. deadline, whenever possible. Gonna hit it? Tell your publisher in advance. Gonna miss it? Same.
  5. Both of these have to do with communication. When you’re a freelancer, other people are depending on you to keep the schedule on track.
  6. Without communication about these things, your publisher’s going to assume things are on track.
  7. @fredhicks Unless the pub sends an email and doesn’t get a reply. Then it’s best to assume the freelancer is behind.
  8. @loganbonner Well, sure; the speculation-in-a-vacuum pendulum swings to two extremes: it’s all going perfectly and it’s all a disaster.
  9. @fredhicks And eventually you learn what radio silence means per freelancer, but it’s easy to start off assuming the worst.
  10. @loganbonner @fredhicks This is the rub. Unless someone is managing the process, and has made that process transparent, comms go first.
  11. If your publisher can’t see the bump in the road coming -- because you didn’t tell him it was there -- he can’t gracefully course-correct.
  12. An unseen bump, hit at full speed, can cause a wreck. A seen bump, even hit, is usually far more gentle.
  13. (Please note: I’m not directing this at any of my current freelancers, who rock. Nobody’s perfect, but they get pretty fucking close.)
  14. (Then again, they’re my *current freelancers* because they have a strong tendency to follow all that I was just saying.)
  15. @fredhicks So true! I think sometimes people don't inform because they are embarrassed, but it is so much worse not to know.
  16. .@jrblackwell Yup! Embarrassment often plays into lack of update. To the embarrassed I say: This is the least bad it will be. Speak up now.
  17. Now folks, here’s the real juice of everything I just said: near 100% of it applies to the publisher-to-customer relationship too.
  18. That shouldn’t really be a surprise. As a freelancer, the publisher is your customer. So at the end of the day, it’s the same relationship.
  19. @fredhicks Some of us have the opposite problem in that sphere. I can be far too quick to make a public announcement.
  20. .@DanielSolis Sure. We screwed that up with the DFRPG license announcement. We made the announcement in late 2005. We published Summer 2010.
  21. .@DanielSolis But importantly, I think the “too quick” risk most often shows up in *initial* announcements. Pre-relationship establishment.
  22. @fredhicks I don't mind when people say "My house exploded, my computer died, my cat's start-up is taking off, etc" Life happens.
  23. .@jrblackwell I don’t even mind when people say “This is taking longer than I expected. I have no excuse.” so long as they say it EARLY.
  24. @fredhicks @jrblackwell The line I learned was, "Bad news doesn't get better with age."
  25. @fredhicks @jrblackwell Yup. The thing to remember is that, no matter the relationship, you are BOTH each other's customer.

Did you find this story interesting? Be the first to or comment.

Liked!

Fred Hicks

Game author and small publisher at Evil Hat Productions, LLC.

Total views
197

Storify

@Storify