How Strategality gets non-technical teams to report developer-ready issues

Monty Kosma is a lifelong software engineer and a McKinsey-trained consultant to top technology executives. As the founder of Strategality LLC, he advises software CEOs and CTOs on how to design product and engineering organizations characterized by creativity and productivity.

Before Marker.io: game of human telephone

Monty described the workflow before using Marker.io as "asking a whole lot of questions in Slack, and begging people to put screenshots and Loom videos in their bug reports."

As a result, a lot of information went missing and resolving issues took too long to be efficient. Sometimes bugs couldn't even be reproduced because they lost too much information.

“Even when people sent us screenshots in Slack, there was always something missing. Either they don't select the entire screen or don't include the URL, and there is zero context. Marker.io really bridged that gap for us.”

Bridging the gap between reporters and developers

When COVID-19 hit, Monty and his team moved to a work-from-home situation too. It became increasingly obvious they needed a tool that made it easy to report.

There are too many people involved, and too many of them don't have a technical background. When he found Marker.io, he immediately saw the power!

Strategality works with Asana and FullStory and the powerful integration that Marker.io supports was the final push.

"We work with Asana and FullStory and other tools like that, and with Marker.io, it is connected. It makes Asana 10 times better. It makes FullStory 10 times better. And all together, it gives us the ability to solve problems efficiently and quickly. It makes our process 100 times better."

The workflow with Marker.io:

1. Take a screenshot with Marker.io when they spot a problem on the platform
2. Add an annotation on the screenshot if needed, and add a title and short description
3. Send off the issue with one click

The ability to capture and include JavaScript console logs with reported issues is in Monty’s view one of the most important features of Marker.io for web development teams.

The engineers and developers now spend less time trying reproducing the bugs and the reporters can report quicker. There is a lot less information getting lost.

Conclusion

For Monty and Strategality, Marker.io is the perfect solution to get quicker and more accurate results. Now the platform of the energy industry client is taking off, there is going to be a continuous stream of feedback, little bugs and updates, so having developers on top of it matters.

Even when in a large team not everyone is equally technical, there is a way to work together.

Monty loves Marker.io for many reasons, and he says he never wants to go back!

‍