43 Matching Annotations
  1. Aug 2020
    1. Beyond its Slack-like functionality, Discord has functionality like a social graph, seeing what games your friends are playing, voice chat, etc. These have been misunderstood by the market. They aren’t random small features. They are the backbone of a central nervous system. Active users of Discord have it on all the time, even when they are not playing games. It’s a passive way to have presence with your friends. And when your friends start playing games it makes it easy to with one click go join them in the game. Bringing your actual social graph across all games. Finally, voice chat makes it possible to talk with your friends across all games, even when you are playing the game. Like when working in a google doc, having to switch out of your game to message is a negative experience. Instead Discord adds functionality to your games even while you are focused solely on them. We will see more companies understand and begin to work on this area.

      Discord, unlike Slack, is the central nervous system (or meta-layer) for the gaming market. You can see what games your friends are playing and join them in real time. You can talk with them while playing a different game.

    2. Slack ironically is more similar to Dropbox than expected. The more time goes by the more it looks like exception handling being needed ubiquitously is a transitory product as we switch off of documents. After all, like Dropbox, Slack makes the most sense as a global communication channel when the workflows themselves don’t have communication and collaboration baked in natively. For documents this is true, but increasingly for modern apps this is false.

      If Slack is an exception handler for when apps don't have communication and collaboration baked in. And if we're increasingly moving away from a document-based model (and towards these apps), then Slack looks very much like a transitory product (not unlike Dropbox).

    3. As a company’s processes mature and the apps they use get more sophisticated, we expect to see the need to go to Slack for exception handling *decrease* over time.

      If Slack is an exception handler for faulty, lacking or immature business processes, then you would expect to see less Slack usage for more mature companies.

    4. Slack serves three functions: Else statement. Slack is the exception handler, when specific productivity apps don’t have a way to handle something. This should decrease in usefulness, as the apps build in handling of these use cases, and the companies build up internal processes.Watercooler. Slack is a social hub for co-workers. This is very important, and full of gifs.Meta-coordination. Slack is the best place for meta-levels of strategy and coordination that don’t have specific productivity apps. This is really a type of ‘else statement’, but one that could persist for a while in unstructured format.

      Kwok identifies three functions that Slack serves:

      1. It is an exception handler for everything that has no place in the other tools used.
      2. It is a social hub for workers.
      3. It is the best place for (inherently unstructured) meta-discussions on a variety of topics.
    5. It’s not that Slack is too distracting and killing individual productivity. It’s that your company’s processes are so dysfunctional you need Slack to be distracting and killing individual productivity.

      Kwok points out that Slack's reputation for being a productivity killer doesn't get at the root of the issue. He argues that resorting to Slack is a symptom of the underlying cause: dysfunctional business processes.

    6. The dream of Slack is that they become the central nervous system for all of a company’s employees and apps. This is the view of a clean *separation* of productivity and collaboration. Have all your apps for productivity and then have a single app for coordinating everyone, with your apps also feeding notifications into this system. In this way, Slack would become a star. With every app revolving around it. Employees would work out of Slack, periodically moving to whichever app they were needed in, before returning to Slack. But productivity *isn’t* separate from collaboration. They are the two parts of the same loop of producing work. And if anything collaboration is in *service* of team productivity.

      The vision of Slack, according to Kwok, was for people to have their productivity in designated apps, and have one central nervous system (Slack) through which they could collaborate. This was based on the assumption that producing and collaborating could be separated.

      Kwok claims that this assumption is wrong. Collaboration and productivity are intertwined, and you might event say that collaboration serves productivity.

    7. As the ecosystem of specialized SaaS apps and workflows continues to mature, messaging becomes a place of last resort. When things are running smoothly, work happens in the apps built to produce them. And collaboration happens within them. Going to slack is increasingly a channel of last resort, for when there’s no established workflow of what to do. And as these functional apps evolve, there are fewer and fewer exceptions that need Slack. In fact, a sign of a maturing company is one that progressively removes the need to use Slack for more and more situations.

      Slack is a medium of last resort. When things go well, and if the app that is used is well designed and mature, collaboration will happen inside it. The need for messaging in Slack is more a sign of an immature process or company.

  2. Apr 2020
  3. Feb 2020
    1. If something is important but not urgent - like complimenting or encouraging the entire team - use email or post in the channel without @-mentioning the team.
    2. Avoid Private Messages When using Slack for work-related purposes, please avoid private messages.
  4. Dec 2019
    1. where we were communicating less formally with each other and with the doctor. The best thing about slack is that we are allowed to create different channels for specific topics like ‘Soliya’ and others like ‘Random’ where we were allowed to send random messages about random subjects or thing that you want to share with the group that isn’t related to anything we’re doing in the course. In addition, it also allowed us to send private messages to the doctor where she answered in a very short time and also to others with us in class

      Slack bridges the communication gap between the Ss and the professor outside the classroom unlike the limitations of emailing and its formality giving unlimited chances of discussing any matter

  5. May 2019
  6. Nov 2018
    1. Copy of same article - with author and date info

    2. Use of Slack in a FACE-TO-FACE class and how much it increased interaction; brings up a point that concerns me and that's what happens when the instructor/TA appear to be available 24/7 given the nature of Slack; good exploration of motivating students to use it (4/5)

    1. How to use the many integrations available in Slack (this is just a primer on how to install integrations with a few samples - see other article for actual possibilities) (1/5)

  7. feedlylab.slack.com feedlylab.slack.com
    1. The Loom integration for Slack; this brings video into Slack and enhances collaboration; I'm bookmarking this because it would definitely be something I would bring up in a paper on Slack (4/5)

    1. One teacher's experience using slack, referencing what things were like before using it and after; contains many ideas on how about how to maximize Slack (3/5)

    1. Starts with a small amount of history and its use; this article actually discusses an experimental seminar done to test the usefulness of Slack in education. (4/5)

      NOTE: MOOC is a Massive Online Open Course)

    1. One instructor's use of Slack, comparing and contrasting other LMS (but he used Canvas); good basic breakdown of the conversational tools and samples of how hey can be used; This is a great primer of Slack's use in the classroom (5/5)

    1. Training video on Slack; marked this site so I have an example of tool training that is available for new users of Slack; could be worth briefly referencing (2/5)

    1. Facebook Workplace is a direct competitor to Slack; this is a thoughtful exploration of experiences using both; if I decide to include any mention of Facebook, this would be a good springboard to more research (3/5)

      Note: in this scenario both are discussed as business tools not in education but other articles I've found show clear parallels

  8. Dec 2017
  9. May 2017
    1. Specific channels

      Here’s where the Slack team suggest feat- as a prefix convention for temporary feature channels.

  10. Feb 2017
    1. Imagine searching for “401k matching” and instead of just receiving relevant messages or files, you also get a list of people in HR that can answer your question, or a list of channels for your query where you might be able to find the information you are looking for, or even a list of commonly asked questions relevant to that topic with links to the channel where each one was answered.

      This would be good.

    2. Relevant search relaxes the age constraint and takes into account the Lucene score of the document — how well it matches the query terms (Solr powers search at Slack).


    3. Recent search finds the messages that match all terms, and presents them in reverse chronological order.


    4. On average, 20% of a knowledge worker’s day is spent looking for the information they need to get their work done.


  11. Nov 2016
  12. Apr 2016
  13. Feb 2016
    1. Slack is communication software popular for handling workplace information flow, project management, customer support, and all kinds of other things.
  14. Mar 2015
    1. To find the right integration, I scoured the internet and tested a few different solutions. Some where just OVERLY complex, some just didnt work, and some were just right (Codename Goldilocks). The one that I found worked perfectly for me was ‘slack-irc-plugin‘, by Jimmy Hillis.