Work: Week 7

I just looked at the calendar and counted: I’ve been at my job for 7 weeks already. Time flies when you’re having fun, I guess, because it feels like just yesterday we started this crazy adventure.

On the other hand, it’s been long enough that we’ve started finding the routine that works for all of us to do what needs doing while staying sane. Benji and I spend his first hour up together, and I make sure to get some of his prep stuff done so Ian doesn’t have to. While we’re hanging, Ian gets ready for his day. I leave the house at 7:15, and get home any time between 6:00 and 6:30, unless I have to stay late.

This unfortunate occurrence will happen more and more frequently over the next month, I expect, as we approach April 20, the next release date. I have several hard deadlines between now and then. My boss told me “We kind of tried to let you know in the interview that this job is really stressful.”

I’m not feeling stressed out yet. Maybe that’s ignorance, and I should start stressing, like when I did my first bike race and I really had no idea what was going on and whether I was safe or not. But I keep checking with my boss and coworker to make sure I’m doing the right things, and so far it seems like I’m on top of everything.

The way the job works is the developers make features based on things called User Stories. We, the writers, find out which User Stories will be going out at the next release. We research the stories, reading the technical specs and trying out the features in the test environment, so we have an idea of how the new feature works. Then we meet with the people in charge of each User Story (Project Managers, PMs) and interview them about their User Stories. Then we write Release Notes, which describe not only the mechanics of the new feature, but emphasize the “Why,” as my boss puts it. We have to really sell the feature, making it sounding exciting and worthwhile.

Release notes are my first deadline. This is a big deal, because it’s the first time my writing goes out to the senior management and all the PMs for review. I have to hand-deliver a hard copy of the release notes to the president of the company for him to read (!).

After I get release notes written, I go into the Help Center and edit or add pages to cover details of the new features. I have two weeks to do this from the time the release notes go out to the time the actual release happens. Many features don’t require a ton of new writing, but rather expanding or modifying existing content. Unfortunately a lot of changes to the look require new screenshots, which are difficult to find and take some time to replace. But some of the changes will require me to write entirely new pages, and that takes time, too.

As I mentioned, I’m not feeling stressed. So far I’ve certainly felt time pressure, and the need to focus and work diligently. As far as I can tell, I’ve not yet fallen behind, and if anything I’m a little ahead of where I need to be.

Unfortunately, I do have an entirely separate, unrelated project that’s quite big and going to take a substantial amount of time, and that’s going to come due right around the end of April, too. Time to engage in some serious time management.

I’m not sure how much blog writing I’ll do as we approach this release, and I don’t know what having a job writing will do as far as my desire to write recreationally. We’ll just have to see. Lately on my bus rides I’ve enjoyed reading Wonder Woman comics on Hoopla or library books on my phone Kindle app. But I’ve had this blog so long, it’s not going away. I’ll just update more or less. We shall simply see what the future holds. As always.

Leave a Reply

Your email address will not be published.