How do small teams manage documents, wikis for projects/features?
At the company that I worked with, people use Google Doc, Gitlab issues, Gitlab wiki, some tools that host UI designs. It's all over the place for product features, project updates, 1-on-1 meeting updates, etc. My friends' teams heavily use Confluence and Google Doc.
I'm wondering what small/medium businesses use to manage documents and knowledge across different platforms? Do they work well for people? Let me know your thoughts.
Thanks.
Trending on Indie Hackers
After reading all the below comments, I see that many people use one or two tools in combination. That's because their purpose of use or their working environment.
You don't feel like creating a reports on notions. At the same time to save a small piece of contents , Google don't isn't a right tool.
Few type of contents like design prototype needs it's own specialized tools.
It's very difficult for companies to come up with a single tool that do everything. It's also very difficult to position such product in marketplace
So forever, people keep using multiple tools in combination
My advice is create a tool that is great for one purpose or environment. Their are already enough general purpose software in the market.
You really hit the spot. I agree that each tool is well built for a specific team or environment in mind. I don't actually want to create another tool since there're too many tools already. I'm just wondering if there's some tool that can help my team manage/organize all documents/contents scattering across different platforms.
If billing / money spent on different platform is a problem then it's very difficult to solve.
If it's a just a problem of organization, then I would suggest you to maintain a Team Page or Project Page.
This page will have a reference link to different document / contents on multiple platforms.
You can even use the API of these platform to show the preview of the contents for more better usability.
You can create a folder structure like UI for better visual perception.
I would call it as Team Dashboard if I have to sum up my thoughts.
I'm using Jira and used that also in my previous startup with a small team of devs. You need to groom your backlog constantly though. Standard agile practices. Then it works out.
Yeah if it's for a team of devs, Jira works pretty well. For me, I have to work with a design team who uses some tool similar to envision, a marketing team who love using google docs. The trick is including those links to Jira tickets manually and keeping them up to date.
We use mostly a combination of Notion and Google Docs. Hope you are having a great weekend!
Hi,
I'm in the process of launching a product for the exact same market.
Here is the link: https://knowhup.com
It's for small teams, especially development teams.
Please check it out and let me know what you think, and sign up for the MVP if you're interested.
That looks nice. I like the demo of Markdown. Currently, we can do the same thing with Gitlab wiki so I would love to see more. Anw, signed up (There's no feedback when I click SignUp button btw ...)
Hi @tonyasking, thanks for signing up!
Glad you liked the demo of the Markdown. Since this is the MVP, we're launching with only the basic functionality, but lots of things are in the pipeline. Will publish a roadmap to the website soon.
I'm also open to suggestions if you have any particular feature in mind.
Thanks for reporting the lack of feedback on the signup button - will fix it right away!
I personally use Notion.so and Ms OneNote in combination.
I use Notion for my personal stuff and I love it a lot. However, for work purposes, I feel some kind of documents can not be moved there. Ex: Gitlab issues, UI/UX design hosting, ... Other than that, I think it's a great tool if I can ask the whole to onboard and collaborate there.
We've been using Notion for a team of 8+ with great success. Use the kanban feature for Sprint tracking and product roadmaps/assignments.
Basically, we ping-ping between Slack and Notion and there is a lot of UI/UX design work to track. Invision links and Loom videos are our go to for posting designs and giving feedback.
I have a central Quip doc that I link everything to: github, facebook posts, google analytics pages, domain names. The reason why I do this is b/c I will forget everything the instant I close the tab and I might need to revisit it.
Quip looks interesting (quite expensive though). Btw, I'm actually doing a similar thing: using Workona browser extension to manage all the links per project/feature. It's still kind of annoying that sometimes my teammates need my help to find some specific documents. Do you share your bookmark collections with others? Is there any collaboration there?
Hmm, I guess I should give some context. Let's say I have a product design doc, eng design doc, marketing doc, and roadmap/execution/time table doc. All of these docs have links in them as well so to share I just have to share the doc with collaborators. Also Dropbox paper is free i think and it's the exact same thing as quip