Traceability across the layers and across business domains Vertical traceability links a strategic priority down through capability and value stream to the resources operations need, and horizontal traceability links the same elements across domains, so a change traces to its intent and can be tested for its knock-on before it is made.
Traceability across the layers and across business domains
A traceability grid with five layer rows and three business-domain columns. The rows run from Strategy at the top, tinted as the origin, down through Competence, Capability and Value stream to Operations at the bottom, with a left axis marking vertical traceability. The columns are Retail banking, Payments, and Risk and compliance, each cell naming the artefact at that layer for that domain. The vertical trace steps down the retail-banking column as a dashed accent arrow at each layer boundary, its head docking the top of the card below, and a dashed accent arrow crosses the capability row into payments to mark the knock-on across a domain. A legend draws each glyph in the direction it runs.
Vertical trace Layer Retail banking Payments Risk and compliance Strategy Cut onboarding time Faster account opening Grow instant payments Move money in seconds Meet FCA duties Evidence-led assurance Competence Digital onboarding One identity check Real-time clearing 24/7 settlement Controls assurance Continuous monitoring Capability Verify a customer Automated KYC Settle a payment Instant rails Screen a transaction Risk scoring Value stream Applicant journey Apply to first login Payment journey Instruct to credit Case journey Alert to disposition Operations KYC team and tools People, data, systems Ledger and gateways Rails, reconciliation Analysts and models Staff and detection
Vertical trace: strategy down to operations
Horizontal trace: knock-on across a domain
