KT Portfolio Site

Blog

  • UX Case Study: Risk Model Utility

    The Regulatory Reality

    Financial institutions live in a world of models. Credit risk models, market risk models, operational risk models – thousands of algorithms making billions of decisions that determine who gets loans, how much capital banks need to hold, and whether financial systems remain stable.

    When these models fail, economies collapse. When they’re poorly managed, regulators impose massive fines. When they’re not properly documented, audits become nightmares.

    Crisil’s Model Infinity was designed to solve the chaos of model risk management through systematic process design and comprehensive oversight capabilities.

    The Stakeholder Complexity Map

    Model risk management involves more moving parts than most enterprise software. My research revealed a web of interdependent roles, each with different priorities and success metrics:

    Model Developers create and maintain the algorithms

    Model Validators stress-test and challenge model assumptions

    Risk Managers oversee model performance and compliance

    Auditors verify that everything follows regulatory requirements

    Business Users rely on model outputs for decision-making

    Each group needed different information, different workflows, and different levels of detail. The challenge was creating one platform that served all these needs without overwhelming anyone.

    Process Mapping Before Interface Design

    I spent weeks mapping existing model governance workflows – not just the official processes documented in compliance manuals, but how work actually got done.

    Discovery findings:

    • Model documentation was scattered across email, shared drives, and individual laptops
    • Validation processes varied dramatically between teams and model types
    • Version control was manual and error-prone
    • Regulatory requirements were interpreted differently across departments
    • Knowledge transfer during staff changes was inconsistent and incomplete

    The current state was functional but fragile. Any process improvement had to acknowledge existing workflows while gradually introducing better practices.

    Information Architecture for Regulatory Compliance

    The platform’s IA needed to accommodate three distinct requirements simultaneously:

    1. Operational efficiency for daily users
    2. Regulatory compliance for auditors and examiners
    3. Executive oversight for risk management and business leadership

    I developed a layered architecture that could present the same underlying data through different lenses:

    Operational View: Task-focused interfaces for model developers and validators
    Compliance View: Audit trail and documentation interfaces for regulatory reporting
    Strategic View: Portfolio-level dashboards for risk management and executive teams

    Workflow Automation Design

    The platform’s core value proposition was automating manual processes while maintaining regulatory rigor. This required careful analysis of which steps could be automated versus which required human judgment.

    Automation opportunities:

    • Document template population based on model metadata
    • Workflow routing based on model type and risk tier
    • Notification triggers for validation deadlines and regulatory milestones
    • Report generation for standard compliance requirements

    Human oversight requirements:

    • Model validation sign-offs
    • Risk assessment judgments
    • Exception approvals
    • Strategic model governance decisions

    Design for Multiple Mental Models

    Different user types approached model information with completely different mental frameworks:

    Developers thought in terms of model performance and technical specifications
    Validators focused on testing scenarios and potential failure modes
    Risk Managers considered portfolio-level exposure and concentration risk
    Auditors emphasized documentation completeness and process compliance

    The interface design needed to accommodate these different perspectives without forcing users to adopt unfamiliar conceptual models.

    Regulatory Constraint Design

    Every design decision existed within regulatory boundaries defined by SR 11-7, TRIM, SS 1/23, and other global standards. This wasn’t about adding compliance as a feature – it was about designing compliance into the foundation.

    Design implications:

    • All user actions needed comprehensive audit trails
    • Data retention policies influenced information architecture decisions
    • Role-based access controls determined interface complexity
    • Documentation requirements shaped form design and validation logic

    Prototype Strategy for Complex Workflows

    Standard prototyping approaches didn’t work for model governance workflows. These processes often span weeks or months, involve multiple stakeholders, and include exception handling that’s difficult to demonstrate in typical demos.

    I developed scenario-based prototypes that walked stakeholders through complete model lifecycle examples, including edge cases and error conditions. This helped validate both normal workflows and exception handling approaches.

    The Implementation Challenge

    Model Infinity needed to integrate with existing model development tools, risk systems, and regulatory reporting platforms. The design had to accommodate:

    • Data imports from multiple model development environments
    • Integration with enterprise risk management systems
    • Export capabilities for regulatory reporting requirements
    • API connections to facilitate workflow automation

    This required interface design that could handle data inconsistencies and integration failures gracefully while maintaining user productivity.

    Measuring Success in Regulated Environments

    Success metrics for regulatory software are different from typical enterprise applications. User satisfaction matters, but compliance completeness matters more.

    Primary success indicators:

    • Reduction in model documentation time
    • Improvement in audit preparation efficiency
    • Decrease in regulatory finding severity
    • Increase in model governance consistency across teams

    Secondary indicators:

    • User adoption rates across different stakeholder groups
    • System uptime and performance during regulatory examinations
    • Integration success with existing tools and processes

    The Systematic Approach

    Model Infinity succeeded because it systematized what had previously been ad hoc. The platform didn’t just digitize existing processes – it created better processes and then made those processes easier to follow.

    The user experience design supported this systematic approach by making the right actions obvious and the wrong actions difficult. Good governance became the path of least resistance.

    Lessons in Regulatory Design

    Designing for highly regulated industries requires different priorities than consumer software. Users will tolerate interface complexity if it helps them avoid regulatory problems. They value comprehensive functionality over simplified workflows.

    The most important design principle was transparency – users needed to understand not just what the system was doing, but why it was doing it and how it supported their compliance obligations.

    Model Infinity demonstrated that regulatory software doesn’t have to be painful to use, but it does have to be designed with regulatory success as the primary objective.

  • UX Case Study: SASS app for sales

    Overview:

    The goal of this project was to design a user-friendly Software-as-a-Service (SaaS) application tailored specifically for sales teams. The app aimed to streamline the sales process, improve team collaboration, and provide insights into sales performance through an intuitive interface.

    Challenges:

    1. Complexity of Sales Workflows: Sales teams often face complicated workflows, managing multiple tasks like tracking leads, setting up meetings, and following up with prospects. The main challenge was creating an interface that simplified these workflows while still providing advanced features needed by the team.
    2. Data Visualization: Sales teams rely heavily on data to make decisions, but presenting this data in an easily digestible way was crucial. The challenge was to create data visualizations that provided valuable insights without overwhelming the user.
    3. Collaboration Needs: Sales teams often work in collaboration with other departments such as marketing and customer support. We needed to ensure that the app supported seamless communication and task assignment across teams.

    Research:

    We began by interviewing sales teams from various industries to understand their pain points. Key findings included:

    • Complexity in task management: Sales reps often had to juggle multiple tools for CRM, email tracking, and task management, leading to inefficiencies.
    • Lack of real-time data: Sales teams struggled to get up-to-date information on the status of deals or leads.
    • Difficulty in team coordination: Communication between sales members and other departments was often siloed, leading to missed opportunities and delays.

    We also performed a competitive analysis of other sales SaaS tools, focusing on user interface design, features, and ease of use. This gave us a sense of the common features and design elements that resonate with sales teams.

    User Personas:

    1. Sarah, Sales Rep: Needs a streamlined way to track leads, manage tasks, and view performance metrics without getting bogged down by complicated features.
    2. David, Sales Manager: Needs detailed analytics to track team performance, generate reports, and ensure that everyone is meeting their targets.
    3. Lena, Marketing Manager: Needs to share updates with the sales team on new campaigns and provide them with relevant content or leads.

    Design Process:

    1. Wireframing & Prototyping: We began with low-fidelity wireframes to establish the basic structure of the app. The layout focused on simplifying complex workflows with a dashboard-style interface. We used large, easy-to-read buttons and clear sectioning of tasks to ensure quick navigation. A prototype was built using Figma, which allowed us to quickly iterate based on feedback.
    2. Task Flow: The primary task flows we focused on were:
      • Lead Management: Sales reps needed to quickly add and update leads, set tasks, and follow up without switching between multiple tools.
      • Performance Analytics: Managers needed an overview of the team’s performance through charts and graphs that were easy to interpret at a glance.
      • Collaboration Tools: We implemented features such as shared task lists, team chat, and file sharing to enable collaboration between sales and other departments.
    3. Usability Testing: We conducted multiple rounds of usability testing with real sales reps and managers. We asked participants to complete key tasks, such as adding a new lead, creating a sales pipeline, and generating a report. Observing their interactions helped us refine the app’s flow, minimize cognitive load, and remove unnecessary steps.
    4. Visual Design: The final visual design focused on clarity and simplicity. We chose a modern, minimalistic aesthetic with a neutral color palette to reduce distractions and highlight important information. Key actions were highlighted in bold, while secondary features were placed in easily accessible sidebars.

    Key Features:

    1. Lead Tracking: Users can add new leads with a simple form that auto-fills common information based on email addresses. The lead’s progress is displayed on a timeline, with color-coded indicators for each stage (e.g., initial contact, follow-up, negotiation, closed).
    2. Sales Dashboard: The dashboard provides a bird’s-eye view of sales activities, including total revenue, deals in progress, and team performance. Customizable widgets allow sales teams to prioritize the most important metrics.
    3. Collaboration Tools: The app integrates chat, task lists, and file sharing within the platform, allowing team members to communicate without switching tools. Sales reps can mention teammates in comments, attach relevant files, and schedule meetings directly from within the app.
    4. Advanced Analytics: Managers can access detailed performance metrics, such as deal conversion rates, average sales cycle length, and revenue projections. The app supports real-time updates, so decisions are based on the most current data.
    5. Mobile Accessibility: Given the on-the-go nature of sales, the app was designed to be fully responsive, providing the same seamless experience on mobile devices. This ensures that sales teams can access their leads, manage tasks, and communicate with the team from anywhere.

    Results:

    After launching the initial beta version of the app, we gathered feedback from a select group of sales teams. Key outcomes included:

    • Increased Efficiency: Sales reps reported a 30% reduction in time spent switching between different tools.
    • Improved Collaboration: The team collaboration features led to a 25% increase in task completion rates and reduced miscommunication between departments.
    • Better Data Visibility: Managers praised the real-time analytics and visualizations, with 85% of them reporting improved decision-making processes.

    Conclusion:

    This project was a success because it addressed the unique needs of sales teams while ensuring that the app remained intuitive and easy to use. By focusing on simplifying workflows, enhancing collaboration, and providing real-time insights, we were able to create a tool that empowered sales teams to perform at their best. Future iterations of the app will include additional AI-driven features, such as predictive lead scoring and automated follow-up reminders.

    This case study demonstrates how a well-designed SaaS app can transform the way sales teams operate by optimizing their workflows, enhancing communication, and providing actionable insights.