We’ve been using Basecamp at artifakt Digital since day 1. I think it was even one of the very first tools I added to our workflow when first setting up artifakt, which I probably found by Googling ‘Website Project Management Apps’.

Project management is pretty key for me; I’m a bit of a nerd when it comes to project management workflow, and it became apparent to me as I began to manage more and more detail-orientated projects that #Basecamp just wasn’t cutting it for me anymore, and that it wouldn’t satisfy my compulsive, obsessive-like view of project management.

Where Basecamp Worked Well

Basecamp’s beauty is in its simplicity; and Basecamp does that really well. A main part of Basecamp’s philosophy is to limit what features they add, keep it super-simple, and instead, focus on providing a base project management tool that’s easy to use and simple to set up, and that it certainly is. It’s dead-simple to begin managing projects, onboarding new people (even those with limited technical ability), and get setup and running in no time at all.

Where Basecamp Fell Short

In my opinion, simplicity has its drawbacks though; for one, Basecamp was just too simple. I remember about 6 months ago they finally introduced the ability to have a task list that you could identify as one that anyone you identified ‘the client’ couldn’t see. How we worked for so long without that feature is really beyond me. But even this feature was a bit too simple as you could only limit it to the group you identified as ‘the client’, and not individual people instead.

Basecamp is a bit spammy too, or so most of the people on our team and clients say (it’s even earned the nickname of Spamcamp internally). It has a habit constantly emailing the people involved on a project when tasks are added, when a comment is added to a discussion, etc. Most of the time, I’m told, the emails they get have nothing to do with them at all, so they end up deleting it, and inevitably, ignoring Basecamp emails all together. One person on a project we were working on actually had an email folder called Spamcamp with a rule that sends Basecamp emails there to keep his inbox clean!

Finding Something New

I’m always looking for new tools that will improve our workflow, so of course I’d thought about changing project management software before, but couldn’t find anything I really liked; until I met Teamwork.com, and it was basically love-at-first-sight for me.

Screen Shot 2014-06-10 at 3.58.40 PM

Teamwork.com is some serious project management. If I could send all of my feature requests to Basecamp over the years, and they actually implemented them, I’d have something like Teamwork.com already. It fills all of the holes that I thought Basecamp had, and it still presents all of the information to everyone in a way that’s easy for everyone on the project to understand.

Some of things Teamwork.com does that I really like are:

  • It sends way less emails: It has a really nice daily email that gets sent with the information people need, and, when it’s created, it lets you decide whether a task, task list, etc should send a notification email to everyone involved or not.
  • You can make multiple people accountable: When you’re creating a task, milestone, etc, you have the ability to assign it to multiple people, instead of being limited to one.
  • You can set project milestones: Milestones can be set to let you know if everything is moving along at the pace you want it to.
  • It’s private when you want it to be: When you’re creating task lists, tasks, etc, you can control the privacy so that you, your team, or your client can see as little or as much as you need them to.
  • You can set dependencies: If you have a task that you’re creating that is dependent on another task being completed, you can indicate that so that the task cant be marked completed unless the dependent one is.
  • It has a high-level view of projects: Once you set the milestones and the project’s start and end dates, the Project Chart view gives you a bird’s eye view of what’s going on and where each project should be to be completed on time.
  • They listen: I’ve sent a bunch of requests to the folks at Teamwork.com; some they implemented, some they didn’t, but they always acknowledge the feature request. The bottom line is that they listen to what the community wants, and implement it if it makes sense to.

We’re really loving using Teamwork.com so far. If you want to check it out, click here to use our referral link (which we’d really appreciate).

– Andre Bodnar

- Andre Bodnar, Managing Partner of Creative


Your email address will not be published. Required fields are marked *