Discussing Decisions! Card Tables and To-Dos 

One thing i noticed about 37 signals is they are not afraid to break the normal convention and rhat is really good to see . Great insight as always

It'd be really cool to be able to 'kick over' some tasks as a way to curate cards and still have one hand washing the other

Totally agree with fresh start! In the days of dot matrix printers and 12" green monitors, the company reports took all night to print before they got to manager's desks. So we sent an email (in 1984) asking managers to cancel unnecessary reports. Barely a shift in volume! So one day we stopped sending the reports. We waited for the screams. And some screamed, so we added that report to a new list and sent it out. And then silence. Print volume went down by over 80% !! FIMO is an eternal driver :-)

This conversations are sooo amazing, not just for understanding basecamp and the decisions behind but also a glimpse to how you guys work and many other important concepts that translates to many areas for any company! Thanks for that and please keep doing it!

Thanks for explanation, still I think you're making the wrong decision here. Giving something a fresh start is definitively a valid approach that people need to consider from time to time, but forcing it is a bad onboarding strategy. Convince me that to do's are not just card table task with the most simple workflow there is: open - closed. I love you guys for trying to reinvent how things should work, it comes with very good decisions in this case also => 'blocked' is not part of the workflow, but the state of a task. True! The lifecycle of a task starts with a phase that is not really determined already that it actually should be done, but it is considered. True! In the lifecycle of a task it could be that it is determined it no longer is of any use, so it doesn't need to be done and needs to end up in its own bucket. True! Making a to do's different than card table items and make the view not interchangeable. Please reconsider!

I LOVE Card Table but I've found it's introduced a heck of a lot of duplication, frequently to extract comments and discussions from within Cards and them into other tools in other projects. I also find it's quite easy for a Card in Card Table to suffer from and quickly need to become own project ("Create New Project from Card" is a feature I wish existed on a daily basis). Quite possibly I'm using the feature wrong.

love these videos. You guys are the real deal and just getting to know how you guys think and make decisions is very valuable! Can't wait for more of these :)

Very insightful! Thanks a lot!

Love these videos and content. I love reading the book and think it has a great way forward for projects that are not just software.

I just use the card table for sprints. They are a good way of focussing everyone on a group of important tasks for a short period. Todos are just the bread and butter of GTD in project land. Also cards are a great way of showing high level progression of modules through a process. Once a whole bunch of todos are done and signed off and a module is declared finished at the stage the milestone was set, then move it along in cards. It’s a mistake to try and manage everything in cards. In Todoist this is highlighted by the number of times you switch views back and forth because it’s easier to deal with a list of there are a lot of actions and easier to focus on a card when there are a few. The two methods are required and work well together, you just need to decide what and how to use them.

Amazing podcast for founder/developers like me!

Found a way to make both worth together. E.g. our copywriting tasks are under to-dos, as we can execute across projects with the same toolkit and mental state. On the other hand, we have Card Tables for projects such as marketing campaign development.

Okay, for the six-weeks sprint and doing it quickly with only two people. But please, think about your users and their workflow. In many cases, I would love to use this new "Card Tables" feature, but I can't because you simply miss releasing its support in the public API and Webhook. Then no Basecamp integration can use it for now; Everhour, SupportBee, or our own GitLab synchronization etc... I have the impression that you went a bit fast ;-)

Looking forward to the BS3 to 4 transition episode. Pls do it :-)

I think for me there is a lot of trust that you guys are thinking through everything you build. That’s why I wouldn’t have even thought to question this 😂

As a user, this explanation doesn't make up for my frustration at the lack of this feature. I would far prefer if to-dos and cards could be integrated.

👍

My only issue is that card tables are not connected to existing to-dos (can't pull those over). So cards are great for support tickets or the general "need to see if it's assigned, in progress, or done" -> like they said...a conversion tool. But to-dos are great when someone needs to be notified when this thing is done so that they can do their tasks

How do you add multiple card tables to a project?

Ah, no import meant I fudged an import in Hey and regretted it forever.

Sounds like "it's a feature not a bug" rationalization.

Omg please build the portal! Love this idea! And you guys! :)