Content Consumption & Sharing Workflow

I find myself awash in an ever-expanding sea of content. This is in part thanks to the web's empowerment of self-publishing, combined with social networks making it incredibly easy to re-share what my community feel is valuable or interesting articles. Like many people, I encounter this in different contexts, be it via twitter on my mobile while traveling, or via facebook at home on my tablet, or my RSS reader on my desktop machine.

These articles typically fall into 3 categories:

Articles tend to come to my attention via:

Much of my content consumption is on the go, and so I then pass any content of interest into Pocket, which servers as my backlog .. my 'reading debt' list

It's meant to be my 'to-read' list, however it's in need of a big old clean-out, which is itself indicative that my workflow isn't really working for me... or maybe my content consumption habits in general need some attention.

From Pocket, I transition anything which is still interesting into Chrome (see note below), which is finally leads to the last part of my curation process into the following categories:

I then re-share particularly interesting content, back into Twitter, Facebook, LinkedIn. As my content consumption habits are very 'spiky', I use the fantastic Buffer app, to manage the scheduling of the re-sharing of that content. I just put it into the 'buffer' and it'll go out in the next time-slot configured for each social network.

Additionally there is my own content, which is typically either editorial content, to be shared on this blog, or maybe photos - I described my photo workflow earlier this month.

Putting this post together reminded me that the main reason I transition content out of pocket and into Chrome, is because I don't want the URL to be a pocket one e.g. https://pocket.co/sMj3fJ ... so maybe it's time for me to look at alternatives to Pocket.

Putting this post together also made me feel that this workflow is a bit convoluted, so I'll maybe have to consider revamping it - and would love to hear about your workflows please (@bseymour)