Shortcut scales with you

Teams having separate workflows has been big, because in the past, we've had one workflow that we tried to apply across all teams. The workflow wound up with some weird naming conventions, because of things like how a marketer will think of a task as 'done', and an engineer thinks of it as 'shipped'.

The ability to be working on a task list at the smallest level, where I can check things off, all the way up to tracking my entire company's engineering velocity at the milestone level, and being able to do that out of the box without any configuration or hiring a consultant to set it up is very compelling to me.

"I use so many different views. I use one for team planning, one for team sprints, one for a Team’s next sprint. We use Iterations quite heavily and reporting on Iterations. We create a lot of Epics, which we can see. It makes sense for engineers who are used to very hierarchical data structures. It makes a lot of sense, but it's not overbearing."

We chose Shortcut because it was a project management platform that could scale my team. It was simple to use and also had the functionality to help with prioritization and collaboration.

"I have never met a team that loves their task tracker, period. I hear a lot of unsolicited positive comments about the joy of using Shortcut and very, very few complaints. Shortcut is a perfect balance between structure and usability. It gives us what we need, and there's enough flexibility that we've been able to change our processes a lot and still use Shortcut."