I am not sure if this belongs here, or in 2.5 Thoroughness, or if it is already implicitly in one or both.
Review denotes an amount of completed work (a completed program, system, design, etc). When doing professional work, I seek out early, guiding feedback. The feedback is often not on completed work, but on tentative plans for work to be started.
This helps ensure good use of resources (e.g. not using budget on a project that does not align with an employer's interests) as well as ethical compliance (e.g. asking "should I build a crazed AI that wants to enslave humanity" vs "I built a crazed AI that wants to enslave humanity, will you please review my code?").