To be as transparent and efficient as possible, this is how we have set up our tools to handle various types of communication with our consumer teams:

• Figma | Separate Jira-board Figma templates | See my talk for more info 😄 | | - Documentation | - Gitbook
• Storybook
• iOS App
• Android App | Internally available for all staff at Agoda | We keep as much of our documentation as possible in Gitbook - components, tokens, processes, guidelines, etc.

We still find Storybook the best and easiest way to provide interactive examples and to-the-point references.

We have build a bespoke app on iOS and Android where our consumers can play around with our native components. | | - Questions

• Bug reports
• Design reviews | Slack | #ads-questions | We have one channel as intake for all these topics.

We built a slackbot to guide the consumers better, and to track all engagement data, so that we can manage time-allocation for support better.

We have integrated the AI-feature from our documentation platform, so that questions can be automatically answered, whenever the bot finds the right answer in our documentation.

We use a simple ✅ to mark questions as answered, so we can track response and completion lead times, and response rates, and monitor these against our SLA’s. | | - Topical discussions | Slack | #ads-component-button #ads-token-color #ads-asset-icons #ads-tooling-design-linter #ads-process-requests #ads-releases … | We have topical channels in Slack for every component, token type, visual asset type, plugin or process that we introduce.

These are useful for quick and easy feedback loops when discussing requirements, building out new things, or random thoughts and ideas.

All channels are open for anyone in the company to monitor or contribute in.

This is especially helpful for contributions, and transparency in general. |