# Lack of Work Management features in Fibery (Reminders, Dependencies, Notifications, My Work, etc.)

**URL:** <https://community.fibery.io/t/lack-of-work-management-features-in-fibery-reminders-dependencies-notifications-my-work-etc/3319>\
**Category:** Ideas & Features\
**Created:** [June 10, 2022, 4:03pm UTC](https://community.fibery.io/t/lack-of-work-management-features-in-fibery-reminders-dependencies-notifications-my-work-etc/3319 "2022-06-10T16:03:12Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [September 30, 2022, 6:30pm UTC](https://community.fibery.io/t/lack-of-work-management-features-in-fibery-reminders-dependencies-notifications-my-work-etc/3319/31 "2022-09-30T18:30:57Z")

</div>

> [@mdubakov](#):
>
> Usually a successful product does at least one thing exceptionally well. Let’s take some Fibery competitors:

Yes, this seems likely correct to me as well. Small wonder that I agree with a successful startup founder. 😄 Then again isn’t the fact that _Fibery does not do one thing exceptionally well_ actually both a positioning _and_ product problem? 🤔

> [@mdubakov](#):
>
> So no, I don’t think any feature or even area done right will **significantly** increase Fibery growth. It’s a gradual process of polishing, implementing top requests from our target customers, improving getting started, etc.

Interesting. I’m not sure the rest of your post necessarily supports this though. Your approach is basically to try to do most things that “product companies” (where is this vague term actually defined? 🤔) need to do, and do most of them “well enough” that the collective result is “exceptional” in its own way, right? That seems like an extremely difficult and vague problem to solve in a way that is compelling enough _in an obvious way_ to companies using existing solutions such that they switch.

My perspective is that a narrower focus or “wedge” may be a better or even necessary way to approach this. “Product companies” is not really a good wedge IMO. Oh dear, I am starting to depart from agreeing with successful product founder and I feel (genuine!) trepidation that I might look a fool. But so be it. 😅

> [@Eren\_Turgut](#):
>
> However, I do believe that once Fibery is mature **and** polished

How do you evaluate when this has happened? How do you get there without better growth? How long can a company go with MRR \< Burn Rate?

> [@wmaehr\_pr](#):
>
> I don’t think Notion’s success started with the blocks but before that. It was (alongside Slite) the only really simple, elegant collaborative wiki. The databases came later, yes. But it was just simple enough to allow us and others to switch from Confluence, Sharepoint and Google Docs. That’s what it replaced for us and our clients.

Yes, exactly. It made it really easy (and aesthetic+fun) to do something that many companies need.

> [@bonder](#):
>
> - Interview the customers with large, happy teams using the tool. Part talking heads, but a lot of “here’s what we do and how we do it” inside of Fibery (probably a good amount of blurring of confidential info, but well worth it to see that business is being managed inside Fibery.

They do this already quite a bit. They have a whole category on their website for it. 😁

> **[Customer stories](https://fibery.io/customer-stories)**
>
> See how product companies use Fibery to build roadmaps, manage software development, gather customer feedback, and more.

Thing about such cases/stories is they focus on the “won” cases, not the _lost_ cases, which are almost certainly far more important. It’s IMO less important to know why someone chose you than why someone _did not_.

> [@bonder](#):
>
> - Build great “first run” experiences for each of these successful uses cases so that new teams doing similar businesses can get up and running in just a handful of clicks. Example: inventory management, asset tracking, content management calendar, etc.

Don’t they already have this with Templates though? Maybe needs a bit more work, but basically there. And they are even part of new workspace creation/onboarding. It ties in to a further idea/suggestion I have about onboarding though:

> [@Sales-driving features, low-hanging fruit](https://community.fibery.io/t/sales-driving-features-low-hanging-fruit/3341/1):
>
> - Make import an optional part of workspace creation (i.e. make it more discoverable)

This should basically just be part of the onboarding flow alongside template selection (the prompt about what kind of business/user you are), e.g. “Do you have existing data to import? Try one of our awesome integrations (clickable list) or import your CSV here → [button]”.

> [@bonder](#):
>
> - Focus on integrations more. I am not sure there is enough of a spotlight on this (I could be wrong).

I do agree with this and I actually think it’s already a Fibery superpower that is not talked about or demonstrated enough. Few other tools have integrations with anywhere near the comprehensiveness and power of Fibery which can essentially replicate the data model of many other apps.

Anyway, it is hard not to be an armchair product manager. It’s kind of fun. 😄 But really there are no easy answers. As soon as you start to dig in to any obvious product niche or potential wedge, you generally find lots of products dedicated to that thing, and some doing it probably quite well, while the many others in the space fail to gain much traction, and Fibery might well just end up as one of the “also-rans” there too… But maybe, just maybe there is some clever wedge not yet realized… 🤔

---

_[View the full topic](https://community.fibery.io/t/lack-of-work-management-features-in-fibery-reminders-dependencies-notifications-my-work-etc/3319)._
