What you said can be true and the parent still not be a good comment for HN. It's off-topic because 1) the guidelines say politics are off-topic, 2) the guidelines ask us not to introduce flamewar topics without anything new to say, and 3) this article is not about that.
An org publicly posted it's inner process for the benefit of the industry and was attacked randomly by a political extremist without regard for truth, damage to that org or damage to the core value of this site.
I'm sure I'll be called oppressing purplecpa's free speech just for pointing this out but no, Basecamp is not oppressive.
Someone please remind me how Basecamp is relevant?
It's a closed system that doesn't play nicely integrating with anything else... near as I know still doesn't have a Kanban board... or file versions... and search is still pretty terrifying.
I found the article to be an interesting look into an approach to project management at a small, successful software product shop.
You may not find Basecamp relevant, but they still offer a service that people pay for 10+ years after they started. How many of the Kanban board-based project management tools that exist today will still be around in 10 years?
TL;DR: They dig in like ticks with marketing folks and saddle everyone else with dated and inefficient tools. The make integrations next to impossible, exports messy, and seemingly strive to fracture teams by providing duplicate services to tools like Slack, Asana, JIRA, GitHub... etc... that all do everything Basecamp does, but better, AND also offer integrations so all your teams can play nice and work seamlessly. Basecamp is cancer. I'd be surprised if they're still around in 10 years if they don't open their platform up and make it easy to swap components in and out of their closed system.
If a team already has Slack, or Skype, or Flowdock, or HipChat, or Fleep... or any of the other 200 chat tools... now with one instance of Basecamp introduce to a team they also have to check that system for messages from the one team that uses Basecamp in their company. Not even sure you can turn that feature off... but it's inefficient to not have integrations. "One-solution-fits-all" is dead, open APIs and modular tools lead to happy teams.
I don't know enough about Basecamp, so I cannot comment on their product. But, that aside, your comment is not fair. You make it sound like competing with other products (even if they are better, in your opinion) is somehow malicious. Using terms like 'tick' and 'cancer' is just not appropriate.
If you had wasted as much time as I have using Basecamp for the last 12 years you'd understand.
I was a HUGE proponent of their software up until like 2008... when better tools came out, and each new revision of Basecamp I feel like they are doubling down on their backwards-facing, lock all the data in one place, never play nice with any other tools mentality.
I think you're overlooking who, exactly, their product is built for. Most people don't want to use ten different tools. They don't want to optimize every aspect of product management--they just want the basics to work. Most people don't understand what integrations even are. I happen to think it's a fantastic product, and so do many others. If they didn't, Basecamp wouldn't have so many paying customers!
There are certain things that I don't like about Basecamp, but I marvel at their ability to give people what they want. Instead of thinking, "This product is shit!" I think to myself, "Wow! This really taps into a need I didn't know existed in the world! I can learn from this to make better tools myself!"
I also really respect them because they've built a real business. They're profitable, are here to stay, and generally look out for their customers in the long run. They're not a company that treats their users like livestock waiting to be slaughtered for profit.
Do you enjoy not having any sort of best practices process defined in the tool because something is either "done" or "not done"? Does the concept of phases, or different disciplines working together on an issue sail over your head? Do you frequently ask things like, "Why do you need UX, and QA?" Would you rather just say, "F'in Devs are late again" without being called out on not having requirements or copy or design ready in time? Great, Basecamp is your tool.
Do you love hearing yourself talk in your daily status meetings where you go around the room asking people who would rather be working what the progress of each item is? Secretly, do you feel a tool that clearly showed the status of issues to everyone any time they logged in would threaten your job security and prevent you from looking busy when the VP came around? Great, Basecamp is for you.
Does the thought of actually understanding what is going on, getting a handle on the complexity of the modern office terrify you? And do you hate change, so much so that you still use your AOL account? When you go out to dinner, do you insist that they bring you a bladed-spork at every meal no matter the restaurant so you don't get confused as to which tool is for eating soup or cutting your steak? You'll love Basecamp!
Do you want all of your data in one place, free from being updated, or updating, or syncing, with other systems? Do you enjoy manually entering in information twice, or reducing highly skilled developers to typist / copy-paste bots? Is your favorite thing when you get to yell at others because you updated the dates or requirements in your tool, but not theirs? And, do you have no concept why tying issues to code checkins is valuable and productive for the company as a whole? Oh man, Basecamp is for you!
Then don't use Basecamp if it doesn't work for you. It's a tool made by passionate people to help other people work better. They don't claim it works for 100% of people. Why all the anger toward them?
Do you consider yourself to be an empathic person, able to understand their needs? I sincerely hope not. The inability of tech-focused people like yourself to understand that the group of people really give a about the latest tools is astounding.
While there are thousands of companies who want an open, modular system, there are tens of thousands more who could care less about what an 'API' is, what an 'integration' is, or getting fancy SAAS tool A to work with fancy SAAS tool B.
These companies only care about how a tool can help them run a better business, and for that, they're going to look for a single solution that does everything they want. They absolutely will not be looking for 5 tools they can string together to make some Frankenstein 'solution'. And hat's off to them for that, the sooner they realize their business is not a special snowflake the better.
Through contracting, I've been exposed to just about every tool, and combination of tools out there over the last 20+ year as a project / product manager.
Basecamp is cancer. There isn't a team around that wouldn't be better off on Asana, or GitHub + ZenHub, or Atlasssian, or Trello... or anything else.
Would gladly dedicate 5 hours per week in training people on alternatives for free, if it meant I never had to go into a client's office who used Basecamp. The amount of busy work and slop and inefficiency it allows... I get people are blind to better options, but seriously spent a few hours researching and trying the tools. A stitch in time saves nine... measure twice, cut once...
Please compare it to using other tools and see for yourself.
It looks like Basecamp would fit really nicely into our product process, and I think we have a relatively good process. It might not be for everyone, but I don't think it's fair to rule it out for all give your personal experience.
>>> The amount of busy work and slop and inefficiency it allows...
(Disclaimer: I've not used it in a business setting, but do roughly know my way around because we have a "family Basecamp" for some projects)
Have you considered the possibility that something that allows for a bit of "slop and inefficiency" might make for a more pleasant, and perhaps even a more productive, working environment than neo-Taylorist perfection does? I'm not actually 100% sold on the product myself, but the way it's pitched (e.g. "Work can wait") is pretty refreshing in the contemporary marketplace.
It's a tech company that needs to structure its work and teams. So it might be able to speak to a technical audience about - surprise! - structuring its work and teams!
Fantastic article. I find the idea of cycles being pretty core to this. Jason mentioned it in more detail in a comment below, but the fact a stakeholder can't sway an ongoing project until its cycle is finished is huge.
I work on a small team building IT and IS infrastructure for a very sales-oriented business. Stakeholders are always throwing in a new twist at what feels like the most inopportune times. If we could tell them we'll consider it on the next formalized cycle that would be huge for preventing redirections. Stakeholders may not acknowledge it themselves, but they care less about what gets done and more about when. Closing that feedback loop we always be more effective than feature creeping a project into oblivion.
The concept of large and small pieces of work, and having developers rotate between them in naturally forming teams I found to be excellent for morale and hence productivity.
Also once a cycle is locked in, it's rarely adjusted. And no timesheets.
Really basic things that IMO Basecamp is doing a great job advocating for in an industry that still needs it.
Ever since Getting Real (https://gettingreal.37signals.com/) I've agreed with practically everything Jason Fried has ever said. Wish there were more CEOs like him.
29 comments
[ 3.3 ms ] story [ 76.1 ms ] threadI'm sure I'll be called oppressing purplecpa's free speech just for pointing this out but no, Basecamp is not oppressive.
Someone please remind me how Basecamp is relevant?
It's a closed system that doesn't play nicely integrating with anything else... near as I know still doesn't have a Kanban board... or file versions... and search is still pretty terrifying.
You may not find Basecamp relevant, but they still offer a service that people pay for 10+ years after they started. How many of the Kanban board-based project management tools that exist today will still be around in 10 years?
TL;DR: They dig in like ticks with marketing folks and saddle everyone else with dated and inefficient tools. The make integrations next to impossible, exports messy, and seemingly strive to fracture teams by providing duplicate services to tools like Slack, Asana, JIRA, GitHub... etc... that all do everything Basecamp does, but better, AND also offer integrations so all your teams can play nice and work seamlessly. Basecamp is cancer. I'd be surprised if they're still around in 10 years if they don't open their platform up and make it easy to swap components in and out of their closed system.
If a team already has Slack, or Skype, or Flowdock, or HipChat, or Fleep... or any of the other 200 chat tools... now with one instance of Basecamp introduce to a team they also have to check that system for messages from the one team that uses Basecamp in their company. Not even sure you can turn that feature off... but it's inefficient to not have integrations. "One-solution-fits-all" is dead, open APIs and modular tools lead to happy teams.
I was a HUGE proponent of their software up until like 2008... when better tools came out, and each new revision of Basecamp I feel like they are doubling down on their backwards-facing, lock all the data in one place, never play nice with any other tools mentality.
There are certain things that I don't like about Basecamp, but I marvel at their ability to give people what they want. Instead of thinking, "This product is shit!" I think to myself, "Wow! This really taps into a need I didn't know existed in the world! I can learn from this to make better tools myself!"
I also really respect them because they've built a real business. They're profitable, are here to stay, and generally look out for their customers in the long run. They're not a company that treats their users like livestock waiting to be slaughtered for profit.
Do you enjoy not having any sort of best practices process defined in the tool because something is either "done" or "not done"? Does the concept of phases, or different disciplines working together on an issue sail over your head? Do you frequently ask things like, "Why do you need UX, and QA?" Would you rather just say, "F'in Devs are late again" without being called out on not having requirements or copy or design ready in time? Great, Basecamp is your tool.
Do you love hearing yourself talk in your daily status meetings where you go around the room asking people who would rather be working what the progress of each item is? Secretly, do you feel a tool that clearly showed the status of issues to everyone any time they logged in would threaten your job security and prevent you from looking busy when the VP came around? Great, Basecamp is for you.
Does the thought of actually understanding what is going on, getting a handle on the complexity of the modern office terrify you? And do you hate change, so much so that you still use your AOL account? When you go out to dinner, do you insist that they bring you a bladed-spork at every meal no matter the restaurant so you don't get confused as to which tool is for eating soup or cutting your steak? You'll love Basecamp!
Do you want all of your data in one place, free from being updated, or updating, or syncing, with other systems? Do you enjoy manually entering in information twice, or reducing highly skilled developers to typist / copy-paste bots? Is your favorite thing when you get to yell at others because you updated the dates or requirements in your tool, but not theirs? And, do you have no concept why tying issues to code checkins is valuable and productive for the company as a whole? Oh man, Basecamp is for you!
To be absolutely honest: yes.
While there are thousands of companies who want an open, modular system, there are tens of thousands more who could care less about what an 'API' is, what an 'integration' is, or getting fancy SAAS tool A to work with fancy SAAS tool B.
These companies only care about how a tool can help them run a better business, and for that, they're going to look for a single solution that does everything they want. They absolutely will not be looking for 5 tools they can string together to make some Frankenstein 'solution'. And hat's off to them for that, the sooner they realize their business is not a special snowflake the better.
Basecamp is cancer. There isn't a team around that wouldn't be better off on Asana, or GitHub + ZenHub, or Atlasssian, or Trello... or anything else.
Would gladly dedicate 5 hours per week in training people on alternatives for free, if it meant I never had to go into a client's office who used Basecamp. The amount of busy work and slop and inefficiency it allows... I get people are blind to better options, but seriously spent a few hours researching and trying the tools. A stitch in time saves nine... measure twice, cut once...
Please compare it to using other tools and see for yourself.
(Disclaimer: I've not used it in a business setting, but do roughly know my way around because we have a "family Basecamp" for some projects)
Have you considered the possibility that something that allows for a bit of "slop and inefficiency" might make for a more pleasant, and perhaps even a more productive, working environment than neo-Taylorist perfection does? I'm not actually 100% sold on the product myself, but the way it's pitched (e.g. "Work can wait") is pretty refreshing in the contemporary marketplace.
I work on a small team building IT and IS infrastructure for a very sales-oriented business. Stakeholders are always throwing in a new twist at what feels like the most inopportune times. If we could tell them we'll consider it on the next formalized cycle that would be huge for preventing redirections. Stakeholders may not acknowledge it themselves, but they care less about what gets done and more about when. Closing that feedback loop we always be more effective than feature creeping a project into oblivion.
Also once a cycle is locked in, it's rarely adjusted. And no timesheets.
Really basic things that IMO Basecamp is doing a great job advocating for in an industry that still needs it.