Thoughts on the new 'workspace' feature? Does it solve project sprawl?

Used the workspace feature in the trial. It's more than a folder. You can group collections and share them as a set, which was useful for my vendor comparison project.

But it doesn't solve duplicates. If the same paper is in two collections inside a workspace, it's still listed twice. You still need tags for that.

Your last question about workflow is key. It saves time if you have to regularly present or share a group of collections together. If you don't, it's just overhead. Did they mention if this is a paid feature only? I can't find clear pricing on it.

Thanks, that's really helpful insight about the duplicates issue. I was hoping workspaces would handle that automatically, so it's good to know tags are still necessary.

The point about it saving time for regular sharing is interesting. I often need to present grouped research to different stakeholders. If it streamlines that, it might be worth the setup. But like you said, if you don't do that often, it's just another layer to manage.

I'm also trying to find clear pricing details with no luck. The trial seems open, but I'm nervous about moving our team's collections into a feature that might suddenly require a paid tier. Have you seen any announcements about a timeline for that?

That's a good point about the duplicates issue being separate from grouping. I've seen that catch a few people out already. The sharing aspect you mentioned is where I think the real value is, especially for teams who need to keep stakeholders updated without sending multiple links.

I haven't seen a clear pricing announcement either, which is a bit frustrating for planning. Usually the trial features roll into the basic paid tiers, but it's tough to advise people without that info.

You've hit on the core tension with any new organizational layer. Your example with overlapping papers in Competitive Intelligence and CRM Integration is exactly the scenario where a workspace should shine, but it has a specific function.

It groups collections meaningfully for sharing and presentation, acting as a single access point for a project's entire research library. However, for your question on duplicate references, it does not provide a consolidated view. The workspace shows you the linked collections, but each collection still operates independently. So a paper appearing in both will still be listed twice when you view the workspace contents. You'll need a separate tagging taxonomy, as others noted, for true deduplication.

From a workflow perspective, the time saved is almost entirely in recurring external communication. If you frequently need to present that grouped research to your sales team or leadership, having one workspace link is a tangible efficiency. If your process is more about internal analysis and synthesis, the benefit diminishes significantly and might even add overhead.

Hey Evan, your caution about tools that promise organization but don't deliver is super valid. Been there too.

You asked if workspaces just add another layer. For your specific case with those sales ops collections, it can save time, but in a specific way. If you're regularly pulling together the Competitive Intelligence and CRM Integration collections for a stakeholder review, having them in a workspace lets you share one link and present them as a unified project library. That's the meaningful grouping.

But, and this is a big caveat, it doesn't tackle the underlying data clutter. Your overlapping paper is still a duplicate in two separate collections, so for actual day-to-day research work inside the tool, you're right that disciplined tagging is still the only way to get a clean, consolidated view.

The workflow payoff really depends on how often you need to export or present that grouped context versus how often you're digging through the raw references.

Yeah, the sharing benefit is real for stakeholder updates. In my last role, consolidating cost reports from separate accounts into a single view for finance was a game-changer - one link instead of a dozen.

But on your point about unclear pricing, that's the real blocker. It reminds me of cloud providers rolling out new management consoles; they're free until they're suddenly not. You can't build a process around a feature that might get paywalled. Has anyone tried asking support directly? Sometimes they have more concrete rollout timelines than the public announcements.

Your caution is justified. Having run similar benchmarks for organizational tools, I'd frame the value entirely around the specific workflow you described: sharing grouped collections for stakeholder reviews. The time saved is quantifiable if you regularly compile and present those three collections together. You'd shift from sending three separate links and manually navigating between them to a single, persistent workspace link.

However, its function is strictly presentational. It doesn't address the underlying data model, so your duplicate reference problem remains unsolved. The workspace provides a unified *access point*, not a unified *data view*. For clean data, you still need a rigorous tagging taxonomy, as you mentioned.

The biggest unknown variable right now isn't functionality, but cost. Until they release a clear pricing structure, building a critical workflow on it is a risk. It's similar to benchmarking a new cloud instance type without committed-use discounts; the performance might be great, but the total cost is undefined.

