Me Organize Real Simple Now

I’m obsessed with organizing things, and have been since I was a kid: endlessly writing down lists and plans, alphabetizing my book and music collections, compulsively reading every book in a series, etc. Perhaps because of this, I’m an organization tool junkie; I’m always eager to kick the tires on a shiny new technology or system that promises to help me deal with my little problem. Having tried many different tools, I now rely on just three. Here they are:

Pivotal Tracker. This is the single tool I use for managing software projects at the designer/developer work item level. It’s great… very easy to use, full history tracking, lives in the cloud (backed up), optimized for software projects, predicts dates for me, and lets me organize work into a few logical buckets. Some people don’t like the automatic date prediction, and if you need to work that way (“Precisely Scheduled Project Candy-Cane Land”) then it is not the tool for you. I think Pivotal would also work for many other kinds of creative project work — not just sofware — and I’ve suggested this to the good people at Pivotal Labs a few times, but they seem locked on the software space. All the better for us nerds.

Trello.  Trello is my single “big picture” list-making tool these days. At work I’ve just started using it for tracking high-level work project deliverables, e.g. key milestones and handoffs with clients. At home, I use it with Katrin to plan our expenses, prioritize home improvements, track movies, music and books we’d like to buy, and more. It’s simple, visually beautiful, and works on our computers, phones, and iPads. I’ve only been using it a few months now, but I think this one will stick because it addresses so many of the failures that stopped me from using other list-making tools.

Text files. When I’m keeping scratch notes on a project, or drafting a blog post, or trying to organize something that doesn’t fit into a list, it goes into a text file. I write in either straight .txt format or MarkDown to get a teensy bit of formatting. Every file is named yyyy-mm-dd-the-topic-title.md, e.g. “2012-01-27-writing-about-startups.md”, and this gives me a clean way to organize files and rediscover stuff I wrote months or years ago. Within software projects, a few text files in the doc directory suffice for readme’s and specs, and they get stored in our git repository for backup. For personal stuff, gitdocs automatically backs up my docs directory to the cloud. If I need a fancier looking document I generally switch to Google Docs, as I hate trying to reconcile and merge copies of office docs. But I always miss the speed and simplicity of editing a local text file, and I find myself back in text files before long, ast least for the initial drafting step.

Here are some tools I’ve tried that didn’t work well:

  • Rich text “office” docs stored on a file server, e.g. Word, Excel, StarOffice, etc. plus file servers, Sharepoint, DropBox, etc. The richness of these document formats is fantastic for loosely structured content, but I find I always get caught up in formatting content and rearranging it on the page instead of getting down to the real work of writing. (Now that I write code for a living, I grit my teeth when someone sends me an amazingly formatted rich text document. “How long did that take to do?”, I wonder, and “how much better could the actual content have been if you hadn’t spend so much time formatting?” Sorry, all you devs I spammed with beautiful specs at Microsoft.) I’ve also never found a filing system that worked for teams… they all turn into junkyards, and then into graveyards. So I try only to go here when I have to work with big, bulky documents, e.g. video, PhotoShop PSDs, and such.
  • Calendars, e.g. Google Calendar, iCal, Outlook/Exchange. Some people are huge fans of putting everything on a calendar, arguing that it forces time-based tradeoffs, thereby avoiding overcommitment. I find this too constraining. It forces me to think of everything in half-hour or 1 hour chunks of time, which isn’t a natural fit to the kind of work I do right now.[1] It limits my flexibility in deciding what to work on at any given moment. I don’t want silly reminder popups interrupting me every 30 minutes. My calendar drifts towards being 100% blocked out, and then I start chopping time into 15 minute segments… madness. And I find myself spending way too much time trying to optimize which day and time each thing needs to happen on. Time trap.
  • Defect trackers, e.g. JIRA, FogBugz. If you have a defect-tracking list that’s separate from your feature-tracking list, it’s easy to ignore, because it’s one more thing to pay attention to. Plus you have to continually make arbitrary decisions about whether something is a defect, a feature, or in between (“by design”, “spec bug”, etc.). This is a waste of everyone’s time… who cares what you call it, the question is “are you going to do it, and if so, when?” What’s more, the same people who build features are usually responsible for fixing bugs. So I try now to avoid the disconnect by using Pivotal, which combines “bugs”, “features” and “chores” into a single work list.
  • Project schedulers, e.g. Microsoft Project, or Excel for critical paths. Gantt charts and the like are pretty, and the promise of accurate schedule prediction is enticing. But they’re a lot of work to build and maintain, and they rely on people being good at estimating work, managing risk, predicting uncertain future events, and sticking to commitments. In my experience, most people (myself included) are not very good at any of those things. So project schedulers lead you down the path of building a beatiful house of cards, only to have to reconstruct it every week or two when schedule predictions are inevitably proven wrong. They are good only for point-in-time “aspirational” planning, IMO. Some projects do need this (building a new airplane, say), but I’ve found that many do not.
  • Task lists and To-Do’s, e.g. in gmail, Microsoft Outlook, Things, Basecamp, etc. These tools encourage you to break goals down into fine-grained tasks, which you then prioritize and check off when they’re done. I find I tend to put way too many things on task lists, at which point I promptly get overwhelmed with analysis paralysis. Not for me.[2]

