Ideation/Proof of Concept
Frame the problem, the people, and the proof you will accept before any build
Define intended benefits and risks, select relevant RAISEF drivers, and choose early indicators and evidence.
In Ideation/Proof of Concept, teams establish why the system should exist and who it must serve. This stage identifies affected stakeholders and expected outcomes, sets boundaries for data use and safety, and records initial assumptions about fairness, privacy, accountability, and other RAISEF drivers. A lightweight concept includes owner roles, early guardrails, and success criteria tied to measurable indicators that will carry into design and testing. Trade-offs and open risks are logged for review, and simple explanation and oversight paths are sketched to show how people can understand, intervene, or stop the system if needed. A go or no-go decision is based on this evidence, not on enthusiasm.