Be careful not to throw your weight around without knowing it.
Yesterday I was in a board meeting for a company I advise. Great group, strong business, profitable, all the good stuff. But the owner-CEO was stuck. He felt like he’d laid out a pretty clear vision and direction, but people’s priorities kept shifting. This thing was important, then all the sudden it was this other thing. Lots of bouncing around, not quite enough focus. He didn’t know what was causing it, but it turns out it was him. But how?
We dug into it. As we went, I recognized the problem.
As much as we’d like to pretend we’re just one of the crew, the owner is the owner. And when the owner makes a suggestion, that suggestion can easily become high priority. It’s rarely what the owner intends, but it’s often how it’s received. When the person who signs your check says this or that, this or that can quickly become the most important thing.
It’s like the old EF Hutton ad “When EF Hutton talks, people listen.”
So something as minor as “Are we doing enough on Instagram?” can shoot Instagram to the top of the marketing priority list. It was a mere suggestion, but now it’s a mandate. “Why would he be talking about Instagram unless he really thought Instagram was super important?”
What’s worse is when the owner finds him or herself in the weeds. Meddling too much in this problem or that problem. If that’s where they’re spending their attention, people assume it’s top priority. It may be a mere curiosity, but that’s not the impression it makes. If she’s looking over there, then we should be looking over there. The owner’s presence in a problem area can re-prioritize the organization’s plate without intending to.
And that’s just one example. But owners like to lob ideas all over the organization, and often many at the same time. You can think of them as tiny pebbles being tossed into a pool. When the pebble hits the surface, it radiates small waves. If you’re in that pool, you’ll be affected. A splash over here sends waves this way, a drop over there sends them in another direction. Before you know it, the stillness is broken up by intersecting rings of water. It can get chaotic pretty quickly. And after a while, it’s unclear where all the action started, it’s hard to trace. It’s just busy, churning water. It takes a long time to settle it back down again.
So if you own the place, be careful what you say and when you say it. Most of the time your word carries more weight than you wish. Reserve that weight for when it’s really necessary.
How to spend your time when there’s nothing left to do?
This morning something happened that reminded me of an important lesson re: time well spent.
Three of us are working on an illustration project for our forthcoming book, “It Doesn’t Have to be Crazy at Work”. In our previous books, we had an illustration per essay. This time we’re going in a different direction. Rather than an illustration per essay, we’re aiming for ~15 full page spreads spaced evenly throughout the book.
We’re going to be illustrating historical and contemporary figures with work methods that line up with our point of view on work. People who’ve done big important things without pulling all nighters, working crazy hours, or forgoing leisure for the eternal hustle.
Here’s an early example of a spread:
We like the direction, and so does our publisher. We’re going for it. So now we’re off to find interesting subjects to illustrate and feature. It’s research time. That means there’s going to be some design downtime — a gap in the project for the designers.
Now, back to what happened this morning… The designer leading the layout charge offered to continue to explore layout concepts while we look for more subjects to feature. He wanted to tweak the layout on the right, add some more details to fill out the space, etc. We’re happy with it, but could we be even happier with it? The tweak muscle yearns to be flexed!
That’s a perfectly natural reaction. Certainly there’s always room for improvement. And there is always more to explore. Always.
Always is the problem.
The always option is where you turn time well spent into time wasted. That time could be used on other projects that need attention, rather than projects that desire attention. The layout above is perfectly fine — it doesn’t need tweaking now. The designer may desire to tweak, because designers love to design! There’s a tendency to keep pushing the thing you’re on because you’re already in the middle of it. Natural. But it’s on us to inject a sense of enough so we don’t sink good time into something that doesn’t need it. Going from 99% to 100% is expensive. I’d rather we spend that 1% going from 0% nothing to 1% something (or 50% on the fence to 51% conviction) on something else.
So I gently reminded him that we’re all good here. He did great work, the layout looks great, and there’s even a risk of fucking up a good thing (it’s always easier to fuck up a good thing than to fix a bad thing). There’s more to do elsewhere, and his time would be better spent on those things.
He agreed. We’ll come back to the layouts once we have new subjects to illustrate and design. And maybe then we’ll see a different way forward once we have more examples in front of us. Now isn’t the right time to continue to tweak. Let’s wait to see if new ideas pop up via new work that has to be done rather than revisiting what we’ve already done.
When we launched Basecamp 3, we introduced a new way for client services firms to work with their clients. We called it the Clientside. It was an entirely separate part of a Basecamp project where all client-facing communications lived. Essentially, it was a mini project within a project — a distinct space with separate tools and a different interface.
Conceptually it made sense, but practically it was inflexible and not collaborative enough. It worked well for some people, but it missed the mark for far more. We fell short of what we hoped we’d be able to create.
So we put our heads together and spent a couple months working on a complete revamp. Today we’re introducing something better.
Introducing Clients in Basecamp!
Starting today, not only can you send messages to clients, but now you can work with clients using all the same tools you already use with your team. That means you can assign clients to-dos, share files and folders, schedule events and meetings, chat around the Campfire, and even ask clients automatic check-in questions! If you can do it with your team, you can do it with your clients. And now it all happens in the same place as the rest of the project — no more separate Clientside. It’s everything you’ve been asking for.
You’re in 100% control of what clients see. Clarity and privacy is at the core of this new feature. That’s why everything in a project is now labeled as “private to our team” or “the client can see this”. Plus, to reduce anxiety and prevent “oh shit, they weren’t supposed to see that” moments, everything in a project starts off as private just to your team. When you’re ready to share something — a message, a to-do, a file — just flip the switch:
Whenever you post something new, you’ll have the option to specify if the client should be able to see it or if it’s private just to your team:
For example, here’s a to-do on a to-do list the client can see. It’s also assigned to Victor, your client:
And here’s a message thread about a revised headshot. The client can see it, and they’ve responded below:
And here’s an email you’ve forwarded in that you don’t want the client to see. It’s been marked private for your team only:
And finally, here’s a combination of files and folders. The client can see some folders, but not others. For clarity, only the ones they can see are labeled with the “The client sees this” tag:
Log-in or email-only — It Just Works!
We all know how hard it can be to ask a client to get used to using a new system. Even an easy system like Basecamp 3. So, Basecamp works even if your clients don’t want to learn anything new. Clients can respond to Basecamp messages right from their inbox, and new email they send you can be forwarded to Basecamp where your whole team can see them. Regardless if whether a client logs in and posts something directly to Basecamp, or they respond to a message via email, you’ll always have everything in one organized place inside the Basecamp project.
Fantastic! How do we turn it on?
Go into a project, click the “Add/remove people” button. This is the same way you’d invite anyone to a project:
2. Then click the green “Add people” button and select “Invite a client to the project” from the bottom of the menu.
Now you’re off and running. Any existing content will be private, and anything new you add to the project will give you the option to mark something as private or visible to the client.
Back to the future?
If you’ve used Basecamp Classic or Basecamp 2, this new setup may ring a bell. You’d be right — it’s based on a similar approach. What’s changed is both the interface and the default privacy setting. In Classic and 2, everything in a project was visible to a client until you marked it private. Problem with that was that you could easily make a mistake and reveal something you didn’t intend to. But then it was too late. That’s why in Basecamp 3 we’ve flipped it. Everything is private by default. You have to expressly give a client permission to see something. It’s much safer this way. Less anxiety ahead.
What if we liked the Clientside?
If you’re an existing customer that used the Clientside in the past, you can continue to use it on any project in your account. It’s no longer an option for new customers, or for existing customers who’ve never used the Clientside before, but if you have, and you still prefer it, it’s all yours. You can even use the Clientside on existing projects and the new way on new projects. Further, if you relied heavily on the Approvals feature, you’ll want to continue to use the Clientside as there’s currently no equivalent feature outside the Clientside.
This is a big change, a big deal. We think you’re really going to like it. You’ll have the power and flexibility to collaborate with clients in true Basecamp style without any of the limitations imposed by the previous Clientside approach. And most importantly, you’ll always have 100% control over what messages, to-do lists, folders, files, Campfire chat, and automatic check-ins your clients can see and participate in. This way you can keep the private work private, and the shared work visible — all in the same project so everything is organized together.
Questions? Comments? Post ’em below. Thanks again for using Basecamp 3!
For years people have been asking us how. How do you design things? How do you code things? Why do you do it this way vs. that way? How do you think about writing? How do you think about what makes it into a product and what does? How do you decide which features to build and which ones not to? How do you stay up on everything that’s going on in your business?
We’ve written about these topics for years — and we’ll keep writing about them — but we want to bring some show to the tell. So we started a new YouTube Channel called Getting Real. To start, DHH and I will be posting occasional videos of actual day-to-day work. Down the road other people at Basecamp may join in.
You in business? What are you doing to last? Not to grow. Not to gain. Not to take. Not to win. But to last?
I wouldn’t advocate spending much time worrying about the competition — you really shouldn’t waste attention worrying about things you can’t control — but if it helps make the point relatable, the best way to beat the competition is to last longer than they do.
Duh? Yes, duh. Exactly. Business is duh simple as long as you don’t make it duhking complicated.
So how do you last?
Obviously you need to take in enough revenue to pay your bills. But we’ve always tried to reverse that statement: How many bills do you need to pay to limit your revenue requirements?
Rather than thinking about how much you need to make to cover your costs, think about how little you need to help you survive as long as you want.
Yes, we’re talking about costs. The rarely talked about side of the equation. I’m honestly shocked how little attention costs get in the realm of entrepreneurial literature.
Whenever a startup goes out of business, the first thing I get curious about are their costs, not their revenues. If their revenues are non-existent, or barely there, then they were fucked anyway. But beyond that, the first thing I look at is their employee count. Your startup with 38 people didn’t make it? No wonder. Your startup that was paying $52,000/month rent didn’t make it? No wonder. Your startup that spend 6 figures on your brand didn’t make it? No wonder.
Even today… Some of the biggest names in our industry are hemorrhaging money. How is that possible? Simple: Their costs are too high! You don’t lose money by making it, you lose it by spending too much of it! Duh! I know!
So keep your costs as low as possible. And it’s likely that true number is even lower than you think possible. That’s how you last through the leanest times. The leanest times are often the earliest times, when you don’t have customers yet, when you don’t have revenue yet. Why would you tank your odds of survival by spending money you don’t have on things you don’t need? Beats me, but people do it all the time. ALL THE TIME. Dreaming of all the amazing things you’ll do in year three doesn’t matter if you can’t get past year two.
2018 will be our 19th year in business. That means we’ve survived a couple of major downturns — 2001, and 2008, specifically. I’ve been asked how. It’s simple: It didn’t cost us much to stay in business. In 2001 we had 4 employees. We were competing against companies that had 40, 400, even 4000. We had 4. We made it through, many did not. In 2008 we had around 20. We had millions in revenue coming in, but we still didn’t spend money on marketing, and we still sublet a corner of someone else’s office. Business was amazing, but we continued to keep our costs low. Keeping a handle on your costs must be a habit, not an occasion. Diets don’t work, eating responsibly does.
Try it for a year. Think less about revenues and more about costs. In many cases they’re easier to control, easier to predict (seek out fixed costs that’ll stay the same as you grow, vs things that get more expensive as you grow), and easier to manage. But only if you keep them in mind as you make decisions about how you’re going to last — and outlast.
Fired up about a new idea, but can’t seem to get traction to make it happen? Chat rooms aren’t traction, they’re treadmills. Lots of talk without going anywhere. You need Basecamp 3 — discussions, to-do lists, schedules, the ability to hold people accountable. Don’t just talk about it, do it with Basecamp.
Accountants have FIFO (first in first out) and LIFO (last in first out). Product designers have HFEL (hard first easy later) or EFHL (easy first hard later).
No matter the project, there are things you’re more confident about and things you’re less confident about. No brainers, maybe brainers, yes brainers. Assuming you have limited time to complete a project (we spend a maximum of 6 weeks on most projects), you have to decide how to sequence the work. Do you pick off the hard stuff first? Easy stuff first? What to do?
It depends, of course. I don’t have any answers for you, but I can share some of the things we think about when deciding what to do when.
First we get our bearings.
Does this feel like a full project? Is it probably going to take all the time we have? Lots of moving parts? Does this work touch a lot of other things, or is it mostly self-contained? Do we feel like we’ve mostly got it down, or are there some material unknowns we haven’t quite nailed down yet?
If it feels big, and full, and challenging with some significant unknowns, we almost always start with the hard stuff first. The worst thing you can do in that situation is kick big challenges down the road because you’ll inevitably run out of time. You’ll either make bad big decisions that way, or you’ll push the schedule out, or you’ll work late or work weekends. All those are big no-no’s for us, so we tackle the hard stuff first.
Sometimes we start with a quick spike. We put a few days into it and see if we’re able to make any meaningful forward process. That’ll reveal if the problem is really as big as we think it is, or we’ve been overestimating the shadow of worry its been casting. But waiting until later isn’t an option. We chip away at the big rock to see if it’s sandstone that’ll break down easy, or granite that’ll require heavy machinery.
Once we have a sense of where we’re at, we think about what we need, as a team. I don’t mean what does the team need as far as tooling or technology goes, but what do we need emotionally? Do we want to slog along without any short-term visible progress, or can we grab a quick win and start to pick up some momentum? It depends — how did the last project go? Are we coming off a high or a low? If a low, maybe we should find some quicker wins to fuel the spirit. If a win, maybe we’re already feeling good enough about ourselves to go heads down without anything material to show for a few more days. The past plays a surprisingly important role in the present.
We’re currently working on some significant improvements to the way our customers work with their clients in Basecamp 3. It’s a big project, and we’ll likely be working on it over two 6-week cycles. There are unknowns — both technical and visual — but the last time we tried to tackle this problem we ended up putting a lot of work in with nothing to show in the end. We didn’t ship what we built because we 1. didn’t finish on time, and 2. didn’t feel great about what we built, and 3. didn’t want to put more time into a bad time. Therefore, this time, we ran easy and hard in parallel. The programmers worked on a hard problem first, and the designers worked on an easy one. It was a nice way pour the concrete foundation and choose the paint colors at the same time.
On the design side of things, we often try to stay away from the details early. Details can turn into quicksand. We never want to get stuck on something early on — that’s a surefire way to burn too much time on something that’s going to change later anyway. Never ever get stuck on something you just know you’re going to change later. So when we start a design project, we typically go from very big to very small. It’s a bit different from choosing hard first or easy first, but it’s still a choice. We still have to decide where to begin.
One other thing I wanted to add, but don’t know where to put: We aim to avoid feeling like we have something to prove. That’s hero language, and we don’t do hero. We do work. We have work to do. Big and small — we’re satisfied by doing good work and getting it done in the time we give ourselves up front. Heros are only satisfied by rescuing things, doing the impossible, or saving the world. We’ll leave those antics to teams that run on fumes. We’ll run on a good night’s sleep.
I wrote this essay without reading it back — a stream of consciousness burst. I’ve had a bit of writer’s block this week, so I’m trying to bust through by just writing raw thoughts and getting my fingers moving again. I hope it was helpful. Any questions?
We’re close to finishing up a refresh of the Basecamp 3 interface on web and desktop. We’re planning on launching it in the next few weeks, so we wanted to give you a thorough preview before it shows up in a browser near you.
A combination of reasons, really. One, we have some new ideas that we didn’t have when we launched Basecamp 3 a few years ago. Now feels like a good time to modernize. Two, we have some cleaning up to do. We’ve updated the product hundreds of times over the last few years, and we’ve introduced some inconsistencies and rough edges. Time to pause, clean it up, and set the stage for the next few years. And three, we think this new design makes Basecamp more enjoyable to use, and far more approachable for new customers. It was a heck of a lot of fun to do, too!
Further, we’ve always believed in following the same pattern car manufactures follow. Major model updates every few years, and mid-cycle refreshes about half way into a model cycle. Basecamp Classic (February 2004), Basecamp 2 (March 2012), and Basecamp 3 (November 2015) are our major model updates (entirely new code under the hood, entirely new designs, etc), and the Basecamp 3 refresh like the one we’re about to launch in early 2018 is equivalent to a mid-cycle refresh in the car world.
Lastly, we approached this as a refresh, not a redesign. We wanted to update navigation, page layout, typography, buttons, placement, and proportions, while still retaining a familiar Basecamp 3 feel. A freshening up, not a flushing out. We know our customers are in the middle of important work, and they rely on Basecamp to help them manage the load, so we wanted to tread confidently, but change carefully.
Let’s take a look at some screens
First let’s look at the screen that shows all the posts on the message board inside a specific project or team. The new design is wider, bolder, and more confident. Fewer floating objects, stronger left margin so text all starts from the same place, stronger callout of comment count in big blue circles, less dead space at the top of the screen, more messages visible without scrolling, etc. Before on the left, after on the right.
And now let’s compare what an actual message board post looks like. Here you’ll see a tighter layout, fewer intersecting and overlapping shapes, stronger masthead, better type, reorganized metadata, and overall better use of space. It just feels a whole lot more confidence inspiring, which is important when making company-wide announcements using the message board.
Automatic Check-ins are of the most popular features in Basecamp 3, and they’re getting a well-deserved overhaul.
Let’s look at the check-in page itself. Here’s an example from “What did you work on yesterday?”. The previous design is on the left, the new design is on the right. We’ve cleaned up the top quite a bit, and replaced an “Add your answer” button with a field you can just type directly into. We’ve tucked some infrequently used subscription options into the ••• menu, vs. having them messily exposed. And you’ll also see a hint of the new answers/comment design — individual comments are now encased in a light grey shape to hold them together and separate them from everything else on the screen.
We’ve tweaked the schedules design as well. While it inherits the new header design you’ve seen elsewhere, we’ve replaced an ambiguous “Subscribe” button with a clearer, front-and-center “Add this schedule to your Google Calendar, Outlook, or iCal…” link. Further, we’ve tightened up the header, and given things a bit more room to breathe, so the screen just feels more solid, less floaty. Before’s on the left, after’s on the right.
Project/Team home screens
We’ve put everything on a white sheet, vs directly on the background. It helps eliminate awkward negative gaps, shapes, and alignment, and it just tidies things up considerably. The page feels more sure of itself, and better organized overall.
Docs & Files
Docs & Files also get a white sheet, a new masthead, a general clean up, and the new look:
Navigation and background
You’ll see in the screenshots above, that we’ve lightened up the background. Less beige, less yellow. It’s paler, but still a trademark warm tone. We want Basecamp to feel comfortable and cozy, not cold and clinical like so much software out there.
We’ve also placed the navigation straight on the background, vs. in a strip. This cleans things up and emphases the content below rather than the navigation above. Further, we’ve added a “backsheet” behind the breadcrumb which further emphasizes hierarchy and adds some structure.
“New” buttons are also all in the same place now. The current design has them centered and big in some places, while small and top left in other places. Now they’re always top left on the same line as the headline like this:
While this remains a work in progress, and the final product may look a bit different from the previews you see here, the gist will be the same. We aimed to make the interface and user experience more consistent and predictable, the text more readable, and the hierarchy clearer and more intuitive. Further we tweaked the typeface, sizing, spacing, and proportions to make everything feel more comfortable, and removed a bunch of fussiness from the design. Overall, we feel great about where we’re headed here, and we’re eager to share the final version with everyone soon.
Thanks for following along, and thanks for all the feedback along the way. We’ve built plenty of it into the redesign.
Are you chained to the green dot? Turn it off and break free.
As a general rule, nobody at Basecamp really knows where anyone else is at any given moment. Are they working? Dunno. Are they taking a break? Dunno. Are they at lunch? Dunno. Are they picking up their kid from school? Dunno. Don’t care.
The vast majority of the time, it just doesn’t matter. What matters is letting people design their own schedule around when they can do their best work.
A couple days ago we launched Phase I of a Basecamp 3 refresh/redesign. One of the more significant changes was a redesigned nav bar at the top that consolidated the Pings, Hey, and Campfire menus into a single, unified Hey! inbox menu.
Sometimes when you push for a big change, you overstep. We overstepped, plain and simple. Our customers let us know loud and clear that Pings are a separate category of notification that continues to deserve its own special place in the nav bar. They’re right — when someone’s trying to get ahold of you directly, it’s important to elevate that above notifications that inform a whole group.
We’re sorry we let some of you down.
So today we’re bringing back the Pings menu as its own menu (Campfires are still consolidated into the new Hey menu). Over time we’ll continue to explore ways to improve notifications, but as of now, Pings live alone! We also may revisit Pings vs. Direct/Private Messages language, but that’s for another day. For now, Pings it is!
A nice silver lining is that we were able to improve the new Pings menu to include previews of the last line someone sent you. So hopefully this makes up a little for our snafu 😀.
Here’s a screenshot of the new Pings menu in action:
And the new Hey! menu is the same as before, just without Pings:
Thanks again to everyone who shared their thoughts, and for being patient and understanding while we re-evaluated our decision. Product development is a constant struggle between too much, just right, and not enough. Sometimes you get end up on the wrong side of right. While we can’t always guarantee everyone will like our decisions — it’s impossible to please millions all the time — we vow to continue to do our best to benefit our customer base as a whole. ❤️
Over the next few months we’ll be rolling out a visual refresh to make Basecamp 3 even easier to use — and more approachable for new users. Today we launch the first set of updates.
Most products get more complicated as they go. More stuff, more screens, more options, more ways to do things. It’s natural — evolution tends to create more complex creatures over time. Software development is no different.
That’s why it’s on us to push back on complexity and clutter as we go. If we’re smart about it, we can add power and clarity over time, while making everything feel simpler than before. With that in mind, we’re ready to share what we’ve been working on for you.
Phase 1 goes lives today
First things first. This initial refresh is centered around simplifying the global navigation at the top of the screen.
We’re going from this:
Simple on the surface, but there are a variety of deep changes behind the scenes. Let’s look at them…
NEW: A single, unified inbox called Hey!
Previously, Basecamp 3 had three separate inboxes: Pings for direct messages, Hey! for posts, comments, to-do assignments, automatic check-ins, @mentions, and Campfires for group chat rooms. It made technical sense as these are all different things that run at different speeds, but we don’t think the mental overhead of three inboxes was worth the trouble. Don’t we have enough inboxes in our lives already?
So we’re switching to a single unified inbox. Everything goes in the Hey! menu. Now if there’s something for you to see, there’s only one place to look. And it’s been totally redesigned.
At the top you’ll see a row of faces and a plus button. Want to send someone a private, direct message? Just click their picture, or hit the plus button and type their name if you don’t see them listed. We used to call these Pings, but we’ve renamed them Direct Messages. Same feature, more familiar name.
Below Direct Messages, you’ll see a NEW FOR YOU block. All your notifications flow into here. Direct Messages, new comments, new posts, threads, Campfire chats, @mentions, new to-do assignments, etc. If you need to know about it, it’ll line up right here. Direct Messages now have previews as well, so it’s easier to see what someone wants to tell you without having to click into it. And Campfires now show who posted the last chat.
Last, you’ll see all PREVIOUS NOTIFICATIONS. Once you read something in NEW FOR YOU, it drops down to PREVIOUS NOTIFICATIONS for safe keeping and easy access. Plus there’s a link at the bottom to see all previous notifications — a screen we warmly call the Heystack.
As part of the navigation cleanup, we’ve eliminated the Reports menu and consolidated Reports and Activity into a single screen. Now when you click on Activity, you’ll see this:
Reports that used to be in a separate menu are now front and center at the top of the Activity screen. Just click a button to switch to a different report. For example, here’s what’s on Conor’s plate:
And here are all the to-dos added and completed across our account on Friday December 8th:
Simpler, clearer, and fewer places to go to get at the information you want. We’ve also improved how you select a person for a report. You’ll see that when you select “Someone’s activity” or “Someone’s assignments.”
Revamping the global navigation by consolidating and simplifying means there are fewer places you need to go to stay on top of it all. Concentrating power in a few key places, rather than spreading it out, puts more of what Basecamp can do for you front and center. And it makes it a whole heck of a lot easier for new users to learn. We’re excited for you to get your hands on it.
Preview of Phase 2
With Phase 1 now live, let’s turn our attention to a preview of what’s coming shortly in Phase 2.
Phase 2 is a broad overhaul of key screens, while still keeping things familiar enough so people aren’t disoriented. We know our customers are in the middle of important projects, so change comes carefully.
This phase of the refresh hits things like project home pages, message boards, to-do lists, automatic check-ins, etc. Plus some more tweaks to navigation. All new typography, better use of space, fewer elements on each screen to help you focus on what really matters, consistent placement of key buttons, better proportions, a toned back background, etc. Big stuff that touches nearly every screen.
Keep in mind this is work in progress, and still subject to change, but here are some highlights:
So there you have it! An all new navigation and Hey! inbox is available today on the web and desktop. And a few weeks from now we’ll push Phase 2 live. We think you’re going to love the overall simplification moving into 2018.
Wishing everyone the best!
And, BTW, if you haven’t tried Basecamp 3 yet, now’s the time. Since switching to Basecamp 3, 89% of customers reported having a better handle on their business, 84% report more self-sufficient teams, and early 60% have fewer weekly meetings! Want to be there too? Sign up to try Basecamp 3 for free, today.