Relying Party Center
Overview
The Relying Party Metering initiative introduced a new capability within the HITRUST platform for organizations to monitor and manage relying-party usage. The experience needed to give customers greater visibility into license consumption while supporting a scalable licensing and pricing model for the business..
The Challenge
The project began with cross-functional discovery sessions involving product leadership, engineering, business stakeholders, and subject matter experts.
The initial request was simple:
"Design a way to track and manage relying party usage within the platform."
Rather than designing screens immediately, I focused on understanding the business objectives behind the request.
Through stakeholder interviews, product discussions, and workflow analysis, I identified how relying parties interacted with the platform, how usage should be measured, and how metering could support both customer transparency and long-term product strategy.
Discovery
As discovery progressed, several opportunities emerged.
Organizations needed a simple way to:
Understand their relying party utilization
Monitor license consumption
Track usage over time
Identify capacity limits
Make informed purchasing decisions
Reduce uncertainty around licensing
From a business perspective, leadership also needed a scalable solution that could support future pricing models while remaining intuitive for enterprise customers.
These insights shifted the project from simply displaying usage data to creating a product capability that aligned customer value with business growth.
Defining the Experience
I translated the discovery findings into workflows, early concepts, and prototypes that explored how organizations could review and manage relying-party activity.
The experience was structured around the questions administrators were most likely to ask:
What is our current usage?
How much capacity do we have remaining?
How has our usage changed?
Are we approaching a licensing limit?
What action should we take next?
This question-based structure helped establish the information hierarchy and kept the interface focused on decisions rather than raw system data.
Early concepts allowed the team to evaluate terminology, metering rules, navigation, data visualization, and administrative workflows before moving into detailed interface design.
Ui Design
I designed the Relying Party Center as a centralized enterprise dashboard that transformed complex utilization data into clear, actionable information.
The experience included:
Current usage and capacity indicators
License-utilization summaries
Historical usage trends
Status and threshold messaging
Relying-party management tools
Guidance for addressing capacity needs
Visual hierarchy made current status immediately visible, while supporting details remained available for deeper review. Charts and indicators provided context around usage without requiring administrators to interpret raw data.
I used reusable design-system components and responsive patterns to create a consistent experience that could scale as licensing rules and reporting capabilities evolved.
Validation and Collaboration
I partnered closely with product managers, engineers, executives, business stakeholders, and subject-matter experts throughout the project.
Regular design reviews helped us validate workflows, clarify metering logic, refine terminology, and evaluate technical feasibility. As business and product requirements evolved, I iterated on the designs while maintaining a consistent experience and a clear connection to the original customer needs.
This collaboration was particularly important because design decisions affected more than the interface—they also influenced how usage was defined, measured, and communicated across the platform.
My contribution and outcome
I helped lead the experience from discovery through design refinement. My contributions included facilitating stakeholder discussions, analyzing requirements, mapping workflows, defining the information hierarchy, creating prototypes, designing the enterprise dashboard, documenting component behavior, and partnering with engineering throughout implementation.
The resulting Relying Party Center established a scalable framework for communicating license utilization and managing relying-party activity. It gave organizations clearer visibility into usage, remaining capacity, and emerging licensing needs while creating a foundation for future pricing and monetization strategies.
The project also introduced reusable dashboard, data-visualization, and status-messaging patterns that could support additional administrative and reporting experiences throughout the HITRUST platform.