pant-artifact-pressure-test

name	pant-artifact-pressure-test
description	Pressure-test a product artifact, argument, or proposal when no specialist PANT scenario fits. Use for general grounding, contradictions, evidence, and readiness; not work clearly served by a specialist.
license	CC-BY-NC-SA-4.0
type	workflow
category	find-the-right-pressure-test
phase	3
status	review
modes	["feedback","dialogue"]
entry_paths	["direct","guided","best-effort"]
pressure_levels	["constructive","skeptical","resistant","hostile-room"]
audience	["Product Manager","Product Owner","Business Analyst","Product Leader","Product practitioner"]
best_for	["Reviewing a product artifact or argument that does not require a specialist scenario","Finding the consequential claims, contradictions, assumptions, and evidence gaps","Beginning useful work while identifying a better specialist when needed"]
not_for	["Specialist roadmap, strategy, business-case, market-sizing, tactical-plan, or executive-decision work","Formal legal, financial, security, regulatory, clinical, or safety review"]
evidence_required	["Artifact, argument, proposal, or description of the work","Available context about audience, decision, and consequence"]
produces	["Prioritized general pressure test","Claim, evidence, contradiction, and action brief","Optional follow-up dialogue and debrief"]
estimated_time	10-30 min
depends_on	[]
combine_with	["pant-meeting-rehearsal","pant-executive-decision-review"]
sources	["Phase 0 Product and Research Synthesis, PANT, 2026"]

PANT Artifact Pressure Test

Purpose

Provide structured dissent for a product artifact or argument when no specialist scenario materially improves the review. Ground critique in supplied material, prioritize consequential weaknesses, convert findings to action, and route only when specialization is useful.

When to Use

Use for product proposals, decision memos, presentations, demonstrations, research summaries, plans, narratives, and other artifacts whose specific scenario is unclear or outside the current catalog.

When Not to Use

Prefer the roadmap, strategy, business-case, market-sizing, tactical-plan, or executive-decision specialist when its decision is central. Use pant-meeting-rehearsal when the primary job is conversational practice rather than artifact review. Do not pretend this generalist provides specialist professional approval.

Supported Modes and Entry Paths

• Feedback: Default. Apply the bundled feedback contract.
• Dialogue: Follow up on one unresolved claim or rehearse defense of the artifact one question at a time.
• Direct: Start from the supplied material immediately.
• Guided: Explain the claim-evidence-decision relationship and ask only what changes the review.
• Best effort: State audience, decision, and consequence assumptions; review with reduced confidence.

Decision Being Prepared For

Prepare the artifact to inform, recommend, request, align, or support a consequential product decision. If no decision exists, clarify the intended audience response without manufacturing an approval request.

Typical Audiences

Product teams, cross-functional partners, leaders, executives, customers, sponsors, portfolio groups, and other decision participants.

Inputs

Best input is the artifact plus audience, intended response, stakes, and known evidence. Minimum input is the artifact or a description of its argument. Everything supplied counts as context.

Direct example:

Use pant-artifact-pressure-test on this proposal. Identify what survives, the three most consequential weaknesses, unsupported claims, contradictions, and the smallest revisions that improve readiness.

Sparse example:

I have a product document that feels weak, but I do not know which review I need.

Quick Start

1. Identify artifact type, intended audience response, and consequence.
2. Read general artifact logic.