Andrée Archbold

Without exit criteria, workstreams close with open items for operations to pick up. Agree what each workstream must deliver to close, and confirm it at steering group before releasing the team. #ProgrammeDelivery #Governance

Hand-built test data misses the cases real data contains. Use masked production data for system and acceptance testing, with privacy sign-off before anyone loads it. #Testing #Banking

A RAID log updated once a month is a record, not a control. Review risks, issues and dependencies weekly with their owners, close what's resolved and escalate what isn't. #ProgrammeDelivery #Governance

Paying customers isn't the last step. Check a sample of payments against the calculation, confirm the root cause is resolved, and get independent assurance before telling the regulator it's complete. #Remediation #Governance

Customer risk ratings go out of date as circumstances change. Set a review cycle by risk level, track overdue reviews weekly and report the backlog to the AML/CFT compliance officer. #AMLCFT #FinancialCrime

When two programmes need the same data engineers or testers, agree priority at portfolio level, not team by team. Publish the allocation and review it every month. #Portfolio #ProgrammeDelivery

The first four weeks set a programme up. Confirm the sponsor, governance, team, plan and RAID log before work starts, and the programme runs on facts from day one. #ProgrammeDelivery #Governance

Every date and deliverable promised to the regulator needs an owner, a tracker entry and a weekly status. Report progress before the regulator asks, and flag any risk to a commitment the week it appears. #RegulatoryCompliance #Governance

Data migration on a core banking change needs its own lead, plan and testing. Run at least three trial migrations, reconcile every one, and get business sign-off on the data before cutover. #Transformation #Banking

Lessons learned reports help most when the next programme reads them at mobilisation. Keep them in one place, tag them by theme, and review the relevant ones before you set the first plan. #ProgrammeDelivery #Governance

Agree acceptance criteria with the business before each piece of work starts. The team knows what to build, testers know what to check, and sign-off becomes a formality rather than a negotiation. #Agile #ProgrammeDelivery

Every change to a transaction monitoring rule or threshold needs a recorded reason, test evidence and sign-off. A clear audit trail lets the bank show the regulator why each setting is in place. #AMLCFT #FinancialCrime

A regulatory date doesn't move, so the plan needs contingency from the start. Hold back time in the schedule, track it weekly at steering group and release it only with an agreed reason. #RegulatoryCompliance #ProgrammeDelivery

Every steering group paper needs one clear question for the group to decide. Put the decision on page one, with the options and your recommendation, and keep the detail in the appendix. #Governance #ProgrammeManagement

AI tools can draft status reports, summarise test results and check requirements for gaps. Keep a named person accountable for every output, and record in the decision log where the team used AI. #AI #ProgrammeDelivery

A remediation programme can't forecast cost or timing until it knows which customers are affected. Define the population, the period and the calculation method first, and get sign-off on them before any customer contact. #Remediation #Governance

AML system changes go live smoothly when the analysts who use them help design them. Bring operations into requirements and testing, and plan training before go-live, not after. #AMLCFT #FinancialCrime

When two programmes change the same system in the same quarter, plan them together. Keep one dependency register across both, agree release dates jointly and give one person authority to decide when they clash. #ProgrammeDelivery #Portfolio

Escalating an issue early is ownership, not failure. Bring it to the steering group with the impact, the options and a recommendation, so the decision gets made in one meeting. #Governance #ProgrammeDelivery

Decisions made in meetings and not recorded get reopened. Log each major decision with the rationale, the owner and the date. When scope or priorities get questioned later, the record answers it. #Governance #ProgrammeManagement