playbook:principles:deep

The DEEP principle (Demystify, Empower, Explore, Protect) offers a practical framework for integrating AI tools like GPT into organizational workflows with clarity, accountability, and creative potential. It is particularly applicable to onboarding, automation design, and teamwide use of generative tools.

  • Demystify — Make the system understandable. Reduce the “black box” effect by showing how outputs are generated.
  • Empower — Give users meaningful control, including the ability to refine, override, or redirect outputs.
  • Explore — Encourage experimentation and creative use, especially in low-risk contexts.
  • Protect — Safeguard user agency, privacy, and organizational integrity. Build guardrails against misuse or overreach.

GPT Onboarding

  • Demystify
    1. Add a “How It Works” section to internal wiki explaining GPT context, memory, and limitations.
    2. Include example prompt → output pairs to show transparency.
  • Empower
    1. Provide editable prompt templates (e.g. client email drafts, meeting summaries).
    2. Train users to revise outputs rather than accept them passively.
  • Explore
    1. Maintain a “GPT Sandbox” page or room where staff can post, test, and share creative GPT uses.
    2. Use Slack/Element tags to group “exploration” use cases.
  • Protect
    1. Publish and reinforce an AI usage policy: no client names, financials, or personal data in prompts.
    2. Encourage hallucination reporting; normalize correction behavior.

Automation & Workflow Design

  • Add a DEEP checklist to new workflow or automation rollout docs:
    1. Demystify: Have we explained what this AI-assisted step is doing?
    2. Empower: Can the user tweak or bypass it when needed?
    3. Explore: Can this system evolve with team input?
    4. Protect: Have we considered data boundaries, auditability, and fallback?
  • Use “DEEP Compliant” tags to label internal tools that meet this standard.
  • A short DEEP explainer can be integrated into weekly onboarding routines.
  • Maintain a list of DEEP-compliant tools and workflows under `tools:` or `playbook:` depending on scope.
  • Encourage teams to apply DEEP independently when designing systems or prompts.
  • playbook/principles/deep.txt
  • Last modified: 2025/12/08 03:11
  • by marcel