It’s been a while since I posted anything that wasn’t related to Salesforce, hasn’t it? Here’s something a little different, but still cheerleading technology and tools I like, which I used to do a lot more of.
Over 3 years ago, I wrote a blog post about my quest to find decent project management software for Fight Colorectal Cancer. That post was quite popular for a while and still gets a fair number of page views. Commenters either sympathized, or used the post’s page rank to promote their own wares.
Right around the time I started at KELL Partners last year, I helped our team implement Smartsheet as our main tool for keeping track of timelines, requirements and deliverables with clients and internal projects. Truth be told, had Smartsheet existed in this form 3 years ago, I wouldn’t have been so frustrated. It meets all the requirements I mentioned in that post and then some.
Right now we have 389 active sheets in our Team account. I’ve been asked a few times, “Why Smartsheet? Why aren’t you just using Google Docs?”
Yes, some of what we’re doing in Smartsheet could be done in Google Docs. But aside from the fact that KELL doesn’t use Google Apps so documents wouldn’t be centralized and owned by the company, Smartsheet does so much more than just flat spreadsheets. Every time I use it, I find some cool new way to make it work better.
What is Smartsheet? It’s an Excel/Google Doc-like online app that generates spreadsheets that are more dynamic than just rows & columns. In addition to spreadsheets, there’s quite a bit of Microsoft Project thrown in (it can even import Project files). The interface is very simple to learn and use, which makes it ideal for sharing with clients of all technical backgrounds. You need a paid account to create sheets after the free trial expires. But those sheets can be shared with anyone, either through a named user or through a publish link that anyone can view if they know it.
Here’s why I think Smartsheet is a better choice than Google Docs for team collaboration, so I can just point to this post in the future.