DaS™ — Integration Section.
--
Overview
Welcome to the night and the last article of the 3x3 series — Confluence for Designers looking at the communication structure for medium and large organisations to achieve transparency, which leads to frictionless and smooth design delivery.
This article aims to address the most overseen part of our operational presence and the inevitable future. Our products and services are constantly connected and integrated with other products and services, consuming each other’s data, commands, and interactions. The complexity of these connections has become overwhelming and sometimes misunderstood.
Let’s take a fashion retail startup as an example to explain what the integration section can offer to your team and business in the most simplistic way.
What does the Integration Section do?
The integration section looks at the company ecosystem.
In the Hello [001↗] section, we have discussed ways of working which reflect the Google Workspace with drive, sheets, documents, mail and presentations in one ecosystem. Followed by Slack, Messenger and Teams as they collaborate with bigger brands who use the Office365 package.
In the Business [002↗] section, we look at the software for resourcing, HR and accounting — let’s say FreeAgent [003↗] or Xero[003↗]. Followed by the legal software managing their T&C[003↗] across multiple countries. That comes down to fulfilment centre software [003↗] that operates their livestock.
For the Research [003↗] section, they use TypeForm for surveys[003↗] as well as Qualio [003↗] in combination with Google Workspace.
When it comes to the Content [003↗] section, they use Google Documents in combination with Shopify [003↗], which is problematic from the versioning perspective that it already makes their business less adaptable.
In the Experience [003↗] section, they are more fortunate as this also combines the Design [003↗] section. After Trying out the inVision[003↗], Mural Board[003↗] and miro board[003↗], they settled on…
