Rocketlane

What do you like best about the product?

Project management is easy, and supports automation.

What do you dislike about the product?

Integrations can be better with other apps.

What problems is the product solving and how is that benefiting you?

Using it for professional services and management.

What do you like best about the product?

I like that Rocketlane is quick and flexible when it comes to changing dates and rearranging tasks, starting from a more generic template. Including steps with checkboxes, linking out documentation, and having no need for a username or password, simplifying things for our customers with a magic link, is pretty convenient. The user-friendly layout stands out to me. I also appreciate the reporting and time sheets where we can quickly add and submit projects, finding it user-friendly. Lastly, their use of templates is great—I can build out and attach different things to a template without being tied to it.

What do you dislike about the product?

Dependencies can be a challenge. So sometimes whenever you're setting up a project and you have multiple tasks and you set up dependencies and those... You need to change the date on one. You need to change the data in a lot of places, and that part is not all that intuitive. Also, when you're looking at it like a Gantt chart, of a project or the projects in a timeline version versus swim lane version, sometimes that's a little bit, less intuitive. In the the timeline version. A little bit more choppy, so it doesn't lay things out in a way that you'd really expect to see. It.

What problems is the product solving and how is that benefiting you?

Rocketlane breaks down complex onboarding into simple tasks, linking documentation and tracking metrics. I find it quick and flexible for changing tasks, with user-friendly templates and timesheets enhancing our implementation process.

What do you like best about the product?

Project Templates are one of the biggest time-savers for me because we can reuse the structure of a delivery without forcing every project into the exact same shape. With role-based placeholders and dynamic conditions, we can adjust the plan based on what was actually sold. And with Spaces, allocations, and automations, a new project can kick off with most of the operating model already set up. That reduces the initial setup work, but the bigger win is avoiding the small, easy-to-miss tasks that don’t get noticed until they turn into a blocker. The Customer Portal has also changed how we work with clients. Rather than sending a status email and then a separate list of pending documents and approvals, we can share the project plan, action items, files, FAQs, training, and approvals in one branded space, while still controlling exactly what the client can see. I also rely on Project Updates, automations, and timesheets to keep projects moving without having to manually nudge every next step. The update templates keep milestones, risks, and approvals consistent, and the automations take care of routine transitions when a phase changes or a form is completed. Status meetings became noticeably better once everyone could see the same project state before joining the call.

What do you dislike about the product?

Automations need more care than they might seem at first. One bad rule can push a project forward, change what the client sees, or create work nobody expected. We treat important automations almost like workflow changes in code: we test them first on a controlled project, check the edge cases, and only then reuse them more broadly.

What problems is the product solving and how is that benefiting you?

An enterprise onboarding started to slip because of a pretty ordinary misunderstanding. The client assumed we were already configuring an integration, while our team was still waiting on credentials from their side. We did have a project plan, but the key dependency was scattered across an internal sheet, email threads, and team tasks, so no one had a clean, shared view of what was actually blocking progress. We moved the project into Rocketlane using a phased Project Template, added placeholders for Implementation, Solutions, and Customer Success, and set up dynamic conditions so module-specific tasks only appeared when they were relevant. Through the Customer Portal, the client could see the exact action items and documents we were waiting on, which immediately reduced back-and-forth. Our first automation still had a flaw: it moved the project to “Ready for Configuration” as soon as a form was completed, even when an internal approval was still missing. We tightened the trigger so both conditions had to be true, and we added a recurring Project Update to keep risks and dependencies visible. After that, we stopped maintaining a separate tracker just to figure out who was blocking the project. The client had a much clearer view of what they owed us, and I could spend more time handling real exceptions instead of chasing tasks the system was already capable of tracking.

What do you like best about the product?

Rocketlane has been a great tool for managing my projects. It’s very easy to use, and as a visual person, I really appreciate its clean, simple, and intuitive interface.

What do you dislike about the product?

One thing I dislike is having to manually mark each subtask as N/A when the primary task itself is already marked as N/A.

What problems is the product solving and how is that benefiting you?

It helps me stay organized, track project progress, and easily see what needs to be done without feeling overwhelmed.

What do you like best about the product?

The collaboration opportunities, the ability to track projects in different ways, and the overall overview are really helpful. Support has also been great when it comes to adjusting things and making tweaks so it works for our business.

What do you dislike about the product?

The adoption rate, and making sure people are sticking to their targets, are the main areas for me. Training and best-practice use cases could be clearer, and the reporting could be enhanced as well—although that might just be down to my own lack of knowledge.

What problems is the product solving and how is that benefiting you?

I use it to track time spent, make sure projects are moving forward, and ensure colleagues are sticking to deadlines. I also use it to track any risks.