OKRs
  • About OKRs
  • The market
  • Why build ourselves?
  • Product philosophy
  • Product Decision Record
  • Key milestones
  • Features
    • OKR Unit
    • OKR Views
    • Default Sorting in views and Filters
    • OKR details page
    • Filters
    • Notifications
    • Move and Paste feature
    • Personal Starring ⭐️
    • Due date as an attribute
    • Cloning OKRs to a new quarter
    • Help Section
    • OKR dependency resolution
    • Drag and Drop (Upcoming)
    • Visibility control 🔒
    • Admin Page (Upcoming)
    • Search
    • Sort feature
    • Slack Integration
  • Key Documents
  • Data Strategy
    • Success Metrics
    • Reporting/Metrics Dashboard
  • Program Management
    • Team
    • Working Principles
    • Toolkit
    • Meetings Schedule
    • Product Roadmap
    • Release notes
  • Major links
    • Project Board
    • Design Mockups
    • Feature Discussions Document
    • xto10x Google Drive
    • xto10x Wiki
    • xto10x Slack
    • Staging (OKR tool)
  • Templates
    • Document Template
    • Voice and Tone
Powered by GitBook
On this page

Was this helpful?

  1. Templates

Voice and Tone

PreviousDocument Template

Last updated 5 years ago

Was this helpful?

The goal of this wiki is to create a single source of truth for all members on the project, and to get new team members up to speed quickly. It is important that the content not only be accurate and up-to-date, but also sound that way. Write confidently and with authority. What you write now will probably be here forever.

Guideline

  1. Use short words, short sentences and short paragraphs. This ensures the document is accessible. Use as little jargon as possible.

  2. When you link to external documents, include a short summary of the most important take-aways above the link.

  3. Avoid excessively long sentences which overuse the word “and".

    • Incorrect: Write with more confidence and learn to project executive tone and find all errors.

      Correct: Write with more confidence. Learn to project executive tone. Find all errors.

  4. Follow the as much as possible. Put essential information first, then supporting or explanatory information in order of diminishing importance. Put the least important information at the bottom. Use the different heading types to help create this hierarchy.

inverted pyramid format