If you haven’t figured it out by now, I’m obsessed with finding ways to work faster and smarter.  I’ve talked about designing and brainstorming faster with my whiteboard and Balsamiq‘s mock up tool.  I spent over 600 words describing how I organize my email inbox, and I can’t wait for Ativiti to launch so I can share even more ideas about process.

Given all that, it’s no wonder I enjoy working for a startup.  From my experience, it’s the ultimate test in your ability to get a lot done in very little time.  There are always a million things you have to do.  There’s absolutely no way you can accomplish everything.  How do you figure out what gets done and what doesn’t?  When no one is telling you what to do, what’s the most important thing you should be doing?

From my experience with this and previous jobs, there’s the things you have to get done, no matter what, and then there’s everything else.

Things that have to get done, no matter what.

In most normal jobs, “the things that have to get done, no matter what” take up most of your time.  In a startup, though, these things are the least of your worries.  At a startup, the things that have to get done, no matter what, are the things that you’ve figured out already.  You know your payroll process.  You know your QA process.  Make them as fast as possible.  Make them take up 10% of your time.  You have to spend the rest of your days figuring out your new marketing strategy, the next product launch, the bug fix, and …

Everything else.

If 90% of your time is spent on everything else, what does that time look like?  How do you figure out the next most important thing for you to work on?  Your work has to constantly move a process forward, a contract forward, a task forward, the company forward.

Are you creating something new?

Working at a startup means you have the potential to create something new just about every day.  You can’t actually create something every day, but that’s the potential.  It takes a lot of prep work to create something new, especially to do so correctly.  Creating requires a process — brainstorm, refine, plan, build, refine — and with each step you’ll have to ask yourself the same question, what’s the most important thing I should be doing?

Are you doing something that will bring attention to your organization?

No news is bad news for a startup.  Find a way to get people talking about you.  There’s many ways to bring attention to your organization — create something new, improve your page rank, generate buzz on the blogosphere.  If you’re doing this, you’re always doing something important.

Are you creating something that’s lasting and replicable?

You’re creating something new.  We’ve established that.  You’re also creating something that may have to last.  You need to assess whether what you’re creating is a one-time activity or not.  Pulling a report is never a one-time activity.  Writing a feedback email isn’t either.  Obviously, this has to be balanced with a startup’s short-term need for speed and agility, but a little planning up front helps ensure longer term success.

Are you improving an existing process?

You’re taking a process from the person who first created it.  The problem is, you’re not someone who just takes a process as-is.  You want to question and improve it.  With enough people thinking like this you can quickly go from a guy writing a payroll check to an electronic, efficient direct deposit payroll system.  Be sure the time spent fixing your process justifies the effort, though.  If it takes several hours to reduce a back office process from three clicks to two, it might not be worth undertaking right now.  It might still be worth fixing, but not until a million other things are taken care of.

Are you developing something you can pass to another team?

You not only have to create things that can be passed to your own internal teams, you may need to make your work presentable to another team in your company or another company altogether.   You can’t simply give the administrative assistant a payroll task without re-explaining your process, highlighting any exceptions.  Your specification has to be written unambiguously in order for development to pick up where you leave off. What’s acceptable for internal team distribution often requires a new draft entirely for other teams.  Factor this extra effort into your planning.

Are you learning something new, something that you can re-use?

You know what you’re doing right now.  But do you know what you’re doing a year from now?  You should have an idea.  What will you need to know then that you don’t know now?  A few pilot programs now will make it easier for you to answer that question later.

Are you fixing something that’s broken?

Fixing something that’s broken helps make sure you’re not wasting time on things that don’t fit these criteria.  Remember what I said above, though, the effort mustn’t exceed the reward.

Finally, in this economy, there’s the most obvious question you should be asking yourself whenever you prioritize your work –

Is this going to make us any money?

Forget everything else.  If all else fails, focus on generating revenue.  In this economy, there’s nothing more important that you could be doing right now.

Related articles by Zemanta

• Dumb Little Writing Tricks That Work: Free Association (gointothestory.com)
• How to Collaborate (myventurepad.com)

Posted in How To, Process, Startups | No Comments »