Why do you use 37Signals products? Simplicity, UI, Hype?
After watching various videos and seeing the growth of 37 Signals, it makes me curious why people use their applications. They clearly have less features and I don't see that as a large issue. Since they are mostly designers you would expect the UI/UX to be good. Finally I'm sure that some just jumped on their products because of the RoR hype. So if you use a 37 Signals product, why do you continue to use it?
27 comments
[ 2.8 ms ] story [ 83.9 ms ] threadIf you haven't read their manifesto on keeping things simple, you should - the 'lack' of features is intentional.
It's also easy for me to use with less technical people. As it's not overwhelming unlike some similar tools, they can start using Basecamp straight away. I don't have to sit down and give them a walk through.
I also like how it's flexible. I don't have to adjust my workflow to their software.
Analysing what those things are seems a good idea if you're trying to emulate it, and you can't do that by "Trying the app yourself". The best way, as the OP has done, is ask customers why they pay for it.
I have tried Campfire, and I'm still not quite sure why people pay for it. I think you can take simplicity too far personally. It could be replicated on a weekend (As was done at google with huddlechat) so I don't see the value proposition there. I haven't tried basecamp so maybe that's more complex.
For example, compare Highrise with Salesforce. My company (a 50 person consulting firm) is moving away from SF to HR right now, even though SF has many, many more features. Why? Because HR has all of the features we need, and most of the features we like (but don't absolutely require). And we are much, much more productive when using HR. It's easier to use. I don't have to think much when filling in information. The reports take me about 5 seconds to read and comprehend. This time savings is very valuable to me and my company - I've got better things to do than think about how to use a CRM application. The features Salesforce possesses that HR lacks, by contrast, don't have any value.
You'll get it if you just look at things through a slightly different lens. You might be getting tripped up by the confusion of effort and size with value. Value is what software has to a customer - effort is the cost software has to developers. And size is just a number. It would be nice if these three number always correlated. But unfortunately, that isn't the case.
The iPhone looks extremely simple. But it's a ruse - it's actually massively complex and a feat of engineering. It's hard to copy.
I agree, it takes a lot of thought to decide what to leave out - lack of features can be a good thing. But those decisions are not really defendable in terms of IP (Unless you complain Huddlechat 'stole' your whole UI and they roll over)
I haven't used basecamp or highrise extensively, so perhaps they make up for campfire.
I have to attribute this to Basecamp's simplicity: it doesn't do a lot of the things we want, but we can fake it for the most part. Instead of prescribing how we should be managing our projects, Basecamp takes as little information as possible and lets us decide how to use it.
So, basically, we use it because it solves problems we need solved. Same reason we use anything else.
The products are simple and obvious in their nature. That is why we use them.
Personally, I use Backpack after trying (and not liking) a whole bunch of other solutions for todo lists. I tried
- Outlook
- Pen and paper
- Simple text file
- Command line todo tool (Lifehacker)
- Remember the milk
- Google tasks
and I'm probably forgetting something, it's been a while.
I use Backpack because it's:
- Incredibly simple and intuitive to use
- Offers organization system that makes sense (pages, notes and lists - I use nothing else)
- It's easy and fast to find anything I want
- I can use it everywhere - on my phone, desktop, and the web. I use the web-based client at work and at home, also Mac desktop widget at home, and Satchel on my iPhone. The synching is seamless everywhere.
I'm not going to dignify the "RoR hype" with a response.
For collaborating on projects with clients, 37S makes a product that has limitations but the overall user experience makes it better than their competitors.
LP and Wrike both share serious access/security flaws (LiquidPlanner grants global access to anyone who is shared a workspace (clients,projects,folders) and Wrike allows anyone who is shared a virtual project folder to go on and share it with anyone - (who can easily delete the entire virtual project folder and all its children). These open, Web 2.0 collaborative ideals don't work well with a company focused on multiple client projects (all of which must be confidential).
Most of the other project management software still seems sterile, and you have no sense of who is creating it. As far as features go, if everyone on a team isn't using a feature, that feature doesn't exist anyway.
With the high profile of 37signals team, you get a sense that if anything was drastically wrong with the software, the user base will be able to hunt down Jason Fried and get the thing working again. If they're not gonna fix it, Jason Fried will be the first person to say so.
Thats straightforward, and people use straightforward as a proxy for 'good.'
Maybe we don't use it to its fullest but all it ends up doing is archiving conversation threads and being a file repository. Just looking now there are 3 month late todo items that I don't think will ever get closed. After a while every project seems to drift off of it and end up using a combination of email + bug tracking.
As far as my experience with the apps has gone they're nice, and they do work well, but I don't believe they're worth the hype. It might be that I haven't seen enough "bad" software but I've seen simpler web apps that work just as well.