Two-Way Sync is the Future of Work: Here’s Why
The days of every team working in their corner out of the same software are long gone. Now, everyone has access to a vast array of dedicated tools to get their work done. But that comes with a drawback; the tool silo.
When everyone’s working from their own platform, their work becomes trapped within that tool’s boundaries by default. That means any process that involves multiple teams has to hop over those boundaries. That’s why the integration market exploded, pretty much in line with the growth of the software tool market.
But while there are many options for leaders looking for integration solutions, one type of solution will emerge above the rest as the new standard: two-way sync. Here’s how — and why it matters.
Centralized vs. distributed truth
The quest for the single source of truth is a perfectly natural reaction to a simple reality: truth is everywhere. Whether you’re managing a sales pipeline, a marketing campaign, or a software development workflow, you’re dealing with individual nuggets of truth spread out over multiple tools, teams, and collaborators. These bits of truth not only contribute to the overall process, but if the wrong one falls through the cracks, it can have a devastating impact on your broader workflow.
Take a sales pipeline, for example. What elements of truth do you have to deal with here? There’s contact information for the potential lead, sure. There’s any collateral or documentation that might have been sent out. If you offer a free trial, then you potentially have multiple data points reflecting how they’re using your product or service. Then there’s every message, email, and conversation you’ve had with them, as well as fixes or features the lead’s waiting on. Already, you’re dealing dozens of little bits of truth, spread out over messaging tools, contact management software, a pipeline management platform, support tools, development tools and more. With a sales process often coming down to quick reactions and having the best information available, it’s natural to want a single place where everyone in that process can get the information they need.
With a single source of truth, data is pulled from every tool in your process and transferred to one platform. This centralizes truth that’s naturally spread out over multiple tools.
And that’s the main problem. Trying to establish a single source of truth just creates one massive silo and forces everyone into it.
Your processes are made of networks of distributed truth. Every collaborator can only make the best decisions when they can work within that network from their tool of choice. A single source of truth can’t do that.
Let’s take the sales pipeline example again. Imagine a salesperson has to deal with a lead they’re trying to re-engage. Imagine this lead is the difference between making this month’s quota or not. It’s not just that one salesperson’s commission on the line, but the whole team’s performance is at stake. That salesperson needs to know if there are any open support tickets affecting that lead, when the last conversation happened, what their product usage is, and more. Do you think a single source of truth can give them the ability to quickly pull up all that information from their tool of choice?
This is just one example of a process that drives the need for adding an integration solution to your tool stack. But why does this need exist in the first place?
Functional structure vs. cross-functional work
Distributed truth is hard to collect in one place because we don’t build our tool stacks to match the way we work. They match the way our organizations are structured.
No matter what industry you’re in, your teams are organized along the functions you expect them to perform. Marketers are organized in teams — like public relations and digital marketing — that fall within a marketing department. Developers are arranged according to their specialty, from full stack developers to back-end specialists, or by application module, all within the same department. The same is true for HR, operations teams, and the rest of the organization. While you might have individual collaborators with a different skill set within a team, like a developer in a marketing team, they’re still “part of the team.”
Is it any surprise, then, that each team assembles their own tool stack, regardless of what anyone else is using?
If everyone worked exclusively within department lines, this wouldn’t be a problem. But the reality is nearly all workflows cross those lines. That’s because they depend on cross-functional work. Marketers work more closely with developers and product managers than ever before. Customer success and sales teams rely on experts throughout the company to help them close deals and hold on to valuable customers. Recruiters work with marketing to create assets that attract new talent. There isn’t a single workflow that can’t benefit from the input of multiple teams and multiple departments.
That sort of cross-functional collaboration becomes all the more challenging when you look at all the tools each team uses — and how little those tools actually interact.
We all know the number of tools we’re using has exploded in recent years. But what about the tools that don’t even go through typical acquisition channels? The tools you don’t even know your teams are using?
Shadow IT is already a big problem for organizations: 80% of workers admit they use SaaS applications that weren’t approved by IT. But the proliferation of apps and services built in-house, using no-code and low-code platforms, is an even bigger problem. IDC predicts that over 500 million of these will be developed by 2023.
So not only is each team acquiring tools that match their department’s needs, but soon they’ll be building their own. That leads to distributed truth across more apps than you can imagine, and it’s going to make having the right integration solution more important than ever.
The state of integration
The market for software integrations isn’t the same as it was six years ago — when Unito first saw the world. It’s a crowded market, full of big-time players across all categories, from workflow automation solutions to massive iPaaS (integration-platform-as-a-service) options designed for enterprise clients with big IT departments and bigger budgets.
Most of the integrations on the market today fit in one of these three categories:
- One-way automation: These integrations use simple, trigger-based logic to power automations in a huge repertoire of tools. A trigger might be, say, “when an email is received,” while the action is “create a new task in my project management tool.” These integrations are often known as iPaaS and workflow automation solutions.
- Native integrations: These are integrations that are built into your software tools. They’re much simpler than even automation solutions, often just plucking a few lines of data, an attachment, or a link from one tool and displaying them in another. However, their advantage is that you can use them without leaving your tool of choice.
- Extract, transform, load tools: These tools are essential for maintaining databases, building detailed reports, and getting more out of your data. They pull data from your SaaS tools of choice, transform it, and load it into databases and similar platforms. They’re exclusively one-way tools. These are called ETL and Reverse-ETL tools.
Most of the robust integration tools on the market fall within one of these categories. They’re great for automating large batches of repetitive tasks, but they don’t actually bring your tools together.
Why it’s not enough
These solutions are straightforward, easy to learn, and widely applicable. It’s not uncommon to find an automation platform with hundreds of integrations, since the simplicity of the logic can easily be replicated across tools. But their main drawback?
Once an automation runs its course, it’s over. It might create a new work item in your tool, but there’s no relationship between that item and the one that created it. That means updates made in one tool won’t be reflected in the other.
How many of your workflows work in exclusively one direction? Is there any process in your business that doesn’t depend on constant collaboration between teams and across tools?
Despite one-way automations ruling the integration market, they’re not enough for your workflow. That’s why the market needs a new standard: two-way sync.
What is two-way sync?
If an automation is a one-way sprint, two-way sync is a relay race. A team of people working together towards one common goal, passing the baton onward until they cross the finish line.
A two-way sync solution doesn’t just create work items in one tool or another. It creates a relationship between work items that carries updates back and forth between them. That means work can continue, in either tool, without anyone missing the latest update. Less catching up needs to happen in chat tools and emails, since everyone can see what’s going on from their tool of choice.
The bite-sized version? Automations go in one direction, once, then they’re done. They’re like wrapping up your work neatly before throwing it over a wall. You don’t see it land, can’t tell if the other team got it, and have no idea what’s happening. Sometimes you get a window. But a window doesn’t let you do more than peek in on the other side.
A two-way sync solution doesn’t give you a window. It smashes the wall down.
Why should two-way sync be the standard?
Because it matches your workflow’s needs. There isn’t a single business process that can survive on one-way automations alone, not without involving a ton of manual work, missed updates, and frustration.
Hard boundaries between teams and departments are a thing of the past. No matter what industry you work in, your daily to-do list depends on other teams just as much as it does the people on your team. And because each team uses its own tools, you need to have a way to bridge the gaps between them.
Automations are like taking a file and sending it on to another team through a garbage chute. There’s no way to know if your work actually ended up in the right place, no way to get feedback, and no way to check on updates. Not great if you need to collaborate over time.
With a two-way sync, it’s like having every department, every team, and every collaborator sitting right by your side. You can communicate with them, collaborate with them, and keep them updated in a snap, no matter which tools everyone is using. That’s a game-changer.
Two-way sync and distributed truth
One-way integrations and automation solutions can only send data along a path. When your work tool is just one node in a network of distributed truth, that makes a one-way integration little more than a window into that network. You can send things through, even get an eye on the broader process, but that’s it. Say you’re escalating a support ticket to the development team. With this approach, you send it off, it disappears in a hole, and you might get a few updates by email or chat — if you’re lucky.
With a two-way sync solution, you’re able to participate actively in every bit of the process, no matter where your tool sits in that network of truth. That’s because these solutions keep everything updated throughout your process. Your support ticket is visible in your tool of choice, and you see all the updates from the development team as they prioritize it, work on it, and complete it. You can even provide context and guidance from your tool.
How to tell true two-way syncing from imitators
It’s not impossible to build something approximating a two-way sync with an automation solution. In fact, some of those solutions even advertise themselves as two-way sync solutions. That said, they don’t provide true two-way syncing. And if it’s not true, then your workflow will suffer for it.
Here are just a few questions to ask yourself when trying to determine if a workflow management solution is an automation or true two-way syncing:
- How long does it take to set up? A two-way sync solution can support any number of work items between your tools with a single setup. An automation solution will ask that you build multiple automations to make this happen. You’ll need one per operation (e.g. creating a new work item in one tool or updating a specific field). And if you want things to update in both directions, you’ll need to double that number. That can add up to dozens of automations.
- Is there a risk of an infinite loop? With an automation solution, you run the risk of creating work items endlessly until someone spots the mistake. A true two-way sync solution has ways of automatically detecting these loops and keeping them from happening — rather than expecting you to do it yourself.
- Can it handle hierarchy? Individual automations stop at a single work item or, at best, a single field in that work item. For example, a new lead in one platform might create a new task in a project management tool. But that’s where it ends. A two-way sync solution works across all levels of your work item, natively, and automatically. That includes comments, subtasks, attachments, custom fields, and more.
- Does someone need to constantly manage it? When your “two-way sync” operates on a foundation of a dozen automations, it’s easy for something to go wrong. Unless you have someone keeping an eye on your workflow, you might start seeing more missed deadlines and more requests for updates before realizing your automation went bust.
- Who’s doing the work? Two-way sync involves technical work to match up work items from both tools and prevent issues. In a true two-way sync solution, that work is happening behind the scenes. In an imitator, you’re expected to do that work yourself. That can take setup time from minutes to months.
True two-way syncing solutions work in the background and they do what they say they do. You don’t need to build a patchwork of one-way automations to achieve a real relationship between your work items. And while there may be many imitators out there, take that as a sign that two-way syncing is slowly becoming the standard for the integration market, rather than the outlier. It’s best to get ahead of the curve while you still can.