Collaboration and Project Management Tools

Design isn't solo work. Even if you're the only designer on the team, you work with product managers, developers, and stakeholders. Clear communication and organized project management are what separate a successful project from a failed one — not design quality alone.

The problem is there are too many tools in the market, and each one claims to be the best. In this article we'll talk about the most important tools you actually need as a designer, when to use each one, and how to build an effective working system.

Miro and FigJam: The Digital Whiteboard for Collaborative Thinking

When a team needs to think together — whether brainstorming, running a workshop, or mapping — it needs an open space for ideas. Miro and FigJam are the most popular digital whiteboard tools.

Miro:

Miro is the world's most popular whiteboard tool. An infinite white canvas where you can put anything: sticky notes, diagrams, wireframes, mind maps, flowcharts.

Miro Uses for Designers:

• Design Workshops: when running a workshop with the team — for example a Design Sprint or Crazy 8s — Miro provides ready-made templates for every exercise
• User Journey Mapping: mapping the user's journey from when they first hear about the product to becoming a regular user
• Affinity Mapping: after user interviews, gathering insights on sticky notes and categorizing them into groups
• Stakeholder Presentations: creating a board with research, findings, and designs and presenting it in a meeting

A Practical Scenario:

You're working on a new app and need to run a Design Sprint with the team in a week:

• Monday: create a board in Miro with the problem statement, the current user journey, and competitive analysis
• Tuesday: the whole team puts ideas on sticky notes, then votes on the best ideas
• Wednesday: the winning ideas get turned into a storyboard on the same board
• Thursday: take the storyboard and build a prototype in Figma
• Friday: test the prototype with real users

FigJam:

FigJam is Figma's own whiteboard tool. The key advantage is that it's integrated with Figma — you can drag designs from Figma into FigJam and vice versa.

When to Use FigJam Instead of Miro:

• If the whole team already uses Figma — no need for an extra tool
• If you need quick brainstorming without complex templates
• If you want to connect the whiteboard directly to designs

When to Use Miro Instead of FigJam:

• If you need advanced templates (Miro has hundreds)
• If the team includes people who don't use Figma
• If you need integrations with other tools like Jira or Confluence

Jira: Project Management for Larger Teams

Jira from Atlassian is the most popular project management tool in the software world. If you work at a tech company, you'll likely use Jira.

Why Designers Need to Know Jira:

• Your tasks as a designer are usually tickets in Jira
• Developers work from Jira — if you don't understand their workflow, communication will be difficult
• The Product Manager plans Sprints in Jira — and needs to know when the design will be ready

Key Concepts:

• Epic: a large project — for example, "Checkout page redesign"
• Story: a part of the Epic — for example, "Design the address entry screen"
• Task: a specific task — for example, "Create 3 layout options"
• Sprint: a time period (usually two weeks) the team commits to completing a set of tasks
• Board: a board with columns — To Do, In Progress, In Review, Done

A Practical Scenario:

The Product Manager has created an Epic called "Onboarding Redesign." Inside it are Stories:

1. Research: interviews with new users
2. Design: designing the new onboarding flow
3. Prototype: creating an interactive prototype
4. Testing: testing with 5 users
5. Dev: implementing the design

You take Stories 1–4 and break them into Tasks, placing them in the Sprint. Every day in the standup, you update the team on progress. When you finish a Story, you move it to "Ready for Dev" and developers start working.

Tip: Don't treat Jira as a design tool — it's an organization tool. Put links to Figma files and research docs in the ticket description.

Trello and Asana: Simpler, Faster Alternatives

Not every team needs Jira. If you're a freelancer or working in a small team, Trello or Asana may be more suitable.

Trello:

Trello works on a Kanban board system — columns and cards. Very simple and you can start using it in 5 minutes.

Trello Uses for Designers:

• Managing Freelance Projects: a column for each client or each phase (Brief, Design, Review, Delivered)
• Design Backlog: a column with all the ideas and improvements you want to make
• Content Calendar: if you're creating content — posts, articles, or videos

A Practical Scenario — Freelancer:

You have 3 clients at the same time. Create a Board with:

• Backlog: all new requests
• This Week: what you'll work on this week
• In Progress: what you're working on right now
• Client Review: waiting for feedback from the client
• Done: what you've completed

Each card has: task description, deadline, Figma file link, checklist.

Asana:

Asana is a bit more powerful than Trello — it has different views (Board, List, Timeline, Calendar) and supports subtasks and dependencies.

