Welcome! We're here to help you get Marker.io up and running in your organization. This guide will walk you through each step to fully integrate Marker.io into your workflow.
Key Contacts
To keep things running smoothly, we recommend having a few key people involved. Here’s who we usually work with:
Role | Responsibilities |
Marker.io Owner | Manages overall setup and usage. |
Integration Owner | Handles connecting Marker.io to your other tools (e.g., Jira, Azure). |
Technical Lead | Resolves any technical issues or roadblocks. |
Business Lead | Ensures Marker.io aligns with your business goals. |
Security Lead | Ensures that all security protocol are in place including SSO. |
Implementation Timeline
Setting up Marker.io can take anywhere from a day to a few weeks, depending on your specific needs and the availability of key people (like your Jira or Azure admins).
Note: When key leaders join our onboarding sessions, the time it takes to implement Marker.io shortens noticeably. This early involvement makes it easier to tackle decisions and address challenges that may come up.
Here’s an overview of the main steps
Step | Estimated Time | What’s Involved |
Account Setup | 1-2 hours | Decide how to invite users (SSO, invite links, domain join). |
Integration Connection | 0-2 days | Link Marker.io to tools like Jira or Azure with admin access. |
Technical Checklist | 1-2 hours | Follow our setup guide to ensure smooth operations. |
Customize Forms & Workflows | 1-3 hours | Tailor forms for various users; configure tags and priorities. |
Security Setup | 1 day | Enable SSO, audit logs, and data masking features. |
Training Sessions | 1-2 sessions | Train your team on using Marker.io effectively. |
Best Practices Review | 1-2 hours | Ensure your setup aligns with industry standards. |
Final Testing & Go Live | 1-3 days | Run tests, fix any final issues, and launch Marker.io. |
Step-by-Step Breakdown
Set Up Your Account:
Decide how you’ll invite people (Typically SSO).
Connect Your Integration:
You'll need someone with admin access (like a Jira or Azure admin) to help link your tools. It's best to create a dedicated user account, like "Marker.io Admin," to connect everything. This keeps things simple and organized. Here's why that's important.
Technical Checklist:
Ensure that you are well set up for success by stepping through our user-friendly tech set up guide here.
Customize Your Forms and Workflows:
Fine-tune your forms for both technical and non-technical users. Make sure reports go to the right people, with the right tags and priorities. See our advanced form guide here.
Consider custom-meta data:
Typically, enterprise customers like to collect a lot of additional context on their bug reports. Check out our latest guide on collecting this useful information here.
Security Setup:
Make sure features like SSO, audit logs, and data masking are enabled for maximum security.
Training Sessions:
We’ll help your team get the hang of Marker.io. One session usually does the trick, but we can run more if required.
Best Practices Review:
We’ll review your setup to make sure it follows industry best practices.
Final Testing and Go Live:
Run final tests, fix any last-minute issues, and launch Marker.io.
Measuring Success and Tracking Adoption
How do you know if Marker.io is making a difference? Here are a few things to look out for:
Smoother Issue Reporting: Is your team finding it easier and more enjoyable to report issues? If they’re happier with the process, that’s a win.
Quicker Fixes: Are bugs getting fixed faster because all the right info is being captured automatically? Speeding up the resolution process is a good sign that things are working.
More Bugs Being Reported: Now that it’s easier to log issues, are your team members reporting more of them? More reports mean a better final product.
Less Time Spent on Bug Management: Are your teams spending less time tracking and managing bugs? If so, Marker.io is doing its job.
Clearer Communication: Is everyone on the same page more easily? When communication improves, it’s a clear indication that things are clicking.
Consistent Bug Reporting: Are you regularly logging and fixing issues? A steady stream of bug reports means Marker.io is becoming a natural part of your process.
When you’re consistently logging at least 30 bugs a month, that’s when we know you’ve fully adopted Marker.io. It shows that the tool is integrated into your workflow and delivering real value to your team.
Regular Check In
We’ll check in every three months to make sure things are running smoothly and help with any new needs.