Quantcast

How Personalized App Experiences Enhance Enterprise Governance

When you’re creating an enterprise app, there are many elements to consider: functionality, integrations, user experience, and, the often overlooked priority: governance. 

 

One App, Multiple Views

Enterprise apps will need to tap into a plethora of data sources to function, containing both business and customer information, some of which could be sensitive. If data is not managed correctly, you could face fines and legal penalties. And from a usability level, not everyone needs to see everything. Different information is required by different users to complete their jobs.

But you don’t want to build multiple apps for different users. Instead, you can create unique, contextualized experiences for different end users to dynamically adapt to their needs while protecting sensitive data at the same time. 

 

How to create a personalized app experience 

Using Bizagi, governance is built in at an application level, so you can personalize your enterprise app for different groups of end users.

Each end user will have a contextualized view of the app, seeing a smart portal that contains all the actions and data that they need to do their job. 

By defining end users, or ‘Personas’ as they’re known in the Bizagi platform, you can ensure that they only see information and activities that they are cleared for. You can use the Experience Matrix to assign which data each persona can see and, even more importantly, what they can do with the data. 

To build an app in the Experience Matrix, you require three sets of information: Personas, Business Objects, and Interactions. These building blocks are based on your business processes and create unique experiences for each user.  

Discover how to build an app in Bizagi.

Let’s look at an example. In this case, we’ll use a procurement application and the different people and actions involved in that business process.

In the experience matrix below, you’ll see three different types of persona, a departmental manager, and a member of the procurement team. Each plays a different role in the business process of procuring goods.

  Procurement experience matrix 1.png

 

These personas move in different contexts on the same app, so you can use the Experience Matrix to assign them different interactions and provide them with contextualized and personalized apps, so they only see data and actions relevant to them. 

In this example, we’ll name these people Michael, Camila, and Martha. Let’s have a look at the experience that each of them is able to have based on what’s defined in the experience matrix.

Procurement experience matrix 2.png

 

Michael’s view shows him the procurement requests he has made previously and the status of each of those requests:

Procurement experience matrix 3.png 

Michael is then able to take the action of making a new request, in this case he wants to purchase some furniture:
Procurement experience matrix 4.png

The request goes to Camilla, who is able to see a view of procurement requests in her team and how that relates to the different vendors that they work with:
Procurement experience matrix 5.png 


Camila can also see a dashboard that gives her an overall view of the cost and status of the different purchase requests in her department:

Procurement experience matrix 6.png 

Camila can then navigate to Michael’s individual request, review the details, and decide if she wants to approve or request Michael to make changes:
Procurement experience matrix 7.png

 

Once approved at a departmental level, the request goes to Martha in the Procurement team for approval. Martha has a view of the different pending approvals in her home page:

Procurement experience matrix 8.png 

Martha is then able to review the case according to the company’s procurement policies, and approve it, deny it, or request changes:
Procurement experience matrix 9.png

 

The benefits of personalized app experiences

Control access: You can ensure end users only see information and activities they are cleared for. This puts controls in place for safeguarding critical data and means that sensitive information isn’t unnecessarily exposed. 

Ensure data privacy: By defining end-user permissions, you can rest assured that your data remains private. This guarantees compliance with international data standards such as GDPR and helps to avoid unnecessary fines. In just the past four years since GDPR was put in place, fines are becoming more commonplace, with over €2.84 billion of fines issued, including a record fine given to Meta in 2023 for €1.2billion, according to Data Privacy Manager. 

Provide a contextualized solution: In the digital world, context is key. You can define stakeholder roles that dictate which information and actions are available to the user based on their role and skills. Even better, you can set rules in your work portal to dynamically adjust and reflect to any changes, so they don’t have to ask for information that has already been provided.  

Accountability: By assigning tasks, processes or views to stakeholders, it makes it clear who is responsible for certain actions. Plus, by specifying stakeholders, you will have an audit trail of who has accessed the system and performed certain actions. 

 

Build governance into your apps with Bizagi

Bizagi's governance is built-in at every level, from the application itself to the developers creating them to help you enforce quality and security standards. 

Find out more about how Bizagi can implement governance at all levels of app creation and management.