Exactly. It's a presentation layer, not a data management layer. You're spot on that the value hinges entirely on quantifying the "regularly pulling together" part.

If you're doing that stakeholder review weekly, the time saved on link management and context switching might justify it. If it's quarterly, the overhead of maintaining another layer probably isn't worth it. You need to run the numbers on your actual meeting cadence.

The core problem remains: you're paying an organizational tax by managing tags for deduplication *and* workspaces for presentation. That's two systems for one set of data. Always makes me wonder when the true cost of a "free" feature is the time spent maintaining it.

Your caution about clean data is the key piece. I've set up similar workspaces for product launch research, and it forces a choice.

You can have a neat presentation layer for stakeholders, or a truly de-duplicated source of truth, but not both with this feature. It's great for that specific "stakeholder review" use case people mentioned, but if your main pain point is that messy overlap of papers between collections during actual research work, then no, it doesn't solve project sprawl. It just puts a nice cover on it.

That underlying tension, managing tags for data *and* workspaces for presentation, might actually add more overhead if your goal is cleaning up the sprawl itself.

You nailed the core distinction about it being more than a folder. The grouping for sharing is the actual feature; everything else is just window dressing.

That duplicate issue is a perfect example of where the marketing meets reality. They're selling it as a solution for project sprawl, but it's really just a convenient packaging tool. If your sprawl is about having too many separate links to send, it helps. If your sprawl is about messy, overlapping data inside those collections, it does absolutely nothing.

The pricing opacity is classic. Building team processes on a feature in permanent trial limbo feels like building on sand. I wouldn't commit anything mission-critical until they declare it a permanent part of a tier.

Your caution about clean data is the key piece. I've set up similar workspaces for product launch research, and it forces a choice.

You can have a neat presentation layer for stakeholders, or a truly de-duplicated source of truth, but not both with this feature. It's great for that specific "stakeholder review" use case people mentioned, but if your main pain point is that messy overlap of papers between collections during actual research work, then no, it doesn't solve project sprawl. It just puts a nice cover on it.

That underlying tension, managing tags for data *and* workspaces for presentation, might actually add more overhead if your goal is cleaning up the sprawl itself.

Thanks for laying out your questions so clearly, Evan. Your point about getting burned by tools that add complexity without solving the real clutter problem really resonates.

I think you're right to be skeptical. From what you've described, it sounds like your main issue is that messy overlap of papers between your collections, and everyone here seems to agree the workspace doesn't fix that. It just groups them for sharing.

But I'm curious about something no one's mentioned yet - what happens if you *do* try to use tags more rigorously alongside the workspace? Is it realistic to manage both, or does it just create two places to check for updates? Feels like it could double the maintenance work.

You're asking the right question about doubling maintenance work. Based on my experience with knowledge bases, managing both tags and workspaces can create a significant coordination overhead. The workspace becomes the "public facing" structure you share, while your tags are the "back-end" system for your own organization.

What often happens is you find yourself checking two places for completeness. For instance, if you add a paper to your Competitive Intelligence collection, you'll tag it appropriately, but you'll also need to verify it's correctly represented in the relevant workspace view you've set up for stakeholders. This isn't automatic; it's a manual mental check, which defeats the time-saving promise.

The justification truly depends on how rigid your stakeholder presentations are. If the format is identical each time, the workspace is a set-and-forget package. If you're constantly tailoring what you show, you're essentially maintaining two dynamic systems for one body of work. In that case, you'd probably be better off investing all that time into a bulletproof, hierarchical tagging system and just sharing filtered views.

The "set-and-forget package" scenario you describe feels like a fantasy. When was the last time stakeholder needs remained static for more than a quarter? The moment you need to add a new collection or exclude a few sensitive items for a specific audience, the workspace setup is brittle.

You're right about the coordination overhead, but it's worse than that. This dual-layer system introduces a new failure mode: the workspace view drifts from the tagged reality, and you don't notice until you're in the presentation. Now your "unified access point" is showing stale or misaligned data. It's not just double maintenance, it's double risk.