Task-Boundary Mode
How task-instance boundaries are drawn from the event stream. Applies to every Task SoP, Step SoP, and Variants view.
Opportunity
Surfaced
Medium Impact
UX
Intake Session Fragmentation
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)
148 hrs
Annual (17 users)
1,953 hrs
$146,505
Projected (1,000 users)
114,906 hrs
$8,617,942
Description & Data Evidence
'View Intake Processing' screen durations (wall-clock time on screen) vary enormously by case type: 'Follow-up Other' averages 3,778s vs 'Other' at 15s (256x ratio). Overall CV is 1725%, indicating extreme fragmentation. 863 intake sessions across 171 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
5/5
Actionability
5/5
Specificity
5/5
Remediation Alignment
5/5
Key Findings
- 'Follow-up Other' intake avg 3,778s vs 'Other' at 15s
- 256x variability ratio between case types
- Overall: avg 1,240s, median 2s, CV 1725%
- Max single intake session: 516,130s (8,602 min)
- Metric: wall-clock screen duration (task-mining events have no interaction dwell)
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 |
|---|---|---|
2347125 |
8602 min session | Extended intake screen duration |
2337820 |
5822 min session | Extended intake screen duration |
2355499 |
1334 min session | Extended intake screen duration |
2309395 |
254 min session | Extended intake screen duration |
2349955 |
182 min session | Extended intake screen duration |
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
Why do 'Initial - Other' cases require 20x more time in the intake screen than 'Follow-up' cases?
Identifies what's different about 'Other' cases — source data quality, routing, or manual review requirement.
2
Are users waiting for specific external inputs before they can click 'Push to Case Processing'?
If yes, a 'Pending External Info' status would let sessions close cleanly.
3
Is the Phobos screen being used as a primary document viewer because it's more convenient than opening source files?
Reveals whether the long session is productive work or a workaround for a UI gap.
Remediation Ideas
- Pre-populate intake forms with available case data to reduce manual entry
- Case-type-specific intake templates with required fields only
- Auto-classification of incoming cases to route to appropriate intake workflow
- Guided intake wizard with progress indicator and validation
Implementation Roadmap
Effort
Small
Timeline
4-6 weeks
Primary Owner
Ops + Engineering
Dependencies
- Phobos workflow configuration access
- Business rules for 'Pending External Info' status
Phased Delivery
- Status schema + rules definition (1-2 weeks)
- Phobos config changes (2 weeks)
- Rollout + training (1-2 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
Medium
Confidence the agent-detected pattern is real
Feasibility
25% weight
High
Ease of building the remediation
Adoption
20% weight
Medium
Likelihood users change workflow
Compliance
15% weight
High
Simplicity of PV validation path
1953 hrs × 0.88 =
1719 hrs / year
At 1,000 users: 101,117 hrs / year
· $7.6M