Traditional reports versus Insights

Understanding the differences between Traditional reports and Insights, including their strengths and ideal use cases, helps LSAs make recommendations that align technical capabilities with business objectives. This decision is strategic because it shapes how users interact with, and derive value from, data.

Traditional reports in Pega Platform™ provide a foundation for structured data presentation. These reports are effective when the primary requirement is delivering consistent views of data that can be reproduced, distributed, and archived.

Core characteristics

Traditional reports provide stability and completeness. They present data in a structured, tabular format that emphasizes thoroughness over interactivity. After configuration, these reports deliver consistent output for formal business processes, compliance requirements, and standardized operational workflows.

Ideal use cases

Use traditional reports when business requirements include the need to:

• Generate comprehensive list reports that require detailed data in multiple columns. For example, a compliance officer reviewing all open cases with full attribute sets benefits from the column-based presentation of Traditional reports.
• Provide standardized operational reports that change infrequently. Monthly financial summaries, quarterly performance reports, and annual compliance documentation are examples where stability and consistency are required.
• Integrate with batch scheduling and automated distribution. Many processes depend on reports generated at specific intervals and distributed by email or shared repositories.
• Meet compliance and audit requirements that mandate specific, reproducible formats. Traditional reports maintain the formal structure required for regulatory submissions.
• Support print formatting for physical distribution or archival purposes. Traditional reports provide control over page breaks, headers, footers, and layout.

Insights provide a modern approach to data exploration and analysis. Built for interactivity and visual appeal, Insights enable users to explore data dynamically, identify patterns, and drill down into details within an intuitive interface.

Core characteristics

Insights prioritize engagement and flexibility. Unlike Traditional reports, Insights respond to user interactions in real time, enabling exploratory analysis without technical expertise or report redefinition.

Ideal use cases

Use Insights when business requirements emphasize dynamic analysis and interactive exploration to:

• Create executive dashboards that display key performance indicators in charts, gauges, and trend visualizations that update in real time.
• Monitor operations where real-time updates are required, such as contact center queue depths and service level agreements.
• Provide drill-down capabilities for root cause analysis, such as navigating from regional sales totals to individual transactions.
• Enable dynamic filtering, sorting, and data exploration for business analysts.
• Visualize trends and patterns through charts and heat maps when identifying seasonal patterns or outliers is more important than raw data.

Consider the following guidelines when you select the appropriate reporting feature:

Choose Traditional reports when:

• The report format is standardized and changes infrequently.
• Print formatting and physical distribution are required.
• Compliance or audit requirements mandate specific formats.
• Users need comprehensive tabular views with extensive column details.
• Integration with batch scheduling and automated distribution is required.
• The primary use case is archival documentation or formal record-keeping.

Choose Insights when:

• Users need to explore data from multiple perspectives.
• Real-time or near-real-time data updates are valuable.
• Visual pattern recognition is more important than detailed tabular data.
• Users require drill-down capabilities for root cause analysis.
• Self-service analytical capabilities reduce support overhead.
• Dashboard presentations for landing pages or operational monitoring are needed.
• Complex calculations based on multiple data sources enhance analytical value.

Hybrid approach

In many environments, LSAs design reporting architectures that use both features strategically. For example, monthly financial reports might use Traditional reports, while executive dashboards use Insights.

Summary

Traditional reports provide stability, consistency, and comprehensive structure for formal reporting processes. Insights deliver interactivity, visual engagement, and analytical flexibility for modern data exploration. 

By selecting the appropriate reporting feature - or even by combining both - LSAs create reporting solutions that balance user experience, system performance, and business value.
 

Check your knowledge with the following interaction: