E · Collaboration, communication, and influence
Communication
Making information, judgment, and evidence actionable for the listener.
Classification boundary
Include: Include making information, judgment, context, and evidence clear enough for others to act.
Choose a neighboring leaf when: Use conflict navigation for competing goals; use the questioning path for systematic clarification and evidence seeking.
This capability may appear in standards across different stages. Explore stage expectations
37 questions
Choose a group based on the evidence you need. Groups follow existing question formats, not difficulty or mandatory prerequisites. Each batch has up to eight questions.
Judgment and options20
Compare goals, constraints, options, and trade-offs.
Questions 1–8
- 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?
- 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 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?
- 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?
No questions in this section match your target. ·
Questions 9–16
- 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?
- 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?
- 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?
- 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 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?
No questions in this section match your target. ·
Questions 17–20
- 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?
- 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. ·
Experience and reflection17
Use past facts to examine contribution, results, and learning.
Questions 1–8
- 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?
- 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?
- 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 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 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?
No questions in this section match your target. ·
Questions 9–16
- 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?
- 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 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 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?
No questions in this section match your target. ·
Questions 17–17
No questions in this section match your target. ·
No questions in this capability match your target. ·