HOME

•

ABOUT

HOME

•

ABOUT

HOME

•

ABOUT

Compliance AI

Product Design [sole]

Pyxos AI [US]

2024

Navigating the landscape of privacy laws is challenging for businesses managing personal data. The complexity of legal requirements demands an investment of time and human resources for compliance, leading to the creation of data silos that restrict data access. By automating the compliance process, this compliance assistant reduces manual labor, cracks the walls of data silos, and integrates privacy compliance into business operations. 


The AI Documentation is a crucial feature of the product, designed to analyze client compliance policies and optimize compliance. As the sole Product Designer on this project, I’m responsible for shaping a future where businesses can thrive in innovation while navigating the complexities of privacy laws.

The Plan

By April 2024, the goal is to integrate the Document Center within  the AI-driven privacy compliance platform. Outlined by the product manager, the roadmap includes:

1. Integrating an Advanced AI Engine able to summarizg elements from privacy policies and related documents.

2. Development of Document Management Functionality, allowing users to upload and manage documentation.

3. Generation of  Reports, offering users insights into how their policies compare with industry standards.

4. Recommendations and Policy Creation Assistance tailored to each client’s context.

My first task was conducting a market analysis to understand strategies of major players in the field. Insights included:

1. Mapping Status of Competitors,  identifying leading entities’ and market positioning in privacy compliance technology.

2. Analyzing Possible Outcomes of File Uploads, investigating how competitors handle file uploads in terms of processing, analysis, and feedback.

3. Scoring Visual Design Patterns 

4. Understanding Data Privacy Presentation, examining how competitors communicate data privacy policies and practices.

These insights provide a strategic foundation for further development and innovation of the platform, ensuring it meets and exceeds industry standards.

The next step involved a strategic discussion on hierarchy and functionality. This discussion included me, the Product Manager, the Head of Design, and the Lead Engineer. The focus was on refining the platform’s capabilities and user experience, addressing specific questions such as:

1. Support for Multiple File Types
Deliberating whether the platform should enable all agents to support multiple file uploads or if this feature should be exclusive to the compliance manager. 

2. One-Off Uploads from Chat Interface
Considering the feasibility and utility of allowing users to upload documents directly through a chat interface.

3. Scope of User Uploads in the Document Center
Discussing the number and type of files users can upload in the Document Center. This is crucial for ensuring the platform is tailored to the specific needs of the users and the kinds of critical documents for compliance analysis.

4. Transparency on uploaded data
How to assure users their data is handled securely and used for compliance analysis, to build trust and ensure compliance with data privacy regulations.

In these collaborative sessions, I created low-fidelity designs, which brought clarity and depth to our discussions. These initial designs served as a tangible foundation, enabling stakeholders to visualize and better understand the proposed complex concepts and functionalities. They facilitated more informed and productive conversations and ensured everyone involved had a clear and cohesive vision of the project’s direction, bridging the gap between abstract ideas and practical implementation.

The next step involved a strategic discussion on hierarchy and functionality. This discussion included me, the Product Manager, the Head of Design, and the Lead Engineer. The focus was on refining the platform’s capabilities and user experience, addressing specific questions such as:

1. Support for Multiple File Types
Deliberating whether the platform should enable all agents to support multiple file uploads or if this feature should be exclusive to the compliance manager. 

2. One-Off Uploads from Chat Interface
Considering the feasibility and utility of allowing users to upload documents directly through a chat interface.

3. Scope of User Uploads in the Document Center
Discussing the number and type of files users can upload in the Document Center. This is crucial for ensuring the platform is tailored to the specific needs of the users and the kinds of critical documents for compliance analysis.

4. Transparency on uploaded data
How to assure users their data is handled securely and used for compliance analysis, to build trust and ensure compliance with data privacy regulations.

In these collaborative sessions, I created low-fidelity designs, which brought clarity and depth to our discussions. These initial designs served as a tangible foundation, enabling stakeholders to visualize and better understand the proposed complex concepts and functionalities. They facilitated more informed and productive conversations and ensured everyone involved had a clear and cohesive vision of the project’s direction, bridging the gap between abstract ideas and practical implementation.

The next step involved a strategic discussion on hierarchy and functionality. This discussion included me, the Product Manager, the Head of Design, and the Lead Engineer. The focus was on refining the platform’s capabilities and user experience, addressing specific questions such as:

1. Support for Multiple File Types
Deliberating whether the platform should enable all agents to support multiple file uploads or if this feature should be exclusive to the compliance manager. 

2. One-Off Uploads from Chat Interface
Considering the feasibility and utility of allowing users to upload documents directly through a chat interface.

3. Scope of User Uploads in the Document Center
Discussing the number and type of files users can upload in the Document Center. This is crucial for ensuring the platform is tailored to the specific needs of the users and the kinds of critical documents for compliance analysis.

4. Transparency on uploaded data
How to assure users their data is handled securely and used for compliance analysis, to build trust and ensure compliance with data privacy regulations.

In these collaborative sessions, I created low-fidelity designs, which brought clarity and depth to our discussions. These initial designs served as a tangible foundation, enabling stakeholders to visualize and better understand the proposed complex concepts and functionalities. They facilitated more informed and productive conversations and ensured everyone involved had a clear and cohesive vision of the project’s direction, bridging the gap between abstract ideas and practical implementation.

Next Steps

As the project is being developed, next steps include:

• Designing high-fidelity prototypes
• Validating the proposed designed
• Understanding metrics
• Handing off design to engineering team
• Running Quality Assurance on developed product

Takeaways

1. AI Reduces Complexity
By automating tasks such as document analysis, data interpretation, and compliance assessment, AI reduces the need for extensive manual effort and expertise. This simplification not makes compliance more accessible to businesses while increasing efficiency and accuracy. 

2. Collaborative Sessions with Key Stakeholders Are Essential
The project’s progression underscores the importance of involving key stakeholders in early-stage discussions. The collaborative sessions align the platform’s development with technical feasibility and user needs.

Nothing great is build alone.

Reach out to collaborate.

Nothing great is build alone.

Reach out to collaborate.

Nothing great is build alone.

Reach out to collaborate.

ADI MEIRA

Linkedin

•

Mail

ADI MEIRA

Linkedin

•

Mail

ADI MEIRA

Linkedin

•

Mail