Customer Health Dashboard System

One-Liner

Built Power BI dashboards integrating Dynamics, JIRA, and PSA data to track customer health and flag at-risk accounts 1-2 weeks earlier than previous methods.


Full Context

The Situation

Customer risk was being identified reactively—often after issues had already escalated. Data existed across multiple systems (Dynamics CRM, JIRA, PSA) but wasn’t consolidated or actionable. Leadership needed visibility into portfolio health; consultants needed early warning signals.

Your Role

Designed and built dashboard system that consolidated data across systems, defined health indicators, established thresholds for intervention, and created operational workflows for using insights.

The Approach

  • Mapped data sources: Dynamics (account data), JIRA (issues, progress), PSA (resource allocation, timeline)
  • Defined health indicators: milestone completion, open issues, stakeholder engagement, risk flags
  • Built Power BI dashboards with drill-down capability
  • Established thresholds that triggered intervention playbooks
  • Created executive summary views for leadership visibility
  • Trained team on dashboard usage and interpretation

The Outcome

At-risk accounts identified 1-2 weeks earlier. Intervention playbooks triggered automatically based on health signals. Dashboards used in executive communications and steering committees. Contributed to 92% on-time delivery performance.


Metrics & Impact

MetricValueContext
Earlier risk detection1-2 weeksCompared to previous methods
Systems integrated3Dynamics, JIRA, PSA
Dashboard usersTeam-wideConsultants and leadership
Delivery performance92% on-timeEnabled by visibility

Dashboard Components

  • Account health scores
  • Milestone tracking
  • Open issue trends
  • Risk burn-down charts
  • Conversion defect rates
  • Test pass rates

Skills Demonstrated

Primary Skills

Secondary Skills


Resume Usage

Appears in: 21/25 variants

Bullet Point Versions

Technical audience (detailed):

Built Power BI dashboards integrating Dynamics, JIRA, and PSA data to track implementation health, conversion defects, test pass rates, and risk indicators—enabling earlier intervention and informing executive communications.

General audience (accessible):

Created data dashboards that identified at-risk customers 1-2 weeks earlier, enabling proactive intervention and improving delivery outcomes.

Leadership focus (strategic):

Developed customer health monitoring system providing portfolio visibility to leadership and triggering intervention playbooks that protected delivery performance.

Abbreviated (space-constrained):

Built Power BI health dashboards flagging at-risk accounts 1-2 weeks earlier.


Transferable Themes

  • Problem-solving under ambiguity
  • Cross-functional collaboration
  • Technical execution
  • Leadership / influence without authority
  • Process improvement
  • Innovation / creative solution
  • Crisis management
  • Data-driven decision making
  • Stakeholder management
  • Scaling / growth
  • Cost reduction
  • Revenue generation

Best theme for this project: Data-driven decision making and proactive risk management


Interview Preparation

STAR Format

Situation: Customer risk was being identified too late—often after escalation. Data existed across Dynamics, JIRA, and PSA but wasn’t consolidated. Leadership lacked portfolio visibility. Consultants were reactive rather than proactive.

Task: Build a health monitoring system that would surface risk earlier and enable proactive intervention.

Action:

  • Mapped data across three source systems
  • Defined health indicators based on implementation experience (milestones, issues, engagement)
  • Built Power BI dashboards with account-level and portfolio-level views
  • Established thresholds that triggered specific intervention playbooks
  • Created executive summary for leadership review
  • Trained team on interpretation and response protocols

Result: At-risk accounts identified 1-2 weeks earlier. Team adopted proactive intervention approach. Dashboards became standard tool for project governance. Contributed to maintaining 92% on-time delivery.

Likely Follow-up Questions

  1. “What metrics did you include in the health score?”
  2. “How did you handle data quality issues across systems?”
  3. “How did you get the team to actually use the dashboards?”
  4. “What interventions did you trigger based on health signals?”

Potential Challenges/Objections

ConcernResponse
”How do you know it was 1-2 weeks earlier?”Compared timing of risk identification in dashboard vs. when issues would have surfaced through escalation in pre-dashboard period.
”Power BI dashboards are common—what made yours effective?”Integration across systems, clear thresholds tied to intervention playbooks, and embedding into team workflows rather than standalone reports.

Parent organization: Tyler Technologies Similar projects:


Reflection

What went well:

  • Cross-system integration provided comprehensive view
  • Thresholds tied to playbooks drove action
  • Leadership visibility improved governance

What you’d do differently:

  • More automated alerting (vs. dashboard checking)
  • Better mobile access for on-the-go monitoring

Unexpected lessons:

  • Dashboard adoption requires workflow integration, not just access
  • Health metrics need regular recalibration as business changes

Main pages:

  • what-ive-done — Technical achievement demonstrating data integration and analytics skills
  • my-superpowers — Primary evidence for Power BI, customer health monitoring, and data-driven decision making

Target roles:

Related: See Status Pack Automation, Customer Success Playbook System