You’ve tried spreadsheets, email threads, maybe even magic eight balls, yet projects still stall, priorities clash, and deadlines sneak up on you. If this sounds familiar, it’s time to rethink your strategy and look at two proven systems: Kanban and Scrum. Both belong to the broader agile framework for product development and project management, and both aim to bring clarity to chaos.

Scrum hands you sprints, short, fixed intervals where a defined group (Product Owner, Scrum Master, development team) tackles a set of tasks, then inspects and adapts at a sprint review. It’s rhythm with guardrails.

[Kanban](https://wedo.com/tag/kanban-2) hands you a board, lanes for each stage of work, limits on how much you start, and a focus on steady flow. No roles are carved in stone; your team tweaks policies as it learns.

In this article, we’ll explore both frameworks, compare their roles, rituals, and tools, and help you choose the one that fits your team’s rhythm.

## What Is Scrum?

[Scrum](https://scrumguides.org/) structures work into time‑boxed bursts, typically two to four weeks, so teams can ship bite‑sized updates at a steady clip. The goal is simple: break big projects into manageable chunks, inspect progress often, and adapt quickly.

### Defined Roles

- **Product Owner**: Owns the backlog, sets priorities, and answers questions about requirements.
- **Scrum Master**: Coaches the team on Scrum practices, removes impediments, and protects the team from distractions.
- **Development Team**: A cross‑functional group of team members who design, build, test, and deliver the work items.

These roles are non‑negotiable, no hybrids, no “part‑time Scrum Master.” Clear ownership keeps everyone accountable.

### Key Artifacts

- **Product Backlog**: The master list of features, bug fixes, and technical tasks, all ordered by value and urgency.
- **Sprint Backlog**: A subset of the product backlog chosen for the current sprint, complete with sprint goals and estimated effort.
- **Increment**: The sum of all “Done” work items at the end of a sprint. Every increment must meet the team’s definition of done.

### Core Events

1. **Sprint Planning**: Decide what goes into the sprint. The product owner presents high‑priority items; the development team commits based on capacity.
2. **Daily Scrum**: A 15‑minute standup. Each team member answers: What did I do yesterday? What will I do today? Any blockers?
3. **Sprint Review**: Demonstrate the increment to stakeholders, gather feedback, and update the product backlog.
4. **Sprint Retrospective**: Reflect on the sprint process, identify improvements, and plan changes for the next sprint.

### Cadence and Due Dates

Sprints enforce regularity. Because sprints are fixed in length, you get a predictable rhythm: you know exactly when the next sprint review will happen and when due dates are locked in. This makes forecasting easier and gives the team a clear “heartbeat.”

### Metrics

- **Velocity**: Average number of story points (or other units) completed per sprint. Used for forecasting future work.
- **Burndown Chart**: Tracks remaining work within a sprint to signal whether the team is on track.

Scrum works best when you need structure, defined roles, regular checkpoints, and clear due dates. It’s not magic, but it does bring a disciplined flow of work that many teams find invaluable.

## What Is Kanban?

[Kanban](https://www.icagile.com/resources/intro-to-kanban-what-it-is-how-it-works-benefits-and-core-principles) is an agile method centered on visualizing work items and managing the flow of work. It originated in manufacturing but has since been adapted for software and product development. Unlike Scrum, Kanban does not require fixed‑length iterations or prescribed roles.

### Core Principles

1. **Visualize Work**
    - Use a Kanban board with columns (e.g., “Backlog,” “In Progress,” “Review,” “Done”)
    - Each card represents a work item, such as a feature, bug fix, or task
2. **Limit Work In Progress (WIP)**
    - Set explicit limits on how many cards can be in each column
    - Prevents overloading the development team and highlights bottlenecks
3. **Manage Flow of Work**
    - Track how long cards spend in each stage (cycle time)
    - Aim for a steady, predictable throughput rather than bursts of activity
4. **Make Policies Explicit**
    - Define entry and exit criteria for each column
    - Clarifies expectations for team members and reduces ambiguity
5. **Implement Feedback Loops**
    - Hold regular reviews (e.g., weekly or bi‑weekly) to inspect flow and process
    - Adjust WIP limits or policies based on data and team feedback
6. **Continuous Improvement**
    - Use metrics like lead time (total time from request to delivery) to identify areas for improvement
    - Encourage every team member to suggest tweaks to the process

### Kanban Boards and Work Items

A typical [Kanban board](https://kanban.university/kanban-guide/) has columns that match stages of your workflow. Cards move from left to right:

| **Backlog** | **Ready** | **In Progress** | **Review** | **Done** |
| --- | --- | --- | --- | --- |
- **Work Items**: Each card includes a description, assignee (team member), and due dates if needed.
- **Swimlanes**: Optional horizontal rows for different priority levels or work types (e.g., “Urgent,” “Maintenance,” “New Feature”).

### Metrics

- **Cycle Time**: Time a card spends from “In Progress” to “Done.”
- **Lead Time**: Time from when a card enters the backlog to completion.
- **Throughput**: Number of cards completed in a period.

### Flexibility and Roles

[Kanban](https://wedo.com/blog/wedo-integrates-the-kanban-view) doesn’t mandate roles like Product Owner or Scrum Master. Team members share responsibility for pulling work, reviewing policies, and facilitating improvements. You can introduce roles as needed, but the method thrives on adaptability.

### Kanban Method Variations

- **Kanban for Ops**: Focus on rapid response to incoming issues, ideal for support teams.
- **Evolutionary Change**: Start with your current process, overlay a Kanban board, then evolve.

Kanban works well when priorities shift unpredictably, work items vary in size, and you need a clear view of the flow without the overhead of fixed‑length sprints. Continuous improvement is built in, letting you refine your process one tweak at a time.

## Key Differences Between Kanban and Scrum

Now that we’ve outlined each method, let’s revisit their main contrasts without retracing every detail.

### Structure and Roles

[Scrum](https://wedo.com/blog/when-agility-becomes-a-necessity) gives you guardrails: a Product Owner who owns the backlog, a Scrum Master who keeps the process honest, and a development team that delivers in sprints. Those roles don’t budge until the sprint ends. Kanban, as we saw, drops role requirements. Any team member can pull work, tweak policies, or coach peers, if you agree who does what, ownership can spread more evenly.

### Cadence and Planning

We’ve described sprints as fixed intervals with locked‑in goals and due dates. That predictability can feel like a heartbeat for planning. Kanban swaps that for a continuous flow: items move independently through your persistent board. You set due dates per card, not per sprint, and you can reshuffle priorities anytime, as long as you respect your work‑in‑progress limits.

### Board Management

In Scrum, the board resets each sprint. You clear out “Done,” refill with new items, and track progress until the next reset. Kanban boards persist. Columns stay put, and cards cycle through until done. This ongoing view makes it easy to spot long‑running work or chronic bottlenecks without rebuilding the board every few weeks.

### Handling Change

Sprint boundaries protect focus by freezing scope mid‑sprint. If an urgent bug appears, you wait for the next sprint or declare an exception. Kanban keeps its doors open: add, remove, or re‑prioritize cards anytime, provided you don’t exceed your WIP limits. That flexibility is a boon when work arrives unpredictably.

### Measuring Success

Scrum teams track velocity (story points per sprint) and use burndown charts to see if they’ll hit the sprint goal. Those metrics guide sprint forecasts. Kanban teams focus on flow metrics: cycle time (from “In Progress” to “Done”), lead time (from request to delivery), and throughput (items finished over a period). These numbers tell you how smoothly work moves and where to tweak.

### Continuous Improvement Rhythm

Both frameworks value learning. Scrum packs its inspect‑and‑adapt into a sprint retrospective at the end of each cycle. Kanban spreads feedback across regular improvement meetings or even on‑the‑fly discussions. You adjust policies and limits whenever the data or your gut says something’s off.

In short, if you want timeboxed guardrails, defined roles, and calendar‑driven due dates, Scrum fits the bill. If you need flexibility, a persistent view of work items, and the ability to change course at any moment, Kanban might be your best bet.

## When to Use Scrum

[Choose Scrum](https://wedo.com/blog/when-agility-becomes-a-necessity) when your project benefits from clear milestones, regular checkpoints, and well‑defined roles. If you need a Product Owner to prioritize the backlog, a Scrum Master to shield the team from distractions, and a development team to focus on a sprint’s worth of work, Scrum provides the structure you need.

Scrum shines in product development efforts where features build on one another. You can plan a series of sprints, each “called sprint” lasting two to four weeks, with set due dates that align to release dates or stakeholder reviews. The sprint review gives you a formal moment to demo work items to stakeholders, gather feedback, and refine the product backlog for the next sprint.

Teams that thrive on predictability also gravitate toward Scrum. Velocity (the average number of story points completed per sprint) lets you forecast how many sprints it will take to finish work items. If hitting dates matters (for a marketing launch, compliance deadline, or major product milestone), knowing when your sprint review falls provides reliable checkpoints.

Scrum frameworks also help new Scrum teams learn agile practices. The defined ceremonies like sprint planning, daily Scrum, sprint review, sprint retrospective create a repeatable rhythm. This rhythm can guide teams that haven’t yet mastered continuous improvement, giving them a safe container to inspect their process and adapt.

In short, when your work calls for strict sprint cadences, predictable due dates, and formal roles like Product Owner and Scrum Master, Scrum is likely the better choice.

## When to Use Kanban

Kanban is your go‑to when work arrives unpredictably, priorities shift often, or tasks vary widely in size. If your team handles support tickets, maintenance requests, or unplanned bug fixes, Kanban’s continuous flow lets you pull in urgent work without waiting for the next sprint.

You’ll set up a Kanban board, define stages that match your process, and assign explicit work‑in‑progress (WIP) limits. This keeps you from overcommitting: if “In Progress” is full, you finish existing cards before starting new ones. As cards move rightward, you track cycle time and lead time to spot bottlenecks and smooth the flow of work.

Kanban works well when you:

- Need flexibility on due dates. Instead of locking in dates for a sprint, you attach due dates to individual work items and adjust as you go.
- Want to minimize overhead. No mandatory sprint planning, daily standups, or sprint review, though you can borrow these ceremonies if they help.
- Aim for continuous improvement. Regular feedback loops, weekly flow reviews or quick retrospectives, let you tweak policies, column definitions, or WIP limits whenever you spot inefficiencies.
- Prefer visual transparency. A persistent Kanban board makes it clear what everyone is working on, what’s blocked, and what’s next, all without rebuilding the board each cycle.

In development teams where rapid response matters, Kanban is often a natural fit. It lets you balance demand against capacity, make flow issues visible, and improve steadily, one tweak at a time.

## Combining Scrum and Kanban: Scrumban

Sometimes the best answer lies between two extremes. Scrumban merges the rhythm of Scrum with the flow focus of Kanban, giving you structure without sacrificing flexibility.

### Why Scrumban?

- You like sprints for planning and reviews but want Kanban’s continuous flow to handle interruptions.
- Your team needs to limit work in progress to avoid context‑switching, yet still report velocity for stakeholders.
- You want regular retrospectives but also quick, on‑the‑fly adjustments to WIP limits or board policies.

![Infographic in English showing when to use Kanban, Scrum or Scrumban: unpredictable work, strict deadlines, flexibility, WIP limits, transition.](https://wedo-assets.sos-ch-gva-2.exo.io/Which_framework_fits_your_workflow_best_en_a9fc6e3696.png)

### How Scrumban Works

1. **Sprint Planning Lite**
    - At the start of a sprint, pick a small set of high‑priority work items, not a full sprint backlog.
    - Use this meeting to set goals, but leave room for new cards to enter the board when capacity frees up.
2. **Kanban Board with WIP Limits**
    - Maintain a persistent board with columns that reflect your workflow.
    - Apply WIP limits in critical stages, like “In Progress” or “Review,” to force focus and finish tasks.
3. **Daily Standups**
    - Keep the quick check‑in: What did you do yesterday? What will you do today? Any blockers?
    - Use the board during standups to make bottlenecks and progress visible.
4. **Sprint Reviews and Retrospectives**
    - Hold sprint reviews to demo completed work and gather feedback on deliverables.
    - Conduct retrospectives to identify process tweaks—both at the sprint level and for ongoing Kanban policies.
5. **Flow Metrics and Velocity**
    - Track cycle time and lead time to spot delays in the workflow.
    - Optionally measure velocity for completed work items to aid forecasting without overcommitting.

**When to Adopt Scrumban**

- Your team is comfortable with Scrum but needs more agility for unplanned work items.
- You’ve outgrown strict sprint boundaries and want a continuous improvement mindset woven into every day.
- You need to balance predictability (due dates, sprint reviews) with adaptability (WIP limits, dynamic priorities).

Scrumban can act as a stepping stone: Scrum teams can introduce Kanban principles gradually, while Kanban teams can adopt sprint cadences for better planning and stakeholder engagement. By blending routines and flow controls, Scrumban creates a hybrid that adapts to real‑world demands without adding unnecessary ceremony.

![Comparison table in English of Kanban, Scrum and Scrumban: structure, roles, metrics and best use cases.](https://wedo-assets.sos-ch-gva-2.exo.io/Kanban_vs_Scrum_vs_Scrumban_what_fits_your_team_en_ff6df415d3.png)

## Conclusion

Scrum and Kanban each bring order to the madness of product development. Choosing between Scrum and Kanban isn’t about right or wrong, it’s about fit. One method gives you scheduled cycles and role clarity, the other offers a live, pull‑based board and adaptive pace. If you need both predictability and flexibility, Scrumban blends planning checkpoints with on‑demand task intake.

[WEDO](https://wedo.com/features) takes these frameworks out of theory and into practice. With built-in Kanban boards, sprint planning tools, custom workflows, and real‑time analytics—all hosted securely in Switzerland—[WEDO](https://wedo.com/features) keeps every task, meeting, and deadline in one place. Whether you’re running a sprint review, tweaking your flow of work, or tracking cycle time, [WEDO](https://wedo.com/features) adapts to your process so your team can focus on what matters: getting things done.

Ready for a smoother workflow? [**Try WEDO** today](https://wedo.com/signup).

Discover whether Kanban, Scrum or Scrumban best fits your team. Learn their key differences, use cases, and how WEDO’s platform streamlines your workflow.

Illustration with a magnifying glass and a gear, next to the text: Kanban vs. Scrum: Which One Should You Use?

large_32-kanban-vs-scrum-which-one-should-you-use.png

medium_32-kanban-vs-scrum-which-one-should-you-use.png

small_32-kanban-vs-scrum-which-one-should-you-use.png

thumbnail_32-kanban-vs-scrum-which-one-should-you-use.png

32-kanban-vs-scrum-which-one-should-you-use.png

Kanban vs. Scrum: Which One Should You Use?

Sometimes, you don’t need more tools to manage your work. You just need a better way to see it.

That’s the problem the Kanban board was designed to solve. It gives teams a clear view of what needs to be done, what’s in progress, and what’s already finished, without juggling endless checklists or buried updates.
Originally developed in manufacturing, the Kanban method is now one of the simplest and most effective ways to manage projects across software, marketing, operations, and more.

In this guide, we’ll explain what a Kanban board is, how it compares to Scrum, where it works best, and how to make it part of your workflow using the right tools.

## What Is a Kanban Board?
Let’s start from the beginning. A Kanban board is a visual way to organize work, track progress, and see what’s getting done, without digging through spreadsheets or inboxes.

At its core, it’s simple. You have columns that represent different stages of work, like “To Do,” “In Progress,” and “Done.” Tasks live on cards that move across the board as the work moves forward.

Most Kanban board apps follow this format, with features like due dates, checklists, tags, and assignees layered on top to help teams stay organized.

The idea comes from the original Kanban method, developed by Toyota to manage workflows on factory floors. Over time, it’s evolved into one of the most widely used techniques in modern project management, especially for teams that need flexibility and real-time visibility.

Whether you're managing a solo project or working with a full development team, the board’s purpose stays the same: make the work visible, limit what’s being worked on at once, and keep everything moving in the right direction.

And the best part? You don’t need a complicated setup to get started. A few columns, a few cards, and you’re already using a system that scales as your workflow grows.

## Kanban vs Scrum: What’s the Difference?
Kanban and Scrum are both popular frameworks within agile methodology, but they take different approaches to organizing work. If you’ve used task boards before, chances are you’ve encountered both, even if you didn’t realize it.

Let’s break it down.

![Image comparing Kanban and Scrum. Kanban is based on continuous flow, flexibility, work-in-progress (WIP) limits, and evolving priorities. Scrum relies on a structured approach with defined roles (Scrum Master, Product Owner), time-boxed sprints, and sprint planning with fixed deliverables.](https://wedo-assets.sos-ch-gva-2.exo.io/Kanban_vs_Scrum_Whats_the_Difference_en_6aedc0dd6f.png)

Scrum works in time-based sprints. Teams commit to a fixed set of tasks every two to four weeks, with structured roles like product owner, scrum master, and development team. It’s great for teams building toward a clear, deadline-driven release. The rhythm is tight, with regular planning and review sessions baked into the cycle.

Kanban, on the other hand, is continuous. Work doesn’t wait for a sprint to start or finish. Instead, tasks move fluidly through a kanban board, giving teams more flexibility to adjust as priorities shift. It’s ideal for handling a steady stream of work, whether that’s support tasks, internal projects, or content pipelines, without needing to reset everything every few weeks.

Where Scrum locks the sprint, Kanban teams focus on keeping things flowing. They often use limits on how much can be worked on at once (called the limit work in progress) to prevent overload and reduce blockers. And instead of sprint retros, they make small, regular improvements based on what’s actually happening in the workflow.

However, the two approaches aren’t opposites; many teams combine them. You might plan in sprints and track in Kanban. [WEDO](https://wedo.com/features) supports both ways of working, but its flexible task board setup makes it especially useful for teams who want real-time visibility and the ability to adjust as things change.

If your projects evolve quickly, involve cross-functional input, or don’t follow a strict sprint cycle, Kanban project management might be a better fit and easier to manage in a tool that’s built for flexible collaboration.

## How a Kanban Board Actually Works
A [Kanban board](https://kanban.university/kanban-guide/) turns a list of tasks into something you can see and move. The structure is simple: columns represent stages of work, and cards represent individual tasks. As a task progresses, its card moves from one column to the next, usually from “To Do” to “In Progress” to “Done.”

That movement isn’t just for show. It’s a way to visualize workflows, track real progress, and keep everyone on the same page without needing a meeting to check in.

Here’s what you’ll find on most digital kanban board apps:

- **Columns:** These are customizable, so they can match your actual process. A content team might use “Draft,” “Review,” and “Published.” A software development team might use “Backlog,” “In Progress,” “QA,” and “Released.”
- **Cards:** These represent tasks, user stories, or individual items of work. They often include a title, description, assignee, due date, and status.
- **Movement:** Cards move across the board as work happens. This is how teams get real-time updates on what’s active, what’s stuck, and what’s finished.

The board view creates clarity. Team members can see what needs attention without scanning through a long task list. When used consistently, a Kanban board helps spot bottlenecks early, like when too many tasks pile up in the “In Progress” column, so teams can refocus and rebalance.

One of the key principles behind the Kanban method is to limit work in progress. That means only working on a few tasks at a time, instead of trying to tackle everything at once, which keeps quality high and context switching low.

The result? A more focused team, fewer dropped tasks, and a system that’s always up to date, and not just when someone remembers to update the status.

## Kanban Board Use Cases
The beauty of a Kanban board is how easily it adapts to different kinds of work. Whether you’re part of a software development team, managing internal operations, or running creative projects, the same simple board structure can help you keep track of tasks, reduce friction, and deliver work with more consistency.

Here are some of the most common ways teams use Kanban project management to stay organized.

### Software Development and IT
Engineering teams often rely on Kanban for ongoing, fast-moving work, like bug fixes, support tasks, and feature rollouts. Each card might represent a user story, issue, or task, moving through stages like “Backlog,” “In Progress,” “Code Review,” and “Released.”

It’s especially useful when paired with Agile practices or as a flexible alternative for teams that don’t work in strict sprints. Software development teams also use visualization tools to spot bottlenecks, limit blockers, and review throughput over time.

### Product Teams
From roadmap planning to feature delivery, Kanban helps product managers and cross-functional teams keep track of priorities without losing momentum. Cards often include specs, mockups, or links to related documentation. The product owner can quickly see what’s in progress and whether any tasks are stuck or overdue.

### Marketing and Creative
Campaigns, content pipelines, and design requests all flow better with a board. A marketing team might set up columns like “Ideas,” “In Progress,” “Client Review,” and “Published.” Each card can have assignees, a due date, checklists, and file attachments, and the team gets a clear board view of progress at a glance.

### Operations, HR, and Admin
Kanban is not just for technical or creative teams. HR might track employee onboarding steps using a Kanban board. Operations teams can manage recurring tasks like inventory restocking or compliance reviews. Any team that needs to manage projects with repeatable stages can benefit from a Kanban board template that maps their workflow.

### Agile or Hybrid Teams
For teams that follow agile methodology, Kanban can complement or even replace Scrum processes. A scrum team might use a board to visualize the sprint backlog and progress during daily standups. Hybrid approaches like Scrumban blend the flexibility of Kanban with Scrum’s structure, giving teams the best of both systems.

Whether your team is co-located or remote, Kanban helps team members stay aligned without micromanagement. It simplifies coordination, improves visibility, and works for just about any kind of project.

## Choosing the Right Kanban Tools
If you want to get the most out of a Kanban board, the tool you use matters. Some apps keep it simple, while others add more structure for teams working across multiple projects. The best setup is one that matches how your team already works.
Here are a few things to look for when comparing Kanban board apps and project management tools.

### Customizable workflows
Your tool should let you create a board that [matches how your team actually works](https://wedo.com/features/tasks). That includes the ability to rename columns, change their order, and organize tasks based on the structure that makes sense for your project.

### Shared views that keep everyone aligned
A clear board view helps team members see what’s being worked on, what’s blocked, and what’s done. Everyone should be able to access the same task list and make updates in real time, without needing separate check-ins to stay in sync.

### Built-in task details
You’ll want a board that lets you assign work, set due dates, and add context to each card. This makes it easier to follow up, especially when multiple people are involved in a task or when deadlines are important.

### Real-time visibility
Updates should show up as they happen. A board that reflects changes in real time makes it easier to manage work without extra messages or duplicated effort. It also helps teams spot delays early, before they become actual blockers.

### Ties into how your team already works
A board is most useful when it’s part of your overall workflow. That means choosing a project management tool that doesn’t just show cards on a screen, but also supports how tasks are created, assigned, and completed, ideally without needing to switch platforms.

## Using a Kanban Board in WEDO
If your team already tracks tasks in WEDO, setting up a [Kanban board](https://wedo.com/tag/kanban-2) doesn’t require a new tool or extra steps; it’s already built into the way the platform works.

Each workspace in [WEDO](https://wedo.com/features) gives you a column-style board view, where tasks are organized by section. You can structure those sections to reflect your team’s actual process, whether that’s “To Do / In Progress / Done” or something more specific like “Planning / Approval / Launch.”

As work progresses, tasks can be moved across columns with a simple drag and drop. You’ll always have a clear visual of what’s active, what’s finished, and what might be waiting on input from others.

Every task card in WEDO can be assigned to one or more team members, with a clear due date, notes, and optional status updates. You can filter views by deadline, status, or assignee, which helps surface what needs attention without scanning the full board.

What makes WEDO especially useful is how your Kanban board connects with the rest of your work. Tasks created during meetings or added to a shared project space are automatically visible to the team, which means fewer things fall through the cracks.
You don’t need to manually copy notes or build separate task lists; everything stays in one place, updated in real time, and easy to follow.

![Video demo showing how the Kanban view works in WEDO: create, move, and track tasks across columns for clear team coordination.](https://wedo-assets.sos-ch-gva-2.exo.io/kanban_en_22cee3a3d5.gif)

Whether you’re managing a full project or just want to keep your daily work more organized, WEDO gives your team a Kanban-style setup that’s simple to use and flexible enough to grow with your workflow.

## Conclusion
A Kanban board does more than organize tasks. It helps teams see their work clearly, stay focused, and make steady progress. Whether you’re working in product, operations, marketing, or development, the Kanban method gives you a system that’s easy to understand and easy to stick with.

WEDO makes it simple to bring this approach into your team’s daily workflow. You can create tasks during meetings, organize them in a clear board view, and keep everything moving, without needing a separate tool just to stay on track.

Ready to manage projects with more clarity and less friction? Start your [WEDO free trial](https://wedo.com/signup) today.

Learn how Kanban boards work, how they compare to Scrum, and how to use them across teams with real-time visibility in WEDO.

Illustration with the text "What Is a Kanban Board?" on the left and task card icons arranged in a grid on the right, on a blue background.

large_26-what-is-a-kanban-board.png

medium_26-what-is-a-kanban-board.png

small_26-what-is-a-kanban-board.png

thumbnail_26-what-is-a-kanban-board.png

26-what-is-a-kanban-board.png

What Is a Kanban Board? Tools, Apps, and Project Use Cases Explained

## Managing a project from A to Z with WEDO

What are the main features related to project management? With WEDO you can :

* Prepare agendas for project meetings,
* Write the minutes of your project meetings in real time,
* Distribute tasks and follow up on them from one meeting to the next,
* Share important project files with project members,
* Inform all your stakeholders about the project's progress,
* Keep a global overview of all ongoing projects.

Let's discover these different steps together in detail.

## 1\. Create a workspace for the project

For each project, we advise you to create a specific workspace. WEDO also allows you to link your project to the team concerned. Through each workspace, you will find all the information you need to ensure the progress of your project.

A workspace is organized into 4 necessary tabs to manage your project:

* **The Info tab:** view the project's progress
* **Meetings tab:** find all the meetings organized within the framework of the project
* **Tasks tab:** track all tasks linked to the project
* **Files tab:** share important files related to the project

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_1_4bbf50e66b.gif)

For the _**Sustainable Development**_ project, I created a specific workspace by grouping the members concerned. For each project, you choose who can access the information in order to ensure the confidentiality of the data.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_1_4bbf50e66b.gif)

## 2\. Manage Project Tasks

From the **Tasks** tab of the workspace, you can list the different tasks to be completed within the project. You can schedule them in time, define their priorities and, of course, assign them to the different project members. **Tip:** Use the magic wand that appears at the end of the section to carry out these actions in a few clicks on a task list.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_2_b136c06349.gif)

In the task details section, you can add additional information. For example: the **planned date**, a **deadline**, a **file to attach** or a **comment** you want to leave to the person in charge of it.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_2_b136c06349.gif)

## 3\. Create custom fields by project phase

In the context of a project, it is possible that the fields proposed by default in the details panel are not enough for you. This is why we have developed a feature called **Custom Fields**. It is now possible to add fields in the task details area, for example: the duration of the task, a progress status, a progress percentage etc. The possibilities are endless! Each organization can therefore create **custom fields** according to its own criteria and needs.

Here, my **_Sustainable Development_** project is divided into 4 phases: **Pre-project**, **Launch**, **Development** and **Communication**. I have therefore created a custom field of the type "drop-down list" by adding the phases of my project in the options to choose from.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_3_ed508e37a7.gif)

These fields and their options are created from the network settings and can be applied to all tasks or only activated for tasks in a specific workspace/project. Note that at this time, only the administrators of your network are allowed to create custom fields via the network settings.

Another use case: I could **Add a custom field** of type **Number** in order to be able to enter the **Duration in minutes** of each task. For better readability, choose an **icon** to illustrate this field in the details panel.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_3_ed508e37a7.gif)

If I go back to my _**Sustainable Development**_ project, I can now add the **Duration in minutes** for each task.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_3_ed508e37a7.gif)

## 4\. Sort the project's tasks

WEDO is very flexible in terms of displaying tasks, by offering many alternatives to select from according to your needs. For example, you can sort the tasks **By deadline**, **By user** and even by **Project phase** thanks to our previously created custom field.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_4_29af741a41.gif)

All tasks in WEDO can be displayed in List view or in Kanban view. The latter allows us to visualize the tasks in the form of cards organized according to the project phases. It is then very easy to see who is doing what and for what deadline!

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_4_29af741a41.gif)

## 5\. Add a project status

In each workspace, you have the possibility to add a status. But what are the use cases for this feature? Here are some ideas...

The status of a workspace allows you to inform the members of the project about :

* The launch of the project,
* A detected risk (concerning resources or logistics for example),
* A possible delay (due to unexpected or an overload of work),
* Or more generally, important information during the project.

The use of statuses throughout the evolution of your project will give you a history of important events visible in the activity flow.

In my **_Sustainable Development_** project, I want to inform participants about the **Launch phase.** From the **Info tab**, by clicking on **Update Status,** I can determine if the project is **ON TRACK**, **AT RISK** or **OFF TRACK**. I can also choose the **Start date** and the **Deadline date** for the project.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_5_69c838bba8.gif)

To summarize:

* The **Project Status** will be visible at the top left next to the project title,
* The latest status will be visible at the very top in the **Info** tab,
* And finally, the history of the last statuses is visible in the **activity stream**.

Statutes are a simple and efficient way to inform members about the progress of your project.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_5_69c838bba8.gif)

## 6\. Organize project meetings

For the **_Sustainable Development_** project, the first project kick-off meeting has already taken place. In the Meetings tab, I find the minutes of this first meeting. Here is the agenda we created with the minutes which contains: information, decisions and tasks distributed among the project members.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_6_417448fab8.gif)

Today we are participating in the second meeting of this project for which we already have a validated agenda. As we start the meeting, we notice that the three tasks that were under Agathe's responsibility are now completed. It is very easy to follow the progress of the tasks from one meeting to the next!

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_6_417448fab8.gif)

At the end of the meeting, we can close the meeting so that WEDO can generate a minutes that can be accessed instantly.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_6_417448fab8.gif)

In the **Meetings tab** of the _**Sustainable Developmen**t_ workspace, you will find all the minutes of the meetings held to ensure the smooth running of your project.

## 7\. Share files with project members

To ensure smooth collaboration and to provide your team with the necessary documents, you can share files within your project. Important project files are visible in the **Files** tab of the workspace. Here, we find, for example, the **Risk Matrix** document that was discussed during the first meeting.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_7_627cd13051.gif)

Note that you can also upload files to be shared with members directly from the tab. WEDO's secure infrastructure offers you a safe solution for sharing files with different stakeholders.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_7_627cd13051.gif)

## 8\. Keep an eye on all projects in progress

Thanks to WEDO, you can get a global view of the different projects in progress. For example, if I want to follow the progress of the **Management** team's projects, I can do so in a few clicks. I can see that my **_Sustainable Development_** project is **ON TIME** and that its progress is 25%.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_8_224134f2fc.gif)

The same goes for the **Informatics** team. I can see all their current projects. In this case, I see that there are three projects in progress with different statuses. Here, the **Office 365 Migration** project is overdue and needs urgent discussion between managers.

From the list view, note that it is possible to sort projects by name, **status**, **progress** or **due date**.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2021_06_8_224134f2fc.gif)

For your information, workspaces that are not projects are identified as **continuous workspaces** and are distinguished by a gray progress bar. This global view allows you to keep an eye on all the projects in progress and to quickly see their status.

## Simple and efficient project management with WEDO

Through these different examples and use cases, we have shown you how WEDO allows you to easily manage different projects and how to ensure an efficient follow-up or the achievement of set objectives. Our collaborative tool is constantly progressing and other developments are already planned. However, right now, you are performing the basics of project management, namely:

* Share information with project members,
* Distribute responsibilities in the form of tasks,
* Allowing everyone to know how the project is progressing,
* Keep a global view on the projects in progress within your company.

Your organization is already working with WEDO and you want to implement an efficient project management? Discover the [Projects](https://help.wedo.swiss/en/collections/2435444-les-projets) collection in our help center!

You have a project to manage over three months with a long list of tasks, weekly meetings and important files to share with the project members? We have the solution to simplify this work that can sometimes be tedious! Discover 8 WEDO features that will help you reach your goals and complete your project in the best working conditions.

A woman standing at the head of a conference table addressing her team, overlaid with the text “How to manage a project with WEDO?” and “Use case”

large_9-how-to-manage-a-project-with-wedo.png

medium_9-how-to-manage-a-project-with-wedo.png

small_9-how-to-manage-a-project-with-wedo.png

thumbnail_9-how-to-manage-a-project-with-wedo.png

9-how-to-manage-a-project-with-wedo.png

How to manage a project with WEDO?

Custom fields allow you to add detailed information to the tasks of your network in a structured manner. There is an infinite number of use cases possible with the 6 predefined types that we offer.

## Use case

In this article we propose three use cases to help you understand the custom fields:

* Add a custom field to estimate the duration of the tasks,
* Add a status on the tasks linked to a project,
* Add services concerned with management’s tasks

In a general sense, a custom field can be available on all the tasks of the network, or only in one or several workspaces.

## Add a custom field to estimate the duration of tasks

To create a new custom field, go to _Profile > Settings > Custom fields_ tab. Then click **Add custom field.**

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive1_1304187a99.png)

A window will pop up asking you to choose among six types of fields. To estimate the duration of tasks in minutes, you will need to select “Number”. 

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive2_5d4f3a2160.png)

Enter a name for your custom field and choose an icon to represent it in the details pane of your tasks. You can then choose to make the custom field available on all your tasks, or if you only want it to be available in one or several workspaces. 

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive3_b2e0359b5a.png)

Then, click **Save.** 

Next to each task of your network will now appear the field “Duration in minutes” in the details pane of the task, with the icon you have chosen:

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive4_be95a31753.png)

