Synthia Salomon prescribes narrow priorities

Synthia Salomon used a thread on X on May 21 to argue that teams create execution problems when they rely on vague assumptions instead of explicit priorities and written decisions. Her post set out a short operating method for cross-team work: narrow the priority list, invite dissent early, force discussion into specifics, document exact decisions and success measures, and make sure every team carries the same message. The thread focused on handoffs, where product, engineering and adjacent groups often leave meetings with different versions of what was decided. Salomon said the result is avoidable friction later in delivery. ### Which team problem was Salomon trying to solve? Salomon’s thread described a familiar planning failure: multiple teams think they are aligned because they agree on broad goals, but they have not agreed on trade-offs, timing or what success looks like. She said teams should “narrow priorities aggressively” rather than carry a wide list of loosely defined goals into execution. In her framing, ambiguity at the start becomes rework later when stakeholders discover they were operating from different assumptions. (x.com) Her advice centered on cross-functional settings where one decision is repeated across product, engineering and other stakeholders. She said a single discussion should produce one clear version of the plan, rather than separate interpretations passed from team to team. ### Why did she want dissent brought in early? Salomon said teams should ask “What could go wrong?” early, before plans harden and before disagreement becomes a late-stage escalation. (x.com) She presented that question as a structured way to surface objections, dependencies and risks while the cost of changing course is still low. The thread did not present dissent as open-ended debate. (x.com) Salomon tied it to specifics such as trade-offs and timelines, indicating that objections should be concrete enough to change the plan or clarify ownership. That approach pushes discussion away from general concern and toward identifiable risks. ### What did she say teams should write down? Salomon said teams should document exact decisions, not just themes or intentions. (x.com) She paired that with success metrics, so that the written record captures both what was chosen and how the outcome will be judged. Those details matter because they reduce the chance that each stakeholder group carries a different version of the same meeting. (x.com) A written decision with metrics, owners and timing gives later participants a reference point when execution moves across teams. ### How does one message change execution? Salomon said teams should deliver “one unified message” across groups. In practice, that means the same decision, rationale and measure of success should be repeated in the same terms to every stakeholder set, instead of being reinterpreted by function. (x.com) Mixed versions across teams can create additional review cycles, conflicting expectations and duplicated work. (x.com) Salomon’s thread treated message discipline as an execution tool, not a communications exercise, because the same wording helps preserve the original decision as work moves between teams. ### What is the practical checklist from the thread? The checklist in Salomon’s posts was direct: cut the priority set down, ask what could fail, force specificity on trade-offs and timelines, record exact decisions with success metrics, and keep the message consistent across teams. (x.com) The thread’s emphasis was on reducing ambiguity before delivery starts, rather than resolving confusion after handoffs break down. The two X posts remained available on May 21 under Synthia Salomon’s account. Readers looking for the full wording can review the linked posts directly on X. (x.com)