DOMAIN E
Collaboration, communication, and influence
How to help others understand, negotiate, commit, and move together.
See this capability domain in stage expectations. Open the capability model
Choose a capability first. Each preview shows up to three questions; open it for focused batches.
151 questions · 5 capabilities
Communication37
Making information, judgment, and evidence actionable for the listener.
- Teams across three time zones rely on asynchronous reviews, but critical feedback often arrives after implementation is complete. How would you locate where the delay occurs and adjust information and decision cadence?
- A cross-time-zone team relies on chat history for handoffs, and recipients repeatedly misunderstand status and open decisions. How would you shape handoff information and verify understanding?
- Someone hands you a very vague question. How do you clarify first, then give a structured answer?
- A decision is being handed to a colleague in another city to carry out. How do you keep the reason behind it from getting lost?
- A product page advertises automation accuracy without a key applicability limit, and customers have used it in purchasing decisions. After finding the issue, how would you decide whether to withdraw, correct, and notify?
- You discover an incident may affect customer data, but the affected list and restoration time are unknown. How would you organize the first notice and subsequent updates?
- You have five minutes to brief a leader on a project that is not going well. How do you structure the message?
- How do you explain something clearly enough for your manager to see its value or its problem? When they do not take it seriously at first, how do you organize what you say and choose the evidence and the timing?
- Walk someone with no background through a project you did. How do you order the telling?
- Tell me about a real time, because of insufficient up-front research, you halted or substantially overturned a plan when engineering was halfway through. How did you treat it, and how did you reassure the engineering team and rebuild trust?
- A vendor risk may affect a launch, but neither cause nor likelihood is clear. Leadership wants an answer today. How would you report facts, unknowns, safeguards, and the next update time?
- A storage migration could briefly hide some customer data, but the business owner does not know replication lag or rollback limits. How would you explain risk and enable a sound decision?
- A launch decision must be made today, but one key experiment result is missing. How would you distinguish facts, assumptions, unknown risks, and reversible options in your update?
- An incident delayed some orders but lost none, and the business owner must decide whether to pause a promotion. How would you explain the impact?
- An unverified external dependency prevents a reliable date, but leaders want an update. How would you communicate progress and uncertainty?
- A review covers several options and unresolved issues; afterward, attendees disagree about the decision and ownership. How would you record and confirm the outcome?
- Delivery will slip by two weeks, partly due to an internal estimation error and partly to new customer requests. How would you explain the situation and next steps?
- A key metric declines: engineering cares about system errors, operations about handling efficiency, and the business about revenue impact. How would you communicate the same facts?
- A technical review debates several implementation details before agreeing on the user or system problem. How would you set goals, constraints, and comparison criteria, then decide which disagreements need validation?
- Leaders spend only ten minutes weekly on updates, yet the project has multiple risks, decisions, and dependencies. How would you structure a concise update?
- You are leaving a project with an unconfirmed risk that may affect launch. The successor has limited context. How would you hand it off?
- Project documents are fully accessible, but meetings repeatedly revisit decided options and newcomers do not know what can be reopened. How would you improve decision records?
- A small user study suggests a workflow obstacle, but the team wants statistical significance before changing anything. How would you move forward?
- Frontline teams report a high risk in the release window, but each upward update is softened to “we are monitoring it,” so decision-makers take no action. How would you correct the information loss across reporting levels?
- A weekly report requires red, yellow, or green, but a cross-team dependency is unconfirmed and the delivery team fears blame for marking red. How would you report the risk and secure a decision?
- A migration has several internal risks; decision-makers need to know customer-date impact and resource needs. How would you compress technical detail into decision-ready information?
- A service incident affects customer data processing. Support needs user impact, employees need instructions, and compliance needs a timeline. How would you organize communications?
- A stakeholder asks for “an intelligent recommendation entry point” without explaining the outcome. What would you ask to clarify the user task, measure, and hard constraints?
- A review shifts from whether to launch into ownership, budget, and user understanding. How would you notice when discussion moves away from the decision and restate the decision needed?
- Refunds rose in one region just after a payment change. Which questions would help distinguish plausible causes?
- A reviewer requests microservices, but you think the bottleneck is release coordination. What would you ask about user impact, failure boundaries, and growth constraints?
- The most senior person speaks first in reviews and others tend to agree. How would you change question order and discussion format to gather independent evidence?
- You want to test whether a new home page is clearer, but may ask “isn’t this more convenient?” How would you rephrase and seek behavioral evidence?
- Conversion may have fallen because of traffic, experience, price, or sales follow-up. Time is limited. How would you sequence questions by diagnostic value and cost?
- A candidate or colleague says “the team became much more efficient” but has no baseline. How would you ask for context and evidence while keeping the exchange collaborative?
- Usage fell one week after launch, but customer contracts renew quarterly and training is incomplete. What would you ask to determine a meaningful decision window?
- A major customer requests a feature, and sales believes the whole market needs it. What would you ask about samples, use cases, and counterexamples?
No questions in this section match your target. ·
Conflict navigation31
The goals, facts, and decision rights behind a disagreement.
- After you escalated a delivery risk, a colleague felt bypassed and stopped sharing information promptly. How would you repair the relationship while preserving necessary risk transparency?
- In a cross-functional review, you notice the lead’s proposal omits a migration step that would change metric definitions. The meeting is ending and an external partner is present. How would you intervene and follow up?
- Product considers the risk acceptable, while security wants a delay; each cites different impact scenarios. How would you clarify facts, decision rights, and executable options?
- How do you coordinate conflicts between departments? When their goals and performance measures differ, how do you find an approach all can accept, and how do you make it stay stable over time?
- A disagreement was not resolved and the group decided to proceed with one option. What do you leave behind so it can be reviewed later?
- A partner believes you intentionally delayed a project during review; you believe you were raising risks. Both of you communicate less as a result. How would you reconstruct facts and repair collaboration?
- Suppose online business metrics are cut in half and resources are halved, and product, operations, and engineering must get through the crisis together. How do you work with the other two functions in this situation to decide what to protect, what to cut, and how to share the burden, rather than pushing blame around?
- The business sponsor insists on the original release date, but a limited rollout shows refund rates and support tickets exceeding agreed bounds. Product thinks the sample is too small, while security wants to pause. How would you turn the dispute into a decision?
- Tell me about a conflict you went through. What did each side want, and how did you handle it? Looking back, what would you do differently?
- Both teams say the other is not cooperating and the project is stuck. Would you first clarify shared goals, responsibility boundaries, and delivery commitments? What else would you verify?
- Product blames engineering for being slow, engineering blames product for changing requirements daily, and operations blames product for missing tools and engineering for instability. How do you turn this mutual blame into everyone speaking one shared business language and taking joint responsibility for results?
- You and your manager disagree, even clash. How do you express your judgment, and how do you keep things moving when they finally disagree with you?
- After a growth metric falls, product blames traffic quality and operations blames conversion; neither wants ownership. How would you handle it?
- In a review, a colleague says your proposal misses a constraint, using an accusatory tone. How would you respond and move the discussion forward?
- Two owners agree on the data but prioritize short-term revenue versus long-term retention. How would you clarify the disagreement?
- One person favors shipping on time and fixing later; another believes current defects harm customer trust. Each thinks the other is slowing the project. How would you handle it?
- After a results presentation, two contributors both claim key contributions, and the team avoids each other. How would you establish facts and repair collaboration?
- A partner repeatedly misses deliverables and affects your work, citing different reasons each time. How would you address it while protecting the shared goal?
- You believe a project risk should be shared with a customer or executives, while your manager wants more evidence first. How would you handle it?
- A short message you sent was read as dismissing a colleague’s work, after which they stopped sharing updates. How would you clarify and restore collaboration?
- After a reorg, two teams each believe the other owns a customer issue type, causing tickets to bounce. How would you clarify boundaries and transition?
- In a review, a senior owner interrupts others and calls objections “not understanding the business.” You need to raise a risk without derailing the meeting. What do you do?
- Frontline teams bypass a process you introduced, saying it adds work without improving outcomes. How would you understand resistance and decide whether to change it?
- Two teams consider their work critical to quarterly goals and depend on the same expert. How would you facilitate an evidence-based decision while preserving collaboration?
- An uncommunicated decision created extra work for a partner team, which felt disrespected; you also believe information was incomplete. How would you repair this?
- Product believes recent complaints come from a few unusual customers, while support sees a general process flaw. How would you assess representativeness and handle the disagreement?
- What would you do if your manager's priorities differed from the team's judgment?
- An incident spans an interface contract and caller handling, and both teams believe the other owns it. How would you lead a review and create a shared fix?
- An architecture board chooses a new technology, but implementers believe migration risk is underestimated. The decision is announced but work has not started. How would you handle dissent and execution?
- After several reviews, everyone verbally agrees, yet product, engineering, and operations interpret the boundaries differently during implementation. How would you resolve the conflict and prevent recurrence?
- A platform upgrade requires service teams to take migration risk; they want full guarantees from the platform team. Neither side will pilot first. How would you design a joint validation?
No questions in this section match your target. ·
Negotiation25
Reaching commitments all sides can execute within constraints.
- Two leads disagree on building platform capability first versus delivering a customer feature first. Meetings repeat the same arguments without new evidence. How would you establish a decision process and a deadline?
- A project has borrowed an analyst from another team for two months, but the assignment has no clear end condition and the original team’s ongoing work is backing up. How would you negotiate scope, review timing, and return conditions?
- The upstream team wants rapid API changes while downstream teams need long compatibility and have no spare capacity. How would you negotiate versions, ownership, and cost?
- Describe a time engineering found a technical constraint, undefined edge state, or unexpected cost while implementing your design. How did you clarify the real constraint, negotiate behavior and scope, and confirm that the final implementation still supported the core user task?
- Two teams have committed to quarterly goals, and a critical skill turns out to be held by only one engineer. Both request priority access. How would you negotiate an executable allocation while making the unmet side aware of the cost and review conditions?
- You receive a product requirement and find that building it as written is both costly technically and will give a poor user experience after launch. How do you bring a technical alternative and persuade product to change the requirement? Tell me about a real case.
- When you ask the product and engineering teams for an operations tool, such as coupon configuration or automatic tagging, how do you justify its necessity to engineering rather than asking them every time to run a query by hand and pull the data?
- A partner adds operational and reporting requests every week, calling them included services. Team capacity is affecting other customers. How would you establish facts and negotiate scope or service level?
- Sales promised several customers faster response times, but operations capacity has not increased. How would you renegotiate service levels and eligibility with sales, product, and service teams?
- A downstream team wants near-real-time responses and high availability, but platform capacity, cost, and failure modes are not discussed. How would you negotiate?
- A vendor requires extra fees and a longer lock-in to meet the date, beyond your authority. You need information without committing on the spot. How would you proceed?
- A project needs customer-level data from another department, but it includes sensitive fields and teams disagree about retention and purpose. How would you negotiate an executable arrangement?
- A partner will provide limited pilot capacity but fears unconditional scale-up if it succeeds. How would you define the pilot agreement and expansion gates?
- Engineering wants an iteration to reduce recurring failures, while the business fears delaying customer features. How would you negotiate goals, investment, and returns?
- The date cannot move, but the full solution is no longer feasible. The business wants all features retained. How would you propose alternatives and negotiate consequences?
- A customer expects immediate responses to all requests, but contract scope, staffing, and severity do not align. How would you communicate and negotiate?
- A research team wants broad exploration and user access, but only two weeks remain and the business needs one key decision. How would you negotiate scope?
- A vendor delay has affected the launch window, but the vendor attributes it to changing requirements and will not offer remedy or a credible plan. How would you proceed?
- Your team asks another team to provide an interface early, but your own testing capacity is unconfirmed. How would you negotiate commitments both sides can execute?
- A dependency team verbally promises a quarterly interface but will not assign an owner, capacity, or milestones. Your project has already committed externally. How would you renegotiate?
- The contract has not changed, but new security reviews materially increase effort while budget is fixed. How would you renegotiate scope, timing, or cost?
- A business partner demands a launch this quarter but will not define the initial scope or name an acceptor. How would you turn date pressure into an executable staged agreement?
- An executive escalates a major account while high-risk cases from other customers have waited two days. How would you negotiate service order and explain the fairness rule?
- Two departments each expect the other to own ongoing operations. They can help temporarily, but no team will take permanent ownership. How would you negotiate handoff and capacity?
- Both agree to ‘reduce customer waiting,’ but one tracks first response while the other tracks final resolution. How would you negotiate a shared outcome and individual responsibilities?
No questions in this section match your target. ·
Stakeholder influence33
Moving cross-team outcomes without direct authority.
- Several teams agree in a review to improve data quality, but two weeks later no one has taken the implementation work; each lead believes agreement itself completed the collaboration. How would you turn consensus into ownership and checkpoints?
- A project sponsor changes success from launch, to adoption, to cost reduction, affecting different teams each time. How would you make changes explicit and protect teams from repeated rework?
- Several teams use a metric with the same name to make opposing decisions, but you cannot mandate a definition. How would you build an influence path?
- The vendor contract promises average availability, while the business cares about data recovery and incident notification. How would you align internal stakeholders to drive change?
- Did you ever try to break out of your resource or collaboration limits, such as bringing other teams in or asking upward for larger resources? How did you make the case, and what happened?
- Product promises features, engineering promises dates, and operations promises ticket handling, but nobody owns whether customers complete the key task. How would you reset goals with these leads?
- A cross-functional review is shortened to ten minutes, and decision-makers only want to know whether launch can stay on schedule. Your evidence shows two risks with different impact scopes. How would you organize the information so they can make an informed choice quickly?
- You want to push something valuable to the team in the long run that nobody is asking for now. Why do it, how do you persuade others, do you push top-down or bottom-up, and how do you show its value?
- When would you escalate a cross-team problem to a higher level, and how would you describe it?
- Has this solution had any influence outside your organization, such as being adopted by other companies or communities, shared publicly, open sourced, or written up? What is the evidence?
- Your project depends on another team fixing a data defect. They have higher-priority work and no reporting relationship with you, but customers cannot reconcile accounts. How would you make the case and offer decision evidence?
- When you give an overall report upward, how do you present it and win more resources for the team? When different organizations have different goals, how do you connect your team's goals to theirs?
- You want another team to change an interface, but you have no authority over them. What do you do?
- A cross-department meeting records a decision, but an affected team says it cannot deliver on time. How would you confirm who accepted the decision, which objections remain, and who owns the next step?
- The release owner decides to ship on schedule. The security team says residual risk exceeds its acceptance range, but leadership chooses to continue. How would you record dissent, responsibility, and review conditions and clarify executable scope and escalation boundaries?
- Several teams maintain similar interfaces with inconsistent cost and user experience. You must promote a shared approach without management authority. How would you build adoption?
- Leaders have approved a new review process, but frontline staff report more waiting and workarounds. You do not own the final decision. How would you prompt reassessment?
- Near launch, a security review finds design issues and the business says requirements arrived too late. How would you improve involvement in future projects?
- A key department will not commit capacity because most benefits accrue to other teams. How would you understand concerns and build support?
- A business owner distrusts a new dashboard because it conflicts with existing reports. You must encourage use without mandate. What would you do?
- A project spans sales, product, engineering, and support, each with different goals and cadences and accountability only for local output. How would you create joint progress?
- A team rejects a new way of working because it may add coordination cost. You believe it could address repeated delays but lack local evidence. How would you proceed?
- A project improves short-term metrics but increases maintenance burden and complaints; executive reporting shows only growth. How would you broaden the assessment?
- An infrastructure change would reduce maintenance risk across teams, but no business department wants to fund it. How would you build support?
- Expert analysis does not support an intuitive business proposal, yet the owner wants to proceed. How would you help both sides make an evidence-based decision?
- Departments use different customer identity rules, causing duplicate service and compliance risk. You must promote consistency across local workflows. How would you proceed?
- A project needs a business owner to confirm rules, but they have missed reviews for weeks. How would you keep work moving without making unauthorized decisions?
- Research finds users struggle at a critical step, but engineering and operations see change as too costly. How would you get the evidence discussed and turn it into action?
- You find that an executive-backed plan may miss its goal and have no immediate alternative. You need to report the risk while keeping teams moving. How would you act?
- The team promised a feature externally, but new user evidence suggests the core problem may not exist. Without final authority, how would you reopen the decision without triggering personal defensiveness?
- A dependency team asks you to decide every trade-off, interrupting your work and preventing its own judgment from developing. How would you change the collaboration?
- An executive wants a fast decision, but user research and frontline operations are absent. How would you bring in evidence without delaying indefinitely?
- A stakeholder repeatedly requests color and layout changes without user evidence, and the changes may weaken hierarchy. How would you respond and define a testable option?
No questions in this section match your target. ·
Feedback25
Giving and receiving feedback so that it turns into action.
- A colleague says you often overturn a plan late in discussion. You believe those instances followed newly discovered risks. How would you understand the feedback and decide whether to change your behavior?
- A team member keeps saying they want more central projects. How do you find out what they actually want?
- You shared a business line’s operating context with an engineer, who then started reallocating resources on their own. How do you handle it, and how do you change how you share in future?
- You point out that a proposal lacks user evidence, and your colleague hears “you think I am not capable.” They stop engaging. How would you clarify what the feedback is about, the evidence behind it, and the next step—and check that it was understood?
- Several people say in an anonymous survey that you lock onto a conclusion early. You believe you are shortening meetings. How would you understand the feedback, verify impact, and try to change?
- A colleague repeatedly changes an interface at the last minute but believes they communicated it in chat. Partners still get blocked. How would you give feedback without debating intent?
- You have just taken over a team, and a former peer is now your direct report. Their delivery is strong, but they repeatedly interrupt others in reviews. How would you prepare for and conduct your first feedback conversation?
- Tell me about a time you received feedback that made you uncomfortable. What did you change afterward?
- A colleague delivers on time but often changes interfaces without notice, creating downstream rework. How would you give feedback?
- Your manager says you failed to communicate risk proactively, though you believe you shared it across channels. How would you respond and assess whether improvement is still needed?
- You are told to “have more impact” without examples or expected behaviors. How would you ask for actionable detail?
- A teammate sees promotion feedback as inconsistent and unsupported, and has lost trust. You must explain the process and support growth. How would you respond?
- Your manager often changes direction at the last moment, causing repeated rework. You worry direct feedback may strain the relationship. How would you raise it?
- A colleague improves handoffs after coaching, but omissions recur weeks later. How would you diagnose the cause and continue support?
- A teammate interpreted your feedback as denying promotion potential, though you meant to identify one skill gap. How would you correct it?
- Peers say you go too deep into details, while partners want you involved earlier in detail reviews. How would you interpret both and decide what to change?
- Two partners tell an employee opposite things: one says they are too cautious; the other says they move ahead without alignment. How would you translate the feedback into context, behavior, and impact?
- An employee repeatedly misses goals. You only said ‘be more proactive’ without defining behavior or support. How would you reopen the conversation?
- You asked a report to surface risks before delivery, but twice they raised blockers just before launch. How would you check understanding, explore causes, and agree on observable change?
- A team member repeatedly commits to dates before checking dependencies, arguing that the process has no confirmation owner. How would you separate system and individual causes?
- A team member asks you to be blunt, then says you only focus on flaws after you raise quality issues. How would you clarify feedback preferences and evidence?
- Your manager says you under-delegate; your team says decision boundaries are too vague. How would you test each impact and decide what to change or clarify?
- You told a colleague they escalated risks too late; since then they communicate less. How would you reopen the conversation, own any delivery issues, and retain the necessary standard?
- Two team members made similar mistakes, but you were harsher with one because they are more senior. How would you check expectations and correct the response?
- A partner lead is under pressure from layoffs but repeatedly bypasses agreed workflows, affecting your team. How would you choose timing, support, and escalation?
No questions in this section match your target. ·