Personas and building out Landing Pages for Roles/Personas

Question

I wanted to reach out to the community as we are struggling with the UI for our user community and their adoption of Collibra.
Who has used the persona templates and been successful implementing landing pages for those roles/personas?
I’d like to see if anyone is willing to share their implementation and skillset that was needed to implement. Please help! Thanks!

Dmytro Lugovyi · Answer

This is really great discussion and amazing examples!
Every persona will probably have a different set of needs and different user journeys. So if we want to make their journey easier we have to understand their typical requests and think about how we can make their life easier through the dashboard configuration, workflows, views, filters etc.
I would like to recommend have a look at this page where you can find a recording of the session where we talked about how to identify a persona’s needs and how to help them to do their job (aka how to drive adoption of the platform). You will also find there downloadable content, it’s a methodology for how to do that and also the description of the typical personas.
https://community.collibra.com/forum/t/january-2022-how-to-develop-user-personas-to-drive-adoption/1433

Tina Keller · Answer

Ladies, thanks for the replies and excitement around this topic. I thought I was alone.
I’d love to get us together and talk thru this more and the best way for us to each approach this effort. How should we set something up for the 3 of us?

Tina Keller · Answer

Ladies, thanks for the replies and excitement around this topic. I thought I was alone.
I’d love to get us together and talk thru this more and the best way for us to each approach this effort. How should we set something up for the 3 of us?

jennifertemple · Answer

Wow, fantastic suggestions @katherine.waters - love to hear what others are doing and I may steal some of your ideas . We did set up some persona specific dashboards, because that was what we were supposed to do, but honestly, I doubt they get used. Instead, I have found use case specific pages way more useful than defining all of the needs by persona. For example our main welcome page has links to our Business Glossary, KPI and Reporting Library and our Data Catalog. These links are pictures to make it visually appealing. They link to Community pages, where I used more pictures and links in the description of that community page to get folks to the views and information they need. I also created some training videos and documents which are available from another dashboard - the Training Center. I think the key is to create the views your end users need and provide links to them on Community or Dashboard pages. That seems to be working for us. I do have an enhancement suggestion in the ideation portal to be able to provide a widget similar to Last Viewed/Most Viewed that pulls assets from a predefined view - could be so useful on the dashboard page (for example creating a view of the assets you subscribe to and seeing that list on a dashboard ). You can vote for that idea here: https://productresources.collibra.com/ideation-platform/?id=CAT-I-416 should it be something you would also find useful.

katherinewaters · Answer

Hi Tina!
I am not sure if you have a specific persona template you are referring to. I am actually working on this now as well and would welcome any example use cases you have identified as priority for your personas. Most of our users have stated they find it difficult to navigate the tool as well. We are working on building a use case dashboard, Since we have 6 personas I do not think we will have separate dashboards for each but maybe one that has several common use cases for each (Data Scientist, Data Analyst, Data Engineer, Business Analyst, BI Developer and Data Steward)
We did develop a dashboard to address the concern around the UI overall in December. It leverages the Collibra provided widgets and has links to custom views such as pre-filtered searches for both Data Attributes and Entities on our logical model. This way the user can select the link and then type the word related to the data they need (such as Charge Code) and the search is already pre-filtered to look at either entities or attributes. When they select them we have descriptions on the attributes and entities and they can then use these to see associated columns and tables to determine if it fits their needs. WAY easier than using the search bar on it’s own as that tends to leave people frustrated or confused.
We also added a section on the dashboard that highlights the tags available in the catalog and there are several we listed with hyperlinks to a pre-filtered search on that tag, we chose ones that are tied to our most commonly accessed data to list here. This was another way to resolve the issue of users not being able to navigate/find the data they are looking for in the UI. We also decided to create a community dedicated to feedback from users and loaded prior feedback we received here along with a quick form that uses a workflow to notify us and place the information into this community for our review. We hoped seeing other questions where we responded with answers would be helpful to our customers.
We did not any special coding skillsets to develop this. And one last note, if you haven’t seen the Covid Dashboard Collibra developed you should check it out. It is a great example of persona based dashboards and is quite beautiful! The reason we did not use this is because it required some web development and customized coding to achieve ,which we did not have available to us.
Thanks!

1	Grant Rollerson SUNCORP CORPORATE SERVICES PTY LTD
2	Tom Friesen Algonquin College
3	SB S Benson Plus3 IT
4	S stefan_busch
5	Brian Lloyd USA TODAY Co.
6	D daverichard