## Add a status on the tasks linked to a project

To create a new custom field, go to _Profile > Settings > Custom field_ tab. Then click **Add custom field.**

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive1_1304187a99.png)

For a status on the tasks of a project, the appropriate custom field will be “Dropdown list”.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive5_c7b63ba24d.png)

Enter a name for your custom field and choose an icon to represent it in the details pane of your tasks. Then select the second option: “No, I want to choose in which workspaces it’s available”. 

You can then enter the different status that you would like to have in your project: 

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive6_ff141f8924.png)

Note that you can choose a different color to represent each status. 

To activate the field in a workspace, you need to go to the settings of the workspace in question (here, it is _Zero Paper Project_) and select the _Custom fields_ tab. The list of custom fields available for activation will appear. You can then choose to **Activate** the field that interests you for this project.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive7_5ef6596455.png)

From now on, you can select the status of each shared tasks in your Zero Paper Project.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive8_4d33c7a613.png)

Note that you can also sort the tasks according to their status:

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive9_39b8b2d33c.png)

## Add the services concerned with the management’s tasks

To create a new custom field, go to _Profile > Settings > Custom field_ tab. Then click **Add custom field.**

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive1_1304187a99.png)

Here, you will need to select “Multiple choice”. 

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive10_b54ff0cc41.png)

