I hope this short essay helps anyone trying to monitor site uptime or pipe any kind of alerts into Teamwork Chat.
Many of you may know that Foliovision began as a client service agency and not a software company. Our first big service was migration from Typepad to WordPress. We were literally doing dozens of migrations a month at one point. Project management in bulk was essential to the premium client experience we wishes to offer.
We started with Basecamp but eventually outgrew it (there’s a long post about our Basecamp to Teamwork migration) and moved to Teamwork (back then TeamworkPM). Teamwork Projects at the time had a much worse design than Basecamp (latest version looks pretty good and even allows CSS customisation) but lots more tools (recurring tasks was a big one for us) at the time. As happy as the upgrade in features made us at the time, there was still one key feature missing. Later we called this feature Observer Status.
Christmas came early in 2015 for Foliovision. On St Patrick’s Day actually. I got the email from Teamwork to tell me Observer Status had gone into beta. Believe it or not, Observer Status is finally here in Teamwork and it’s awesome.
Observer Status will change the lives of smaller service driven agencies growing into larger agencies.
Let me start by telling you why we want Observer Status.
Our main project management tool is Teamwork as you may know. Teamwork is a great tool with all kinds of advanced functionality. Alas often the basics don’t work. In this case Message subscription management.
I’ve written to TeamworkPM about five or six times about their incompetent management of message subscriptions. In the bad old days (pre-thrashing by Foliovision), TeamworkPM tried to make everyone subscribe to every message. It was hell. Clients emailed our entire team (up to 35 people at a time) for the smallest issue. We couldn’t get any work done.
37signals don't do client work anymore and live in a bubble. If you face clients and billing, TeamworkPM is a much stronger solution.