Getting Started With Slack

Welcome to the Practical Service Design Slack community! Here's a quick guide to getting started with our Slack instance.

Get Slack set up

Once you create your account, make sure to download the Slack app for desktop, and the Slack app for your phone. Visit Slack's downloads page to get these apps!

For desktop, we suggest adding Slack to your user's login items (Mac) so that the app launches when you start your computer. This way, you can automate connecting with the community (if that's what you want to do).

If you want, you can customize your sidebar colors (this is helpful for when you are part of multiple Slack teams). Do this by visiting your preferences in the main dropdown on the "Service Design" Slack channel name in the sidebar.

Join channels

Our Slack channels can change daily, as we enable letting members of the community create channels. That said, our community is careful about our channels. When you join, you will be automatically added to several channels. You can easily leave a channel if you are not interested in "watching" it.

To discover new channels, from the sidebar click directly on "Channels" to browse and search for channels.

Here is our guide to our Slack channels (last updated 9/12/16):

  • Channels we think everyone should consider being part of (auto-added):
    • #general – The default, free-for-all, open discussion channel for everyone. Post questions, ideas, and discussion topics here.
    • #introductions – When you join, post an introduction here about you, where you work, what you do, and what you're hoping to get out of the community.
    • #links-and-articles – For posting any sort of link or article to share with the community.
    • #jobs – For posting job seeking announcements or opportunities.
    • #case-studies – For posting specific links to case studies in service design.
    • #events – For posting upcoming (or past) events for the service design community globally. Any sized event welcome, though specific local meetups should be organized in the local geographic channel.
    • #new-to-sxd – For helping those new to service design get started.
    • #trenches – For sharing and getting feedback on projects and work in-progress.
    • #shenanigans – Your outlet for when you want to post something not related to service design directly, or something silly.
  • Channels that are aimed at a more specific audience (opt-in):
    • #help – If you need help with our slack community or technical issues. 
    • #laboratory – For those who want to discuss the high-level theory and practice of service design, and advance the field.
    • #portfolios – For discussing and sharing portfolios.
    • #speaking-presenting – For community around public speaking.
    • #wiki – For those working on the Service Design wiki.
    • #blueprinting – For those wanting to discuss service blueprinting as a method.
    • #books – For talking about service design books.
    • #spaces – To share what your workspace looks like, and where service design happens.
    • #meetup – A channel to facilitate real-time conversation during virtual meetups.
    • #awesome-quotes – For quote sharing.
    • #best-of – For capturing the best of our Slack for future newsletter.
    • #futures – For discussing and envisioning the future.
    • #webinars – A channel to facilitate real-time conversation during webinars.
    • #topic-itil_itsm – For discussing how service design integrates with ITIL and ITSM.
    • #role_consultancy – A channel for those working in an agency or consultant context.
    • #role_in-house – A channel for those working in-house inside a company.
    • #enterprise – Enterprise-level service design and lean practice.
    • #snippets – For sharing micro-case studies.
    • #blessed – Irony and sarcasm only, please.
  • Channels for geographical regions: The rule of thumb with our local channels is critical mass. If the community has a need for a geographic channel, what regional level will be most useful for communicating, and support our critical mass of community members in that region? These channels are created on demand by the community.
    • #local-asia – Asia
    • #local-australia-nz – Australia or New Zealand
    • #local-canada – Canada
    • #local-chicago – Chicago, USA
    • #local-euro – Europe
    • #local-hungary – Hungary
    • #local-losangeles – Los Angeles, USA
    • #local-miami – Miami, USA
    • #local-nyc – New York City, USA
    • #local-portland – Portland, USA
    • #local-sfbayarea – San Francisco Bay Area, USA
    • #local-stlouis – St. Louis, USA
    • #local-sandiego – San Diego, CA, USA
    • #local-seattle – Seattle, USA
    • #local-siliconvalley – SF Bay Area Silicon Valley folks
    • #sdn_boston – For Service Design Network Boston
  • Channels for folks interested in helping out with our community:
    • #community-planning – The primary channel for ideas for how to improve, grow, or add to our Slack community.
    • #planning-curation – Specific conversation for subgroup interested in curating content in the community.
    • #planning-events – Specific conversation for subgroup interested in curating community events.
    • #planning-web – Specific conversation for subgroup interested in helping out with the Practical Service Design website as a resource (that's this!)

Set notification preferences

Once you have joined channels and set up your Slack apps, it is important to customize your notification preferences so that you are receiving notifications only from channels you want to, during the times of day you want to.

You can customize notifications per-channel by clicking on the notifications icon when you are in a channel. There are also account-wide notification preferences you can set. We suggest the following:

  • Do not disturb - set this for your non-work times so that you don't get pinged while you are not working (unless you want to!)
  • For channels you want to watch, set notifications to all activity.
  • For channels you are part of but don't want constant notifications for, set notifications just to highlight words (which you can specify) and mentions.

Community guidelines

Please read our initial announcement about launching the community of practice.

  • Have respect and consideration for all members of the community.
  • Try to keep conversations to the correct channels.
  • Stay on topic. Our community is a community of practice for service design. If conversation veers too off on a tangent, we may ask you to move it to #shenanigans or to another platform.
  • Create a safe and welcoming environment! Anyone who is mistreating others or abusing information will be removed from the community.

We welcome your ideas and feedback on improving this page as a resource for the community! Contact Megan or Erik in Slack, or join the #community-planning channel to discuss and coordinate.