Skip to main content

Organization Pack

The Organization Pack helps large product teams manage feedback across multiple products, teams, and initiatives.

What Problem Does This Solve?​

Without Organization Pack:

  • All feedback is mixed together in one flat list
  • Hard to coordinate across multiple product teams
  • Can't track progress on specific initiatives
  • No way to roll up metrics for leadership

Organization Pack fixes this by adding structure for multi-team environments.

Key Features​

1. Projects and Initiatives​

What it is: Group cards into projects or initiatives.

Example structure:

  • Project: "Mobile App Rewrite"
    • Cards: "Add offline mode," "Improve performance," "Redesign navigation"
  • Initiative: "Enterprise Readiness"
    • Cards: "Add SSO," "Implement RBAC," "Add audit logs"

Benefits:

  • See all work related to a project in one view
  • Track completion percentage
  • Coordinate across teams

2. Multi-Level Hierarchies​

What it is: Organize work in nested levels.

Example:

Enterprise Push (Initiative)
├── Security (Project)
│   ├── Add SSO
│   ├── Implement RBAC
│   └── Add audit logs
├── Scalability (Project)
│   ├── Database sharding
│   └── Cache layer
└── Compliance (Project)
    ├── GDPR features
    └── HIPAA features

Benefits:

  • Clear structure for complex work
  • Easy navigation
  • Roll-up progress tracking

3. Roll-Up Dashboards​

What it is: See aggregated metrics across projects.

Metrics available:

  • Cards per project
  • Completion rate by initiative
  • Cards by team
  • Cards by status within project

Use case: Answer questions like:

  • "How is the Mobile App Rewrite progressing?"
  • "Which initiative has the most unresolved feedback?"
  • "What percentage of Enterprise Push is complete?"

4. Team Workspaces​

What it is: Separate areas for different product teams.

Example:

  • Team: Mobile
    • All mobile-related feedback
  • Team: API
    • All API-related feedback
  • Team: Dashboard
    • All dashboard-related feedback

Benefits:

  • Teams see only relevant feedback
  • Reduced noise
  • Better focus

5. Cross-Project Views​

What it is: See how work spans multiple projects or teams.

Example: View all "performance" work across all teams.

Use case: Coordinate cross-cutting concerns like performance, security, or accessibility.

Who Needs This Pack?​

Multi-Product Companies​

If you have 3+ distinct products, Organization Pack helps keep feedback separated and organized.

Example: A company with a web app, mobile app, and API platform.

Large Product Organizations​

If you have 5+ product managers or multiple teams, you need structure.

Example: Enterprise company with 50 people in product org spread across 8 teams.

Portfolio Management​

If leadership needs to track progress across multiple initiatives, roll-up dashboards help.

Example: VP of Product presenting quarterly initiative progress to the board.

Platform Teams​

If you manage multiple integrations or modules, organizing by component helps.

Example: Platform team managing 15 different integration types (Slack, Jira, Salesforce, etc.).

Setting Up Organization Pack​

1. Enable the Pack​

  1. Go to Settings → Packs
  2. Find Organization Pack
  3. Click "Enable" (or start free trial)
  4. Confirm

2. Create Projects​

  1. Go to Settings → Projects
  2. Click "New Project"
  3. Enter project name (e.g., "Mobile App Rewrite")
  4. (Optional) Add description
  5. (Optional) Set owner (PM responsible)
  6. Save

3. Assign Cards to Projects​

Option 1: One at a time

  1. Open a card
  2. Click "Add to Project"
  3. Select project
  4. Save

Option 2: Bulk assign

  1. Filter or search for related cards
  2. Select multiple cards
  3. Click "Bulk Actions" → "Add to Project"
  4. Select project
  5. Apply

4. Create Hierarchy (Optional)​

  1. Go to Settings → Projects
  2. Create a parent project (e.g., "Enterprise Push")
  3. Create child projects (e.g., "Security," "Scalability")
  4. Link child projects to parent

Using Projects​

Project View​

Navigate to Projects view to see:

  • List of all projects
  • Card count per project
  • Progress percentage
  • Project owners

Click any project to see cards within it.

Filtering by Project​

From the main dashboard:

  1. Click filter icon
  2. Select "Project"
  3. Choose one or more projects
  4. Apply

Result: See only cards in those projects.

Project Dashboards​

Each project has a dashboard showing:

  • Status breakdown: How many cards in each status
  • Tags: Most common tags in this project
  • Recent activity: Latest cards added or updated
  • Velocity: Cards accepted/pushed over time

Use case: Weekly project review with stakeholders.

Team Workspaces​

Creating Team Workspaces​

  1. Go to Settings → Teams
  2. Click "New Team Workspace"
  3. Enter team name (e.g., "Mobile Team")
  4. Select team members
  5. Save

How Team Workspaces Work​

Each workspace has:

  • Its own card list
  • Its own projects
  • Shared workspace members

