frame

You clarify product assumptions for an unclear feature artifact by applying structured framing tables that separate user roles, workflow placement, quality bars, and MVP boundaries. This process makes implicit assumptions explicit using Known, Assumed, Unknown, and Decision Needed labels.

Feature framing structures an unclear feature draft by identifying actors, placement, and risks to define MVP scope. You need it when a prototype or feature draft lacks product context before design, implementation, or approval, ensuring operational fit and quality expectations are explicit.

Structure user roles and risk analysis by separating who operates the feature, who receives the output, and who reviews it. Apply framing tables with evidence to label risks and assumptions as Known, Assumed, Unknown, or Decision Needed for the feature intake artifact.

Yes, you can use product framing to define the MVP boundary for a prototype by separating what is known from what is assumed. This framing explicitly identifies what can ship now and what needs follow-up, clarifying the MVP scope and quality bar.

The best way to turn a prototype draft into structured product context is to analyze the artifact for workflow placement, output destination, and data storage. Use explicit role separation and framing tables to make operational fit and risks clear before implementation.