Task-Boundary Mode How task-instance boundaries are drawn from the event stream. Applies to every Task SoP, Step SoP, and Variants view.
Dashboard / Rework / Phobos-to-Veeva Context Switching
Opportunity Surfaced
Medium Impact UX

Phobos-to-Veeva Context Switching

Opportunity Lifecycle

1
Surfaced
2
Accepted
3
Remediating
4
Remediated
Status persists in your browser. In production, these actions notify team members, trigger workflows, and begin value-realization monitoring.

★ Savings Opportunity

Assumes $75/hr fully loaded cost. Pilot: 19 days. See methodology.
Pilot Period (19d)
48 hrs
Annual (17 users)
628 hrs
$47,078
Projected (1,000 users)
36,924 hrs
$2,769,262
Risk-Adjusted (17 users, annual)
577 hrs
0.92× composite · see breakdown ↓

Description & Data Evidence

'View Processing Queue' in Phobos remains open for avg 149 min (median 22 min, max 3661 min) as a background session while users perform actual work in Veeva Safety, Word, and other apps. 64 such background sessions detected across 56 cases.

Self-Evaluation Scores

The platform grades each finding on four dimensions (1–5 scale). Low scores flag findings that need more data or clearer remediation before acceptance.

Overall 4/5
Actionability 5/5
Specificity 4/5
Remediation Alignment 5/5

Key Findings

  • 64 background Processing Queue sessions (>5 min) detected
  • Average dwell: 149 min, max: 3661 min
  • 56 cases, 7 users affected
  • 159.0 total background hours in pilot period

Case Evidence

Specific case IDs pulled from the pilot data where this pattern is most pronounced. In production, clicking a case opens its full event timeline.

Case ID Signal Context
2353948 219 events Across 2 apps
2317182 214 events Across 2 apps
2349955 198 events Across 2 apps
2355714 193 events Across 2 apps
2345982 191 events Across 2 apps

Validation Questions

0 of 3 answered
Before accepting this opportunity, work through the questions below with the relevant subject-matter experts. Your answers lock in the acceptance criteria and — when you toggle Share with Pyze — inform how our agents surface similar patterns in the future.
1
What specific information from the Phobos 'Processing Queue' page do users need to reference while working in Veeva?
Identifies what a persistent overlay or deep-link would need to surface.
2
Is the 'Advance/Proceed' click in Phobos a compliance requirement or just a signal?
Determines whether the manual handshake can be automated.
3
Why are narratives being edited in standalone Word instances?
Confirms the Word usage pattern ties to the same Phobos-Veeva context gap.

Remediation Ideas

  • Push notifications when queue items are ready, eliminating polling
  • Auto-refresh queue with real-time updates instead of manual checks
  • Integrate queue status into Veeva Safety sidebar to avoid app switching
  • Smart queue prioritization to reduce time spent scanning for next case

Implementation Roadmap

Effort
Medium
Timeline
8-12 weeks
Primary Owner
Engineering (Integration)
Dependencies
  • Deep-linking capability between apps
  • Webhook / status sync design
  • Browser extension infrastructure (optional)
Phased Delivery
  1. Integration design (2 weeks)
  2. Webhooks + deep links (4-6 weeks)
  3. UAT + rollout (2-3 weeks)

How Risk-Adjusted Savings Is Calculated

The risk-adjusted number is the annual savings multiplied by a composite factor of four independent dimensions. Each dimension is rated High (1.0×), Medium (0.8×), or Low (0.5×). See full methodology.

Detection 40% weight
High
Confidence the agent-detected pattern is real
Feasibility 25% weight
Medium
Ease of building the remediation
Adoption 20% weight
High
Likelihood users change workflow
Compliance 15% weight
Medium
Simplicity of PV validation path
627 hrs × 0.92 = 577 hrs / year
At 1,000 users: 33,970 hrs / year · $2.5M