Enter a name for your custom field and choose an icon to represent it in the details pane of your tasks. Then select the second option: “**No, I want to choose in which workspaces it’s available**”, enter the different “Services” and click **Save.**

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive11_4a5008f16c.png)

To activate the custom field in the _Management_ workspace, you need to go to the settings of the workspace in question and select the _Custom fields_ tab. The list of custom fields available for activation will appear. You can then choose to **Activate** the field that interests you for this workspace.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive12_9dda7c3f4b.png)

You now have the possibility to choose one or more services for each task that is in the Management workspace. 

![](https://wedo-assets.sos-ch-gva-2.exo.io/2018_07_diapositive13_ba2da623cc.png)

## Sharing tasks and custom fields

If you share a task in a workspace, the available custom fields of the workspace will automatically appear in the details pane of the task. If you remove a task from a workspace, the custom fields will simply be masked. This flexible system offers you to share tasks that will remain intact and no data will be lost. 

**We can improve WEDO thanks to your feedbacks. Please let us know if you have any suggestions or ideas to improve and develop our tool.** 

Custom fields allow you to add detailed information to the tasks of your network in a structured manner. There is an infinite number of use cases possible with the 6 predefined types that we offer. 

large_2018-07-custom-fields

medium_2018-07-custom-fields

small_2018-07-custom-fields

thumbnail_2018-07-custom-fields

2018-07-custom-fields

Custom fields

## Sections in WEDO

For a few weeks now, WEDOhas made it possible to choose the sorting of task lists: by date, by due date, by user, by workspace and by priority.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2017_04_diapositive1_89876a0b24.png)

