Skip to content

💬 GetCimple Messaging Guide

This guide combines our messaging standards, consistency checklist, and review process into one practical resource for our 3-person team.

🎯 Core Messaging Principles

1. Governance-First Positioning

GetCimple is a governance and compliance platform, not a technical security tool.

✅ Say This:

  • "Governance oversight solution"
  • "Cybersecurity compliance management"
  • "Board-level risk management"

❌ Not This:

  • "Security monitoring tool"
  • "Technical security solution"
  • "Network monitoring system"

2. Technology Freedom

We provide governance without mandating technical choices.

✅ Say This:

  • "IT departments maintain full autonomy"
  • "Complements technical teams' work"
  • "Supports existing technology choices"

❌ Not This:

  • "Controls technical implementation"
  • "Mandates specific technologies"

3. Multi-Board Access

Directors switch between companies individually - no unified view.

✅ Say This:

  • "Efficient context switching between boards"
  • "Individual board access with clear separation"

❌ Not This:

  • "Unified view across multiple boards"
  • "Cross-board dashboard"

👥 Writing for Different Audiences

Directors

  • Focus on governance outcomes and liability reduction
  • Emphasize time efficiency
  • Use terms like "oversight," "due diligence," "governance"

Management/IT Teams

  • Emphasize operational autonomy
  • Focus on reducing board reporting burden
  • Use terms like "efficiency," "automation," "workflow"

Compliance Teams

  • Focus on audit trail and documentation
  • Emphasize standardized processes
  • Use terms like "compliance," "evidence," "audit-ready"

✅ Quick Content Checklist

Before Writing

  • Know your audience (directors, management, or IT staff)
  • Review this guide for messaging approach
  • Check related content for consistency

While Writing

  • Position GetCimple as governance (not technical security)
  • Respect technology freedom principle
  • Use correct multi-board messaging (individual switching)
  • Keep language appropriate for audience

Key Terminology

  • Company: GetCimple (not Get Cimple or getcimple)
  • UI Framework: shadcn-svelte (not shadcn/ui)
  • Audience Terms:
  • "directors" (not "board members")
  • "management teams" (not "managers")
  • "governance oversight" (not "technical security")

Before Publishing

  • Run spell check
  • Verify all links work
  • Get peer review (15-30 minutes)
  • Update related documents if needed

🔄 Simple Review Process

As a small team, we use peer review:

  1. Write using this guide
  2. Self-check with the checklist above
  3. Peer review - have a teammate check for consistency
  4. Publish the content

Time Required: 15-30 minutes per review

📊 Tracking Quality (Keep It Simple)

  • Run automated checks weekly: npm run docs:check:consistency
  • Fix broken links immediately
  • Review messaging questions in weekly team sync
  • Update this guide when we learn something new

🛠️ Helpful Resources

Templates

  • Process docs: /docs-internal/docs/04-business/processes/templates/process-narrative-template.md
  • Technical guides: Follow existing architecture docs
  • UI/UX docs: Check /docs-internal/docs/07-design/ for patterns

Automated Tools

  • Check links: npm run docs:check:links
  • Format docs: npm run format:docs
  • Check consistency: npm run docs:check:consistency

📚 Example Messaging

Positioning GetCimple

  • ✅ "GetCimple helps board directors demonstrate governance due diligence"
  • ✅ "Streamlined cybersecurity compliance oversight without managing technical details"

Technology Freedom

  • ✅ "GetCimple complements your existing technical security infrastructure"
  • ✅ "IT teams maintain full autonomy while providing governance transparency"

Multi-Board Management

  • ✅ "Efficient switching between board contexts"
  • ✅ "Individual company governance with enhanced workflow"

Remember: Keep it simple, consistent, and focused on our users' needs. When in doubt, ask the team!