Last week we introduced custom color schemes to Backpack. While our customers love the new feature, we’ve also gotten questions about why we chose to build a color picker for Backpack. Aren’t there other things we could spend our time on? Why was customizing colors a priority? Actually custom colors were the latest push in a series of updates to take Backpack a level up. Here’s a look at the string of updates and how custom colors fit in to the story.
In late 2008 we decided Backpack was due for some development. The last major push was “BPMU”—Backpack Multiuser—in February ‘08. The multiuser capability gave businesses and small teams the chance to organize their lives and work with Backpack. Adding multiple users to Backpack was a big effort. As usual, we did the bare minimum necessary, but there were still a lot of details, edge cases, and challenges. By the time we launched in February ‘08, we were glad to be finished and also really excited to use Backpack together as a team.
Marinating with multiple users
The best part of building ‘as little as possible’ comes after launch. Every feature you skipped or held off on is free open space in the app for later development. Instead of a lot of baggage and maintenance, a bare-minimum release means new possibilities for feedback. After we launched BPMU in February, the customer feedback and personal experience we accumulated became a magnetic field that gradually pointed our compass for development. By late 2008, we knew where to go next.
Mere access versus real collaboration
While Backpack can do a lot of things, the core of the app is Pages. One thing we learned is that giving access to Pages isn’t enough. Notifications are the blood that keeps distributed communication alive. Plenty can happen in your application but if nobody ever gets an email notification then changes are likely to go unnoticed. So our first priority was to work notifications into Backpack Pages. On December 6 we pushed a feature allowing customers to send email notifications to everyone sharing a page after they create a page or any time they make updates to a page.
Improving permissions for multiple users
We also learned that “on or off” wasn’t enough access control for our customers. People wanted to use Pages to share knowledge with their teams, and they also wanted to be sure their knowledge was safe from unintended changes. Feedback from customers taught us that read-only permissions deserved a place in Backpack. So along with the page notification push in early December, we revised the “Make a new page” screen so that permissions could be set up-front before the page was even created. This set the stage for stronger permissions. Two weeks later we followed through with a read-only option on the permissions section of the “Make a new page” screen.
“Comments-everywhere”
We included a Messages section in the original BPMU release for discussions. In the months after BPMU’s launch, we discovered that discussions often relate to a specific task or note on a Page. It felt wrong every time we had to leave the Page we were working on to start a discussion about it somewhere else. The solution was “comments-everywhere”—a feature we actually built in September 08 for Basecamp to-dos and milestones. The change allowed customers to post comments directly to list items and notes on their Pages. These in situ discussions hit two birds with one stone. First, customers could create a discussion directly attached to the piece of content under consideration. Second, each comment in the discussion generates email notifications, which keeps teams actively involved in the app even when they don’t log in to manually check for changes. On January 17 we launched commentable lists and notes on Backpack pages.
Managing a growing collection of Pages
Team collaboration on Backpack also created an itch to organize Pages. The more people on an account, the more Pages are created. Before long the All Pages section and each person’s sidebar of bookmarked pages can become unwieldy. Two features fought back to give customers control over their pages again. We added drag-and-drop reordering to the sidebar on January 8, and three weeks later we followed up with a new feature that allows customers to add Tags to their sidebar. Tags in the sidebar give you quick access to a collection of pages on a particular topic. Both of these features have cleaned up the sidebar and helped our customers to organize their growing collections of Pages.
Topping it off with branding and ownership
All the updates from December and January were functional changes that affected the mechanics of what customers can do with Backpack. The decision to add custom color schemes at the end of our sprint was a bit different. The previous updates were about notification, permissions, and organization. Custom colors are about ownership and identification. We want teams and individuals using Backpack to feel their account uniquely belongs to them. Colors may seem trivial, but in everyday life we make choices about fabric, furniture and paints that transform the objects we acquire from the outside into “my clothes,” “my room,” and “my desktop.” Identification and intimacy of this kind improve our customer’s experience, and any way that we increase their satisfaction with a product of course benefits us as well.
But most of all, colors are fun. And in a way, the custom color picker celebrates an exciting set of improvements to Backpack and tops them off with a free interaction—one that exists only for the fun of using it.
Here’s a 500 foot view of the improvements to Backpack since December:
December 6: Page notifications and set share settings up-front
December 22: Read-only sharing, new “All Pages”, collapse checked items
January 8: Drag and drop to reorder sidebar links
January 17: Post comments on list items and notes
January 24: Bookmark tags in your sidebar
February 7: Custom color schemes
With a strong set of Backpack improvements behind us, we’re excited to turn our attention to Basecamp and Highrise in the coming months. Thank you as always for your continued support and stay tuned!
Peter Urban
on 11 Feb 09I think the branding feature is a great step forward. I differentiates BP from the more generic stuff that Google and Zoho etc. do. Way to go.
Carlos Taborda
on 11 Feb 09I understand that some people ask “why did you spend time on that and not on xyz”. However, I don’t think users get the entire vision you guys have in your product. I know customers are supposed to be right all the time, but I don’t think they need to agree with everything you guys do.
So, the customer is right, but to a certain limit.
HB
on 12 Feb 09What are the best ways to gather feedback from users during a private beta and immediately after launch?
Reuben
on 12 Feb 09Good question @HB. How does 37signals gather feedback? We have used surveys but you often get both extreme ends of the spectrum, people love you or hate you.
How do you guys get good quality feedback that you can use to drive your next feature decisions?
JF
on 12 Feb 09HB/Reuben: Gathering feedback is maybe the easiest thing we have to do. Everyone has opinions and they get them to us in a variety of ways. Email, forum posts, Twitter, surveys, blog posts, blog comments. We hear from thousands of people every year.
All feedback is good feedback, but like anything, it has to be weighted and considered in context. Context includes other feedback as well as our own plans and vision for the products.
Mike Rundle
on 12 Feb 09I’m a little confused by this post. Surely you didn’t write your own color picker but instead used a Prototype/Script.aculo.us plugin?
There are so many great drop-in color pickers out there, was it worth the time to reinvent the wheel?
JF
on 12 Feb 09Mike, we wrote our own. Details in the announcement for Basecamp. Check the comments for more details about why we weren’t happy with the off-the-shelf ones.
SS
on 12 Feb 09Mike, there’s a lot more to making Backpack’s Color settings page work than just dropping a color picker plugin onto a page. (We did reuse the JavaScript component we wrote for Basecamp.)
David Wagner
on 12 Feb 09I like your post here on Product Decisions; however, can you please comment on your decision NOT to put a calendar (like the one in Backpack) into Basecamp. From the forum entries that I have seen this has been an overwhelming request by many, many Basecamp customers. I have been a Basecamp customer for a few years now and after numerous inquires to this question I have not received an answer.
pwb
on 12 Feb 09Mike Rundle, the mind-boggling truth is that there are ZERO decent color pickers available. Here is one of the worst: http://developer.yahoo.com/yui/colorpicker/
pwb
on 12 Feb 09Wow, they went with the same horribly difficult to use color picker as YUI. I don’t see anyone can like this color picker. Is it similar to PhotoShop or some other app I’ve never used?
Adam
on 12 Feb 09@pwb: Yup. It’s very similar to Photoshops. Perhaps not the most user friendly in a web context, but lots of people will be familiar with the layout.
Matt Henderson
on 12 Feb 09I’m wondering why you haven’t ditched Writeboards in Basecamp in favor of Pages. I, and most people I know, find Pages far more useful (especially given the features you mentioned above).
In our organization, Writeboards are almost never used, because of the 15 or 20 seconds it takes to simply load them. It feels like that experience when you call customer support of a company in the US, and spend a few moments listening to VoIP clicks and pops as you’re routed to a call center in India.
Keith
on 12 Feb 09Well I can say that everything that has gone into the BP changes in the last few months has been really appreciated! Great work, and the color pickers on BP are bar none the best for doing something simple because they are quick and give you an easy way to replicate colors between different elements with the HTML color codes.
Michael
on 12 Feb 09I’m praying Highrise gets the attention before Basecamp, even though it probably won’t.
Matthew Scott
on 12 Feb 09@37 Signals- I’ve been using your suite of applications for a year now.
I’m saying what you have already heard so many times…but, I’m so impressed with your consistent and constant improvements based on feedback.
I think I finally get it (I’m slow)...the blog and live Justin.TV are constant sources of seeking to listen to your customers and in-turn build a loyal customer following.
I will be one of those customers.
In a world of crappy & over-engineered web applications, I thank you for being “everything” we need vs. what everyone wants.
Jim
on 12 Feb 09I question this post. You meant to explain why colour picker was chosen as part of a “Grander plan” of sorts.
But then you mention that the “decision to add custom color schemes at the end of our sprint was a bit different,” and I would argue doesn’t relate to the other issues above. It seems more a “hey, that’d be neat” free interaction of which you speak.
zephyr
on 12 Feb 09I used have this theory that users of applications liked to change colors because they felt they had very little control over the rest of the application. I guess I have to reconsider…
jd
on 13 Feb 09For mere mortals, Photoshop-style color pickers totally suck.
Murphy
on 13 Feb 09I always thought it was kind of odd that Backpack had such a limited color picker, so I’m a touch giddy to try it out. It’s a little thing, apparently too little for some people to consider important, but I think it makes a big difference. What was that word again… Fun?
This discussion is closed.