“Excellent Resource. Strong Partner Mentality. Super Reliable. ”
We've worked with four different outsourced development groups and OneTree is tops. STRENGTHS: Partner Mentality. OneTree has a very strong partner mentality. They are willing to take responsibility when they make mistakes, or don't meet expectations. They will regularly ask how they are doing, and seek feedback on how to improve. Then actually implement the feedback and loop back with us to report improvements or changes made. Responsive to our Needs. They are responsive, talented, and willing to put forth the effort to achieve goals and priorities to meet deadlines. There are multiple times where their developers will work after hours to solve issues or meet deadlines. This is invaluable to getting things done. Quality of Output. They have talented developers who do a thorough job. The key is to provide thorough user stories, which drives the quality of the output from developers. The more thorough the user story, the more efficient the output from developers. They really are a talented bunch of developers. Time Zone. One benefit, as well, is their time zone aligns well with our time zone. WEAKNESSES: Strategy. OneTree is great as a developer partner, but the client needs to define and communicate a strong strategic direction about where they want to take their business and technology stack. Once OneTree understands this direction, they are a great making it happen. Think of OneTree as your execution partner. Product Manager. We've found that we need to be the Product Manager and own the user experience of our website in-house while utilizing OneTree as our development team. This means we need to have a strong understanding of trends in our market, understanding the customer journey on our site, identifying points of frictions, and what we need to do to be on the cutting edge. We come up with the roadmap and then utilize OneTree to execute the roadmap. QA. Generally OneTree QA does an excellent job finding issues. However, at times, issues or errors will slip through and we catch them on our end. This can be frustrating if a ticket is on a tight timeline.

