The Secret Sauce Behind Steve Rubel’s Lifestream Workflow and Revamp of Mine
I have recently decided to seriously spend some time focusing on how to improve my Lifestreaming workflow. I have found that creating an effective workflow is one of the most challenging aspects of Lifestreaming. I don’t feel my current method is very good and needed to change. There are many variables that will determine your workflow. Which tools & services you use to create content (Flickr, YouTube, iPhone) as well as the networks you post them to (Facebook, FriendFeed, Twitter) will dictate many things.
Here are my plans and goals.
- Identify all my current desktop & mobile tools currently used to post content
- Look at how content is currently displayed on the services I’m posting to
- Review my cross-post and sync methods across all my existing services
- Modify the tools or processes currently in place making them more effective and eliminating duplication
So the catalyst for me getting this process started was posting photos from my iPhone. I no longer wanted to use Twitpic. I currently sync my twitter account to Facebook. I want my mobile photos to be displayed as thumbnails in my Facebook feed as opposed to tweets with a Twitpic link. FriendFeed displays the Twitpics fine, but I want the best solution across all services.
I’ve been doing a little research on the various services out there that do cross-posting including Pixelpipe, Ping.fm, and Tarpipe. After some testing I’ve started to experiment with Posterous’ auto-posting features. So far I’m pretty happy but have issues with duplication based on my current workflow.
Then the other day I noticed that Tweets from Steve Rubel are using the FriendFeed short url service yet are linking to his Posterous. So I went back to read his Lifestreaming Workflow post. In it he gave the overview on how he captures, processes, and shares content but not the nitty gritty details. Luckily a commenter posed a question that prompted Steve to provide the details I was looking for.
Steve’s secret sauce
That information helped me understand how he was doing it. I’m not a fan of relying on RSS to get scooped up because I like the immediacy of posting but it got me thinking differently about how to improve my workflow. I’m willing to make sacrifices to my workflow to remove duplicity and RSS is quickly improving around the needs of the real-time web so it may not be an issue in many cases.
Anyways, I will continue testing and improving my workflow and will post the results once I have reached a comfortable process I decide to use. In the meantime I would love to hear about your current methods and possibly include them in my future post. Either leave details in the comments or you can email info to me.