The sections are automatically created according to the chosen sorting mode.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2017_04_diapositive1_89876a0b24.png)

## Switch from the list view to the kanban view

In each task list, there is a button to switch from the list view to the kanban view.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2017_04_diapositive2_a0965a0cfd.png)

![](https://wedo-assets.sos-ch-gva-2.exo.io/2017_04_diapositive2_a0965a0cfd.png)

Sections are automatically transformed into columns and tasks appear as cards that can be moved from one column to another.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2017_04_diapositive3_a5f941acbc.png)

![](https://wedo-assets.sos-ch-gva-2.exo.io/2017_04_diapositive3_a5f941acbc.png)

Moving a card from one column to another changes its properties. For example: By sorting the tasks by user with the kanban view display, you can assign the tasks to different people by moving them to the corresponding person column.

## Create your own sections

Let's imagine that you want to create a workspace for _**Project Y**_ that consists of four phases. The four phases are _Pre-project,_ _Launch, Development, Communication_.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2017_04_diapositive4_bf9039232d.png)

Create the Project Y workspace then go to its _Settings_ \> _Custom sections_ tab. Enter the four phases and move them in the desired order. In the _Default View_ tab, you can choose the sort and view that should be selected by default in this workspace.

![](https://wedo-assets.sos-ch-gva-2.exo.io/2017_04_diapositive5_55ff0e3243.png)

Here's the result:

![](https://wedo-assets.sos-ch-gva-2.exo.io/2017_04_diapositive5_55ff0e3243.png)

Note that tasks sorted by section can be organized manually in the desired order.

## Conclusion

Thanks to the Kanban view, manage your projects visually. The kanban view makes it easy to monitor the progress of projects and the custom sections allow you unlimited use cases: project milestones, progress statuses, groups by department, and more.

## Also to be discovered in this version

Custom sections can also be used in checklist templates.

The sorting of tasks has been improved for greater simplicity and understanding.

The **_Organize_** button has been moved to each section to allow a more precise and intuitive use of the functionality.

A new option in the _**Organize**_ button allows you to set deadlines on the fly for tasks.

It is now possible to create folders in the main menu to group workspaces. Example folders: _Departments, Projects_, etc. To create folders, go to your _Profile_ \> _Network Settings_ \> _Menu_ tab. Here you can create folders and drag and drop the different workspaces to organize them. Note that the changes you make are valid for all users on the network.

Finally, the _Files_ tab automatically groups all files related to sessions or tasks in each workspace. First steps in document management in WEDO? Possible...

For all those who prefer to work visually: discover the Kanban view.

large_2020-05-wedo-integrates-the-kanban-view

medium_2020-05-wedo-integrates-the-kanban-view

small_2020-05-wedo-integrates-the-kanban-view

thumbnail_2020-05-wedo-integrates-the-kanban-view

2020-05-wedo-integrates-the-kanban-view

WEDO integrates the kanban view

Trello

Asana

Decisions

Monday.com

eSéances

MS Teams

MS Planner

OneNote

Every day, we juggle a series of tasks, from answering emails and attending meetings all the way to cooking dinner or finally folding that pile of laundry staring us down for days. Task management is everywhere around us, whether we realize it or not. 

But here's the catch: managing tasks is more than checking boxes. It's making sure the right boxes are checked at the right time, by the right people.

For individuals, good task management can mean less stress and more time to spend on what matters most to them. For teams and organizations, it's the difference between controlled chaos and seamless collaboration. When done well, task management becomes a superpower, moving businesses toward growth and ensuring projects are delivered on time (and with fewer sleepless nights).

In this guide, we're going to explore strategies, tools, and best practices that turn task management into a fine-tuned system. Whether you're wrangling your own to-do list or leading a team toward big goals, this can be your roadmap to staying on top of your game. 

Let's get started!


The Ultimate Guide to Task Management: Strategies, Tools, and Best Practices

There’s a special kind of dread that comes with a recurring meeting invite.

It’s always there, every Tuesday at 10, or even worse, every Friday at 3, clogging up your calendar. People join out of habit. Cameras off. Agenda optional. And somewhere between the first status update and the fifth half-decision, you realize: this meeting isn’t helping anyone. It’s just... happening.

A lot of recurring [meetings](https://wedo.com/features/meetings) were meant to create structure. Instead, they often create inertia. Same attendees, same talking points, same outcomes (or lack thereof). Over time, they stop being useful and start being background noise.

But here’s the thing: it’s not the recurrence that’s the problem. It’s the lack of structure. And when you fix that, you stop wasting time and start making it count. In this post, we’ll walk through how to redesign your recurring meetings to create real clarity and value, so people leave with direction, not déjà vu.

## The Compounding Cost of Poorly Run Recurring Meetings

One bad meeting wastes time. A recurring one builds a culture of wasted time.

It’s not just an hour lost every week. It’s five people spending one hour each, every single week, often just to rehash the same updates or decisions that never landed. Multiply that across a month, then across multiple teams, and you’re suddenly burning dozens of hours on meetings no one finds valuable.

And that’s just the obvious part.

Poorly structured recurring meetings come with hidden costs:

- **Delayed decisions -** when ownership isn’t clear, decisions get deferred.
- **Lost accountability -** if follow-ups aren't tracked, nothing moves forward.
- **Fragmented focus -** context switching and repeated discussions drain attention.
- **Participation theater -** people show up, but mentally check out.

Over time, these meetings start functioning as placeholders rather than progress points. And because they’re recurring, they rarely get reevaluated. The longer they stay broken, the more time, trust, and attention they quietly erode.

The worst part? Teams often *feel* this happening, but don’t know how to fix it. So the meetings stay. And the drain continues.

## Signs Your Recurring Meeting Is Broken

You don’t need a survey to know when a recurring meeting is off the rails. You can feel it. But just in case you’re on the fence, here are the most common red flags:

- **There’s no real agenda.** Maybe there was one once, but now it’s just bullet points copied forward, or nothing at all.
- **It’s the same conversation every time.** No progress, just recycled talking points.
- **A few people dominate, others stay silent.** It’s unclear who’s supposed to speak, so only the loudest voices fill the gap.
- **People multitask or don’t show up at all.** Engagement drops when the meeting stops delivering value.
- **Nothing gets documented.** Decisions, context, and action items vanish the moment the call ends.
- **Everyone leaves with a different interpretation of what just happened.** No shared record means no shared understanding.

When even the organizer doesn’t look forward to the meeting, that’s a signal. Recurring meetings aren’t passive calendar events. If they aren’t driving alignment, clarity, or momentum, they’re just slowly draining it.

## What a Structured Recurring Meeting *Should* Look Like

![The Structure of a High-Value Recurring Meeting — infographic showing six key elements: clear purpose, evolving agenda, defined roles, documented decisions, progress review, and intentional attendance.](https://wedo-assets.sos-ch-gva-2.exo.io/the_structure_of_a_high_value_recurring_meeting_en_897b3c5b75.png)

Not every recurring meeting is a lost cause. The good ones do exist, and they don’t happen by accident. Here’s what separates a structured, high-value recurring meeting from the kind people join out of obligation:

- **There’s a clear purpose.** Everyone knows *why* this meeting exists, whether it’s to resolve blockers, review key metrics, or make decisions. If the purpose changes, the format changes with it.
- **The agenda evolves.** It’s not a static checklist. It’s built in advance, focused on outcomes, and time-boxed. New topics are added intentionally, not out of panic or filler.
- **Roles are defined.** Someone’s leading the discussion. Someone’s capturing notes. Someone’s accountable for follow-ups. If no one owns it, it won’t get done.
- **Progress is reviewed.** Last week’s action items don’t disappear into the void. They show up again, visibly, until they’re done or resolved.
- **Attendance is intentional.** If someone doesn’t need to be there, they don’t get dragged into the call. Relevance drives participation, not habit.

When a recurring meeting is structured this way, it stops being a placeholder and starts becoming a lever for progress. It helps people show up prepared, stay engaged, and leave with clarity, not confusion.

## How to Fix a Broken Recurring Meeting

If your recurring meeting feels off, it probably is.

And like most of us, you probably don’t want to keep pulling people into a meeting that isn’t helping anyone move forward.

However, you don’t need to overhaul your calendar or reinvent how your team works. A few thoughtful changes can make a big difference, bringing structure, purpose, and energy back into the rhythm.

![Fix Your Broken Recurring Meeting: 7 Smart Changes — infographic showing seven tips for improving recurring meetings with icons for each step.](https://wedo-assets.sos-ch-gva-2.exo.io/fix_your_broken_recurring_meeting_7_smart_changes_en_a22c5c7735.png)

Here’s where to start.

### Reconsider the standing invite

Sometimes the most helpful thing you can do is hit pause.

Cancelling a recurring meeting, at least temporarily, can create space to rethink its purpose. You’re not removing it out of frustration. You’re making room to rebuild it with the right intent.

This also signals to the team that their time matters, and that the meeting will come back stronger, not just… back.

### Set a purpose and an end date

Not all recurring meetings need to last forever. In fact, most shouldn’t.

If a meeting exists to help move a project forward, consider setting a natural expiration point. You can always restart it later if it’s still needed. But adding an end date gives everyone a reason to focus, make decisions, and avoid dragging things out just to fill the time slot.

And if the meeting’s purpose can’t be clearly defined in one sentence? That’s a sign to rethink it entirely.

### Get clear on what the meeting is for

Vague goals lead to vague meetings.

Before restarting the series, take a moment to clarify what a successful version of this meeting would look like. Is it meant to surface blockers? Make decisions? Align on progress?

If you can define the purpose clearly, the rest, agenda, frequency, attendees, gets much easier to shape.

### Refresh the format so it works for the team (not just the calendar)

If your current format feels flat, it probably hasn’t been updated in a while. Look at what’s missing:

- Are the same few people speaking while others check out?
- Are action items getting lost after the call ends?
- Does the meeting feel disconnected from what’s actually happening week to week?

Now’s the time to make the structure work harder:

A dynamic agenda, a few defined roles, and a consistent way to track outcomes can go a long way.

### Set new norms for how the meeting runs

As the format changes, so should the expectations.

It helps to say them out loud, or better yet, write them down. Things like:

- “Add topics to the agenda before the meeting”
- “Use the first few minutes to review open action items”
- “End with a recap of who’s doing what”

You’re not making it rigid, you’re making it clear. And that clarity gives people a reason to stay engaged.

### Make attendance flexible

Not every meeting needs to be a full house. If only three people are actively working through a handoff or decision, everyone else can sit it out.

Encourage people to attend when it’s relevant, not just because their name is on the invite. That shift alone can turn a meeting from a time sink into a focused working session.

### Give the structure somewhere to live

It’s tough to keep a recurring meeting useful if the details are scattered across inboxes, chat threads, and documents.

When your meeting prep, discussion, and follow-ups are all in different places, things slip. And people lose track, not because they don’t care, but because they don’t have visibility.

That’s why having a centralized tool matters. One place for agendas, notes, and action items. One place to stay aligned.

### Revisit the structure regularly

Fixing a recurring meeting isn’t a one-time task, it’s a habit. Once you’ve got the structure working, set a reminder to check in on it every few months. Is the agenda still relevant? Are action items getting done? Has the purpose shifted? Small course corrections over time can keep the meeting sharp and valuable, instead of slowly drifting back into autopilot.

## Why WEDO Makes Recurring Meetings Work

Let’s face it, recurring meetings aren’t going away. And honestly, they shouldn’t. When they’re structured well, they can keep teams aligned, accountable, and moving forward without the daily scramble. The problem is the lack of visibility, ownership, and follow-through.

[WEDO](https://wedo.com/features) gives recurring meetings the infrastructure they’ve been missing:

- **Shared agendas** that evolve week to week
- **Real-time note taking** so nothing slips through
- **Automatic follow-up tracking**
- **Integrated [task management](https://wedo.com/blog/how-to-choose-the-right-task-management-tool-for-your-team)** that connects discussion to action
- **One space for context, decisions, and accountability**, before, during, and after the meeting

No more toggling between docs, inboxes, and sticky notes. No more repeating the same update three weeks in a row. With [WEDO](https://wedo.com/features), your recurring meetings don’t just feel better. They actually work better.

Ready to make your recurring meetings worth everyone’s time? [Try WEDO for free today](https://wedo.com/signup) and see what structured meetings can actually do for your team.

Tired of unproductive recurring meetings? Learn how to structure them for clarity, engagement, and follow-through, without wasting everyone’s time.

“How to Structure Recurring Meetings — illustration showing a process loop with arrows around a gear icon.”

large_39-reccuring-meetings-how-to-structure-them-for-clarity-and-value.png

medium_39-reccuring-meetings-how-to-structure-them-for-clarity-and-value.png

small_39-reccuring-meetings-how-to-structure-them-for-clarity-and-value.png

thumbnail_39-reccuring-meetings-how-to-structure-them-for-clarity-and-value.png

39-reccuring-meetings-how-to-structure-them-for-clarity-and-value.png

Recurring Meetings: How to Structure Them for Clarity and Value

![Illustration showing the integration between WEDO and Microsoft Teams. On the left, the WEDO interface with agenda items; on the right, an active Teams video meeting.](https://wedo-assets.sos-ch-gva-2.exo.io/wedo_teams_en_3bc984dd21.png)

[Microsoft Teams](https://www.microsoft.com/en-us/microsoft-teams/group-chat-software) has become the default meeting room for many organizations. It’s fast, reliable, and deeply integrated into daily workflows. But it’s not built to manage the full lifecycle of a meeting.

It connects participants in real time, but once the call ends, that connection stops. The agenda, decisions, action items, and shared documents? They live elsewhere. Often in people’s inboxes, personal notes, or not at all.

Teams provides the space to talk. What it doesn’t provide is structure. And without structure, even the most productive conversations can get lost in follow-up.

That’s where [WEDO](https://wedo.com/features) comes in.

By integrating directly into Microsoft Teams, WEDO brings full meeting management into the same space where the meeting takes place. From setting the agenda to assigning tasks and locking the minutes, WEDO turns every meeting into a complete workflow, with nothing falling through the cracks.

## WEDO Brings Meeting Structure Into Microsoft Teams

For most teams, the moment a meeting is scheduled in Teams, the scramble begins: backchannel messages, scattered agendas, last-minute doc sharing. People show up uncertain about what’s being discussed or why they’re even in the room.

This kind of disjointed preparation wastes time, drains energy, and turns meetings into something people get through, not something they contribute to.

WEDO changes that without requiring a new system or process. Once added to a Teams workspace, it becomes a tab inside the meeting channel. From there, everything starts to come together.

You don’t need to switch platforms or introduce a new system. Instead, WEDO adds the structure Teams lacks, directly inside the interface your team already uses. From there, you can do everything you need to run an effective meeting:

- Build a shared agenda
- Collect input from attendees
- Attach relevant documents
- Assign roles and clarify objectives
- Launch votes or approval blocks when needed

And none of it happens in a vacuum. Every topic is tracked, every file is in context, and every decision has a place to live, without ever leaving Teams.

This integration allows meetings to move from preparation to execution without breaking flow. No toggling between apps. No chasing files in email threads. Just one workspace where discussion and documentation stay connected.

![Screenshot of the WEDO app in Microsoft Teams showing a list of upcoming meetings with date, status, and participants, plus a form to add a new meeting.](https://wedo-assets.sos-ch-gva-2.exo.io/wedo_meetings_teams_en_caa3e23498.png)

For teams that already rely on Microsoft Teams to collaborate, WEDO fills a very specific and often overlooked gap: it gives the meeting lifecycle a defined start, middle, and end, without needing to leave the environment people are already working in.

::button-primary[How to integrate WEDO with Teams]{link="https://help.wedo.com/en/articles/48757-integrate-wedo-into-microsoft-teams"}

## Keep the Meeting on Track, and Make It Count

Once the meeting begins, WEDO stays open in the Teams tab, right alongside the call, so everything stays in context. The agenda isn’t something people saw once in a calendar invite. It’s right there, visible and active, guiding the discussion as it unfolds.

As the conversation moves forward, so does the documentation. Notes are written live. Tasks are created in real time, with deadlines and assignees. Decisions are recorded directly under the item they relate to.

This kind of live collaboration creates clarity in the moment. No one’s wondering what was said or who’s responsible for what. And if alignment is needed on the spot, voting blocks allow participants to weigh in and move forward without delays or email follow-ups.

The collaboration feels natural because it’s happening where the conversation is happening, in the same interface, with the same people, in real time.

WEDO makes meetings easier to follow *while they’re happening*, not just easier to summarize afterward. Which means less confusion, fewer follow-ups, and more time spent moving work forward instead of revisiting what was already covered.

## After the Call Ends, the Work Continues

The real test of a meeting isn’t how much was discussed, it’s what happens after.

Without structure, even productive conversations lose momentum. Tasks get forgotten. Decisions blur. The same topics resurface week after week, because no one can find the original context.

WEDO closes that loop, *still inside Teams.*

Once the meeting ends, every task, note, decision, and document stays exactly where it belongs. Meeting minutes aren’t buried in a shared drive or manually rewritten after the fact, they’re already done. You can lock the report to preserve its integrity, and request electronic signatures directly from within the platform, whether you need SES, AES, or qualified signatures with legal weight.

Tasks remain connected to the specific agenda item they came from. If someone needs to review why a decision was made, they don’t have to guess. They can open the meeting, find the topic, see the discussion, and track the resulting action, all without leaving Teams.

That kind of traceability builds accountability. People know what they’re responsible for. Nothing slips through the cracks. And when you come back to the next meeting, the conversation can move forward instead of starting over.

WEDO makes that continuity automatic. The meeting doesn’t disappear once the call ends. It becomes part of a living record the whole team can rely on.

## Control, Privacy, and a Clear Line of Ownership

![Map of Europe highlighting Switzerland with markers for Zurich and Geneva. Text: “Your data is safely stored in Swiss data centers located in Zurich and Geneva.”](https://wedo-assets.sos-ch-gva-2.exo.io/data_storage_en_16a2492132.png)

Bringing [WEDO](https://wedo.com/integrations/ms-teams) into Microsoft Teams does more than streamline your meetings. It reinforces trust in how your information is handled.

Even while operating within the Teams interface, WEDO keeps all meeting data, like notes, documents, tasks, and decisions, under its own roof. Content is stored securely on servers located in Switzerland, where it remains subject to WEDO’s strict data protection policies and your organization’s governance standards. No data is shared with Microsoft. No content is duplicated or processed outside the WEDO environment.

This separation is important. Many collaboration tools prioritize integration at the expense of ownership, but WEDO takes the opposite approach. It offers full interoperability with Microsoft Teams without relinquishing control over your content. That means you can collaborate in real time without compromising on confidentiality, data residency, or compliance.

For organizations working in sensitive environments, whether legal, financial, public sector, or research-focused, knowing exactly where information is stored, who can access it, and how long it’s retained isn’t a preference. It’s a requirement.

WEDO helps you meet that requirement without extra complexity. Meeting content stays visible and accessible to the right people while remaining protected and centralized under one secure system. Teams provides the space for discussion. WEDO ensures the record is complete, accurate, and entirely yours.

## The Meeting Space Is Only Half the Equation

Microsoft Teams gives you a place to talk. WEDO gives you the structure to make it count.

From preparation to follow-up, WEDO fills the operational gaps that Teams doesn’t address. Agendas stay visible, decisions are documented in real time, and tasks remain tied to the conversations that created them. Everything lives in one place, connected to the meeting, and accessible to the people who need it.

And because WEDO keeps your data under your control, you can collaborate with confidence, without compromising on ownership, privacy, or clarity.

If your team already runs on Microsoft Teams, [WEDO](https://wedo.com/features) doesn’t ask you to change how you work. It simply makes every meeting easier to run, easier to track, and harder to forget.[Try WEDO for free today](https://wedo.com/demo) and turn every meeting into something you can build on.

Discover how WEDO brings complete meeting management into Microsoft Teams, streamlining agendas, notes, and action items in one integrated workspace.

Graphic titled “WEDO + Microsoft Teams.” Shows an online meeting with several participants, WEDO agenda items, and icons for microphone, calendar, and meeting.

large_update-teams-en.png

medium_update-teams-en.png

small_update-teams-en.png

thumbnail_update-teams-en.png

update-teams-en.png

WEDO + Microsoft Teams: What Your Meetings Were Missing

In the fast-paced world of administrative management, executive assistants play a crucial role. The Swiss army knives of any organization juggle many tasks and deadlines while supervising those of others. Faced with these challenges, they often find themselves overwhelmed by routine, repetitive responsibilities. We immersed ourselves in the daily lives of 6 executive assistants who use the WEDO platform to understand the workings of their organization, the challenges they face, and the tools they have put in place to facilitate their management.

According to our study, the most time-consuming tasks for executive assistants revolve mainly around administrative functions. These activities, while necessary, tend to monopolize a significant proportion of their working time, preventing them from concentrating fully on more crucial aspects of their role, such as operational and strategic development.

Among the most time-consuming tasks in their job descriptions, the executive assistants surveyed identify the following:

**1. Meeting preparation:** preparing agendas and presentation documents, taking and sharing minutes, following up on decisions and tasks delegated at meetings,

**2. Diary management and meeting organization:** planning and coordination of appointments, team meetings, and conferences, taking care to avoid scheduling conflicts,
**3. Document preparation and management:** drafting, proofreading, and organizing important documents such as reports, presentations, correspondence and contracts,

**4. Project coordination:** managing and following up on specific projects, liaising between different departments, and meeting deadlines.

Internal and external communications, administrative support, and human resources management closely follow those.

## How to lighten the administrative load for an executive assistant?

When asked what tools were used to monitor collaboration before WEDO was integrated, the most common programs were Outlook, Word (for taking minutes), and Excel. However, these tools had significant limitations. Respondents reported difficulties related to the cross-functionality of information between different team members. For example, these tools were not conducive to **active, real-time collaboration when taking PVs**, making this task often cumbersome and time-consuming, and necessitating numerous round-trips. The systematic use of e-mail to distribute these documents wasted considerable time without guaranteeing effective communication.

Furthermore, the limited nature of these tools prevented efficient tracking of tasks and projects. Users faced significant challenges maintaining a clear, up-to-date overview of projects. In short, although these tools are widespread and familiar, their use in team collaboration and project management needs to be improved.

This situation underlines the importance of cross-functional tools and solutions to lighten the administrative workload. With the implementation of WEDO, the executive assistants surveyed were able to optimize their administrative processes.

### 1. Meeting preparation and management

![computerized agenda for real-time note-taking](https://wedo-assets.sos-ch-gva-2.exo.io/reunion_ENEN_aad2ef7f0e.png)

One of the most time-consuming aspects of the job is the preparation of meetings. With WEDO, executive assistants benefit from automated management and considerable time savings in preparation and follow-up. The platform enables uniform management of minutes, clear distribution of post-meeting tasks, and automatic tracking of topics from one session to the next. Users report an average time saving of 55% for these tasks.

![save time spent on meetings](https://wedo-assets.sos-ch-gva-2.exo.io/55_ENEN_83c8604c19.png)

WEDO's meeting module lets you integrate blocks of paragraphs, tasks, file attachments, personal notes, votes and signatures, among others.

![testimonial Regula Oberdorfer](https://wedo-assets.sos-ch-gva-2.exo.io/Regula_Oberdorfer_ENEN_1a54d3c30f.png)

### 2. Project management and task tracking

![efficient task management](https://wedo-assets.sos-ch-gva-2.exo.io/tasks_ENEN_be99588a59.png)

Project management and tracking represent another major challenge. WEDO simplifies this task by offering clear delegation possibilities, the creation of checklist templates to standardize processes, and real-time task tracking. This leads to better prioritization and more efficient day-to-day management.

![testimonials Aline Volery and Nicole Thalmann](https://wedo-assets.sos-ch-gva-2.exo.io/testimonials_Aline_et_Nicole_ENEN_11a8dc6cff.png)

### Use case: facilitating HR processes and the transmission of specifications

When executive assistants are involved in HR processes, the integration of WEDO proves to be a major asset. The platform makes it possible to standardize on-boarding and off-boarding procedures by means of specific checklists. These checklists, drawn up for each stage of the process, automatically assign the relevant tasks to the team members concerned. This method ensures structured, efficient management of personnel transitions, eliminating the operational uncertainties often associated with the question "What steps should I take?".

By simplifying these processes, WEDO not only eases the workload for HR managers, but also contributes to a clear, documented handover of tasks and knowledge from one employee to the next.

![simplified hr processes](https://wedo-assets.sos-ch-gva-2.exo.io/Modeles_checklists_ENEN_fdf58af70f.png)

One of the decisive advantages of WEDO, highlighted by our management assistants, is the ease with which recruitment interviews can be documented in real time. Each exchange can be recorded directly in a standardized (and customized if required) agenda, enabling these interactions to be saved methodically and instantaneously.

### 4. Transmission of information

WEDO lets you link documents to tasks or meetings, ensuring that all the necessary information is in the right place. Global search makes it easy to retrieve documents, and to find a specific file based on a keyword found in the PDF file.

In terms of communication, WEDO users particularly appreciate the immediate visibility of entries and the ability to restrict access to certain information.

![Alexandra Locher](https://wedo-assets.sos-ch-gva-2.exo.io/Alexandra_locher_ENEN_e53527e95c.png)

**We asked our users to rate the platform on a scale of 1 to 10, to qualify the positive impact WEDO has on their daily tasks.**

![Best collaborative software for executive assistant productivity and organizations](https://wedo-assets.sos-ch-gva-2.exo.io/preparation_reunion_note_ENEN_1_d92c7629a1.png)

![Alicia Aubert](https://wedo-assets.sos-ch-gva-2.exo.io/Alicia_Aubert_ENEN_5d3644b8f7.png)

Executive assistants can greatly ease their workload by equipping themselves with a collaborative platform. Do you have any questions or doubts about WEDO's compatibility with your needs? We'll be happy to give you a short 30-minute demonstration.

::button-primary[Try WEDO for free]{link="/signup"}

::button-primary[Schedule a live demo]{link="/demo"}

In the fast-paced world of administrative management, executive assistants play a crucial role. The Swiss army knives of any organization juggle many tasks and deadlines while supervising those of others

An executive assistant speaking on the phone with colleagues blurred in the background, overlaid with the text “How to make an executive assistant’s daily life easier” and “Use case”

large_1-making-daily-life-easier-for-executive-assistants.png

medium_1-making-daily-life-easier-for-executive-assistants.png

small_1-making-daily-life-easier-for-executive-assistants.png

thumbnail_1-making-daily-life-easier-for-executive-assistants.png

1-making-daily-life-easier-for-executive-assistants.png

Making daily life easier for executive assistants

Held once a month, quarter, or half-year, as required, these privileged meetings provide a confidential and open communication space, encouraging in-depth discussion of individual and collective objectives. They create a valuable opportunity to discuss each employee's specific challenges and needs, fostering better mutual understanding. Moreover, these meetings provide a framework for recognizing individual achievements and contributions, reinforcing a sense of accomplishment and belonging to the team. Thanks to these personalized exchanges, bilateral meetings contribute to more effective personnel management, more focused professional growth, and solid, fulfilling working relationships.

## Key topics for a bilateral meeting

During a bilateral meeting between a team leader and an employee, several key topics must be addressed to ensure effective communication and optimal management. Here are some of these topics:

### 1. Ongoing assessment
Discuss objectives for the current period and assess progress and results achieved. Identify successes and areas requiring further attention.

### 2. Professional Development
Explore opportunities for employee development, training, and professional growth. Identify skills to be strengthened and possible progression paths.

### 3. Feedback
Exchange constructive feedback on work performed, highlighting strengths and addressing areas for improvement. Encourage open dialogue to stimulate continuous learning.

### 4. Needs and Challenges
Allow employees to express their needs regarding resources, assistance, or support to accomplish their tasks. Discuss possible obstacles and find solutions together.

### 5. Work-Life Balance
Address workload-related issues, stress levels, and work-life balance. Identify measures to support employee well-being.

### 6. Projects and Initiatives
Discuss future projects, new initiatives, and potential employee contributions. Encourage active participation and creativity.

### 7. Management feedback
Offer employees the opportunity to share their feelings about management, work methods, and team communication. Foster an environment of trust and continuous improvement.

### 8. Focus on Vision
Ensure that the employee understands and adheres to the team or company's overall vision, values, and goals.

### 9. Resources and Support
Identify the resources required for the associate's success and ensure that he/she has the proper support to carry out his/her tasks.

### 10. Long-Term Planning
Examine longer-term perspectives and discuss the employee's career aspirations and how these align with team or organizational goals.

_"Enabling discussions in bilateral meetings, in a more intimate way and with a long-term vision, brings a notable benefit to the employee's career in the company. It makes them feel valued, heard and recognized above all. Setting clear, long-term objectives is a real motivator for them."_

**Marie Rudaz-Jaeggi**, *[AmbitionSuccess.ch](http://ambitionsuccess.ch/)* - MORGES

Team leaders and employees can establish fruitful collaboration, foster professional development, and maintain a positive working climate by addressing these topics regularly and in-depth at bilateral meetings.

## Use WEDO to keep track of your bilateral meetings!

![1_1 ENFR.png](https://wedo-assets.sos-ch-gva-2.exo.io/1_1_ENFR_78b8a89537.png)

With WEDO, you can prepare your agenda jointly with your manager or colleague. In this way, each participant can prepare the questions or topics to be addressed.

Generally speaking, the agenda items for a bilateral meeting are recurrent. WEDO enables you to set the topics so that they recur from one time to the next to ensure that discussions are followed up and that objectives evolve.

Once completed, the minutes are locked and remain available to both participants for consultation.

::button-primary[Schedule a live demo]{link="/demo"}

During a bilateral meeting between a team leader and an employee, several key topics must be addressed to ensure effective communication and optimal management.

A smiling person listening to their counterpart in a one-on-one meeting, overlaid with the text “Topics for a one-on-one meeting” and “Use case”

Kanban

Kanban vs. Scrum: Which One Should You Use?

What Is a Kanban Board? Tools, Apps, and Project Use Cases Explained

How to manage a project with WEDO?

Custom fields

WEDO integrates the kanban view

Ready to dive in?Start your free trial today.