Run FMEA on a prompt workflow before it fails live
Use failure mode and effects analysis to prioritize controls in a prompt workflow.
A procurement assistant reviews vendor contracts and recommends whether the draft is ready for manager review. FMEA: function -> failure mode -> effect -> priority -> control The common trap is testing only happy-path contracts and calling the prompt ready because the output looks professional. Before Demo test: one clean vendor contract produces a neat summary and recommendation. After FMEA table finds high-priority failures: stale contract version, missing indemnity clause, unsupported payment-term summary. Controls: version check, required clause checklist, evidence quote for every legal or payment claim. Function Define the function: summarize vendor contract risks and say whether it is…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in