WEBCODA'S STORY
A game changer for the dev team and clients...
Customer since
No. of BugHerd projects
No. of bugs created
No. of team members (+guests) using BugHerd
Sydney based development agency Webcoda has a mission to turn complex client needs into elegant and easy web applications. Their client feedback and bug tracking process, however, required an upgrade to fit their elegant and easy brand message. Webcoda were specifically on the lookout for a tool that allowed the capture of bugs and feedback from clients in a visual, contextual and simple manner.
"Before BugHerd, clients would try to send screenshots with scribbles we couldn't decipher or dozens of emails with issues we were often unable to recreate."
Sasha Shevelev
Webcoda Co-Founder
It was a no brainer that the process could be drastically sped up. Instead of spending hours on back and forth emails and phone calls, Webcoda avoids having the “but it works on my computer” conversation by including BugHerd early into the feedback process. So much so that when they pitch new clients, BugHerd is included as an example of how the company reduces UAT time, in turn saving the client precious hours on a build.
Webcoda can be pedantic about ensuring that every issue, no matter how small, is captured in an initial design review. Such a thorough review process sets up the build-up for greater potential success, whereas previously it may have been tempting to ignore initial small perfections.
The speed and ease of logging tickets in BugHerd affords this level of attention to detail.
Once the internal team is happy to proceed, Webcoda sets up their clients as members, so that they can track their tickets live in the Kanban view. The clients really get into seeing the process and progress of their feedback being resolved.
The commenting functionality means that the dev team and clients can still communicate and clarify with fewer, if any, emails and phone calls.
"We use BugHerd with all of our client facing projects. There is no better way for the client to log visual issues."
The Royal Botanic Gardens of Sydney’s website required a large redesign with thousands of pages, templates and modules to deliver in the very short timeline of less than 6 months.
Clear and streamlined communication was essential, with only a small team on the client side. Using Bugherd on the project allowed the quick resolution of issues, sometimes within minutes, while the client was still entering content. In this particular project, the ability to work collaboratively and in real-time saved the client thousands of dollars in build time by going straight to the dev team and cutting out the middle person.
Most importantly the client was super engaged and thrilled that the process was so easy with minimal hours spent on rounds of feedback.
Studio Moso is a digital agency based in Melbourne, Australia with a clientele that ranges from large scale banks to local glass manufacturers. The agency provides digital web services, including user experience, web design & development and UX design.
While managing projects involving external and internal stakeholders the team at Studio Moso needed to find a website feedback solution that provided an infrastructure to not only support their internal feedback needs, but that could also loop in external stakeholders.
Ultimately the product selection needed to minimize the number of email and document exchanges, thus save precious team member time and in turn reduce project budgets.
Every staff member at Studio Moso uses BugHerd on an almost daily basis. In fact, the Studio Moso team is one of the earliest adopters of BugHerd (2012). Today they are using the tool as a part of their studio feedback infrastructure.
Studio Moso mainly uses BugHerd with new clients, before launching the final website, feature or campaign. They do occasionally use the tool on a live site to mark up changes as required.
After finishing the internal QA process of the new site, the Studio Moso team provides client access to BugHerd. The clients mainly use Chrome capture screenshots to pin issues and feedback, creating tasks for the team to action.
With the help of the upload documentation function, the feedback loop can get started and bingo! The tasks are sent back to the QA manager at the studio.
Once all the tasks have been collected from the client, the studio account manager will jump in and validate the tasks by replicating them. Once completed, the content of the tasks will be modified for the developer or the account manager to take over the ticket to be resolved.
Once the requested tasks have been completed, the tasks gets dragged and dropped to the DONE column on the Kanban board. In the tasks final review stage, the client gets the tasks assigned to them for one final review for them to be closed off.
The whole process usually takes under 2 weeks, for multiple rounds of feedback and communication. Imagine doing that all over email… shudder.
It’s really hard for us to remember a time prior to BugHerd! We have on a few occasions not provided a client with BH access and it’s been a slew of documents + emails with changes - enough to know that it’s saving us time (and money) by providing client access to it!