Download the full 2021 State of Project Management report

How do companies use task managers as part of their project management? This question was burning a hole in our to-do list for our tasks feature, so we did something about it. We knew that this in-depth research could help companies think about how they work in a new way. We surveyed over 50 respondents about their practices with task managers at work to get a deeper, more honest look behind the scenes.

Here are a few highlights from the results.

Survey says: The task-management industry needs a little task management.

The project management software industry is whopping 

 and is expected to hit nearly $6 billion by 2027. We think we know why.

What the survey results reveal is that task-management practices are all over the place. Most companies are jugging two or more tools, overlapping responsibilities, and making it harder for themselves to report and get actual work done (because 

our brains don’t love context switching

Teams can’t even handle standardization of one project management tool, let alone all the extras.


Teams are crafting quite the tech-stack cocktail.

64% of teams are using multiple task managers.

We saw a theme with engineering and development teams using Jira while the rest of the organization worked on other project management tools.

"Yes, different teams use different tools (brand team uses Jira, UX uses Asana, dev uses GitHub, etc.)"

"Monday and Jira overlap - Each also has stuff the other doesn't include. The long tail of tasks is spread evenly and chaotically."

The most popular task managers in our survey:

Honorable mentions (35%): Linear, ClickUp, 

Task assignment and prioritization have little uniformity across organizations.

The way people assign tasks is all over the place. Some have a project or product manager who give tasks, whereas others have an every-contributor-for-themself approach. And no one knows how to prioritize them.

"We're pretty fluid as a startup, so no real 'management' of tasks, tasks are added by anyone, discussed and prioritised."

"At the moment, engineers self-assign according to their area of expertise. The engineering lead should also help with assigning. However, the process is still a little broken as the engineering leader doesn't quite grasp prioritization, so it often is a task between the designer and product manager."

When prioritization doesn’t happen in the actual task manager, that’s when “touch bases” and “fleshing out” comes into play.

“Let’s take this offline” is where project management is really happening.

A lot of convos are happening around tasks in a separate arena than the project management tools. We’re coining the term “work-planning inception” because that’s what many companies are doing — creating tasks around the tasks.

use the comment functionality in the task manager

The new work norm: disjointed conversations, lost information, and notification overload.

Information overload is real, and it’s destroying productivity.

Poor task management = information overload (or not enough).


When employees receive hundreds of emails a day, they miss a huge chunk (up to a third). 

, satisfaction, burnout, and bad business.

Additional issues that come from messy task management:

Work planning inception (when managing your tasks becomes a task)

“I moved to Asana versus an Excel status sheet that I have a weekly meeting with the client and review, and it drives me crazy. It takes me an hour trying to update that, and it's always an hour before the call.”

Task managers aren’t inherently bad—we love them! According to a recent report from 

, project management software adoption is linked to high-performing projects.

The way teams use task managers is the problem. We know these 50 companies aren’t alone. 

How is your team using task managers? Do you fall into the new work-inception norm? Read the full report to see what trends you identify in your organization. You may find that your frustrations aren’t so unique after all.

And it's more complicated than you thought. Our State of Project Management in 2021 report is the most comprehensive data on what teams are doing with their task managers.

State of Project Management in 2021 Report Reveals How Companies Use Task Managers

Let's face it: you’re over toggling back and forth between Asana, Slack, and Google Docs for every. little. update. 

That’s exactly why email marketers are ditching distractions and collaborating right inside HubSpot using Cord.

Easily collaborate with teammates and manage approvals

Email pros are the best at “workflows,” but sometimes it’s their own that gets thrown off. More changes and more eyeballs = less efficiency in getting work done.

And it’s worse than ever. According to the 

Litmus “2020 State of Email Workflows”

 report, the pandemic made the approval process worse for email teams.

 Nearly 70% of companies changed their strategy, adding extra stakeholders to the approval process. This added more to the email marketer’s plate: 37% of teams reported spending over two hours on approvals alone in 2020, up from 20% in 2019.

How will Cord help clear your plate as an email marketer?

You forgot if you asked Darius from design about the preferred logo in Slack or Asana. Or maybe it was Google Docs? Gah. Email managers can invite their copy and design teams into HubSpot to spare the search for notes. Spend more time ensuring you have sleek graphics and powerful messaging.

 No more screenshots pasted in a deck, bad PDF saves, or “New Campaign Test_v.98” for email creative reviews. After so many back-and-forths with your manager, going past Review and pressing SEND looks so tempting. Get there faster with centralized feedback on drafts.

There’s nothing quite as satisfying as seeing your campaign land in people’s inboxes. You did it!

Cut distractions with do-it-all-in-Hubspot integrations

You’re setting up campaign workflows, marrying design and copy, and optimizing landing pages. HubSpot is your home base for it all, whether you like it or not.

 without getting sidetracked by the pings from your team’s project management tools. 

Integrating with tools like Asana and Slack, Cord ensures project management isn’t another chore.

Cord allows you to make intentional, not distracting, visits to Slack (you know, for when you need to get right to business without being thrown into a whirlwind of GIF wars). Selective notifications means you won’t miss your @mentions but you can stay working in HubSpot.

Email marketers love that Cord is unobtrusive but easily accessible via a sidebar on the right of your browser.

 to address feedback in real-time. You can even chat quickly back and forth. The best part? It integrates with apps you already use.

For example, let’s say you need the price of a product in a sales email. You can message @Laura: “Can you confirm with Sales that this is the correct price?” Then:

Assign this task for Laura in the sidebar, to which it then 

. Then, update any task’s status in less than a second with Cord.

 into HubSpot (coming soon!). No more switching tabs.

 with your conversation for other people to chime in. Cord sends a link to the campaign with replies in a thread so it won’t crowd up your channel.

Cord is a Chrome extension that adds Google Doc- like collaboration to your HubSpot tab. Here’s how to install it:

Go to Cord.com and click “Add Cord to Chrome for free”

Sign-in with Slack (don’t have Slack? You can sign-up to be notified when we add support for Google and Microsoft Teams)

Watch a 30-second onboarding video to learn how you can start using it immediately

Better email management and collaboration = you shining at your job. 

With Cord available for HubSpot, you can focus more on managing campaigns in the space you work best. What are you waiting for?

HubSpot is the big orange beast we all love to hate. Sure, the platform has a better user experience than other email solutions. But just because it’s all-in-one doesn’t mean there’s only one person involved.

Work with your team directly in HubSpot with this add-on

ICYNT (In Case You’re Not Tom): On 4/20, Tom sent a hot take about how more efficient marketing ops is the answer to better B2B marketing departments.

Tom’s thesis resonated with us. As a B2B SaaS company in the workflow biz, we get the pain points of messy marketing ops and a changing how-work-gets-done landscape.

So Tom, not that you asked, but here’s our take.

Embrace remote, global talent without sacrificing unity.

“An astounding amount of talent at a fraction of the price of your city can be found when you open up roles to fully remote candidates.”

 who plan to shift to more remote work even after the pandemic permanently.

Fully remote work is scalable, cost-effective, and promotes diversity.

 and employees thousands. But arguably even more critical is the impact on the diversity of your team.

It’s not easy to achieve diversity when you keep fishing from the same pond. Gender and ethnically diverse companies are 

, even as much as 35 percent. By expanding your recruiting efforts outside of your city, or even country, you find people with fresh takes and practices.

One big caveat: your tech stack has to be async-work-friendly for those amazingly talented and diverse humans.

Automate everything (that you can). Integrate everything else.

“Most tasks now performed by lower-level marketing resources can be

Companies don’t need to keep hiring marketing assistants or buying new software. They need to automate.

 to do the work. We coined a term for the work done to plan and prioritize work: “work-planning inception.”

Automation (done well) eliminates the round-robin of that.

 automate Asana or Trello tasks, project management hits a threshold. That’s why we’ve created a way to manage tasks inside the tool you’re working in.

Because creating tasks should never be a to-do item.

In-app task management needs these three things to succeed:

On-the-spot creation (aka, not only after meetings)

Relevant context (e.g., screenshots and links)

Collaboration (e.g., ability to @mention)

This can help teams scale their project management without hiring more team members to manage projects.

There’s no need for a steep value ladder.

“As team members progress and master their tasks, they should either be handed onto a junior team member or to a machine as per the step above.”

Like anyone scaling a business or a team, there are growing pains. And there’s an art to letting go.

You hit the nail on the head when you said: “everyone on your marketing team should be climbing the value ladder.”

Cord helps marketing leaders pass the baton to junior team members by leaving clear documentation, onboarding guides, and a lifeline (aka an ability to chat or ask for feedback) exactly where they'd need them.

Whether members of the marketing team are in an app like 

, Google Analytics, Trello, or on your company’s website making some updates, they can quickly chat with their manager in context. This can eliminate the tendency to “jump on a quick call” or create a Slack-storm.

Meet less without sacrificing collaboration.

We know “asynchronous work always wins” as you said. When teams stop jumping into group-think mode and actually 

Tom, we love that you have zero scheduled meetings at Fame and bCast. Cheers to that.

Cord helps eliminate meetings by adding context without the need for screen-sharing or bad walkthroughs.

Asynchronous work still requires collaboration (just not all on Zoom calls). That’s why it’s better to keep conversations where the work happens-- don’t throw off the deep-work groove.

Document everything, but not just in a Drive somewhere.

“If we agree that asynchronous communication beats synchronous, then we need to get better and more organised with the documentation of the information needed to run the marketing department.”

Documentation is the enemy of the infamous "move fast and break things." But if you don't document, you're going to move fast, in a circle, and break the same damn things over and over again.

Toggling back and forth between where the work happens, your company’s chat app, email, and a report on the work is dead.

Instead, document what you anticipate reusing again to set up teams for success and avoid bottlenecks.

A sucky onboarding experience sets up a new hire for failure, and they’ll be 

With Cord, you can provide the resources right within the apps where work is happening by:

Adding annotations and comments explaining how things work

Provide next steps and reminders (aka, digital post-it notes)

Documentation right where it needs to be is a lot more convenient than outdated walkthroughs lost in Confluence or Coda (or Google Docs, if you're still into that).

Empower your team to take tasks across the finish line. Team members can send messages from inside the tools they work in to Slack to quickly get their manager’s input or approval, whether that's from 

, social media ad platforms, or analytics dashboards.

And we mean beyond the flying unicorns in Asana. Track campaigns and other milestones KPIs in analytics tools. Use Cord to nod to wins, emphasize significant initiatives, and share performance and opportunities with the team.

Cord enables B2B marketing teams to create, collaborate, and update the status of tasks where deep work happens. Sounds like a way to keep growing.

So Tom, when’s a good time to show you 

 on “the power of marketing ops,” and we have some thoughts.

Hey, Tom Hunt — We know how to make B2B marketing ops even better.

That’s exactly why email marketers are ditching distractions and collaborating right inside Mailchimp using Cord.

You forgot if you asked Darius from design about the preferred logo in Slack or Asana. Or maybe it was Google Docs? Gah. Email managers can invite their copy and design teams into Mailchimp to spare the search for notes. Spend more time ensuring you have sleek graphics and powerful messaging.

 No more screenshots pasted in a deck, bad PDF saves, or “New Campaign Test_v.98” for email creative reviews. After so many back-and-forths with your manager, pushing that hairy monkey hand button looks tempting. Get there faster with centralized feedback on drafts.

There’s nothing quite as satisfying as a hairy chimp hand pushing that red button. You did it!

Cut distractions with do-it-all-in-Mailchimp integrations

You’re setting up campaign workflows, marrying design and copy, and optimizing landing pages. Mailchimp is your home base for it all, whether you like it or not.

Cord allows you to make intentional, not distracting, visits to Slack (you know, for when you need to get right to business without being thrown into a whirlwind of GIF wars). Selective notifications means you won’t miss your @mentions but you can stay working in Mailchimp.

 into Mailchimp (coming soon!). No more switching tabs.

Cord is a Chrome extension that adds a collapsible sidebar to your Mailchimp tab. Here’s how to install it:

With Cord available for Mailchimp, you can focus more on managing campaigns in the space you work best. What are you waiting for?

Mailchimp is the hairy little monkey we all love to hate. Sure, the platform has a better user experience than other corporate email solutions. But it can take the strength of a thousand gorillas to bring all the moving parts together.

Heal your love-hate relationship with Mailchimp with this add-on

The adoption of e-mail, and later team chat, inadvertently led us into constant context switching and interrupted work.

 about the haphazard evolution of the internet leading us to sub-optimal workflows. A reader then pointed me to Cal Newport's excellent “

” which explains exactly how this came to be. Cal's rich research into the history of communication at work shows how the adoption of e-mail, and later team chat, inadvertently led us into constant context switching and filled our days with interruptions. Nir Eyal's “

” provides lots of evidence about how brutal these interruptions are to our ability to concentrate and produce good work. They also cause anxiety and generally wreck our enjoyment from our jobs. But new ideas are taking hold, and new habits and ways of collaborating are forming. These can unlock the highly sought after ‘in-flow’ state more regularly. We highlight four of these below, but to understand why they’re important, we first have to go to the root of the problem.

We’re wasting an hour per day on context switching. That’s $10,000 per year.

We're essentially all working with brakes on - an enormous drag on our productivity. It’s caused by context switching. Like when we jump between apps and tasks to search for some piece of info. Or, when you continue a conversation in a separate chat app to the one you do your work in. Often, we start by just looking for an answer in a chat channel history, but find ourselves losing track in a pile of other, new, incoming messages.

Our brains, meanwhile, are capable of only holding one thing at a time. So we don't notice how distracted this makes us and how inefficient this constant de-focusing is. Instead, we just carry on with a false sense of speed from rapidly switching and tackling multiple things. The reality is like one of these movies where in the hero's mind, he's a champion, and then the camera shows us how in reality, he's flailing miserably.

When lab studies keep track of how long it takes to complete tasks in different conditions, we can see that splitting our attention this way simply destroys productivity. Even a single switch every 30 minutes (which is far less than many knowledge workers are able to attain in their average work day) could end up costing over an hour of productivity a day. That's an hour less in the evening to be with your kids or your partner, and for the average knowledge worker (that’s you), this comes to around $10,000 a year. And this is just a conservative, straight-up salary cost of wasting 10-12% of your daily working hours. It doesn't include the barriers this places on creativity and problem-solving, the misery from constant task switching, and the systemic costs of more people and more orchestration needed in bigger orgs.

So why do we context switch so much in the first place?

We need help because we're not sure how to do something in a complex SaaS tool, like AWS or HubSpot. Or we need feedback after creating something - "Is this copy updated?” "Was that the intent for this design?" We need approval, or someone else to continue where we left off, or to let them know it’s ready.

So when, in turn, other people ask us for help, feedback, approval, or hand over their part, we want to unblock 

 as fast as possible. How? By responding and attending to what they need of course, before going back to our other work-in-progress. Doing that, though, interrupts them again, and continues this vicious cycle.

This reveals a fundamental tradeoff, one that seems to have no solution. On one side is latency - how fast can an item that needs several back-and-forths between multiple collaborators be completed, with the cost every back and forth imposes. On the other is throughput - the total amount of projects we can churn out as an organization in a long period of time by making sure we never 'wait' and always work on something.

Scheduling theory, a mathematical formulation dealing with these situations, is filled with surprising results. Sometimes, adding one more person that's able to handle a task reduces waiting times for other tasks by 50x! But even without doing lots of math, we have a way out, by adopting these four tweaks:

Reduce the number of back-and-forths needed to accomplish something, reducing the number of interruptions.

 When possible, give people authority to make reversible decisions themselves. Easy-to-find, clear documentation that reduces the need to ask for help is another way to achieve that.

Increase the number of people able to handle something, increasing the 'slack' in the system.

 With more people who can handle a task, there’s more odds of someone wrapping up a deep work session and becoming available to help. However, you need a mechanism so when someone needs help or feedback, it doesn't break everyone’s concentration. An email CCing the whole team or a message in a channel isn't great (that's the wrong kind of slack 😆). GitHub and similar tools have shared queues of pull requests/diffs awaiting review, and picking the next one removes it from everyone's queue: A much less disruptive workflow for utilizing several people that can work on something. Similarly, in 

, you just leave the message on the page and the people involved with the tool will see it and pick it up.

Don't break your deep flow state by switching into a separate app just to say you're done or ask a question.

 By the time you took a screenshot... annotated it... switched to Slack... found the right channel... wrote the message... you've completely lost your flow and your focus. You're very likely to encounter other distracting messages or unread channels on the way, too. Just finding the right tab again in the sea of identical icons is a drain on your dwindling focus. Especially if there's then back and forth - waiting for new messages and ⌘+Tab-ing between the app where you work and the communication tool. That's why we built Cord, so you can collaborate in context, right next to what you work on, without losing focus.

Make sure that when you go back into a project, all the background info is easily accessible.

 In Cord, it's just there where you left off, next to the page you were working on. All conversations about this item and any new messages, tasks and annotations are right where you need them. This is the ideal solution, otherwise you find yourself searching multiple chats, task managers and internal wikis to remember where you stopped, what were the last decisions made and what's the next step. And you can trust that anyone stepping in for you will find all that info there as well.

In urgent scenarios you still have to ensure responsiveness. Or better yet - work together at the same time with everyone who's needed to resolve the problem. Cord lets you have real-time collaboration and communication (video coming soon!) inside your tools. But for the vast majority of projects, you want to reduce the number of interruptions, increase the number of people available to help, require less effort to communicate and an easier way to get back into context.

The result of these four tweaks will be many more long blocks of uninterrupted work to reach that 'in-flow' state we're all after. The productivity you and others in your org will unlock cannot be exaggerated: Researchers like “Indistrictable”’s Eyal call this the one untapped productivity multiplier in the world today. This is how you can build a company like WhatsApp, acquired when they were serving 250M users with just 28 employees, or like 

Basecamp, where focused work lets them accomplish their projects productively and work less than most other startups

. These would sound like myths, until you take Cal Newport's advice, and put the effort to rethink your workflow and put good tools to use in unlocking the value of focus.

Context switches are a tax on our productivity. And it's a tax we're almost unconscious of. But when we're interrupted to help someone else with their work - or to jump into another app to message someone - it takes us precious time to get back to a productive, creative state of flow. There's ways to avoid that, though, and gain back precious focused time for your entire team. Here's how.

In flow and in context: How to unlock that 10x productivity for your team

The problem with rapid evolution: Blind spots and siloed tools

In biology, rapid evolution can bring about convoluted ways to solve problems. Peacocks' enormous tails are a burdensome mating signal, making the bird clumsier and an easier prey as a result. The wires of the human eye go in front of the photo-receptive cells and lead back through a hole in the middle, giving us all a tiny blind spot where the nerve fibers occlude our vision. It works, but it's not perfect.

 using computers also saw rapid evolution: We moved from desktop apps and file-based sharing to cloud-based web apps, with the average company now using over 88 different web apps, 

. In building on the shoulders of giants, copying and mutating, subsequent generations of software settled on some paradigms: In browser. Based on HTML. Log-in with Google. Open APIs.

What hasn’t evolved yet, though, is a consistent way to work together in these tools. So when we need our teammates for help, approval, feedback, or for them to do their bit, we have no choice but to resort to Slack.

The problems with this method can be hard to see, until you reimagine how you would've built it if you could control everything. Like fish in water, we're so used to the lack of communication in our work tools that we don't even notice the friction it causes. But when we're in 'deep work' mode, trying to finish, say, a marketing campaign that has to go out 

, and we're unsure we put in the right graphic - why do we have to take a screenshot, context switch, find a relevant Slack channel, re-attach the screenshot, write a message, paste the link, and then keep checking the channel back for answers, as our question gets buried under new messages from other people with different asks? We have tools where we get shit done, and other tools for communication, and there's no connection between the two. Other smart folks 

This is akin to trying to build a piece of IKEA furniture with your partner, but without being able to communicate verbally or with gestures. When you want to ask them to pass the screwdriver, or where this wooden bit fits, you have to go to another room, away from where the half-assembled cabinet is, wait for them to come in, talk about it, and go back. Except now, we're on a factory floor trying to assemble 100s of different cabinets, asynchronously, and with one room where everyone is shouting.

The magic happens when world-class communications meets context, inside the tools you use

There are great innovations in communication tools. Simplified, multiplayer, rich-text editing like Notion, voice chat apps, and even 'plain old' Slack is a major improvement over email. But SaaS tools are built for a purpose, and they do their specific job very, very well. Marketers relying on an ad-tech tool, or Devops engineers using a management console cannot and do not want to work elsewhere, so trying to force all workflows into limited capacity tools like Google Docs or your task-manager-meets-wiki-meets-chat can't be the answer. We believe the right answer is empowering these specialized tools. We want to infuse the entire stack with world-class communication.

World-class communication isn't a hyperbole. Most communication that's tacked onto a product as a lower priority feature sucks. Just try and use LinkedIn messaging for more than answering casual recruiting reach-outs for an example of that. The commenting sections of most SaaS apps are even worse. No surprise they aren’t used, causing the vendors to invest even less in improving the feature.

But imagine if communication in SaaS apps was as good, or better, than Whatsapp. They'd have search, mentions, presence, typing and 'seen' indicators, audio messages and the rest of the long list of nuances that make chat products like Whatsapp shine. Suddenly, just chatting where you're already working becomes much more convenient than Whatsapp.

If you can then interact - directly manipulate and collaborate in the tool you're having the conversation in - annotating bits of the page, editing together and creating tasks that track the work that's left to do, you become more effective. You stay in flow and leave a trail that helps others find their way and see what decisions were made and how. You don't have to go far to imagine that: No one using Google Docs ever sends you a link and says "

 - they just leave an annotation there. And if this miraculous chat is accessed and used the same way across any tool you use, with a unified inbox for all your notifications, it's easier to adopt the habit and stay informed.

A unified inbox that’s not everyone’s inbox

Another reason why Slack and the other communication 'destinations' are so distracting and a poor fit for 'contextual conversations' - where there's an item to review, a transaction to complete, or an incident to investigate across several pages - is that in these channels you're essentially in everyone's inbox. In the tools you work in, there's a set of people who are relevant to the task at hand. Once you're working with them on that task, there's no reason for everyone to continually see that conversation. But no mapping exists between the people you work with on a particular task and the channels you have available in Slack: You either spam the entire #design team, or you have to find the exact group - Juan, Michelle, Dan, Celeste (but don't accidentally choose Juan, Michelle, Dan, Diane), in which case they can't ever pull new people in or find where the decision about that marketing campaign was. And once you're in that chat destination, you'll also find you now have 6 other unread channels. In all likelihood nothing there really matters to you (it's probably all people spamming the entire team to get one item done) - but there went your entire concentration and flow.

There's a very good reason and a very good place for the townhall and phone book that Slack, Teams, etc. provide: Announcements like the company's new strategy, and DMs like "

 that are unrelated to a work item in a tool. But stuffing every single request for approval, help or feedback down that channel never works. As the company scales, you end up with 

10,400 page long guides on communications

We want to empower you to focus on the work, and collaborate inside your virtual workshop or atelier, or your own product, internal tool or landing page. That's what you're talking about, so it might as well be where you talk. That's why we built 

. To curve the arc of our tools' evolution towards their collaborative potential.

The way in which computing evolved led us to find ourselves working across different, single-player web-based tools, and communicating in a separate 'destination' like email or Slack. We can design a better way to collaborate.

How in-app collaboration is changing the way we work

Building apps – internal tools or otherwise – is 

. But actually working together with your teammates when code is involved is easier said than done. Taking screenshots, adding annotations, sending a flurry of Slack messages, and then adding Jira tickets is 


In this post, we’ll walk through how to use 

 (a fast way of building internal tools) with 

. Cord lets you add comments, annotations, and guides directly in your favorite apps – so you can talk with your team in the apps you’re working in. 

 and project management tools (Jira, Asana, Monday, etc.) so you can create and manage tickets without leaving your app.

Save time by building internal apps with Retool and Cord

Here’s a few suggestions for how teams use Retool and Cord to build better internal tools without all the back and forth.

Write onboarding guides directly in the app. 

Onboard new members of your team by creating annotations and comments with Cord. Attach relevant files to document how the internal tool works, right inside the tool. This is a lot easier than outdated walkthroughs lost in Confluence or Coda. Plus, teammates can @mention you if they have a question and you can chat directly in Retool– almost like sharing your screen on Zoom, without having to sit through another video call.

Write onboarding guides directly in the Retool app with Cord.

Create tasks that will automatically appear in Jira or Asana. 

Anytime you write a comment using Cord, whether it’s to investigate a bug or change a dropdown to a search input, you can make it an Asana or Jira task so it fits right into your workflow (and it will actually get done!).

Create tasks that will automatically appear in Jira or Asana with Cord.

Your internal ops team can log edge cases and leave a record of the conversation. 

State of Project Management in 2021 Report Reveals How Companies Use Task Managers

Work with your team directly in HubSpot with this add-on

Hey, Tom Hunt — We know how to make B2B marketing ops even better.

Heal your love-hate relationship with Mailchimp with this add-on

In flow and in context: How to unlock that 10x productivity for your team

How in-app collaboration is changing the way we work

Build together in Retool with Cord comments and annotations

Enabling Developer Velocity

Cord + Slack = Collaborative magic ✨

Add comments and annotate inside any tool you use at work, get updates in Slack

Part 2: Server Side Tech Picks

Part 1: Client Side Tech Picks