1
9 Comments

How do you organize links shared on Slack?

Small intro then subject of post in 2nd section below :)


INTRO

Hey Indie Hackers :) I just joined the IH community last week, looking forward to chatting and learning from all of you! Already spent many hours looking through the products page at all the cool stuff you're building, like I'm sure many of you have done also lol. About me : background in mech eng, worked at Apple doing product design for 4 years before coming to Paris 2 years ago, now I'm at a startup studio / innovation consultancy doing more digital service stuff.


PROJECT IDEA

So it's lockdown here in Paris, and I've been itching to do a small project that I can get off the ground quickly to get started (first time doing a muse-type project!).

One thing I’ve been pretty annoyed lately with link management in Slack - lots of links getting shared all over the place, no easy way to find them again and no retrievable record at all of why they were shared in the first place (key learnings, cliff notes, TLDR, etc). The result : links that are shared without much context, read by a few people, and more or less forgotten...ugh.

So I'm thinking about doing something to make this better.

Do you share this frustration with dealing with links in Slack? Have you or your team come up with a way to deal with this? Leave a comment and let me know what it is and how it's working for you!

Also : a quick little survey to help get a better sense of where you would want your team's links stored! (if something's not listed, just put it in the comments haha, I'm really just guessing here)


More updates coming soon! (I'd like to start a weekly posting cadence and try to do the build in public thing, which I find awesome)

Where would you want a library of your team's Slack links stored?
  1. Google Suite (google docs, sheets, etc)
  2. Notion
  3. Evernote
  4. Onenote
  5. Slite
  6. Clickup
  7. Coda
  8. Airtable
  9. Dropbox
  10. Trello
Vote
  1. 1

    Teams that I'm on usually have a central Wiki linking to relevant documents. The Wiki will point to onboarding GDocs (which have information relevant to people joining the team: people, roles, slack channels, etc), list team members, point to relevant engineering resources, etc. Any link that is relevant enough from Slack would just end up here.

    For more short-term things (like tirekick docs, where everyone will use them temporarily and then never again), we just pin links so that they're easy to find.

    Anything that's transiently useful usually gets written into a Google Doc and shared into a team-wide folder.

    1. 1

      yep agreed that the onboarding, organization stuff, HR, internal tools, how we work, methodologies, etc usually is saved in a wiki section and is relatively static, treated like reference area. we use notion for this.

      for the short-term stuff, pinning is a good idea, but do you pin and then unpin or do you just end up with a bunch of pins?

      i think the transiently useful stuff you're talking about is maybe more similar to how we share links - what do you usually write down in the Google Doc? do you use a template or structure? new doc for each link? For us, we share links of all sorts of stuff, articles, new products, blog posts, youtube videos, etc...at best the poster writes a little blurb about what it is, at worst they just post it with something stupid like "check this out!"...

      1. 1

        We pin and unpin. Anytime I pin anything, I go through and unpin stale things.

        For the transitive stuff, it's mostly point-in-time stuff like design docs, meeting notes, etc. The kinds of links you have there (articles, blogs, etc) don't have a place. To be honest, I don't usually miss it when I forget about it. Occasionally I dig stuff up with the from:@user has:link in:#channel search, but oftentimes I don't miss this kinda stuff.

  2. 1

    I designed https://lunarpin.com to improve organizing of important messages so you can come back to them later. What do you think?

    1. 1

      This looks cool for saving messages more generally - i like the part about easily getting back to the exact part of the conversation! Seems to be designed more for the indiv user to save things interesting to him/her, whereas I was thinking of a tool to create a link library of sorts for the whole team, where any team member can go there and easily see key takeaways, TLDR for any link and then visit the link if they want to read the whole thing.

      Curious to know what kind of demand you’ve been seeing, and which acquisition channels have been most successful so far? How many people do you have signed up for the beta? (and how long has it been open for?) What size teams have you been mostly getting interest from?

      In exchange, some hopefully constructive feedback on your product/landing page :)

      • as a user, I find myself wanting to know more about the user experience on the slack side, the dashboard screen is cool for seeing how the stuff is organized afterwards, but how do I save it from slack? (A visual of the « shortcut menu » would help)
      • any way to add notes to a pin? beyond the tags (which are primarily for sorting), to jog my memory about what this convo was about?
      • any way to associate or group multiple pinned messages? (imagine the case where a convo is started on monday, then Thursday it’s restarted but in between there’s a bunch of other stuff that’s not relevant, if only the Monday convo pinned hard to find the Thursday part of it, and if they’re pinned separately hard to know that they’re actually part of the same convo)
      • why does it work section : the way it is laid out makes it seem text heavy (3 big blocks of text next to each other). Maybe some bolded or highlighted text to quickly get the point of each block.
      • simplicity block : u have 2 out of 3 that don’t fit under simplicity : security and integration. For integration, would be helpful to give concrete examples of what could be possible with webhooks to help users visualize the possibilities.
      1. 1

        Thanks for all the thoughtful feedback! I am still trying to nail down my acquisition channels, but thus far have not been able to generate much interest. Trying to figure out ways to break into the space and get an audience. Do you have any recommendations?

        1. 1

          What have you tried already as far as driving traffic to your landing?

          1. 1

            Reddit, IH (community builders, slack), and friends that use Slack. I am a bit at a loss for other channels. At least for beta testers.

            1. 1

              its a good start, this article has a few more channels you could try out : https://www.chanty.com/blog/got-100-free-beta-testers-without-product-landing-page-ready-yet/

              there are also some slack channels/communities you could look into, could be even better given those are people who clearly use slack

Trending on Indie Hackers
After 10M+ Views, 13k+ Upvotes: The Reddit Strategy That Worked for Me! 40 comments Getting first 908 Paid Signups by Spending $353 ONLY. 21 comments 🔥Roast my one-man design agency website 18 comments Launch on Product Hunt after 5 months of work! 16 comments Started as a Goodreads alternative, now it's taking a life of its own 12 comments Join our AI video tool demo, get a cool video back! 11 comments