A little late with my feedback, but here I go. Documents improvements had the most value for me so I’ll focus on that.
(Nested) Documents feedback
- Not yet paid customer (on Trial)
- 2-3 small team inside a SME company (~1000) trying to find a suitable TKM tool that can scale to more teams if it works out well and to incrementally adopt wider
- Use cases: team and system/domain wikis, product management, project management, task management, process management, external vendor collaboration, inter-departmental communication and collaboration, intranet, as a tool for misc domain-specific stuff
I’m quite happy with this development on Documents
Let me break down what was good for me. Then I’ve put my improvement requests below that.
Finally an easy way to build out “team pages” and wiki pages
I struggled to find a good way to structure knowledge team hubs with nested docs and wikis in Fibery, that would scale for dozens of Teams and many more knowledge domains: any solution I came up with felt overly complicated.
These Documents improvements seem to mostly resolve my main issues. It doesn’t resolve some major concerns of mine relating to Search and Document sharing/collaboration, but I didn’t expect that (see improvement feedback below for details).
For sure, in their current form Documents as curated knowledge/wiki are rather simple:
- I lose out on advanced features like gardening and categorizing documents
- Automation and workflows are naturally limited
But the tradeoff for increased simplicity and flexibility seems worth it for most of my use cases.
What I especially like about these last 2 releases related to the Documents story:
- I find Documents (e.g. for wiki) are now easy to create in most contexts
- Document contributions now works fine for the Editor role (before we had to structure Documents using Folders, but folder creation requires the Creator role in Space, and that is a role I wish to minimize to a few Space owners where possible) - now we can nest Docs, this works fine for Editor
- Less maintenance since the Nested document approach also resolve a basic navigation story in the left menu, without additional work
- At least if Document entry is a top-level in a Space, but that works well for most of my use cases
- Now I don’t have to build special index/navigation Documents like User guide (although they come out very nice if one takes the effort to do so)
- Or using awkward workarounds like Table, Board or Tree Views…
Simple yet powerful. I dig it
Makes it easier for my non-linear and unstructured work and knowledge
My team and surrounding teams often work on new initiatives, and we’ve found it typically a bit hard to “place the work” at the early stages. Sometimes it’s just a draft and fizzles out. Sometimes, it’s converted into one or multiple piece of work, often through some early collaboration. And for myself, at least half of the time my work starts with an unstructured draft or loose idea.
While I’m not the most structured person, my teammates are perhaps less so, and that’s been a concern to me with Fibery. Often when working for myself, I felt I had no location to add some draft work except in My Space, and it quickly became cluttered.
For myself, Documents fulfills so many use cases at once in Fibery:
- Document is a reference/managed knowledge
- Document is a draft for potentially future structured work
- Document is sometimes just an ephemeral stash
- Document is a communication tool
- Document is an internal collaboration tool (not yet, blocker for us, but I left a feature request below)
- Document is an external collaboration tool (not yet for us)
I still feel Fibery is lacking some important features for us to work for multiple teams, but I feel a slight shift here in the “right direction” for our use cases, thanks to these more powerful Document primitives, that makes it more straightforward to build and maintain Spaces for Teams and for knowledge domains across many Systems.
Infinitely nested docs that can be easily moved between a private space and other domain Spaces is a powerful mechanism; and I’m glad Fibery finally got that.
Or maybe - based on your awesomely honest communication - this was a happy side effect since Fibery wanted to better support Notion and Confluence import? In any case I feel Fibery looks better for our use cases now!
About converting Document to structured work
I see it’s not yet released but that you already are working on enabling this use case:
- I can start with unstructured work in a Document
- Then I can convert document it into structured work (=an entity)
Combined with the super practical two-panel navigation, this workflow seems to promise a very nice workflow that would fit me just right. Looking forward to testing it!
I’ve also put some improvements I’d love related to Documents below.