KNOWMIUM / MOVING MINDS / HONG KONG
Transamerica Life (Bermuda)
Eight conversation cases · Shared context and confidential role briefings
Choose your case
Open a scenario, read the shared context, then select your assigned role. Keep your confidential briefing to yourself during the conversation.
The Friday Promise
Shared context | Everyone may read this
A Hong Kong high-net-worth client has applied for a substantial universal life policy through a Hong Kong insurance broker in TLB’s specialist HNW distribution network. The proposed policy concerns family wealth and succession planning, with due-diligence material on the applicant, policy owner and the origin of the proposed funding. The intermediary has told the client to expect a meaningful status update by Friday—not a guaranteed policy issue date.
On Wednesday, Customer & Business Operations finds that a source-of-funds explanation does not match supporting documentation. Compliance requires clarification before its due-diligence review can be closed. Underwriting is a separate assessment and has not yet been completed. The intermediary says further unexplained delay could put the relationship at risk.
Operations and Compliance have 20 minutes to agree what evidence is required, how to handle a defensible priority review, who will contact the intermediary, and exactly what can be promised for Friday. Neither party can approve a policy issue or waive checks.
Choose your role
Open only your assigned briefing for the exercise. Role tabs are freely switchable.
No role briefing is open. Select your assigned role above to read it.
If the role tabs do not switch, expand your assigned briefing below.
ROLE A: Customer & Business Operations Manager | CONFIDENTIAL
ROLE A: Customer & Business Operations Manager | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Keep the customer relationship intact and establish a credible path to Friday. You can coordinate work and communication, but you cannot waive required checks.
Your perspective. The team has already spent considerable time collecting materials, and this is not the first application slowed by questions that appeared near the end. The intermediary increasingly treats Operations as the source of the delay. Your team will bear the pressure of explaining any slip, even though it does not control the compliance judgement.
Pressures and constraints
- The intermediary has said the customer will reconsider the application if there is no meaningful progress before the weekend. You have not verified whether this is a firm ultimatum or negotiating pressure.
- Two operations colleagues can prioritise follow-up today, but they also have other time-sensitive cases. A prolonged, open-ended review would disrupt that workload.
- You want a consistent message. Saying simply “Compliance has not approved it” may protect Operations in the short term but could damage trust between the departments.
Information the other parties may not know
- The intermediary may be able to explain one transaction tomorrow morning; the inconsistency may require fresh supporting evidence from the client or their advisers.
- The partner was originally told to expect a status update on Friday, not a policy-issue decision. Later messages blurred that distinction.
Your discretion and boundaries. You can arrange document collection, assign a case coordinator, confirm a reassessment time and propose a factual partner update. You cannot promise Compliance clearance, an underwriting decision or policy issue.
What you need from the conversation. Leave with a practical plan and language that everyone can stand behind—even if the answer to the intermediary is not the one they want.
ROLE B: Legal & Compliance Senior Manager | CONFIDENTIAL
ROLE B: Legal & Compliance Senior Manager | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Protect the integrity of required checks while helping the business make whatever progress is genuinely possible.
Your perspective. The application is high profile, but the remaining questions go to the basis on which the business can understand and assess the customer. Your team is tired of being invited into urgent conversations only after external expectations have been set. Yet an inflexible response would leave colleagues without a way forward.
Pressures and constraints
- You cannot endorse the application while material questions remain unresolved. The perceived value of the customer does not change that standard.
- The review queue is full. If you fast-track this case, there must be a defensible reason and clarity about what other work may be delayed.
- You are concerned that conditional language will be interpreted by the intermediary as an assurance that approval is inevitable.
Information the other parties may not know
- The two outstanding issues are not equally difficult: one could probably be resolved with a focused explanation; the other requires supporting evidence and might change the assessment.
- An analyst raised a related question a week ago, but the request appears to have been routed to a general inbox and may not have reached the operations owner.
Your discretion and boundaries. You can distinguish mandatory evidence from clarification, assign a reviewer for prompt reassessment, specify what information would enable a decision, and agree appropriate wording for an interim status. You cannot pre-clear due diligence, ignore the discrepancy or imply that a completed Compliance review guarantees underwriting or policy issue.
What you need from the conversation. Secure a defensible way to complete the review and a better process for preventing late discovery of similar issues.
The Data Nobody Owns
Shared context | Everyone may read this
At month-end, Finance has again found that the statuses of several Hong Kong policy-servicing requests differ between an Operations case tracker and the extract used for reconciliation. The affected requests include policy loans and surrenders—real types of transactions supported by TLB's Hong Kong customer-service forms. No customer loss has been identified in this fictional case, but staff must manually establish which requests are awaiting documents, approved for further processing or financially completed.
The discrepancy has resurfaced for three reporting cycles. IT supports the data interface, Operations manages the request journey, and Finance needs reliable transaction status and dates for reconciliation. An internal control review has asked for root-cause analysis, an interim reconciliation check and named business and technical owners. Some reporting and IT services across TLB are supported by group affiliates, making hand-offs and definitions especially important.
The Data Governance Lead meets Finance and Operations. They must agree what each status means, who controls each hand-off, what will be done before the next close, and who should authorise any process or system changes.
Choose your role
Open only your assigned briefing for the exercise. Role tabs are freely switchable.
No role briefing is open. Select your assigned role above to read it.
If the role tabs do not switch, expand your assigned briefing below.
ROLE A: IT Data Governance Lead | CONFIDENTIAL
ROLE A: IT Data Governance Lead | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Establish an accountable model that can survive beyond the next reconciliation cycle.
Your perspective. From your perspective, the organisation has treated this as a technical defect whenever the report is wrong and as a business-process defect whenever the source is wrong. That ambiguity prevents an enduring fix. Data definitions, input rules, interfaces and reporting transformations are intertwined; you do not believe a single team can fix everything independently.
Pressures and constraints
- A senior sponsor wants one person’s name against the issue by the end of the week. You are concerned that naming an owner without decision rights or resources will be meaningless.
- The integration team can investigate the transformation logic, but it cannot redesign an operational process without business input.
- You need the teams to distinguish documents received, servicing approved, and payment or accounting completed before any validation rule can work consistently.
Information the other parties may not know
- An interface mapping uses the latest workflow status when an explicit financial-completion date is blank. IT did not define the business meaning of that status.
- You believe a joint working group could diagnose the causes quickly, but it would need dedicated representatives for two weeks—not just attendance at a weekly meeting.
Your discretion and boundaries. You can commit technical diagnostic capacity, propose a distinction between business data ownership and technical control ownership, and establish common definitions. You cannot assign business accountability by yourself or promise a complete platform redesign this quarter.
What you need from the conversation. Agree how the defect will be contained now and how durable ownership, definitions and escalation will work afterward.
ROLE B: Finance Director / Reporting Lead | CONFIDENTIAL
ROLE B: Finance Director / Reporting Lead | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Make reporting dependable and stop month-end staff from repeatedly correcting the same errors.
Your perspective. Finance is held accountable for the accuracy and timeliness of reports even though it does not create the data or control the interface. The manual reconciliation is costly, and inconsistent definitions erode confidence in decision-making. You are tired of hearing that a data issue is “upstream” when Finance still has to explain the consequences.
Pressures and constraints
- The next reporting cycle starts in two weeks. There is no appetite for an experiment that makes this month’s output less reliable.
- You have one analyst spending roughly a day each week tracking exceptions. Their work on other reporting improvements is falling behind.
- You are being asked to sign off on reports even when the underlying root cause is unresolved.
Information the other parties may not know
- One Finance report treats “completed” as an Operations approval, while reconciliation requires the date the related financial transaction is posted. That distinction has never been formally agreed.
- You could provide one experienced analyst for a short working group if that would materially reduce recurring manual effort.
Your discretion and boundaries. You can define reconciliation acceptance criteria, document transaction use cases, share exception evidence and allocate limited analyst time. You cannot assume permanent stewardship of records created by Operations or accept unexplained changes in published figures.
What you need from the conversation. Obtain clear controls for the next close, a shared definition and named accountability for a lasting fix.
ROLE C: Customer & Business Operations Manager | CONFIDENTIAL
ROLE C: Customer & Business Operations Manager | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Protect customer servicing while creating an improvement plan that frontline teams can actually implement.
Your perspective. Operations enters much of the information, but some fields arrive from intermediaries or other systems. Staff work within forms and processes they did not design. You accept that errors happen, yet it seems unfair to classify every downstream mismatch as poor data entry without examining the system design and reporting interpretation.
Pressures and constraints
- Your team is already handling a backlog of customer requests and cannot absorb a major manual clean-up without reprioritisation.
- Changing input rules may slow processing or generate new exceptions unless staff know why the field matters and what to do in edge cases.
- You fear a single “data owner” label becoming a way to redirect blame to your team.
Information the other parties may not know
- Policy-loan and surrender requests sometimes have legitimate pauses for additional owner documents or payment verification; the tracker does not distinguish all these pauses cleanly.
- You could pilot a revised process with a small team and nominate a subject-matter expert, but not commit the entire function to immediate retraining.
Your discretion and boundaries. You can map source processes, nominate a steward, trial revised guidance and help validate exceptions. You cannot guarantee flawless input when definitions are unsettled or accept sole responsibility for transformations IT controls.
What you need from the conversation. Agree responsibilities across the data lifecycle and a practical intervention that does not create a new customer-service problem.
We Built It. They Won't Use It.
Shared context | Everyone may read this
As part of the Target Operating Model improvement effort, an internal project has piloted software to check the completeness of Hong Kong policy-service requests before an Operations reviewer takes over. The fictional pilot covers administrative intake for tasks such as beneficiary changes and policy-loan requests; it does not make coverage, AML or financial decisions. On standard requests, staff spend less time identifying missing fields and duplicated documents.
IT wants to move to a controlled rollout. Operations is unconvinced: the pilot used mostly clean cases, while real submissions may involve trustees, multiple signatories, changed personal information or incomplete supporting material. In customer servicing, a wrong request status can lead to repeated partner queries even when the technology itself is working.
The Solution Lead and Operations Manager must recommend whether to expand the pilot, what types of request it may handle, who reviews exceptions, and what a safe fallback looks like. Neither party can declare the system production-ready alone.
Choose your role
Open only your assigned briefing for the exercise. Role tabs are freely switchable.
No role briefing is open. Select your assigned role above to read it.
If the role tabs do not switch, expand your assigned briefing below.
ROLE A: IT Solutions / Automation Lead | CONFIDENTIAL
ROLE A: IT Solutions / Automation Lead | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Avoid losing a promising improvement through indefinite review, while securing meaningful business ownership.
Your perspective. Your team worked with business representatives during design and believes the core solution is sound. You know it does not handle every exception; that was never the plan for the first release. You are concerned that new requirements are appearing after successful testing and that the organisation may lose the benefits of the investment.
Pressures and constraints
- The sponsor expects a recommendation this week, and your development team is scheduled to move to another project next month.
- Further development is possible, but substantial redesign would displace planned work; small configuration and reporting improvements are feasible.
- You believe measured rollout is safer than remaining permanently in pilot mode, but cannot make Operations take responsibility.
Information the other parties may not know
- The positive results came from straightforward forms. Complex ownership and signatory exceptions have not been robustly tested.
- You can provide enhanced monitoring during a controlled rollout and design a manual fallback if agreed before rollout.
Your discretion and boundaries. You can offer additional testing, exception dashboards, staged release and support capacity. You cannot call the system “fully validated” for situations the pilot did not test or commit unlimited engineering resources.
What you need from the conversation. Secure a decision on the conditions for rollout, further testing or a clearly bounded redesign—along with joint accountability.
ROLE B: Customer & Business Operations Manager | CONFIDENTIAL
ROLE B: Customer & Business Operations Manager | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Protect service reliability and staff confidence while finding a realistic path to improvement.
Your perspective. The automation is promising, and your team does want less manual work. But the test scenarios were cleaner than the actual cases that reach staff. When a customer asks what happened, Operations will still be responsible for explaining and resolving it. Staff have already seen one earlier technology rollout create extra work before it stabilised.
Pressures and constraints
- Your processing backlog is growing; a solution that genuinely saves time would help. A failed rollout could make the backlog worse.
- Experienced employees are worried that the automation will leave them with only the difficult exceptions but no extra support.
- The team is accountable for service accuracy and timely follow-up, not just the number of forms processed automatically.
Information the other parties may not know
- Two senior team members are willing to support another pilot if they help define success and retain a clear escalation path.
- The biggest objection from frontline staff is not losing jobs; it is uncertainty about who is accountable when the automation behaves unexpectedly.
Your discretion and boundaries. You can nominate pilot users, agree operational acceptance criteria, provide real exception samples and support phased deployment. You cannot approve a general rollout without a credible fallback, training and accountability model.
What you need from the conversation. Reach a decision that protects customer experience and allows improvement, even if it changes the original implementation plan.
The Partner Briefing Is Already Booked
Shared context | Everyone may read this
Hong Kong's Opus One Indexed Universal Life product is already on the market and is available only to eligible Professional Investors. Marketing has arranged a refresher briefing for selected distribution partners next week. It will help brokers explain the product's Index Account and Fixed Account features to eligible Professional Investors, and handle servicing questions from high-net-worth clients. TLB's commercial leadership has publicly identified adviser education as important to IUL adoption.
Legal & Compliance objects to a graphic that turns an Index Account crediting floor into a claim that the whole policy cannot lose value—ignoring charges, insurance costs and contractual conditions. Operations says one partner FAQ suggests a faster turnaround for policy-service requests than its team can consistently commit to. Most of the material is usable, but partners already have the date in their diaries.
Marketing, Compliance and Operations must decide which slides or FAQs can be released, what language and service commitments must change, and who can sign off on the final partner pack. The product's eligibility rules and contractual terms are not negotiable.
Choose your role
Open only your assigned briefing for the exercise. Role tabs are freely switchable.
No role briefing is open. Select your assigned role above to read it.
If the role tabs do not switch, expand your assigned briefing below.
ROLE A: Marketing Assistant Manager | CONFIDENTIAL
ROLE A: Marketing Assistant Manager | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Preserve partner confidence and briefing momentum without creating inaccurate promises.
Your perspective. The materials have gone through several review rounds, and distribution partners have started asking when they can use them. You see a real opportunity to demonstrate that the company is becoming more responsive and innovative. You are frustrated that serious concerns are appearing only now, after the timetable was shared.
Pressures and constraints
- Changing the briefing will require explanation to distribution partners and rebooking an already confirmed programme.
- Your team can update wording quickly if feedback is specific; it cannot rebuild the entire partner pack overnight.
- A highly caveated message may be technically correct but so unclear that intermediaries will not understand what is actually new.
Information the other parties may not know
- The session is for a smaller group of authorised partners, with a clear audience segment; it is not a general public marketing campaign.
- The phrase implying broad downside protection was inserted after commercial review; the actual product explanation does not depend on keeping that phrase.
Your discretion and boundaries. You can revise claims, adjust the sequence of briefings, narrow the audience and change the briefing emphasis. You cannot publish unapproved or misleading material, or make operational promises without an owner.
What you need from the conversation. Find a viable briefing plan and accurate pack that preserves credibility with partners and internal teams.
ROLE B: Legal & Compliance Senior Manager | CONFIDENTIAL
ROLE B: Legal & Compliance Senior Manager | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Ensure that communications accurately describe the offering and that important qualifications are not hidden.
Your perspective. The legal concern is not opposition to Opus One or the partner briefing. It is that several claims could be interpreted more broadly than the company can support. If partners repeat those claims to customers, the problem becomes much harder to correct later. You also believe Legal should have been consulted before the external timeline was announced.
Pressures and constraints
- You have limited review capacity and cannot perform a new end-to-end legal review of every asset at short notice.
- A smaller partner briefing still requires clear and accurate statements; a smaller audience does not remove the obligation.
- If the team simply removes all meaningful claims, Marketing will be left with materials that are useless to the business.
Information the other parties may not know
- The principal defect is a headline that conflates Opus One's Index Account crediting floor with the cash-value return on the entire policy. Most other supporting copy appears usable.
- You could review a restricted set of high-priority materials within two days if a single owner consolidates changes.
Your discretion and boundaries. You can distinguish essential revisions from lower-priority drafting improvements, propose clearer language and prioritise a narrow set of assets. You cannot approve claims you believe are materially inaccurate or imply formal approval for material you have not seen.
What you need from the conversation. Support materials that explain Opus One clearly without overstating eligibility, returns or service promises, with an agreed approval path.
ROLE C: Customer & Business Operations Manager | CONFIDENTIAL
ROLE C: Customer & Business Operations Manager | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Avoid creating customer-service commitments that frontline teams cannot consistently deliver.
Your perspective. Your team was brought into the partner-material review late. Customer-facing staff have received a draft process map but not complete guidance for atypical cases. You support the partner education effort, but a misleading FAQ can trigger avoidable enquiries and unrealistic turnaround expectations.
Pressures and constraints
- Your best subject-matter experts are supporting another high-priority initiative this week.
- Partners will expect the service experience described in marketing materials. If staff cannot deliver it, complaints will arrive in Operations first.
- You do not want to be portrayed as the team stopping growth simply because it needs time to prepare.
Information the other parties may not know
- The standard customer journey is largely ready. The unresolved issues concern three less-common exception types and unclear escalation ownership.
- You can provide a realistic service-request FAQ, named escalation contacts and a clear distinction between service targets and guarantees before the briefing.
Your discretion and boundaries. You can nominate escalation contacts, identify operational must-haves, propose a limited pilot and set training requirements. You cannot promise unrestricted service capacity or support published claims that exceed the process as designed.
What you need from the conversation. Secure a credible partner-service explanation that matches what Operations can actually deliver.
The Budget That Works on Paper
Shared context | Everyone may read this
TLB publicly reports that some financial-reporting and IT support comes from Aegon-affiliated companies as it builds more independent internal processes. In this fictional case, a group-supported interface connects Hong Kong policy administration with downstream servicing and Finance reports. It still runs, but changes require several hand-offs and experienced specialists. Planned partner-status improvements and reduced reconciliation work depend on it.
IT wants two-phase funding to modernise the interface, document dependencies and strengthen monitoring. Finance is comparing this with other transformation and service priorities. No major outage has occurred recently, but manual checks and difficult-to-trace mismatches consume staff time. The specific interface, problems and proposal are fictional.
The Finance Director and IT Architecture Lead are preparing a recommendation for the organisation's normal budget approval process. They can adjust scope, sequence, evidence and funding gates; neither can approve expenditure alone.
Choose your role
Open only your assigned briefing for the exercise. Role tabs are freely switchable.
No role briefing is open. Select your assigned role above to read it.
If the role tabs do not switch, expand your assigned briefing below.
ROLE A: Finance Director | CONFIDENTIAL
ROLE A: Finance Director | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Make an investment recommendation that is credible against competing priorities and uncertainty.
Your perspective. The proposal uses words such as “resilience,” “technical debt” and “future-proofing,” but you are struggling to see which benefits are essential and which are speculative. There are other projects with clearer near-term impact. You are not opposed to infrastructure investment; you need a disciplined case and a visible way to control spending.
Pressures and constraints
- Senior management has asked Finance to apply tighter scrutiny to discretionary transformation requests this quarter.
- You worry that approving a large transformation now may create pressure for additional unbudgeted work later.
- The business has not recorded a major outage on this component in the past year, which some executives see as evidence that replacement can wait.
Information the other parties may not know
- You might support a staged investment if the early phase produces evidence and contains a genuine decision point before larger spending.
- You have seen an internal cost estimate that excludes some staff time and transition support, making you sceptical of the headline business case.
Your discretion and boundaries. You can recommend phased funding, agreed risk metrics, scenario analysis and a range of investment options. You cannot promise formal approval or accept benefits that nobody can explain or measure.
What you need from the conversation. Create a recommendation that shows decision-makers the consequences of both investing and deferring.
ROLE B: IT Architecture / Solutions Lead | CONFIDENTIAL
ROLE B: IT Architecture / Solutions Lead | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Prevent a manageable technical weakness from becoming a critical operating constraint.
Your perspective. The platform works today largely because experienced engineers keep it working. It is difficult to change, slows integrations and forces teams to use workarounds. You fear that repeated deferrals will make the eventual migration more expensive and risky. You also recognise that “replace it because it is old” is not a sufficient business argument.
Pressures and constraints
- One of the few engineers who knows the legacy component deeply may move to another role next year.
- A number of planned process improvements depend on integrations that the current platform makes costly to deliver.
- If funding is delayed, you must still maintain service quality with a fixed technology headcount.
Information the other parties may not know
- The preliminary estimate includes contingency for undocumented dependencies between the Hong Kong team and group-affiliated support; there is not yet sufficient discovery evidence to treat it as final.
- A limited discovery and remediation phase could reduce uncertainty and address the most fragile dependencies before a replacement decision.
Your discretion and boundaries. You can offer a staged plan, document maintenance hours and incidents, compare “repair versus replace,” and define resilience measures. You cannot guarantee zero disruption or quote speculative savings as certain.
What you need from the conversation. Leave with a credible path to a decision, including the evidence Finance needs and the risks the business will explicitly accept if it delays.
The Exception That Became the Rule
Shared context | Everyone may read this
In this fictional case, access to a Hong Kong policy-administration support tool includes several privileged accounts used by an affiliated support team. IT documented a temporary exception: account access is being checked manually while an automated recertification control is developed. The interim checks have been recorded, but the technology improvement has already missed its first milestone. The team now requests another three months.
IT says disabling support access abruptly could delay time-sensitive servicing fixes. Risk says a recurring exception requires new evidence, first-line ownership and a decision by an authorised approver. TLB's published Three Lines framework makes the operating team the risk owner and Risk an adviser/overseer—not the person who silently approves the exception. Both recognise that the sensitivity of policyholder information makes access discipline important.
The IT Delivery Manager and Risk Manager are meeting before formal risk acceptance. They must agree what evidence is missing, what interim mitigations are feasible and what recommendation should be escalated. Neither role has authority to override mandatory controls or approve the exception themselves.
Choose your role
Open only your assigned briefing for the exercise. Role tabs are freely switchable.
No role briefing is open. Select your assigned role above to read it.
If the role tabs do not switch, expand your assigned briefing below.
ROLE A: IT Delivery Manager | CONFIDENTIAL
ROLE A: IT Delivery Manager | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Maintain essential business service while getting the remaining control work completed.
Your perspective. Your team is not ignoring the control. The planned automated access review depended on configuration by an affiliated support team and local testing; both have taken longer than planned. You believe that immediately disabling the affected process could cause more disruption than carefully managing the temporary exposure.
Pressures and constraints
- Technical support needs controlled access to the servicing environment; abrupt removal could slow incident resolution, though it would not justify unmanaged access.
- Your delivery team is split between completing the remediation and supporting another committed programme.
- You feel judged for missing the original date, though several dependencies were outside your control.
Information the other parties may not know
- The group-support dependency explains the first extension but not all the current schedule pressure; local priority changes also contributed.
- A narrower interim approach is possible: reduce the number of privileged accounts, make time-limited access requests and tighten independent access-log reviews.
Your discretion and boundaries. You can disclose the dependency history, propose milestones, strengthen interim monitoring, narrow the affected scope and seek business support for a mitigation. You cannot alter the risk acceptance criteria or represent unfinished controls as complete.
What you need from the conversation. Agree a truthful recommendation that protects essential operations and makes the remediation credible.
ROLE B: Risk Management Assistant Manager | CONFIDENTIAL
ROLE B: Risk Management Assistant Manager | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Ensure the organisation does not normalise an unmanaged exception while recognising genuine delivery constraints.
Your perspective. A temporary exception can be defensible when it has a clear owner, effective compensating controls and an achievable exit. Here, the date has moved twice and the case for extension sounds increasingly similar each time. You suspect the underlying work will never be prioritised unless the risk is made visible to the right decision-makers.
Pressures and constraints
- Risk reports outstanding exceptions to management, and repeated extensions damage confidence in the process.
- You need sufficient evidence to advise the authorised decision-maker, including what has changed since the last review.
- A rigid refusal that creates an uncontrolled workaround elsewhere would not improve the situation.
Information the other parties may not know
- The manual review evidence is largely complete, but several access exceptions lack clear justifications. That does not demonstrate that continued exposure is acceptable.
- You may be willing to support a different risk treatment or narrower scope if there is real accountability and measurable progress.
Your discretion and boundaries. You can challenge assumptions, seek evidence, recommend conditions and bring the right approvers into the decision. You cannot waive mandatory controls or approve the extension. You can advise the authorised decision-maker only on a complete, evidenced risk picture.
What you need from the conversation. Reach a recommendation that is transparent about risk, operational consequences and who must decide.
The New Model, the Same People
Shared context | Everyone may read this
TLB has publicly announced work on a new Target Operating Model, intended to clarify accountability, improve execution discipline and elevate service. In this fictional Hong Kong business-unit implementation, the change would give each complex policy-service request a designated case coordinator instead of passing responsibility from one functional queue to the next.
The business leader has committed to showing fewer hand-offs and clearer partner communication within the next quarter. But the same staff must continue processing existing policy-service requests—including beneficiary updates, policy loans and ownership changes—while learning the proposed responsibilities. HR has heard concern about workload, training time and what happens when an exception crosses several specialist teams.
HR and the business leader meet to agree what can realistically be piloted, what existing activities could stop, which supervisors will support the transition and how success will be measured. Neither can conjure up extra headcount or eliminate specialist approval controls.
Choose your role
Open only your assigned briefing for the exercise. Role tabs are freely switchable.
No role briefing is open. Select your assigned role above to read it.
If the role tabs do not switch, expand your assigned briefing below.
ROLE A: HR Director | CONFIDENTIAL
ROLE A: HR Director | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Help the business deliver change without making commitments that depend on invisible employee capacity.
Your perspective. You support the target operating model. Your concern is that the implementation plan treats training, adoption and workload transition as side tasks. When teams are stretched, people may comply superficially with a new process while continuing to use the old one to get work done.
Pressures and constraints
- Employees want clearer responsibilities, but the organisation does not have every answer yet.
- You want managers to own the people side of the transition rather than expecting HR to “manage the resistance.”
- You do not have budget for a large new change programme or long classroom training.
Information the other parties may not know
- Two experienced servicing supervisors are open to the case-coordinator approach but have not been given protected time to coach others.
- You could redeploy a small amount of HR support for targeted manager coaching and transition communications if the leader sets realistic priorities.
Your discretion and boundaries. You can help design role clarification, communication, manager support and measures of adoption. You cannot promise additional headcount or use confidential employee comments as individual evidence against the manager.
What you need from the conversation. Agree how the leader will own and resource the people implications while maintaining momentum.
ROLE B: Business Unit Leader | CONFIDENTIAL
ROLE B: Business Unit Leader | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Deliver visible progress on the operating-model commitment without losing service performance.
Your perspective. The existing processes genuinely need improvement. Delaying indefinitely is not acceptable to customers or senior leadership. You believe employees are capable of more efficient ways of working, but you know there is little spare capacity. You are frustrated when general statements about “change fatigue” appear without actionable alternatives.
Pressures and constraints
- Senior leadership expects evidence of improvement next quarter, and the current service backlog is already visible.
- A sponsor has seen examples of other teams reducing handoffs without extra permanent headcount and expects a credible local pilot.
- If the first milestone slips, you worry the entire programme will lose priority and sponsorship.
Information the other parties may not know
- You could stop two low-value internal status summaries and replace them with a single case dashboard, although you have not yet agreed this with managers.
- The milestone presented to sponsors has become more ambitious than the original implementation plan; it may be possible to report a narrower, defensible early milestone.
Your discretion and boundaries. You can reprioritise work, designate change champions, phase delivery and redefine what constitutes credible first-quarter progress. You cannot add staff immediately or ignore ongoing service obligations.
What you need from the conversation. Leave with a plan that creates genuine early movement without quietly transferring impossible workload to the team.
The Broker Who Wants an Answer Now
Shared context | Everyone may read this
An established distribution partner is helping a high-net-worth policyholder reorganise family ownership of an existing Hong Kong-issued life policy. The client wishes to transfer policy ownership to a family trust. TLB's Hong Kong transfer-of-ownership form explicitly deals with entity/trust ownership and asks whether the existing policy is subject to collateral assignment. Whether this transfer can be recorded depends on the completed documentation and applicable review.
The intermediary has submitted the trust and signatory details, but the collateral-assignment question was left incomplete and the trust signatory evidence remains under review. Operations cannot responsibly promise when the transfer will be recorded. Different status messages have increased frustration. The intermediary fears looking ineffective in front of the client and says other advisers need certainty before discussing the wider estate plan.
The intermediary has called the Customer Operations Manager. They need to establish precisely what is outstanding, who can obtain it, what will happen at the next review point and how to communicate uncertainty honestly. Neither role may override ownership-verification requirements or suggest that an incomplete request is approved.
Choose your role
Open only your assigned briefing for the exercise. Role tabs are freely switchable.
No role briefing is open. Select your assigned role above to read it.
If the role tabs do not switch, expand your assigned briefing below.
ROLE A: Customer & Business Operations Manager (TLB) | CONFIDENTIAL
ROLE A: Customer & Business Operations Manager (TLB) | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Restore confidence through ownership and transparency while avoiding commitments outside your authority.
Your perspective. You know the case has been more difficult than normal, and some internal handoffs were slower than they should have been. You also know that the remaining work involves legitimate specialist review. You worry that a defensive explanation will make the insurer appear evasive, but an optimistic promise could make matters worse.
Pressures and constraints
- The partner is commercially important and has made several frustrated calls to colleagues.
- You need enough cooperation from the intermediary to obtain any remaining client information quickly and accurately.
- You have been asked to improve external communication, but you cannot personally speed every specialist decision.
Information the other parties may not know
- An internal specialist can reassess trust ownership and signatory evidence within two business days once all documents arrive. After transfer, the former owner's myTLB access to this policy ends, so the communications team also needs a clear handover message.
- Previous status updates used inconsistent wording because two internal teams believed the other was acting as the case owner.
Your discretion and boundaries. You can appoint one communication owner, explain what is known and unknown, establish the next review point, and ask for targeted clarification. You cannot promise approval, invent certainty or reveal internal deliberations that should remain confidential.
What you need from the conversation. Keep the partner engaged in a credible process even without giving the definitive answer they initially demand.
ROLE B: External Intermediary / Broker | CONFIDENTIAL
ROLE B: External Intermediary / Broker | CONFIDENTIAL
Your confidential brief | Do not share this sheet
What you are trying to accomplish. Protect your customer relationship and obtain a credible plan from the insurer.
Your perspective. The client has delegated the process to you and expects expertise, judgement and responsiveness. Each request for more information makes you appear less in control. You do not necessarily expect the insurer to abandon its standards, but you are tired of receiving vague updates and having to chase multiple contacts.
Pressures and constraints
- Your customer has asked you to compare an alternative provider if there is no meaningful movement this week.
- You have spent substantial time collecting information and answering changing questions.
- You need specific next steps you can relay to the client without having to admit that you have no idea what is happening.
Information the other parties may not know
- The client can tolerate a short, explained delay if their advisers receive a precise document list and dependable review point; the threatened Friday escalation is not a fixed legal deadline.
- The trustees can probably supply signatory evidence promptly. A family adviser also believes a prior collateral interest was discharged, but has not established what confirmation the insurer requires.
Your discretion and boundaries. You can obtain clarifications, propose a communication cadence, seek a named contact and discuss realistic options with the client. You cannot make TLB approve the transfer or promise the family advisers an outcome you do not control.
What you need from the conversation. Leave knowing what is actually happening, why it matters and what you can responsibly tell your client.