Problem solving 101: 7 signs it’s time to stop what you’re doing
Ian Lurie May 3 2011
A big part of problem solving is stepping away from the problem. Whether you’re writing code, writing a book or trying to figure out why a web site isn’t generating sales, there comes a point where your brain over-saturates and needs a good wringing out.
Here are some common signs you need a break:
- You think trying that same thing for a 40th time will fix the problem. It won’t.
- You’ve begun giggling at the thought of world-ending asteroids. Or am I the only one who does this? I just said too much, didn’t I…
- You find yourself staring off into space, thinking of nothing. That’s your brain telling you to take a break. So take it.
- You’re obsessing about the trivial: Did you just spend 30 minutes trying to get every last fingerprint off your monitor? Yeah. Again, that’s your brain telling you to cut it out. Listen to your brain! It’s got all your marbles.
- The problem is no longer the problem. Say you’re trying to figure out the best way to make an Excel spreadsheet to calculate total sales for 2003. You’ve worked on it for hours. Somewhere around hour 2, though, you started looking for the ideal font. That’s now sucked up all your brain power. Time to reboot—walk away, refocus on the core problem (the math) and deal with the formatting later.
- You’re getting cranky. Joke all you want, but I’m not a naturally cranky person. I’m a little gruff, maybe sarcastic. If I start sounding whiny, it’s definitely time to push back from the keyboard.
- You’re driving over the mountain instead of around it. Look at what you’re doing. No, really look. Are you doing this the hard way? Is there an easier alternative? Unless there’s a benefit to the tougher solution, you’re wasting energy. take a breather.
I’m one of the worst at this, by the way. I’ve been putting a lot of time into coding lately, I’ve found a pattern:
- I plan out the app I’m writing.
- I start writing it.
- Something trivial, like replacing all instances of “buh” in a paragraph, or grabbing one number from an API, leads to utter brain gridlock.
- I fight the desire to hit my computer with a desk chair.
- I walk away for a while.
- I solve the problem.
Don’t be me. Take a break around step 3, and you’ll be far better off.
- Automate Linkscape reporting with Google Spreadsheets
- Why all web developers should learn SEO
- Why SEOs should learn programming
- Dan Cobley: What Physics teaches about marketing
- Analytics plus SEO equals content
- The internet marketer’s guide to the apocalypse
- Follow me on Twitter
- The Real World Unscary Guide to SEO Copywriting
CEO & Founder
Ian Lurie is CEO and founder of Portent. He's recorded training for Lynda.com, writes regularly for the Portent Blog and has been published on AllThingsD, Forbes.com and TechCrunch. Ian speaks at conferences around the world, including SearchLove, MozCon, SIC and ad:Tech. Follow him on Twitter at portentint. He also just published a book about strategy for services businesses: One Trick Ponies Get Shot, available on Kindle. Read More