Back to the Playbook
DefineDE-04
Draft UI concept
Make an interaction idea concrete enough to align on direction before requirements are locked.
Product statusAvailable now
Context in4 required inputsProblem and target user · Key use cases · Design system
TransformationDesigner + Product AgentUI Drafting · Local Files · Code Analysis
OutcomeUI draft or interaction concept with open assumptions.Artifact: UI draft
Owner
Designer
Human + Agent
Participants · Agents
Product ManagerProduct Agent
Trigger
A feature needs visual or interaction exploration before requirements are locked.
Required context
Product BrainProblem and target userFilesKey use casesDesign systemDesign systemCodeCurrent UI and patterns
Optional context
Customer evidenceCustomer evidenceFilesCompetitor examplesArchitectureTechnical constraints
Skills
UI DraftingLocal FilesCode Analysis
Activity steps
- 1Clarify the interaction goal.
- 2Inspect current patterns and the design system.
- 3Sketch candidate flows and screens.
- 4Review the assumptions and iterate.
Output
UI draft or interaction concept with open assumptions.
Artifacts
Creates: UI draft
What good looks like
- Solves the stated problem.
- Follows the design system.
- Assumptions are exposed.
- No accidental commitment to implementation detail.
Quality gate
Product and design review the direction.
Destination
Teklens onlyConfluence
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.