SuccessCOACHING · Emma Enablement · PSIP™

Tool 4: Support Tool Design Specification

Performance Support Integration Protocol · Step 4 — Design

PSIP™ v1.0

Tool 4 of 7 · Step 4 — Design

↑ Import

Purpose: Define the content, format, and language for each support tool matched precisely to the context in which it will be used. One specification per tool. Scope discipline is the critical design decision — minimum viable content, not maximum related content.

Tool Identification

Tool Name

Target Workflow Moment

Five Moments Category

Gap Type Addressed

Date

Scope Definition Scope discipline is the most important design decision — resist adding related content

The scope test: Can a practitioner act on this tool in 30–60 seconds (for Apply/Solve moments)? If no, the scope is still too broad.

Primary Action Supported — The one thing the practitioner does with this tool

Minimum Viable Content — The least information required to enable correct performance

Explicitly Out of Scope — What related content is excluded and why

Format Specification

Format Type

Maximum Length

Language Standard

Primary User Proficiency Level

Progressive Disclosure Needed?

Progressive Disclosure Design — If yes: what is the quick view, and what expands?

Content Draft

Draft the tool content here, or note where it will be developed separately. Apply the scope definition above — if content doesn't directly enable the primary action, remove it.

Content (draft or outline)

60-Second Test — Can a practitioner find and act on the key guidance in under 60 seconds? If no, what must change?