Collaboration @ Visa
People Team Innovation Simulation
A realistic internal conversation. Choose your role below — then stay in it.
What is this simulation about?
Today’s simulation is about what happens after a good idea is created. On Day 1, you developed an early solution connected to a real people-related challenge inside Visa. Today, that idea enters a more realistic internal conversation.
A solution does not move forward because it is clever. It moves forward when other people understand it, test it, challenge it, improve it, and decide it is worth the time, attention, trust, and resources it will require.
In this simulation, two participants will represent the People Team. They will bring an early solution into a stakeholder conversation. The other participants will represent internal counterparts. Their role is not to perform, overact, or create artificial conflict. Their role is to bring realistic pressure from inside a large, fast-moving organization.
- The idea is ready for a small pilot.
- The idea has promise but needs specific changes first.
- The idea is not ready yet, and the group identifies what evidence, redesign, or stakeholder input is needed.
A vague “sounds good” is not a strong outcome. A realistic “yes, if…” or “not yet, because…” can be a strong outcome.
What makes this realistic
This is not an acting exercise. If you are playing an internal counterpart, do not be theatrical. Do not object for the sake of objecting. Do not invent extreme or silly barriers.
Instead, behave like a thoughtful stakeholder who has to protect something real: time, trust, focus, adoption, risk, data integrity, business relevance, manager capacity, employee experience, implementation discipline.
The best pushback is not hostile. The best pushback is specific, grounded, and useful.
- Conviction — you believe in the idea.
- Clarity — you can explain it simply.
- Openness — you can adjust when challenged.
- Real questions, not rhetorical ones.
- Real constraints, not invented ones.
- Real standards — help the group get to a better decision.
Choose your role
Click your role to open your briefing. Once you open it, you will not be able to switch. Do not share your briefing with other participants before the simulation begins.
Do not read other roles before the simulation. The realism of this exercise depends on each person knowing only their own briefing. Resist the temptation to peek.
Solution Lead
You believe in the idea. You are bringing it into the room. You lead the conversation.
Open my briefing →Evidence & Adoption Lead
You support the Solution Lead. Your lens is evidence, adoption, and implementation reality.
Open my briefing →Chair
You are chairing the meeting. You are open but not automatically convinced. You make the conversation realistic.
Open my briefing →Technology / Data / Risk
You represent the responsible innovation lens: data, privacy, AI governance, and employee trust.
Open my briefing →Manager / Business Experience
You represent the everyday reality of managers and employees. You know what actually gets used.
Open my briefing →Solution Lead
You helped develop the idea. You believe in it. Today you bring it into a realistic internal conversation and make the case for moving forward.
You are one of two People Team members bringing the solution into the stakeholder conversation. You helped develop the idea during the innovation work. You believe it addresses a real problem. You are not here to defend a finished product — you are here to test whether it is ready to move forward and to strengthen it through the conversation.
- Whether the stakeholders understand the problem you are solving.
- Whether the solution is specific enough to be credible.
- Whether the group can agree on a useful next step.
- Whether the pushback is helping you improve the idea or simply blocking it.
- How to stay open without losing conviction.
- How to involve your Evidence & Adoption partner at the right moments.
- You need to explain the problem clearly before explaining the solution.
- You need to distinguish between what you know and what you are still learning.
- You need to avoid over-presenting. This is a conversation, not a pitch.
- You need to respond to pushback without becoming defensive.
- You need to help the group move toward a real decision, not just polite interest.
A strong conversation is one where the group does not simply admire the idea. It tests the idea. You are listening for whether the group can distinguish between a good intention and a workable solution, a broad concept and a pilotable design, early evidence and proven impact, enthusiasm and adoption, data and judgment, agreement and commitment.
- The stakeholders understand the problem, not just the solution.
- The pushback helps you improve the idea, not just survive it.
- The group agrees on a specific, realistic next step.
- You leave with a clearer sense of what the idea needs to be credible.
Evidence & Adoption Lead
You are the second People Team voice. Your lens is evidence, adoption, implementation, trust, and practical next steps.
You are the second People Team member. You helped shape the solution, but your particular lens is evidence, adoption, implementation, trust, and practical next steps. You are not the lead voice. You are the grounding voice. You speak when the conversation needs evidence, when it needs honesty about what is not yet known, or when it needs a realistic path forward.
- Whether the evidence base is honest and proportionate.
- Whether adoption has been thought through, not assumed.
- Whether the implementation path is realistic.
- Whether the pilot design is narrow enough to be manageable.
- Whether the People Team is asking for the right thing at the right time.
- Whether the conversation is moving toward a real decision.
- You may need to slow down your partner if they are overclaiming.
- You may need to name what is not yet known.
- You may need to reframe a broad idea as a specific pilot.
- You may need to acknowledge a legitimate concern from a counterpart before your partner does.
- You may need to propose a concrete next step when the conversation stalls.
You are not there to undermine your partner. You are there to make the case stronger by making it more honest. The most credible People Team is one that can say: “Here is what we know. Here is what we are still learning. Here is the smallest useful version of this idea. Here is what we need from you.”
- The group trusts the evidence base because it is honest, not inflated.
- The adoption path is specific, not assumed.
- The pilot design is narrow enough to be credible.
- The People Team leaves with a clear, realistic next step.
- The conversation ends with a decision, not just positive energy.
Chair
You are chairing the meeting. You are open to the solution, but not automatically convinced. Your job is to create the kind of internal conversation that would actually happen.
You are an internal Visa counterpart chairing the meeting. You are not part of the People Team. You are open to the solution, but you are not automatically convinced. You have agreed to spend time with the People Team because the problem may matter, but you need to understand whether this idea is practical, relevant, and worth moving forward.
Do not rescue the People Team. Do not block them for sport. Do not make the conversation artificially easy. Your job is to create the kind of internal conversation that would actually happen before a new people-related solution earns time, resources, attention, or sponsorship.
- Business relevance and competing priorities.
- Manager capacity and implementation effort.
- Evidence of adoption, not just intent.
- Whether the People Team is asking for advice, approval, sponsorship, or resources.
- Whether the group is moving toward a real decision or just polite interest.
- Whether leaders or managers would recognize the problem.
- Why this matters now compared with other priorities.
- What the idea would require from the business.
- Whether the idea is specific enough to pilot.
- Whether success can be seen within a reasonable timeframe.
- Whether the People Team is asking for advice, approval, sponsorship, or resources.
- The People Team over-presents, uses vague language, or avoids trade-offs.
- The idea is too large for a first test.
- The business ask is unclear.
- The success measures are vague.
- The conversation sounds positive but does not lead to a decision.
- The solution is connected to a real pain point, not just a broad people aspiration.
- The People Team can explain who the solution is for and what behavior would change.
- They can describe the smallest useful pilot.
- They are clear about what they need from the business.
- They acknowledge what they still need to learn.
Technology / Data / Risk
You represent the responsible innovation lens. You are not there to shut the idea down. You are there to test whether it can be done responsibly, practically, and credibly.
You represent a technology, data, privacy, AI governance, operational risk, or responsible innovation lens. You are not there to shut the idea down. You are there to test whether it can be done responsibly, practically, and credibly. This is especially important if the solution involves AI, analytics, employee data, manager dashboards, listening tools, career matching, skills data, sentiment, employee stories, or any form of recommendation engine.
- What data the solution uses and why.
- Whether employees understand how their information is being used.
- Whether the solution makes recommendations or decisions.
- Where human judgment remains essential.
- Whether managers could misuse or over-trust the information.
- Whether the idea creates fairness or bias concerns.
- Whether data quality is strong enough.
- Whether the pilot has clear boundaries.
- What data is needed and why — could the same outcome be achieved with less sensitive data?
- What employees would be told about how their data is used.
- What managers would see and what decisions the tool would influence.
- How bias or unfairness would be checked.
- What happens if the insight is wrong.
- Who owns the data and what governance would be needed before scaling.
- Whether the pilot is narrow enough to manage risk.
- The data source is unclear.
- Employees would not know how their data is used.
- The solution seems to rank, predict, score, or recommend people without safeguards.
- The People Team overclaims what the data can prove.
- Managers may see information they are not equipped to interpret.
- The pilot is too broad to govern responsibly.
- Data minimization: only what is necessary.
- Transparency: employees know what is collected and why.
- Human judgment is preserved at key decision points.
- Pilot boundaries are clear and enforceable.
- Governance and accountability are named, not assumed.
- The People Team recognizes that trust, privacy, and fairness are not afterthoughts.
Manager / Business Experience
You represent the everyday reality of managers, employees, and business teams. You know how work actually gets done when calendars are full and priorities are shifting.
You represent the everyday experience of managers, employees, and business teams. You know how work actually gets done when calendars are full, priorities are shifting, and teams are under pressure. You are not anti-People-Team. You simply know that even good initiatives can fail if they do not fit into the flow of work.
- Manager workload and time required.
- Employee experience — does this feel supportive or judgmental?
- Workflow fit — does it integrate with existing meetings and tools?
- Change fatigue — how many other initiatives are already running?
- Practical behavior change — what would a manager actually do differently?
- Adoption across different types of teams.
- Whether managers have the skill and time to use it well.
- What a manager would actually do differently next week.
- How much time the solution requires.
- Whether it fits existing meetings, tools, or routines.
- Whether managers would see it as support, surveillance, or extra work.
- Whether the solution works for different types of teams.
- Whether the idea depends on unusually motivated managers.
- What support managers would need and what happens after the pilot ends.
- It adds another platform or requires significant training.
- It creates new reporting or assumes managers have time they do not have.
- It uses generic scripts or one-size-fits-all guidance.
- It creates anxiety for employees or feels like a compliance exercise.
- It does not explain what would actually change next week.
- It is easy to understand and fits into existing workflows.
- It does not require long training or create unnecessary admin.
- It is specific about the behavior change expected.
- It helps managers have better conversations or make better decisions.
- It can be tested with a realistic group before scaling.
- It supports employees without making managers feel blamed.
You are not trying to defeat the idea. You are trying to make sure that if the idea moves forward, it has a real chance of being used.