A couple of years ago I took up writing again.
This is something I used to
enjoy, but gradually stopped because I simply didn't have the time any more.
When I picked it up again I had no particular goal in mind,
other than as a hobby. Eventually
though, I ended up writing a complete story,
so I went ahead and published it.
At this point I discovered that it's very common for debut authors to find
that they have more books in them than they realised! I now have a
sequel in development, and several other works in progress, and
obviously that has an impact on how I manage my time.
Once I started looking into my progress on each project, and with one
eye on my timesheets, I got curious. Just how many hours are involved in writing
a novel? More to the point, how much of that is actually writing
(the fun part), and how much is proof-reading, editing, typesetting -
and, of course, the dreaded marketing?
Since I track the time I spend working for different client, I decided to start
keeping a record of writing in the same way, treating it as just another work
project, and with enough data I could analyse it in the same way that I do for
paying contracts. Thanks to that, I already have a complete,
detailed, and structured collection of data points to work with.
I started with date, project, activity and the number of hours.
I used Pandas to convert the date to a proper datetime object
then add the day number and day name against each entry, and
the month name against the first day of each month.
This isn't essential for the analysis, but it gives me a way
to differentiate weekdays from weekends in the final result, as
well as placing labels for the months.
Now, on to the code. Normally in my analysis I aim to work backwards from the
questions I want to answer, but in this case I was partly inspired by
this post by Giuseppe Solazzo
showing his fitness tracker steps for 2024, and he was inspired in turn by
Dominic Royé's work plotting
climate circles. In both of these examples, the visualisation and calculations are all done in R.
On the other hand, I tend to work a lot more in Python. Luckily for me
Tomás Capretto had
already looked into coverting a very similar R visualisation by
Cédric Scherer into Python.
Here is Tomás's example
which is already very close to what I wanted to do. The data in this example deals with the amount of
time it takes to crack certain categories and formats of passwords, but all the necessary elements
are there for me to deconstruct and tweak for my purposes.
Next I need to decide what questions
I'm trying to answer with this data. More specifically, what questions do I
think would be well-answered by the radial chart I'm planning to create?
Here are the obvious ones:
Let's start not at the beginning, but with the second question. This one
is better answered with a simple bar chart, at least to begin with.
Plotting, outlining, typesetting,
cover designs, proof-reading, uploading files, and marketing are all
part of the process if you're self-published. The bar chart to the right
shows the breakdown of total hours by category.
It is interesting to see the numbers, and there are a couple of surprises.
Drafting and editing make up the majority of the hours, as I would expect.
Marketing - which includes social media posts, designing ads, and editing
photographs - looks tiny. In fact this
is an almost daily activity, but usually only for a few minutes at a time.
If I reproduce this diagram for 2025 later on, I expect that number will be
significantly higher.
I am shocked by how little time I apparently spend outlining and plotting,
possibly something I need to address!
Proportion of time spent on different tasks
If you're interested in the code I used to
make this chart, you can find the Jupyter notebook here.
And if you got this far and are curious about what I'm writing, the book is available
on
Amazon,
Kobo
and BookFunnel.
To start with, you can see that I didn't start recording the time I spent on writing and writing-related tasks until April 2024. You can also see that I don't find the time to write every single day; even once I'd started logging time in those categories, there are still gaps.
In this case, 444 hours (and counting, since technically the current WIP isn't finished yet). That said, some people do write faster; and not every author would count all of the activities that I've been logging as 'writing'.
I don't typically get more writing done at weekends versus weekdays,
as you might have imagined, but then my working week is quite flexible.
The graph shows that it's very common for there to be short bursts of
four hours or less - that usually means I found a little free time in the evening.
For lines of more than four hours on a weekday, possibly I had a free day with no
paid work to focus on. That said, there are also days where the conditions were
perfect and I was writing and editing late into the night because it was all
flowing so beautifully!