Nothing adds credibility to a software company more than the fact they actually use their own product daily. I've worked for software companies, where I couldn't use the software itself for my daily activities and it become an exercise in frustration for both end user and the dev team, to understand what they should be working on next. Having never used the product before, this walkthrough helped me understand how I could actually use this tool to replace a load of sporadic platform solutions currently in use. Cheers.
Amen to that. We build Basecamp for us - and you. We've been using it daily for 18 years to build our company, build our products (Basecamp ad HEY), etc. It's the center of everything we do. -JF
Very cool. I love how you’re using card tables. Thanks for showing us how you’re using Basecamp. Your point about keeping conversations within context instead of spreading them out over different tools is spot on.
This is dope! Have learnt so much from these videos. One potential suggestion --> having the not now section or all other drop targets update their state to show the lined border as soon as you try and drag an idea. This will be more for newer users to basecamp's products. A visual tell letting them know "Hey you can drop me over here"!
This is the Basecamp I've been waiting for. The 'KANBAN' (sp) is something I always wanted in BC, now you've done it to a level that only 37S can do! THANKS!
Card Table 😍 Can you explain a bit about the journey of a card from the initial Shaping Ideas area to an actual pitch? Mostly interested in WHERE discussion happens to move that from “Hey, got an idea…” to “That’s interesting, keep fleshing it out” to “Let’s write this up in a pitch”. Where does that back-and-forth dialogue typically happen? In the card itself?
Jason thank you for sharing. A few questions: - How does the team arrive at the appetite and why might that vary from the estimate to complete the work ? - How are the pitches shared across ‘spaces’ ? In your example a core group authors pitches initially within the product strategy board. It seems the lifecycle of a pitch is also then tracked in this space. Is it the same pitch instance that is shared and tracked in the product management board or is it duplicated ? - How did this process work when building a new product like Hey ? I assume there were a number of table stakes capabilities that needed to be in place before the product could go live. Do those go through the same pitch process and cycles or did the team follow a different approach ?
Thanks for this Jason! Really love seeing how you all handle this. What do you do if a cycle’s work finishes early (4 weeks but was in a 6 week cycle)? And do you put the quick-wins in the small batch group or are they just for cool down phase?
This is great stuff, but from what I saw, I feel like the context is still separated between many places. Kanban, global chat, and docs. Not sure if there is a way to link these separate things for easier backtracing.
It's fantastic to see that you use the product to build itself ☺ I struggled a bit with the vertical writings on the first panels in the dashboard. I guess the brain starts reading a color at some point. As the widgets are almost squared any reason to not keep them stacked horizontally?
The vertical panes on the dashboard exactly mimic the layout inside the Card Table. Once you're using the tool it all makes sense, and it's nice to see things there same way at the macro and micro level. -JF
Really great to see your thoughts and processes here in a real environment. This is really connecting the dots for me from the Shape Up book principles to application. I want more raw videos like this of 37signals using Basecamp to work. Good stuff 👍 What tool are you using for your fat-marker sketches?
Wonderful, great to hear. I either use paper and scan it (I still prefer the feel of marker on paper to stylus on glass), or use GoodNotes. But it really doesn't matter. Could use a kid's drawing tool - which is exactly the point. Details do not matter at this stage. -JF
I would love to see this walkthrough before you had the kanban boards. We are running our own shape up in Basecamp but it is much noisier. Looking forward to the new tool.
We'd just use to-dos or purely use documents and move them between folders. Ran it like that forever, but with Card Tables it's a whole lot easier. -JF
Very interesting, thanks for putting this together. Does Basecamp ship with templates to build something like this out of the box, or is it more of a blank canvas? How straightforward is it to put something like this together starting from scratch? I’d certainly be interested in a walkthrough of different examples use cases if you have the time and think it’s worthwhile.
Great question. This takes just minutes to set up. I'll record another video showing just how quickly you can build out a project like this. And yes, you can create templates for recurring projects. -JF
Just made another video showing you how to make this project. Super fast, super easy, super powerful in just a minute or so. ruclips.net/video/cy71IipntCY/видео.html
Question or maybe more of a suggestion - would it be possible to perhaps provide a walk through how a company, who is addicted to the rubbish Microsoft products, might possibly use Basecamp (and other tools) to slowly ween themselves off of their reliance of Billy Gates?
Could you possibly add a PULSATING/GLOWING feature for projects IN ACTION or IN PROGRESS?? I still cannot understand why NONE of these boards have a feature like that to EASILY see what's "in progress" to give it a feeling of LIFE. like a heart beat. That would 100% SELL ME!!
Curious how flexible Card Tables are for non-software-dev teams. This is the first feature I've seen in Basecamp that feels not so universal. I can understand having different views for todos, e.g. kanban and timelines which I'm sure I'm not the first user to request, but it feels like this feature may be so opinionated it may not be adaptable for those not following the Shape Up method. I realize the point of the video is about product strategy at Basecamp not this particular feature, but since the cat is out of the bag...
Wildly. It's workflow - every kind of business has those. Has zero to do with Shape Up - it has everything to do with work that comes in, is considered, and then enters a workflow (or not), and then is completed (or not). -JF
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
Nothing adds credibility to a software company more than the fact they actually use their own product daily. I've worked for software companies, where I couldn't use the software itself for my daily activities and it become an exercise in frustration for both end user and the dev team, to understand what they should be working on next. Having never used the product before, this walkthrough helped me understand how I could actually use this tool to replace a load of sporadic platform solutions currently in use. Cheers.
Amen to that. We build Basecamp for us - and you. We've been using it daily for 18 years to build our company, build our products (Basecamp ad HEY), etc. It's the center of everything we do. -JF
Very cool. I love how you’re using card tables. Thanks for showing us how you’re using Basecamp. Your point about keeping conversations within context instead of spreading them out over different tools is spot on.
Thank you so much for sharing this and I am SO excited for the new tables!!!! Keep it up!
Excellent info. Thanks. Looking forward to getting Card Tables. And evangelising Basecamp to anyone who'll listen! ☺
Thanks Ian! Very much appreciate that.
This is dope! Have learnt so much from these videos. One potential suggestion --> having the not now section or all other drop targets update their state to show the lined border as soon as you try and drag an idea. This will be more for newer users to basecamp's products. A visual tell letting them know "Hey you can drop me over here"!
This is the Basecamp I've been waiting for. The 'KANBAN' (sp) is something I always wanted in BC, now you've done it to a level that only 37S can do! THANKS!
So insightful to see how basecamp uses basecamp 😊
Loving this! Looking forward to the Shaping tool, I know we'll be using it immediately.
The tool itself is called Card Table and we're finishing it up for everyone now. Stay tuned! -JF
Great walk-through! Super inspiring. I love how you are keeping everything in one place and in context.
Thanks Lars! -JF
Card Table 😍 Can you explain a bit about the journey of a card from the initial Shaping Ideas area to an actual pitch? Mostly interested in WHERE discussion happens to move that from “Hey, got an idea…” to “That’s interesting, keep fleshing it out” to “Let’s write this up in a pitch”. Where does that back-and-forth dialogue typically happen? In the card itself?
Very insightful, Jason, thanks for sharing.
Digging the new Card Table feature. I do something similar in Trello. Might be time for a switch!
This looks stunning.
Thanks Mischa! -JF
Jason thank you for sharing. A few questions:
- How does the team arrive at the appetite and why might that vary from the estimate to complete the work ?
- How are the pitches shared across ‘spaces’ ? In your example a core group authors pitches initially within the product strategy board. It seems the lifecycle of a pitch is also then tracked in this space. Is it the same pitch instance that is shared and tracked in the product management board or is it duplicated ?
- How did this process work when building a new product like Hey ? I assume there were a number of table stakes capabilities that needed to be in place before the product could go live. Do those go through the same pitch process and cycles or did the team follow a different approach ?
Thanks for this Jason! Really love seeing how you all handle this.
What do you do if a cycle’s work finishes early (4 weeks but was in a 6 week cycle)?
And do you put the quick-wins in the small batch group or are they just for cool down phase?
This is great stuff, but from what I saw, I feel like the context is still separated between many places. Kanban, global chat, and docs. Not sure if there is a way to link these separate things for easier backtracing.
It's fantastic to see that you use the product to build itself ☺
I struggled a bit with the vertical writings on the first panels in the dashboard. I guess the brain starts reading a color at some point. As the widgets are almost squared any reason to not keep them stacked horizontally?
The vertical panes on the dashboard exactly mimic the layout inside the Card Table. Once you're using the tool it all makes sense, and it's nice to see things there same way at the macro and micro level. -JF
Really great to see your thoughts and processes here in a real environment. This is really connecting the dots for me from the Shape Up book principles to application. I want more raw videos like this of 37signals using Basecamp to work. Good stuff 👍
What tool are you using for your fat-marker sketches?
Wonderful, great to hear. I either use paper and scan it (I still prefer the feel of marker on paper to stylus on glass), or use GoodNotes. But it really doesn't matter. Could use a kid's drawing tool - which is exactly the point. Details do not matter at this stage. -JF
@@37signals Ever thought about introducing 'freestyle drawing' feature directly within the Basecamp Doc?
Is normal to have a 3 week pitch? Or are non 6 week pitches an exception?
The major missing thing is automatic numbering for the cards. It' super helpful for git naming conventions.
I would love to see this walkthrough before you had the kanban boards.
We are running our own shape up in Basecamp but it is much noisier.
Looking forward to the new tool.
We'd just use to-dos or purely use documents and move them between folders. Ran it like that forever, but with Card Tables it's a whole lot easier. -JF
Legend! Super useful.
¿ do your other teams (like marketing) do this too?
Similar, but not quite the same. I'll see if I can have someone else give a tour of those. -JF
@@37signals 👆this.
@@37signals thank you!
Would be nice!
Can you share with us how your customer support team uses basecamp?
Very interesting, thanks for putting this together. Does Basecamp ship with templates to build something like this out of the box, or is it more of a blank canvas? How straightforward is it to put something like this together starting from scratch? I’d certainly be interested in a walkthrough of different examples use cases if you have the time and think it’s worthwhile.
Great question. This takes just minutes to set up. I'll record another video showing just how quickly you can build out a project like this. And yes, you can create templates for recurring projects. -JF
Just made another video showing you how to make this project. Super fast, super easy, super powerful in just a minute or so. ruclips.net/video/cy71IipntCY/видео.html
Question or maybe more of a suggestion - would it be possible to perhaps provide a walk through how a company, who is addicted to the rubbish Microsoft products, might possibly use Basecamp (and other tools) to slowly ween themselves off of their reliance of Billy Gates?
Could you possibly add a PULSATING/GLOWING feature for projects IN ACTION or IN PROGRESS?? I still cannot understand why NONE of these boards have a feature like that to EASILY see what's "in progress" to give it a feeling of LIFE. like a heart beat. That would 100% SELL ME!!
Curious how flexible Card Tables are for non-software-dev teams. This is the first feature I've seen in Basecamp that feels not so universal. I can understand having different views for todos, e.g. kanban and timelines which I'm sure I'm not the first user to request, but it feels like this feature may be so opinionated it may not be adaptable for those not following the Shape Up method. I realize the point of the video is about product strategy at Basecamp not this particular feature, but since the cat is out of the bag...
Wildly. It's workflow - every kind of business has those. Has zero to do with Shape Up - it has everything to do with work that comes in, is considered, and then enters a workflow (or not), and then is completed (or not). -JF