Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?
They’ve been such a pleasure to work with. There was one critical staffing change during the middle of the project, but there was barely a bump in the road at all. They’re also really transparent about progress and budget. I really love working with them. I’ve worked with a lot of vendors in my time at Applegate, and I wish I had more like them. We’ve had a really good experience. I especially admire their commitment to their client’s experience.
How did Planet Argon perform from a project management standpoint?
We used a ticketing system through JIRA, so we were able to keep track of progress on sometimes as many as 230 separate ticket items at any given time. Every week, we got budget updates and progress reports. We met weekly as well to hammer out each ticket item.
What did you find most impressive about Planet Argon?
I’ve worked with developers in the past, and it’s not always a seamless experience. I found that Planet Argon had a unique blend of strong technical expertise coupled with strong customer service and interpersonal fluency. I’ve never seen any firm work with clients the way they do. They’re able to execute all the technical items, but then also go through and communicate what they’re doing to someone like me who doesn’t have the technical knowledge they do. They also have people with cross-functional skills. Their lead graphic designer has years of development experience, so he was able to provide guidance about decisions we were making that weren’t in our best interest. For instance, not choosing a particular style that would limit us down the road or cause potential issues. The team really had to train some of us on responsive design and creative treatments and walk us through the backend process. They did a great job communicating effectively.
Are there any areas Planet Argon could improve?
I will say that we spent too much time in the initial creative exploration process. We came in having done our own wireframes and design work, so we knew what we wanted for the most part, but we opened the door for them to spend a lot of time in that exploratory stage. That pushed back our timelines—we initially planned to launch at end of December, but we pushed into February. It also meant that we overshot our internal budget forecasting a bit. I will say that we opened the door for this exploration initially. I think it was a learning curve for all who were involved, as the ultimate outcome resulted in a beautiful product—a fusion of our initial designs and a smarter UX approach.