Letters from a ttRPG Dev to a Freelancer, 4. Post-Publication Activities.
This entry in the Letters from a Dev series is adapted from a letter about what is, and maybe isn’t, a good idea to do after a project you have a credit in gets published and is available to the public. I’ve given similar advice to numerous freelancers, and prospective freelancers over the years (and even have a file on my hard drive that has some snippets of those to borrow from when I am asked about this topic), but I don’t think I’ve ever publicly published any significant portion of the advice itself.
I *try* to always open such letters with congratulations for getting published–creatives in this industry see criticism SO much more than praise or well-wishing, so I like to celebrate those moments of success if possible. Then, I break down my main suggestions for things to do with a project, now that it’s out in the world in its (presumably) final state.
“First, let me say that all this advice comes with a huge proviso — never follow these suggestions if they conflict with your own ethics, morals, best practices, comfort level, or mental well-being. For example, I mention looking for opportunities to talk about your work, including podcasts, but if your mental health will suffer from doing that, don’t. Similarly I suggest keeping praise for your publisher public, and criticism private, but there I am talking about things like typos, or inferences the publisher may not have meant. If you feel you have an ethical mandate to call out a publisher publicly for things such as racism, bigotry, misogyny, and so on, I am in no way telling you not to do that. No one is paying you enough to sell out your ethical code, and I believe we all have a responsibility to try to make the world a better place. Any such instance is going to be too complex for some general advice that doesn’t know all the nuances of that specific situation to apply in any more than the vaguest sense. You’ll need to take those actions you feel most appropriate and/or most effective. That might mean publicly raising your objections, at least eventually if private notes do not seem to be making any difference. It also might not.
I wish I could tell you that any criticism you make, publicly or privately, will be taken as a reasoned, well-intentioned, good-faith effort on your part to make the hobby as a whole better. And, some folks will take it that way. But at both the professional and consumer level, many may not. It’s a risk, and you need to be realistic with yourself about the impact of possibly blowback on your life. If you have specific concerns in this area, please feel free to ask me about them. If you want my private, confidential take on a specific situation I am happy to give it. I might even be able to help.
That huge caveat aside, my general advise for what to do when a product you have a credit in comes along is pretty simple.
Do this first. You never know what may change from your final turnover to the printed page, and there are two good reasons to find out. First, seeing how things you wrote have changed may give you a better idea what that publisher is looking for, which can help you get more work with them. It may even give you insight into haw to be a better writer. If you don’t understand why a change was made, a short, polite note to your contact who got you the contract for the gig and to who you turned over your draft isn’t a bad idea.
Second, if you begin talking about the book, you want to talk about what is actually in it, rather than what you turned over. You neither want to promise people something that has been removed, nor seem uninformed if people ask you questions about things you have no familiarity with.
I sometimes sit with a PDF of the final release on one screen, and my draft on the other, and look line-by-line at differences. Yes, it would be easier for a developer to send you feedback, but that’s all-too-rare in this industry.
Check your NDA
Assuming, of course, you have an NDA. (Check your contract.) Most likely once the book is out you are free to talk about it, but if it’s one part of a multipart project you may be surprised by what hasn’t been revealed yet. Again, if in doubt, a short note asking for clarification to you contact with the publisher normally goes well.
Promote Your Credit
This is a great chance to promote yourself. Make a post talking about having a credit. if there’s some interesting anecdote about the process, that may be worth including as long as it doesn’t put anyone in a bad light (though see the proviso, above). For most social media platforms, including a picture of the cover of the product is a good idea.
This can help get your name out into the industry, remind people you are alive if you are already pretty well known (I still do this, for example), and convince publishers you are a good partner that will help advertise their product once it is out, driving engagement and interest.
Add It To Your Credits Sheet
Ideally, you have a list of all your credits already. If not, time to start! You want to be able to tell people what you worked on, and how you were credited, in case it ever comes up. Seriously, there is a big difference between having one credit, having ten, having 100, and having 1,000. Start keeping track now if you aren’t already, and make time to keep it up to date as things are published. I personally have all the print products I have worked on as a Facebook album, and people finding that has lead to things like consulting work.
Often podcasts and blogs are looking for content related to new releases, and you helped make this one! You don’t want to steal the thunder from the publisher (again, looking like a good partner makes it more like both this publisher and others will want to work with you in the future… but yeah, see the proviso above), but in my experience if you send a note saying “The podcast ‘Second Level Spell’ wanted to interview me about the Battle Pie rules I wrote for the Orkenpie adventure,” they’ll be enthusiastic in their support, and may even boost that on their social media.
I’m bad at this one, so I include it here. You may have no issue with it at all. When I look at my old work I can… obsess over perceived failings. I want to figure out why I didn’t do what the developer did, make sure I learn all possible lessons from the project, and consider all the ways I could have done a better job.
A little of that is fine.
But then it’s time to put it down, and move on. Of course you can do a better job now than you did then–we are all learning and improving all the time. Instead of worrying about what past-you got wrong, turn to what current you is doing that you can apply those lessons to.
Don’t Take Reviews to Heart
For a lot of people, this may mean just don’t read the reviews. I personally am unable to do that, so instead I try to restrict myself to weighing their opinions against my own. Did they find something unclear? Fair enough, do I see their point or not? Is it full of typos? Well, that might mean my turnover was too error-ridden for even professional editors to save it, I can look at that. Do they not like it? Okay, but that’s, like, just their opinion man.
Dissatisfied people tend to be much more vocal than satisfied ones. So if you have to read the reviews, take them with a huge grain of salt. And never let them get you down.”
Support My Patreon
The more support I get, the more time I can spend on writing things like this.
If you enjoy any of my articles, please sign up, for as little as the cost of one cup of coffee a month!
Posted on June 22, 2021, in Business of Games, Musings, Writing Basics and tagged Essays, Freelance Life, From My Files, Letters from a Dev, Writing Basics. Bookmark the permalink. Leave a comment.
Leave a comment