As a rule, when I find myself spending more time organizing the work rather than immersed in doing the work, I have a broken process. At that point I stop, hit the reset button, and start over. The tools I’m using these days are great assistants: they help me arrange my plan, and then they step quietly out of the way.

Thanks Ilia for the nudge to write this.


[1] Outlook/Exchange calendaring was an essential tool for me in my last few years at Microsoft, because most of my workday consisted of meetings. But even so, I used the calendar way too much. Better to leave some ad hoc unscheduled time in the day. Give serendipity a chance.

[2] I’m not sure why I find Trello so much more pleasurable than any of the task list and to-do list alternatives. After all, Trello is at its heart a list-making tool. Perhaps something subtle in its design helps me “chunk” list items at a more appropriate granularity. I’ll have to think more on that.

Don’t be afraid of the Start(up)

I was pretty intimidated — and still am, frequently — by the idea of trying to create or join a startup. Perhaps you’re just out of school, flat broke, and thinking of getting into startups. If so, no problem: you have nothing to lose. But for people with a Stable Job in Corporate World, switching to doing your own thing can be pretty scary.

“How will I pay the bills?”, you might ask. “What if it all goes wrong?”  ”How will this look on my resume?” “What will my friends think?” “Will my family understand what I’m doing?”

Well, to the last of those, I will answer “probably not”. Unless you come from a family of entrepreneurs, your fam will probably have no clue what you’re doing. This will make for lots of awkward holiday dinner conversations. Oh well.

Will you have to take a pay cut? Probably. In exchange for your Stable Corporate Salary you will get to work on an idea you are passionate about, in a work style you own, with a chance at more long-run financial upside. If that tradeoff of short-term money for immediate happiness, immediate control, and long-term financial potential sounds bad to you, stop now.

As for the optics, I guarantee you will become a more interesting person, both on paper (your resume) and in the eyes of your friends. You will be learning new things, meeting new people, stretching yourself. Simply by taking this risk you will be markedly different from everyone in Corporate World. If you go back, you will be noticed. And that’s a good thing.

Lastly, what if it all does go sideways in Startup World? Consider this: when you exit a stable job in which you’ve done well, it’s highly likely you can turn right back around and knock on the door you just stepped out of. All those people you just said goodbye to like you. They miss you. They might even envy you. And they will be happy to see you again.

Pretty good worst case, no?

Don’t be afraid of the start.

#ThanksUnspace

Last night I went to the Ruby Job Fair hosted by the good people at Unspace. It was a lovely opportunity to chat with many smart, friendly people who are building good things with software and hoping to either hire or be hired. Here’s what I was thinking, and what I wish I had stood up to say out loud:

For a brief while, somewhere around beer number three, I had a flashback to 2005 when I moved to Toronto. Things were very quiet in the tech startup scene. Ruby on Rails was just starting to take off. DemoCamp had yet to begin. Lots of smart people were building things with software here, but most of them worked out of IT departments in office towers on Bay Street. The only “tech startup” people could commonly name was RIM, and it was already 10 years old and publicly traded by then.

Things have changed. A lot. There were over 100 attendees at Unspace HQ last night, with at least 20 employers pitching their companies, all vying to hire Ruby developers. I saw a lot of familiar faces, but also many new people I’d never met before. And pretty much every employer in the room was representing a startup. Joey de Villa was there from Shopify. Paul and Geoff from CommunityLend. Katherine Hague and Phil from ShopLocket. William and Bart from Engagio, freshly funded by Fred Wilson of Union Square Ventures. Paul from GaggleUp. Krista and Aidan from Winston. Mike with his University Health Network project. Startups everywhere.

That says a lot about Ruby on Rails; it’s clearly got great traction in the web startup space here. It also says a lot about Toronto and the community that has grown here around Ruby, Rails, and web startups. The barriers to creating startups are coming down. Starting a company is now much more socially acceptable here, desirable even. Designers and developers who want to be true craftspeople increasingly “drop out” of mainstream IT work to join startups. Technologies like Ruby, Rails, git and Heroku continue to reduce the cost of building and deploying great web software. And, at least from my little corner of the web, the local demand for web developers and designers seems to be at an all time high. All subjective, I have no hard numbers to offer, but I believe it’s real.

The startup scene in Toronto is really taking off.

I love that fact.

Much of this has come about organically, due to these enabling factors kicking in at the same time. But it really struck me last night that the community piece is different. This community didn’t just spontaneously assemble itself and become awesome overnight. Instead, a small handful of very diligent community builders, most notably Pete Forde, Meghann Millard and their amazing crew of coworkers at Unspace, worked hard and gave freely of their time and energy to help seed and build this. Free advice. Encouraging pats on the back. Rails Pub Nites. Technologic. Ruby Fringe. FutureRuby. Ruby Job Fairs. Friendship, even. They have done a ton to foster and ignite the web startup community here in Toronto. And they continue to do so.

So I will say it here, and hope others repeat it: Thank you, Unspace. You are doing great things for Toronto. We are proud of you.

#ThanksUnspace

Update 2012-02-13: Fred Wilson personally funded Egagio. The funding is not from Union Square Ventures. Thanks William for the correction.

Follow

Get every new post delivered to your Inbox.

Join 348 other followers