prevoor

Prevoor is a term used in some project management and product development contexts to describe an early, informal evaluation phase conducted before formal approvals or budgets are granted. It is typically performed by a small, cross-functional team and aims to validate the problem, assess rough feasibility, and check alignment with strategic goals. Because it is not a standardized method, definitions and practices of prevoor vary across organizations and industries.

The etymology of prevoor is unclear and its spelling suggests a neologism rather than a fixed linguistic origin. Some sources view it as a blended term drawing on the prefix pre- with the Dutch word voor meaning before, while others treat it simply as a coined label used within certain corporate or consultancy communities.

In practice, a prevoor process yields a lightweight package of outputs designed to enable a quick go/no-go decision about whether to proceed to more formal evaluation. Typical contents include a problem statement, high-level requirements, a preliminary risk assessment, rough cost and timeline estimates, success criteria, and the criteria that will govern a future decision. The format emphasizes speed and clarity to avoid delaying momentum while still surfacing major assumptions and risks.

Applications of prevoor are common in fast-moving environments such as software development, startups, and government pilots, where organizations seek early validation before committing substantial resources. Benefits include faster momentum and improved stakeholder alignment; disadvantages include potential gaps in governance and inconsistent standards if not tied to a broader decision framework.

Related concepts include feasibility studies, business case development, and stage-gate or go/no-go processes. As a loosely defined practice, prevoor remains informal and context-dependent.