Winning support for a proposal by backing it with relevant facts, data and examples rather than assertion.
Good work shows: Links each claim to evidence; answers the likely objections in advance; ends with a clear ask.
Persuading with evidence is one of the communication skills on FinderK.
The job simulations and Skill Paths below include work that is checked for this skill. You do the work in an original fictional company and get feedback on it.
Customers could not pay for about an hour and a half on a busy Saturday. Rebuild the timeline and impact from the logs, write a blameless review that fixes conditions rather than people, book the review and brief customer care without promising what you cannot keep.
Skills: Reconstruct an incident timeline from logs and records; Measure customer impact and error budget use; Write a blameless review that names conditions, not people; Turn contributing factors into owned actions; Brief non-engineers honestly about an incident
Eight people tested a new prescription reorder flow and most said they loved it. Work out what actually happened, rate each problem by the team's rules, report it honestly and hold the line when the team wants a better number or to drop an awkward finding.
Skills: Count usability results by eligibility and observation rules; Rate problem severity from impact and frequency; Separate observations from interpretations in a report; Defend a finding with evidence when a team pushes back