Getting Started for Project Managers
This guide helps project managers, product managers, and team leads organize work effectively. Focus on project organization, task management, and collecting stakeholder feedback.
Your Goal
Set up a system that:
- Organizes multiple projects clearly
- Tracks tasks through completion
- Collects and manages feedback
- Keeps stakeholders informed
Time Investment
About 20 minutes to set up your first project with full task tracking.
Step 1: Plan Your Project Structure
Before diving in, think about how you'll organize:
Questions to Consider
| Question | Example |
|---|---|
| What are your active projects? | Website Redesign, Mobile App v2 |
| How do you categorize tasks? | By feature, by sprint, by assignee |
| Who needs to give feedback? | Clients, stakeholders, users |
| What's your review workflow? | To Do → In Progress → Review → Done |
Step 2: Create Your Projects
Set Up Your First Project
- Navigate to Projects and click New Project
- Fill in the details:
| Field | Example |
|---|---|
| Name | Q1 Website Redesign |
| Description | Complete redesign of marketing site. Goals: improve conversion rate, update brand, mobile optimization |
- Click Create Project
Add Project Context
In project Settings:
- Add Tech Stack tags for technologies involved
- Write a Result Blurb for quick project summary
- Set visibility (keep private for internal projects)
Step 3: Set Up Task Management
Create Your Task Board
- Open your project and go to the Tasks tab
- You'll see a Kanban board with default columns
Customize Task Statuses
Adjust columns to match your workflow:
- Backlog — Ideas and future work
- To Do — Ready to start this sprint
- In Progress — Currently being worked on
- Review — Awaiting approval
- Done — Completed
Add Your Tasks
Break down the project into tasks:
- Click + Add Task in the appropriate column
- Enter a clear, actionable title:
Good: "Design mobile navigation menu"
Bad: "Navigation"
- Add task details:
- Description — Requirements, acceptance criteria
- Tags — Category (design, dev, content)
- Due Date — When it needs to be done
Organize with Tags
Create consistent tags for filtering:
| Tag Type | Examples |
|---|---|
| Type | feature, bug, improvement |
| Area | frontend, backend, design |
| Priority | urgent, high, medium, low |
Step 4: Track Progress
Daily Workflow
- Review the In Progress column — what's being worked on?
- Check Review for items needing your attention
- Move completed items to Done
- Pull new items from To Do as capacity allows
Use the Dashboard
Your Dashboard shows:
- Active tasks across all projects
- Recent activity from your team
- Projects with their current status
Keyboard Shortcuts
Speed up your workflow:
| Action | Shortcut |
|---|---|
| Quick add task | Cmd/Ctrl + K |
| Search | Cmd/Ctrl + / |
Step 5: Collect Feedback
Set Up a Feedback Board
Get input from stakeholders and users:
- In your project, go to Feedback tab
- Click Create Feedback Board
- Configure:
| Setting | Recommendation |
|---|---|
| Name | Stakeholder Feedback |
| Slug | feedback |
| Description | Share your thoughts on the redesign |
| Visibility | Public (for external) or Private (for team) |
Share with Stakeholders
Public feedback boards have shareable URLs:
yourdomain.com/feedback/[board-slug]
Share this link with:
- Clients for project input
- Beta users for testing feedback
- Stakeholders for review comments
Manage Incoming Feedback
- Review new submissions in the Feedback tab
- Categorize by type (Bug, Idea, Question)
- Convert valuable feedback into tasks
- Mark items as Done when addressed
Step 6: Connect GitHub (Optional)
If your project involves code, connect GitHub:
Link Repositories
- Go to project Repos tab
- Click Connect Repository
- Select relevant repos
Benefits
- See pull requests linked to your project
- Track issues from GitHub
- View commit activity without leaving the platform
- Keep development work visible to non-technical stakeholders
Step 7: Capture Knowledge with Notes
Project Documentation
Create notes for project context:
- Go to Notes in sidebar
- Create notes for:
| Note | Purpose |
|---|---|
| Project Brief | Goals, scope, constraints |
| Meeting Notes | Key decisions and action items |
| Technical Specs | Requirements for development |
| Stakeholder List | Who's involved and their roles |
Link Notes to Projects
Associate notes with your project so everything stays connected.
Project Manager Checklist
Initial Setup
- Project created with clear name and description
- Task board set up with appropriate columns
- Initial tasks added with descriptions and tags
- Feedback board created (if collecting external input)
- GitHub repos connected (if applicable)
Ongoing Maintenance
- Tasks updated daily
- Feedback reviewed weekly
- Project status communicated to stakeholders
- Notes updated after key meetings
Tips for Success
Keep Tasks Small
Break work into tasks that can be completed in 1-2 days. Large tasks become blockers.
Instead of: "Build user dashboard"
Try:
- Design dashboard wireframe
- Create dashboard API endpoint
- Build dashboard UI components
- Add data visualizations
- Write dashboard tests
Use Consistent Naming
Establish conventions:
- [Feature] Task name for features
- [Bug] Issue description for bugs
- [Spike] Research topic for exploration
Regular Reviews
Schedule recurring reviews:
- Daily: Quick check of In Progress
- Weekly: Backlog grooming, priority check
- Monthly: Project retrospective
Next Steps
- Tasks & Notes — Advanced task management features
- Projects — File storage, AI insights, and more
- Tutorial — Complete platform walkthrough
Common Questions
How do I manage multiple projects?
Use the sidebar to switch between projects. The Dashboard shows activity across all projects.
Can team members access projects?
Yes, projects are team-scoped. Team members can view and edit shared projects.
How do I export project data?
Tasks and feedback can be viewed and managed through the UI. For bulk exports, contact support.
What's the difference between tasks and feedback?
- Tasks are internal work items your team tracks
- Feedback is input from external stakeholders or users