Define POC exit criteria before kickoff. Use this when a customer asks for a proof of concept, pilot, sandbox validation, or technical trial. When a customer requests a POC or pilot, I will not start configuration until I have written and shared one SMART exit criterion, one MoSCoW scope table, and one acceptance-owner line. The exit criterion will name the workflow, measurable evidence, customer owner who accepts it, and readout date. Any new request must replace a current Must-have or move to phase two. In three days, check whether your next POC has a written exit criterion, scope boundary, and…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in