Read on Twitter
We just launched our @tryramp Slack bot 
Amazing work by @thetkkong.
I'd like to share a few takeaways when designing for @SlackHQ. (Thread
) https://twitter.com/tryramp/status/1295405030468661248
Amazing work by @thetkkong. I'd like to share a few takeaways when designing for @SlackHQ. (Thread
) https://twitter.com/tryramp/status/1295405030468661248
1 - Words matter. The biggest challenge will be translating a visual product into a conversational UI. Writing is hard, I'm more convinced than ever that writing is a key skill that any product designer must cultivate.
2 - Limit the back-and-forth. We were able to keep the scope manageable by limiting the number of consecutive interactions between users and our Slack bot. We introduced forms and buttons early and limited to a single message.
3 - Show, don't tell. When possible, show example notifications. In our case, we're helping Admins decide whether to add our Slack bot to a private or public channel with a "sensitive" message. 
4 - Nuanced notification controls. We suggest a default set but encourage admins to toggle every notification we plan to send to their @SlackHQ workspace. Notice the example message underneath each option to help them evaluate.
5 - Don't reinvent the wheel. Similar to a design system you'll have access to a "drag & drop" library of Slack components. 
Kudos to @SlackHQ for Block Kit (See the docs: https://api.slack.com/block-kit )
Kudos to @SlackHQ for Block Kit (See the docs: https://api.slack.com/block-kit )
6 - Surprisingly, there is no @figmadesign resource for Block Kit, so we made our own. We're putting some final touches on it and plan to release it as a community file. DM me or @tryramp if you'd like a preview.
To sum it up:
Writing matters
Keep it short
Use real examples
Customize notifications
Stick to components
Writing matters
Keep it short
Use real examples
Customize notifications
Stick to components