When to Choose Asana:

• If you need a Timeline view to see the schedule
• If you have complex tasks with subtasks
• If you need to link tasks together (Task B can't start until Task A is done)

The Simple Rule:

• Team of 1–3 people: Trello
• Team of 4–15 people: Asana
• Team larger than 15 or at a tech company: Jira

Notion: The Team's Collective Brain

Notion isn't just a project management tool — it's a complete workspace. You can create documents, wikis, databases, project boards, and much more. It's the place where you store all the team's knowledge.

Notion Uses for Designers:

1. Design Documentation:

Every project needs documentation. In Notion you can create a page for each project with:

• The Problem Statement
• Research Findings
• Design Decisions and why you chose this solution
• Links to Figma files
• Feedback from stakeholders
• The Final Design with screenshots

2. Design System Documentation:

If you have a Design System, Notion is a great place to document it:

• A page for each component with: description, variants, when to use it, when not to
• The Color System with color names and meanings
• The Typography Scale
• The Spacing System
• Do's and Don'ts

3. Meeting Notes:

For every meeting you hold, write notes in Notion:

• What was discussed
• Decisions that were made
• Action Items and who is responsible for what

4. Design Portfolio/Case Studies:

You can use Notion as an initial portfolio — write case studies for your projects and share them as public pages.

A Practical Scenario:

Create a Notion workspace for the team with:

• Wiki: all information about the product and design guidelines
• Projects Database: all projects with their statuses
• Meeting Notes: notes from every meeting
• Templates: ready-made templates for PRDs, design briefs, and research plans

Slack: Daily Communication with the Team

Slack is the primary communication tool in most tech companies. As a designer, you'll spend a lot of time on Slack — so you need to use it right.

How to Organize Slack as a Designer:

• #design: channel for the design team — updates, questions, sharing work
• #design-critique: dedicated channel for feedback on designs
• #design-inspiration: channel for sharing inspiring designs and ideas
• #project-xyz: channel for each major project

Tips for Effective Communication on Slack:

1. Write Sufficient Context:

Instead of sending "check out this design" — write: "This is the third version of the Pricing page design. I changed the layout from 3 columns to 2 because the research showed users get confused by too many options. Looking for feedback on the hierarchy."

2. Use Threads:

Instead of replying in the main channel — use threads. This keeps conversations organized and prevents them from getting lost.

3. Use the Figma Integration:

Figma has an integration with Slack — when you share a Figma link in Slack, it shows a preview of the design. This makes review easier without having to open Figma.

4. Set Focus Time:

Slack can be a major distraction. Use Do Not Disturb during deep design work, and set specific times in the day to check messages.

Building an Integrated Working System

Tools alone won't solve the problem. The important thing is to build a system that connects them. Here's a practical workflow you can start with:

1. Planning (Notion + Jira/Asana):

• The product brief and requirements in Notion
• Tasks and Sprint planning in Jira or Asana
• Every task has a link to the brief in Notion

2. Discovery (Miro/FigJam + Notion):

• Workshops and brainstorming in Miro or FigJam
• Research findings and insights in Notion
• Workshop summary is shared on Slack

3. Design (Figma + Slack):

• Design in Figma
• Design reviews on Slack or in Figma Comments
• Design decisions get documented in Notion

4. Delivery (Figma + Jira):

• Dev Mode in Figma for developers
• Jira tickets get updated with Figma links
• QA feedback comes back as comments in Figma or tickets in Jira

Tips for the New Designer Joining a Team

1. Ask About Tools on Day One:

As soon as you start a new job, ask:

• What are the communication tools? (Slack, Teams, Discord)
• What's the project management tool? (Jira, Asana, Linear)
• What's the documentation tool? (Notion, Confluence, Google Docs)
• Where are the Design files? (Figma team, shared drive)

2. Follow Existing Conventions:

If the team names Figma files a certain way or uses certain labels in Jira — follow the same approach. Consistency is more important than doing something better on your own.

3. Document Your Work:

Every design decision you made — write it down. Not just for the team, but for yourself too. After 3 months you won't remember why you chose that layout.

4. Create Templates:

If you're doing the same thing repeatedly — create a template. Design brief template in Notion, presentation template in Figma, feedback request template in Slack. This will save a lot of time in the long run.

Tools change, but the principles stay the same: clear communication, continuous documentation, and tight organization. If you understand these principles, you'll be able to adapt to any new tool quickly.