✍️ Startup-Appropriate Language Style Guide¶

Direct, practical language guide for a 3-person startup team.

Language Principles¶

Use Simple, Direct Language¶

Choose common words over complex alternatives
Use active voice ("We implement X" not "X is implemented")
Write conversationally as if explaining to a colleague
Avoid jargon unless it's essential technical terminology

Focus on Action¶

Lead with what to do, not background theory
Use imperative verbs (Create, Update, Configure)
Provide specific steps rather than general guidance
Include concrete examples over abstract concepts

Banned Enterprise Language¶

Replace Academic Terms¶

❌ Don't Use	✅ Use Instead
Framework	System, approach, method
Methodology	Process, way, steps
Comprehensive approach	Complete method
Paradigm	Model, approach
Utilize	Use
Facilitate	Help, enable
Implement	Build, create, add
Leverage	Use
Solution	Tool, fix, answer
Optimize	Improve
Robust	Strong, reliable
Scalable	Can grow
Strategic	Important, key

Eliminate Enterprise Patterns¶

❌ Enterprise Theater	✅ Startup Reality
Multi-phase rollout	Launch in stages
Approval matrix	Who approves what
Steering committee	Team decision
Governance framework	How we decide
Stakeholder alignment	Get everyone on board
Best practices	What works
Cross-functional collaboration	Work together
Synergistic integration	Work well together

Remove Unnecessary Complexity¶

❌ Overly Complex	✅ Simple and Clear
In order to	To
At this point in time	Now
Due to the fact that	Because
It should be noted that	Note that
Going forward	From now on
At the end of the day	Finally
Touch base	Talk, meet
Circle back	Follow up

Startup Voice Guidelines¶

Be Direct¶

Start with the main point
Use short sentences (15 words or less when possible)
Cut filler words and unnecessary qualifiers
State facts clearly without hedging

Be Practical¶

Focus on immediate needs over theoretical completeness
Provide specific examples from the GetCimple context
Include actionable steps in every document
Answer "what do I do next?"

Be Human¶

Use "we" and "you" instead of passive voice
Acknowledge uncertainty when it exists
Admit when something is a best guess
Write like you're helping a teammate

Document Structure Patterns¶

Start with Purpose¶

## Document Title

This document explains [specific outcome] for [specific audience].

## Quick Summary

- Key point 1
- Key point 2
- Key point 3

## What You Need to Know

[Essential information only]

## Next Steps

1. [Specific action]
2. [Specific action]

Use Scannable Format¶

Bold key terms on first use
Use bullet points for lists
Include examples in code blocks or quotest
Add section headers every 3-4 paragraphs

Quality Checklist¶

Before publishing any document, verify:

Language Check¶

No banned enterprise terms
Active voice throughout
Short, clear sentences
Specific rather than abstract

Usefulness Check¶

Answers a specific question
Provides actionable information
Includes relevant examples
States next steps clearly

Startup Reality Check¶

Appropriate for 3-person team
Focuses on immediate needs
Avoids theoretical complexity
Can be implemented with current resources

Common Mistakes to Avoid¶

Writing for an enterprise audience - Remember the team size
Including theoretical completeness - Focus on practical needs
Using passive voice - Make it clear who does what
Buried action items - Lead with what matters
Academic tone - Write like you're helping a colleague

Remember: If you can't explain it simply, you don't understand it well enough.