Does anyone know the developer's logic behind limiting the platform to the small number of users who do not require hierarchies/subfolders?

We were hoping to onboard our entire organisation and were happy to pay for all the maker seats, but there are quite a few things we are not understanding.

One such example is subfolders. It would appear that Coda’s navigation problem has long been a source of preventing new paying users, but having digested all the posts throughout the years, it would appear there are still no solutions.

Confusingly, the platform currently has a feature called the ‘quick nav’ bar. This allows users to access their folders from any page in order to quickly navigate to where they need to get to next, which, of course, is a standard feature for similar tools and makes sense why it’s therefore called the ‘quick nav’ bar.

What I and every employee I’ve run this past are struggling to understand is the logic behind restricting the platform to the small number of businesses that are small enough to only require a tiny handful of folders. I say this as Coda appears to bizarrely not offer subfolders, and so with only a flat list of folders, users would be expected to scroll through that entire list, reading the name of each folder until they find the desired one. That might be fine for tiny businesses with less than 10 folders, but it’s seemingly impossible for anyone else.

To put that into perspective, it only takes just 3 hierarchical levels with 10 folders in each to reach 1000 folders. With subfolders, a user only needs to read a maximum of 10 folder names per subfolder level to find what they are looking for, so just 30 names, instead of all 1000 without subfolders! In terms of time, assuming as little as just 2 seconds to read each folder name would be the difference between 60 seconds with subfolders vs 32 minutes (2000 seconds) without subfolders. Do that, say 10 times each day, and you’re looking at 10 minutes total time with subfolders vs approaching 6 hours each day without subfolders! Wasting 6 hours just to find a folder on 10 different occasions is madness. And that’s just one of the many reasons why subfolders are simply mandatory for almost all but a small handful of users!

No solutions:

  1. The ‘shortcut folders’ functionality doesn’t negate the issue.

  2. The folder search box is only useful if one remembers the folder’s name and if the search box is available, which it doesn’t appear to be in places like the move folder feature.

  3. Maintaining an org map Doc doesn’t resolve the issue as it would not be quickly accessible via the sidebar/quick navbar.

  4. In one post, a Coda employee suggested the use of a ‘list pack’, but we have not been able to ascertain what that is exactly and how that would be accessible from the ‘quick nav’ bar?

Considering the concept of subpages has already been implemented, there must be a reason why the designers of Coda think that businesses wouldn’t require subfolders. What if a business has more than a few departments or business processes and then a handful of hierarchical levels within each of those departments or business processes?

I even got into the habit of showing the platform to as many people as possible just to watch the utter shock and bewilderment on their faces when I drop the bombshell that everything has to be managed without subfolders - it’s hilarious. None of this seems to make any sense to anyone here!

We are so confused. The fact that even the developers have stated that the subfolders/nesting folders functionality has been requested so much (even spanning back through so many many years) but they have never done anything about it, suggests it’s almost as if Coda is only being targeted at the small handful of small businesses without hierarchies and therefore allowing them to be able to manage using the platform without subfolders. I believe Coda has just over 10 thousand users vs Notions’ 100 million. Surely, it would be more sensible of Coda to do everything it can to attract more users, not limit them to such an extent.

I’ve run this past several of our engineers, and they have all unanimously pleaded that the implementation of subfolders would be an “easy job” and that it’s crazy not to provide them from day dot. I guess the questions still remain: What is it about subfolders that the developers are potentially so against? Is Coda more aimed at small organisations that only ever have a tiny handful of departments or business processes, and so a flat, hiraracy-less structure is manageable for them?

This all seems so out of the ordinary that we’d love to hear how companies are expected to use the platform with this limitation, as there is definitely a possibility we are missing something completely obvious here.

Even better, if anyone knows why users are being forced into this restriction, that would also be super interesting.

Huge thanks to anyone who has any ideas!

(If any Coda employees are reading this, please feel free to reach out via DM or request my email - cheers!)

Hi @Ersatz_Feign,

You might be interested in this discussion.

You can build and pin a Master Doc for everyone that achieves a much more streamlined and tailored way of finding what you want than navigation through folder structures in the side-bar. The only limit is your creativity.

Hope this helps,

Pablo

I believe this is the 3rd post from, what seems to be, the same organisation on this topic.

The fact that they want to create so many different documents, makes me think that they have a fundamental misunderstanding on how Coda works.

I have asked them elsewhere that they share more about their requirements, or at least reach out to Coda for a Demo.

Seems like they would rather keep complaining, not realising Coda is not Word or Excel. Instead of complaining that doc organisation does not work the way that they want it to work, they should spend that time on learning how Coda actually works.

3 Likes

As a brand new Coda user who is coming from the world of Airtable, where even lower tier PAID accounts have almost no functionality compared to Coda…I can say that not being able to multi nest folders is a problem that never even occurred to me a being a problem.

3 Likes

@Shannon_Bradley

I work as an SAP consultant, and we typically generate hundreds of spreadsheets as part of an implementation, spread across multiple streams (E.g. Finance, Sales, Production etc.)

With Coda I combine dozens of Spreadsheets into a single doc. And they are connected to each other - in the past they were little standalone pieces of information that had to be manually maintained across spreadsheets where info are re-used.

2 Likes

Hopefully, this will aid your understanding somewhat.

2 Likes

Curious to know how you are combining all spreadsheet in one doc? I am trying to see if there is other way better than what I am doing currently. The current requirement, is that whatever happen to 1 document will affect the original one so I am using the link view which is working fine but just wondering if there is other way neater than this. :slight_smile: Thank you.

1 Like

Hi @Macey_Cherry

It depends what you do with the spreadsheets. They can be simple lists, which would translate to simple tables. Our the tables can be connected via relationships.

This is what I use most, presenting the same information using different views. But I also use relationships to cross-reference. A lot.

Sounds like you are well on your way!

2 Likes