Jira vs Nifty: Which is a better fit?

Jake D.: My name is Jake, my company is Uni. We are one to 10 people, and my score for Jira was a four. Before we were using Trello and we didn't like it as much as Jira, because it really only was good for task management, but the tickets and organizing complex projects weren't as strong on it. We also really liked the documentation and the ability to do other things in Jira that Trello didn't offer. So in general just as we grew and had more engineers to manage and more complex software projects to manage, Jira became a better fit for our company. I chose Jira first and foremost, because the devs at my company really liked it and had experience working on it. It also allowed us to manage a front-end and backend team more easily and collaborate with ease compared to the other products we were looking at. It was affordable for startups and also supported us scaling all the way up if we were to grow our org to be much larger. As I had used it in previous companies that were bigger enterprises and saw it used for everything from documentation to ticket management to product management and development, so it just made the most sense for our org as we grew and was very affordable. Getting started with Jira was pretty easy, it took us about a week. We had a designated project manager who went about kind of setting up every user and getting the board set up the way we needed. We had engineering leads trained in how to do ticketing and how to move tickets from beginning to end pretty quickly. I think a lot of people use Jira and have experience with it coming out of school or bootcamp, so it was a pretty easy switch for us. Coming over from Trello, we found it was pretty fast to recreate the tickets and our processes from that. I think my biggest recommendation is just making sure that the engineers really want it. I think that project managers, it really caters to and has a great amount of tools for documenting, doing product recs, doing task management, QA, all of that. But I think if the devs aren't comfortable using it for pointing, using it for work management, it kind of gets out of line or doesn't get set up in a proper way. So, asking your developers to make sure that that's the tool they want and making sure it's set up in a way that's optimal for them I think makes it a much smoother transition, and easier for the business leads and product leads to engage with as well.

Aryana R.: Hi, I'm Aryana, the founder of a coaching and training company, and I give Nifty a four out of five. I was working in Basecamp, and I found it hard to navigate. When I was looking for something, I'd spend a lot of time trying to find that post or that document, and it was frustrating. I decided to go with Nifty. One, the pricing. It was better than anything else that I'd looked at. I also liked it was more intuitive, and it was like I was looking at a desktop, not just this blank screen. I was able to put my calendar in there, my team members, alert people easily. It had kind of this feeling of a dashboard that was modifiable. My team and I are still working on onboarding. I found that this is what I do as a business owner is I get my team to do, "How does this all work?" Then they teach me how to do it. I would say we really ran at it very quickly and we got some projects in there. I was really impressed as we were doing it. Then things got busy, so we started to go back to Google Docs. Interestingly, just yesterday, I was like, "I'm done Google docs. I'm done emails back and forth. I need to get us using Nifty again." I started to put some projects in, some task lists. There's something really satisfying about that, when you can be like, "Tick it off. I did it." If you're considering Nifty, I suggest doing their free trial, if they still have it, and really give it a robust, try. Get your team members working in it and put an entire project in. It's going to help you because you can still use the content if you decide not to continue with their trial, but that's one thing that I wished I'd done when I was researching is just give it a good solid test because then once you do commit to it, you're going to stick with it and you're going to use it fully.