We have some very exciting news to share! It’s a pretty big deal for BugHerd customers, so take a moment to have a read (if you’re really keen for the scoop, you can skip to the headline stuff.
... first, a bit of backstory ...
<insert harp music and screen shimmering>
The moment Matt and I first created BugHerd, we knew we’d created something special. The act of placing a “pin” on a website and having it appear on someone else’s screen was so simple yet so powerful. Immediately it felt like we’d created a little bit of magic. Since that day, every person we’ve shown BugHerd to has had that same “wow” moment when they’ve first logged a bug. There’s something strange and yet magical about being able to leave a message on a website for someone else to see, something that we’re still yet to see elsewhere on the web.
The difficulty for us was that the possibilities for this technology were so broad it made it incredibly difficult to find and focus on a particular use case. Even just within web development there are so many different markets; digital agencies, e-commerce sites, blogs, translators, content editors, startups, user support, design feedback… the list goes on.
For us, it turned out that every customer is an outlier. Everyone had their own special way of using BugHerd.
So we went back to our product and analysed how it’s used and by whom:
- We found that the people who got the most value out of giving feedback on websites was actually the client or stakeholder of a project. They’re less involved in the ongoing process of building a website, but are greatly concerned with the output.
- We found that the people who got the most value out of our Kanban board were developers and project managers. The people tasked with doing and organising the work love the ease of use and flexibility our task board provides.
- We found that designers and front end folks loved the contextual feedback and screenshots that the BugHerd browser extensions provide. With one click they see exactly what the bug reporter sees, what page it happened on and what browser they were using.
To resolve the differences in these use cases, we’re splitting BugHerd into three distinct products. They’ll work perfectly together as a suite but will also be fully-featured standalone products in their own right. Of course, you’ll also be able to use them with other apps of your choice as well.
Welcome to Stack:
First cab off the rank is our new more robust, developer-centric, task board. As soon as we decided that we only need to cater for developers and project managers, it made setting a scope for our Kanban board a whole lot easier. Even today it’s already better than what we had in BugHerd, but in the near future you’ll start seeing a bunch of new things implemented. You’ll be able to use milestones, create sprints, mark dupes, create reports, work across multiple projects at once, do time tracking and estimations and much much more.
We’re not interested in selling a general purpose tool to musicians, painters, students or home renovators. We’re making a robust tool for development teams. Stack is available right now, go try it now here.
The New BugHerd:
BugHerd isn’t going anywhere. We’re reducing the depth of its functionality, but increasing the breadth of its reach. It’ll be less about managing tasks and more about getting consistent accurate feedback and bug reports. Instead of being tied to our task board, you’ll be able to send your feedback just about anywhere. Instead of just being about web, we’ll be getting feedback from mobile, desktop, web and just about anywhere else you can think of. We’ll be putting context into bug reports, and helping you fix things faster…. and of course, it works marvellously with Stack.
The new BugHerd will be open to beta testers in the coming weeks. If you’re not already on the beta list, you can get on it now by signing up here:
Some of BugHerd’s biggest fans aren’t our customers at all. They’re the clients of our customers. With the help of BugHerd, clients and stakeholders have had a voice on digital projects for the first time. Unfortunately, BugHerd was not originally designed with that workflow in mind. Whilst it does a good job, it isn’t the best workflow.
Whilst most users get up and running without a problem, some of the less technically inclined have had difficulties. We realise we need to make it even easier to give feedback. Not only that, but we need to engage those users earlier in the process. As one of our customers told us, “by the time we get to the build, all the discussions have already happened”. We want to give stakeholders a voice, and not just during QA, but across the entire project. If you’re an agency customer, we’re keen to hear from you as we continue to develop Brief.
We realise that the thousands of users that currently pay for BugHerd may not be ready to move to our new products just yet, so we won’t be asking anybody to switch over as part of this launch. We’ll also keep supporting the old app for the foreseeable future, so there’s no need to feel abandoned! We of course hope that you’ll give the new suite of tools a try and switch if you feel that it’s an improvement and if you need help to transition we’ll be here to help you out.
If you have any questions or want to be involved with testing and feedback you can always get in touch with us at firstname.lastname@example.org and we’ll do our best to help you out.
Thanks for reading,
Alan - Founder and CEO of BugHerd