You're viewing a live public demo on fictional data — nothing you change here is saved.

Information duplication · Identified

Financial reconciliation duplicate lookups

Reconciling premium receipts against the general ledger means staff manually look up the same policy record in both the Policy Administration System and the Finance ERP, because the two aren't cross-referenced.

Edit

Friction Priority

High (72/100) — which friction to investigate first, not how valuable the underlying information is (that's Information Advantage, a separate measure).

  • frequency: band 5/5 × weight 0.3 = 1.50
  • estimatedTimeCost: band 5/5 × weight 0.25 = 1.25
  • customerImpact: band 1/5 × weight 0.2 = 0.20
  • riskImpact: band 1/5 × weight 0.15 = 0.15
  • informationAvailability: band 5/5 × weight 0.1 = 0.50

Not yet incorporated (no data source in this system): business impact -- no field in this schema represents it yet; decision significance -- no field in this schema represents it yet; feasibility of intervention -- no field in this schema represents it yet.

Friction cost

Estimated time cost: 300 person-hours per period.

  • estimatedTimeCostHours = frequency x timePerOccurrence x peopleAffected -- a person-hours-per-period estimate, not a currency figure.
  • No error/delay/missed-opportunity cost was supplied -- additionalMonetaryCost is null, not zero, to distinguish 'not estimated' from 'estimated at nothing'.
  • customerImpact and riskImpact are not included in this calculation -- they feed Friction Priority (a separate, ranking-only signal), not the cost estimate itself.

Details

Department
Finance
Workflow
—
Process stage
—
Owner
Finance Reconciliation Lead
Customer impact
Low
Risk impact
Low
Evidence / notes
Illustrative estimate for this demonstration dataset, not a measured figure.

Information assets involved

Information Diagnosis

Friction → Information Diagnosis → Information Asset -- connects this friction to the information conditions behind it, where one exists.

  • Duplicated

    The same policy/premium record is looked up separately in the Policy Administration System and the Finance ERP because they aren't cross-referenced, so every reconciliation re-does the same lookup twice.

    Opportunity: Cross-referencing the two systems once would remove the duplicate lookup entirely.

    Assets: General Ledger & Financial Transactions, Policyholder Master Data

AI Opportunities grounded in this friction

Grounded in the information assets involved above, plus this friction and any diagnosis of it, passed as context -- Friction is a discovery entry point in its own right, not only a filter on assets found some other way.

None yet.