G2

Yusup E.

Frontend Developer

Computer Software

Mid-Market (51-1000 emp.)

9/28/2026

"Basecamp helped us keep UI feedback, bugs, and decisions close to the work itself"

5/5

What do you like best about Basecamp?

We use Card Tables to move work through stages, and To-do Lists with subtasks to break implementation down into responsive states, accessibility, analytics, and QA. I like the simplicity: I can quickly see where something stands without having to maintain a board full of custom fields that nobody updates. Message Boards, Docs & Files, and Automatic Check-ins also help us keep the context around the work, instead of letting important decisions disappear into chat. Message Boards are especially useful for UI decisions that need to last longer than a Slack thread, while Automatic Check-ins let the team answer recurring questions—what was finished, what is blocked, and what still needs attention—without adding yet another status meeting. One unexpected benefit is that developers started writing better updates once they knew the rest of the team could read them asynchronously. Hill Charts are probably the most distinctive part for me. In frontend work, a task can look small on paper and still be very uncertain because an interaction, browser behavior, or a design constraint hasn’t been resolved yet. The Hill Chart gives us a clear way to show the difference between “we still need to figure this out” and “we know exactly what to do; we just need to finish it.” Review collected by and hosted on G2.com.

What do you dislike about Basecamp?

Search and navigation are better than they used to be, but projects with a long history can still get noisy. Older threads, files, and past decisions aren’t always as easy to track down as I’d like, especially once a lot has accumulated. We’ve reduced the impact by sticking to strict naming conventions, using Message Boards for decisions, and reserving Docs for information that should stay stable over time. Review collected by and hosted on G2.com.

What problems is Basecamp solving and how is that benefiting you?

A dashboard redesign made it to the frontend with feedback scattered across Figma, chat, and several PM notes. By the first sprint, we were already losing track of which changes were final and which were still under discussion. To get control of it, we set up a Card Table with Ready, In Progress, Review, and QA, and then broke each component into to-dos with subtasks for responsive behavior, accessibility, and analytics. We also opened a dedicated Message Board for UI decisions so the team had a single place to confirm what had actually been agreed on. At one point, a card looked almost finished, but the Hill Chart still showed it as uphill because the mobile interaction hadn’t been resolved. That kept us from calling the component “nearly done” just because most of the checklist was complete. From there, we separated the mobile behavior into its own piece of work, added a weekly Automatic Check-in for blockers, and let product and design follow progress without scheduling yet another meeting. Basecamp helped us keep bugs, feedback, and decisions close to the work itself, which reduced contradictory changes and made uncertainty much easier to spot before it turned into rework. Review collected by and hosted on G2.com.