🧭 Core Principles¶
🌟 Overview¶
This section outlines the fundamental values, assumptions, and guiding principles that shape the development and positioning of GetCimple. These principles emphasize our dual-target approach, focusing on creating a win-win relationship between board directors who oversee governance and management teams who implement it. These principles serve as our compass for decision-making.
Key Documents¶
Core Principles Documentation¶
- First Principles: The core values and reasoning framework guiding GetCimple's development.
- Messaging Guide: How GetCimple is positioned strategically for executives and directors.
- Decision Framework: Structured approach for making consistent, principle-aligned decisions.
Practical Application Resources¶
- Quick Reference: Concise, printable reference for daily application of principles.
- Documentation Guide: Tailored guidance for writing documentation.
Visual Resources¶
- Diagrams: Visual representations of our core principles and relationships.
Integration Guides¶
- Timeline Authenticity Guidelines: How to set realistic timelines.
🔍 Key Points¶
- Simplicity Above All: Focus on fewer, well-executed features with clear interfaces.
- Stakeholder-Centric Design: Balance director oversight needs with management implementation requirements.
- Calm Productivity: Build at a sustainable pace with thoughtful feature development.
- Pragmatic Profitability: Make efficient use of development resources with value-based decisions.
- Real-World Utility: Favor practical, proven approaches over theoretical ideals.
💡 How to Use These Principles¶
When making product decisions or prioritizing features, reference these core principles:
- For Product Planning: Use First Principles as a checklist to evaluate potential features.
- For Communications: Apply Messaging Guide to ensure consistent messaging.
- For Implementation: Refer to the Reasoning Framework in First Principles to guide technical decisions.
🔄 Application Example¶
When considering a new feature request:
Example: Adding a notification system for policy updates
✅ Simplicity: Limits notifications to essential updates only
✅ Stakeholder-Centric: Provides different views for directors vs. management
✅ Calm Productivity: Batches notifications to reduce interruptions
✅ Pragmatic Profitability: Leverages existing infrastructure
✅ Real-World Utility: Addresses a specific governance need