In Brijj, stakeholders can easily make work requests to their data and insight teams. The request submission portal for this is located in the same place that ongoing work is viewed and managed, reducing the locations that your stakeholders need to visit to collaborate with your teams.
Why does this matter and how does it help?
Its important your stakeholders have a central location to ask questions of your teams. Our research shows that people become frustrated when its not obvious “who to ask”. Having one place for all insight work in your organisation reduces this frustration.
In addition, knowing that all insight requests are coming through the same work request process ensures there is no duplication of effort, and your leadership have a cohesive view of all organisational need.
Think about these questions and points, if you are an insight leader;
How do you know you are aware of every question that’s asked…unless you can be sure every question is asked through the same channel?
How do you know when a piece of work has been asked for in the past…unless you have a mechanism to know what has been asked for and delivered in the past?
How do you know what technical work’s been done before? Work which might speed up delivery of new projects? Especially if the person who did that work has left the business, doesn’t work for you, or it was developed before you even started?
I’m sure you have a good idea of the nature and amount of work you’ve done? But isn’t this potentially a biased dataset because the work you have done…is only the work you can do? What about all the questions, all the insights people need that you couldn’t do? Are you counting those? Aren’t these the questions which dictate the next person you hire, the next Datamart you build, the next piece of tech you buy?
If a question’s asked of another team, but its for your team, how do you know about it? Are you forwarding on all questions that get sent to you which aren’t for you to manage? Is having your customers have to search for the “right person to ask” good service?
All these problems are solved by having one place where all questions are asked for the entire organisation. Its one of the simplest and easiest things you can do to start building more actionable insights.
A word of warning…You don’t want whatever you implement scaring off your non-technical users. Our research shows JIRA, Manage Engine etc can work as a barrier to some stakeholders.
This is probably why ~90% of teams still have email as a central part of their process. This is crazy to us because teams which use some of the worlds most advanced tech to clean and systemize the organisations information, should not be using legacy systems to collect untidy data on the very detail of their work. Madness!
This is the central premise of Brijj and the foundation of everything else it does and will do in the future. Its why its built in the way it is. Its why the experience for your consumer users is as close to email and as simple as possible. Because good things happen when all your questions and requests are systemised and put through one place.