Project Bridgeway · Tool

Change impact — POPIT

Structured analysis of how Meridian's mortgage digitisation affects People, Organisation, Processes, Information and Technology. Pre-seeded from your discovery sessions — edit and expand as your understanding develops.

5POPIT dimensions
23 → 11 daysApplication cycle
£2.8mTarget saving
What is POPIT? A Business Analysis technique for mapping organisational change across five dimensions: People, Organisation, Processes, Information and Technology. It ensures no part of the enterprise is overlooked when assessing impact. Rate each item High / Medium / Low, add your mitigation thoughts, and note anything that came from a specific stakeholder conversation.
Items assessed
0 / 0
✓ Saved
👥
People
Roles, skills, behaviours, culture, change readiness
0 rated ▾
Billie's prompt: Dawn told you the floor is experienced but resistant to anything that adds steps. That's your biggest adoption risk. What training and support plan will you recommend? Also think about underwriters — automated routing changes how cases reach them.
🏛
Organisation
Structure, governance, reporting lines, performance metrics
0 rated ▾
Billie's prompt: Sandra owns the approval workflow and Jonathan owns the governance frame. If the digital process bypasses the paper-based exception sign-off, who authorises edge cases? That governance gap needs an owner before go-live.
🔄
Processes
AS-IS to TO-BE, workflows, exceptions, handoffs
0 rated ▾
Billie's prompt: The AS-IS is 23 days because paper forms sit in queues. The TO-BE promises 11 days — but only if the digital handoffs are clean. Where are the pinch points? Dawn mentioned that branch staff add notes in the margin of paper forms — where does that contextual data go in the digital process?
📊
Information
Data flows, data quality, GDPR, reporting, audit trail
0 rated ▾
Billie's prompt: Alicia flagged that the audit trail for paper-based decisions is informal and inconsistent. A digital system fixes this — but only if the data model captures the right fields. What information does the regulator need to see, and is it built into the solution design?
💻
Technology
Systems, integrations, infrastructure, NFRs
0 rated ▾
Billie's prompt: Rajesh raised the integration risk with the core banking system early. If the portal can't read live case status from the legacy platform, the 11-day promise breaks. The technology dependency chain — portal → integration layer → core banking — is the highest technical risk on the project.
Impact summary
All rated High and Medium items across dimensions — the basis of your change management plan.
Dimension Impact Description Mitigation