Open
Conversation
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

For data visualization, I would rely on Looker (or a similar modern BI tool) for both the semantic layer and the final dashboards, ensuring a unified and trusted analytics environment.
The LookML semantic layer would sit directly on top of our curated dbt models, giving the Execution team a single, consistent source of truth for all calculated metrics such as gross proceeds, average open duration, and success rates. Centralizing these definitions guarantees consistency across all reports at Hiive and eliminates manual calculation errors.
For the visualization strategy, I would design a Transaction Health Dashboard focused on operational efficiency. A Sankey diagram or funnel chart would serve as the primary visualization to map transaction flow across stages—from Opened to Paid or Terminated—clearly revealing volume drop-offs and bottlenecks.
To support deeper operational insights, I would incorporate additional visuals:
This multi-layered approach gives the team visibility into both high-level patterns and stage-level failures, allowing them to monitor performance and act quickly on operational issues.