CoinTracker

Co-founder

It’s powerful enough for the engineering team but incredibly intuitive for people who don't touch code.

We had been trying to adapt flexible tools to product management and it wasn’t working. Our previous tool could be used for everything but it didn’t give us the information we needed most: a clear view of what everyone was working on as individual contributors and where our energy was focused as a company.

Once we started using Linear, things immediately felt faster. The defaults were close to how we approached building product. From issue tracking to the Github automation to quarterly milestones, it fit with our workflow. While we planned to try Linear with my team first, before we could finish the trial the whole company was using it. We don’t just track engineering and design work in Linear but also tasks related to growth, documentation, and support. Even the contractors we work with are in it.

A couple of things changed once the full team was on Linear. One is that we're able to track what is going on in a distributed company which had been hard to do with random docs and outdated lists. Everything is synced in Linear across views and with GitHub, so it’s always up to date. This means people are able to communicate better. They see what is happening and know who to ask questions or what is next.

The second thing is that using Linear built a culture around taking action. We started keeping better track of issues that used to get lost in Slack messages or conversations. It was so fast to create an issue and even enjoyable that people now create issues instead of talking about them.

There had been some concern since Expo is an open source tool and moving to Linear meant that we’d no longer have a single, public source of truth. Using Linear requires this trade off but the benefits have been worth it.

The easiest way to develop, test, and ship universal apps

Expo

Engineering Manager

It's easy enough for my coworkers to update that I always have the current state of the world.

At Render, engineers take turns doing customer support. We'll answer questions in our Slack channels and email users who report in bugs and feature requests. Often, an issue will come up from a user that has been reported before but we haven't gotten around to implementing it yet. The common impulse is to jump in and fix the problem they're having, but it's more helpful to be able to pause and check Linear to see the state of the issue. There's usually a reason we haven't fixed it yet and we'll see that in the description or comments. We make better decisions because the information is updated and in one place.

It's also been helpful that members of our team outside of engineering feel comfortable in Linear. We can share issues without friction and they can use the tool without much onboarding. This has been helpful in planning meetings, where it's so much easier to throw in a link to a Linear issue to share context than to explain the background information verbally.

That's another thing I appreciate about Linear: how easy it is to be onboarded between the UI and simple terminology. Projects, labels, and teams are just projects, labels, and teams. Anyone who opens Linear can understand it quickly. Linear keeps everything in one place in a way that's easy for people to reason with, and I think that's what an issue tracker is for in the first place.

The easiest cloud to host all your apps and websites

CoinTracker

CoinTracker

Founded

Investors

Building with Linear since