Members see:

  • Only cards in their team workspaces
  • Optionally, a global view across all workspaces

Use case: Mobile team works in their workspace without seeing unrelated backend feedback.

Cross-Team Coordination​

Global view: Switch to "All Teams" view to see everything.

Use case: Product leadership wants to see work across all teams.

Shared cards: Cards can belong to multiple team workspaces if coordination is needed.

Example: "Add SSO" affects both mobile and web teams - assign to both workspaces.

Roll-Up Metrics​

Initiative Tracking​

Track progress on multi-project initiatives:

Example:

  • Enterprise Push Initiative
    • Total cards: 45
    • Accepted: 30 (67%)
    • Ready: 12 (27%)
    • Shipped: 8 (18%)

Use case: Show executive leadership quarterly progress.

Portfolio View​

See all active initiatives and their status at a glance.

Metrics:

  • Cards by initiative
  • Completion rate
  • Average time from accepted to shipped
  • Most-requested features per initiative

Use case: Quarterly business review with board or executives.

Team Performance​

Track which teams are processing feedback effectively:

Metrics:

  • Cards processed per team
  • Average time in Needs Signal
  • Accept rate by team
  • Push velocity by team

Use case: Identify bottlenecks or high-performing teams.

Roadmap by Initiative​

View your roadmap organized by initiative instead of status.

Example view:

Enterprise Push
├── Accepted: 15 cards
├── Ready: 5 cards
└── Shipped: 3 cards

Mobile Rewrite
├── Accepted: 20 cards
├── Ready: 8 cards
└── Shipped: 2 cards

Use case: Stakeholder meetings focused on specific initiatives.

Integration with Other Packs​

+ Governance Pack​

Combine with Governance Pack for:

  • Project-level audit trails
  • Initiative-level approval workflows
  • Roll-up compliance reporting

Use case: Regulated company tracking which initiatives address compliance requirements.

+ Visibility Pack​

Combine with Visibility Pack for:

  • Public roadmap organized by project
  • Initiative-specific public pages
  • Customer upvoting per initiative

Use case: Show customers the "Enterprise" roadmap separately from "SMB" roadmap.

Best Practices​

Start with 3-5 Projects​

Don't create 50 projects on day one. Start small and expand as you learn what structure works.

Assign Project Owners​

Every project should have one PM owner responsible for updates and progress.

Review Projects Quarterly​

Every 3 months:

  • Archive completed projects
  • Merge redundant projects
  • Create new projects for emerging themes

Use Projects for Themes, Not Just Features​

Good projects:

  • "Mobile Performance"
  • "Enterprise Readiness"
  • "User Onboarding"

Bad projects:

  • "Q1 Work" (use dates for this)
  • "Random Stuff" (not actually a theme)

Roll Up Metrics for Leadership​

Export roll-up dashboards monthly for executive updates. Shows data-driven progress.

Common Questions​

Q: Can a card belong to multiple projects? A: Yes. Cards can be tagged with multiple projects if they span initiatives.

Q: What's the difference between projects and tags? A: Projects are for organizing work into initiatives. Tags are for attributes (feature area, segment, etc.). Use both.

Q: How many projects should I have? A: Start with 5-10. Most teams have 10-20 active projects at any time.

Q: Can I nest projects more than 2 levels deep? A: Yes. The UI supports up to 5 levels, but 2-3 levels is usually sufficient.

Q: What if my team structure changes? A: You can reassign cards to different workspaces, merge projects, and restructure anytime.

Migration from Flat Structure​

If you're adding Organization Pack to an existing workspace:

Step 1: Create 3-5 core projects based on obvious themes.

Step 2: Bulk-assign cards to projects using tags or search.

Step 3: Leave unassigned cards for now. Assign as you review them.

Step 4: Expand project structure based on what you learn.

Timeline: 1-2 weeks to migrate existing cards. Then maintain going forward.

Pricing​

Organization Pack pricing:

  • Growth: $79/month
  • Enterprise: Included

See all plans

Advanced: Custom Hierarchies​

Enterprise customers can create custom organizational structures:

Examples:

  • By customer segment (Enterprise / SMB / Individual)
  • By product line (Product A / Product B / Product C)
  • By geography (North America / Europe / Asia)
  • By business unit (Sales / Support / Product)

Contact sales for custom hierarchy design.

Examples​

Slack (hypothetical - if they used Distil):

  • Initiatives: Enterprise, Platform, Mobile
    • Projects: SSO, SCIM, Admin Tools (under Enterprise)
    • Projects: API v2, Webhooks, Developer Docs (under Platform)

Atlassian:

  • Products: Jira, Confluence, Trello
    • Each product has its own projects and feedback

Shopify:

  • Merchant Experience: Checkout, Payments, Inventory
  • Developer Experience: APIs, Apps, Themes

Next Steps​