In Brijj, stakeholders can easily see the status of the work they’ve requested along with a view of what other insight work is going on in the organisation. The Kanban is located in the same place that work is requested, reducing the locations that your stakeholders need to visit to collaborate with your teams.
Why does this matter and how does it help?
Last year, we ran research with seven hundred “office workers” who interact with data teams. We wanted to know what works, and what doesn’t.
The number one frustration for stakeholder involved in data analytics projects? Not knowing the status of their work.
We at Brijj have worked in a variety of organisations of all sizes and maturity. Some use systems to gather data requests, (although most don’t) and some use project / task management systems to track their work. But again, our research shows that most don’t, at least from the perspective of their customers.
Ask yourself, do you track your work in a spreadsheet? Do your customers have access to, or know how to use your projects in JIRA / Azure Dev Ops?
I’m sure using these methods works for you…but does it work for your customers?
Think about these questions and points, if you are an insight leader;
Does your customer have easy access to see the status of their work?
Do they have to chase you to get a status update? Is getting an update easy for them to do?
Do they know how their requests fit into the context of wider organisational insight? How do they know if the question they have has been asked in the past?
How do you manage the process of collaboration with your customers through each stage of development?
The best way to solve these issues without a lot of manual back and forth? Give your customers access to this information for themselves.
A word of warning…You don’t want whatever they have access to, to scare off your non-technical users. Our research shows JIRA, Azure DevOps etc can work as a barrier to some stakeholders. Not to mention the sometimes exorbitant cost of giving users access to these systems. You also want to be sure that you don’t overload them with unnecessary information. Do they need to have access to every modelling task and ETL process you are building? No. But do they need to know what stage their request is at, or that it needs some feedback? Absolutely.
What you need, is a system that allows you to keep your stakeholders up to date and engage with them in a way that works for them. But which also gives you the benefits of systemising the full data analysis process.
What you might like to try is a system like Brijj.
We built Brijj to bridge the gap between data and insight creators and consumers. Its one place to take in and manage requests. A place to inform, engage and collaborate with stakeholders that they’ll actually want to use.
Its low cost, especially compared to giving everyone access to your instance of JIRA or Azure DevOps. Not to mention so much simpler for your non-technical customers.
Because its such great value, you wont need to worry about rationing licenses to users who “need it most”. No flipping of permissions, depending on the users need at the time, so you don’t ramp up your subscription. Its a flat fee. Give everyone access and get on with adding value.
Data, Analytics and Insight isn’t about the tech you use or the code you know. Data is is about people, and its managed by people.
With Brijj, you can help people work together, keep each other informed, and start to realise the true value of your insight activities.