Some time back, mathowie poked me about talking to our pal, Scott Andrew, about some of the productivity mojo he uses to keep his one-man acoustic pop army in line. Turns out that, in addition to being a terrific singer/songwriter, Scott’s got a mature system for booking gigs, promoting his work, and maintaining a lively relationship with his many fans.

Although there are tips here that will be useful to everybody (keep it simple; fear not lofi; provide great customer service), the musicians, artists, and other performers out there will most especially learn from what Scott’s got going on; as my friend Sean is fond of saying (in a booming, fakey showbiz-guy voice): "It's not music 'friend'; it's music business!"

Productivity for the Practicing Musician

by Scott Andrew

When Merlin approached me about writing a sort of “Getting Music Done” piece, I initially thought: buh? I’m probably the worst model for artistic productivity. After mulling it over, it occurred to me that I’m probably a very typical model. I have a day job. I have rent. I write songs on a used thriftstore guitar and record them when I can scrape enough gig money together. I spend my creative life in that emotional DMZ between self-assured, passionate DIY ferocity and vague, nagging career dissatisfaction. In other words, I’m just like most aspiring musicians. Perfect! So don’t please look on this article as advice from someone who’s “been there” — I’m still getting there.

I once read a rant by a punk musician who complained that if he had the time and ability to do all the stuff needed for a rewarding music career, he wouldn’t need a record deal. Well, yes. The unsexy truth is that some days you’ll feel more like a Post Office than a rock star. This pisses off some people who’d rather be working on, like, music, instead of bookings or publicity. But that’s okay, because the worst that can happen is: nothing happens. Eventually you get tired of nothing happening, and you resign yourself to the “business” side of the music business. Sigh.

David Allen’s suggestions for lists that are handy to keep around.

Getting Things Done [iCommit.eu]

Rainer Bernhardt has put together a nifty little PHP app for doing GTD via a web interface. It lets you wrangle projects, next actions, calendar items, ad hoc lists, and all the other tactical building blocks of GTD all via your (non-IE) browser. The interface is pretty good and typical workflow is quite easy to navigate through. It has nice touches like attachments, per-item effort estimates, printable views, plus Rainer says he may soon offer email integration which would "eliminate use of a separate e-mail app" for workflow-related planning. Wow.

Although I haven't spent a great deal of time with it, I'm very intrigued by the baked-in "weekly review" functionality, which walks you through most of what you need to look over each week from one interface. Since review gets short shrift from the many folks (like me) who use GTD primarily for task management, I think an addition like this is a terrific idea.

iCommit is, like so many of my favorite apps these days, a non-commercial, one-man operation, so there are a few rough edges, no documentation (yet! coming soon, says Rainer), and it is very much "first come, first served" in terms of seats he can handle on his personal server setup (I hope we don't cream Rainer's productivity boxen with this). But iCommit is worth a look if you've been craving a cross-platform, low-paper implementation of Getting Things Done.

Screengrabs below the cut -- I feel like Michael Arrington!

Is your car smoking from the exhaust pipe?

Reader wemerson was kind enough to correct me on my metaphor in the previous post about tracking down the sources of whining in your life. Turns out that my use of "white smoke" was incorrect. Many thanks -- and I made the correction.

To share the information and prevent future slightly-appropriate-metaphor-makers from repeating my error, here's how to tell what's wrong with your car based on the color of smoke coming out of your tailpipe. From trustmymechanic.com:

• White smoke: White smoke is caused by water and or antifreeze entering the cylinder, and the engine trying to burn it with the fuel. The white smoke is steam...
• Blue Smoke: Blue smoke is caused by engine oil entering the cylinder area and being burned along with the fuel air mixture. As with the white smoke, just a small drop of oil leaking into the cylinder can produce blue smoke out the tailpipe...
• Black Smoke: Black smoke is caused by excess fuel that has entered the cylinder area and cannot be burned completely. Another term for excess fuel is "running rich." Poor fuel mileage is also a common complaint when black smoke comes out of the tailpipe.

Related: in the event that a conclave at the Sistine Chapel has been voting on who the next Pope shall be, here's what Wikipedia says to watch for in terms of smoke (emphasis added):

Values of n Blog: Merlin Mann advises

I'm happy to announce that I've accepted an offer to advise Values of n on the development of their Stikkit web application.

In fact, although I've been using and loving Stikkit for several months now, I've held off talking about it much on 43f until this addition was made official and public¹. But, since I stand to have an advisor's stake in the business as a result of this work, it was important to tell you guys and properly disclose my involvement before doing much gushing in the content well here.

I have a pile of tips for how I'm using Stikkit and have been regularly poking Rael, Michael, and crew (to what I imagine is the point of polite professional annoyance) with feature ideas and things I want the app to do (hint: everything). So I'm glad I can finally start sharing this stuff, here and elsewhere.

This is the first Advisory Board thing in which I've participated (my OmniFocus advising is pro bono and will continue as before), so I'm pretty excited to officially get started.

Anyhow, I wanted you to know about this and to say that I'll be linking back to this post whenever it's appropriate to remind you of my proud involvement in Stikkit. I am enthused about where this project is headed, and I'm honored that Rael and his team have let me in on their process.

1. Note that folks in Canada can catch a demo of Stikkit I did on Call for Help which I taped in December, before this was approaching officialness.