Notion Guide
How we use Notion at Kyndof for project management, documentation, and knowledge management.
Notion is Kyndof's central workspace for projects, tasks, documentation, and structured knowledge. Understanding Notion's structure helps you find information and contribute effectively.
What Notion Is For
Notion is where Kyndof's operational work lives. Think of it as our digital headquarters.
Use Notion for:
- Project tracking and task management
- Working documents and collaborative editing
- Knowledge base and process documentation
- Meeting notes and agendas
- Databases for tracking anything structured (projects, tasks, decisions, KPIs)
- Templates for recurring workflows
Don't use Notion for:
- Code or technical specifications (use GitHub)
- Real-time chat (use Slack)
- File storage for large files (use Google Drive)
- Permanent company policies (use Wiki)
- Financial data requiring strict access control (use dedicated systems)
Notion excels at structured information that evolves over time. It's collaborative, searchable, and flexible.
Workspace Structure
Kyndof's Notion workspace is organized into several top-level sections:
Main Navigation
When you open Notion, you'll see:
Sidebar Sections:
- Workspace Home - Company-wide dashboard and quick links
- Teams - Team-specific workspaces
- Projects - Active project pages
- Databases - Core company databases (tasks, decisions, KPIs, etc.)
- Templates - Reusable templates for common documents
- Archive - Completed or deprecated pages
Favorites: Star pages you reference frequently. They appear at the top of your sidebar.
Key Workspaces
Company Home
- Mission, vision, values
- Org chart and team directory
- Company-wide announcements
- Quick links to common resources
Team Workspaces Each team has its own workspace:
- Engineering - Technical projects, sprint planning, architecture docs
- Design - Design system, project briefs, creative assets
- Sales - Pipeline tracking, client notes, proposals
- Operations - SOPs, vendor management, process docs
- HR - Onboarding, policies, team rituals
Your personal workspace is for:
- Private notes and drafts
- Personal task tracking
- Work-in-progress before sharing with team
Core Databases
Kyndof uses several databases to track organizational information:
Task Database
Where: Tasks Database
Purpose: Track all work items with owners, deadlines, and status
Key properties:
- Title - What needs to be done
- Owner - Position/role responsible (not individual names)
- Status - Not Started / In Progress / Blocked / Done
- Priority - P0 (critical) → P3 (nice to have)
- Due Date - When it needs to be complete
- Project - Linked project this belongs to
- Strategy - Linked strategy this supports
Views:
- My Tasks - Filter by your position as owner
- This Week - Due dates within next 7 days
- By Project - Grouped by project
- Blocked - Tasks waiting on dependencies
How to use:
- Create task from template or duplicate existing
- Assign owner (position, not person)
- Set realistic due date
- Update status as you work
- Comment for updates or blockers
Project Database
Where: Projects Database
Purpose: Track all initiatives with scope, timeline, and resources
Key properties:
- Project Name - Clear, descriptive title
- Owner - Position accountable for delivery
- Status - Planning / Active / On Hold / Complete
- Start Date / End Date - Timeline
- Strategy - Which strategy this supports
- Team - Which team owns it
- Budget - Allocated resources
- Success Metrics - How we'll measure success
Views:
- Active Projects - Currently in progress
- By Team - Grouped by owning team
- Timeline - Gantt chart view
- Completed - Archive of finished projects
Project page template includes:
- Overview and objectives
- Key stakeholders (RABSIC matrix)
- Scope and deliverables
- Timeline and milestones
- Resources and budget
- Risks and mitigations
- Meeting notes
- Decision log
Decision Database
Where: Decisions Database
Purpose: Track major decisions with rationale and accountability
Key properties:
- Decision Title - What was decided
- Status - Proposed / Approved / Rejected / Implemented
- Decision Date - When decided
- RABSIC Matrix - Who had what role
- Rationale - Why this decision
- Alternatives Considered - What we chose not to do
- Impact - Who/what this affects
How to use:
- Create decision record when making important choices
- Fill out RABSIC matrix (see RABSIC guide)
- Document alternatives and why they were rejected
- Link to related projects, strategies, or issues
- Update status as decision progresses
KPI Database
Where: KPIs Database
Purpose: Track key metrics and performance indicators
Key properties:
- KPI Name - What we're measuring
- Owner - Position accountable for this metric
- Target - Goal value
- Current Value - Latest measurement
- Frequency - How often we measure (daily/weekly/monthly/quarterly)
- Goal - Which company goal this supports
- Status - On Track / At Risk / Off Track
Views:
- Company KPIs - Top-level metrics
- By Team - Filtered by team
- At Risk - Metrics not hitting targets
- Dashboard - Visual charts and trends
Other Key Databases
Strategy Database - Company strategies and how they connect to goals
Goals Database - Company and team objectives
Issues Database - Problems, blockers, and incidents
Value Streams Database - End-to-end workflows and process maps
RABSIC Matrix Database - Accountability assignments for decisions