tablet

For us it was an honest version of our website https://fibery.io/anxiety We never replicated this success with other things.

> I dislike using Jira as much as anyone, mainly because it's so excruciatingly slow.

But there is no competing product (suite) that offers comparable functionality and provides the same long-term flexibilty.

This is maybe true, but the future belongs to more flexible software. Eventually Notion [1] or Fibery [2] will replace Jira. They may do it now for smaller team already (10-500 ppl), it just takes time to enter large companies.

[1] https://notion.so [2] https://fibery.io

This. And "Database for Glossary" makes me smile. A single page would be enough.

I always believe in focus. I spent 14 years on my first product, then 5 years on a second (still working on it). Why not take one and iterate?

The short Storyspace review: https://mprove.de/visionreality/text/2.1.11_storyspace.html

BTW, here is the good overview of KMS: A Distributed Hypermedia System for Managing Knowledge In Organizations [1]

[1] http://csis.pace.edu/~marchese/CS835/Readings/kms.pdf

Take a look at https://fibery.io, it addresses several problems you listed:

* Rigid and difficult to experiment

* Difficult to scale with a company

* Difficult to couple OKRs (objective and key results) with tasks

TRIZ is extremely hard to apply beyond engineering areas. I tried to bend it to soft.dev with no luck.

I'd say agile is more about "shortening feedback loops" everywhere.

There is an article that explores the same problem "Post-agile process agnosticism" [1]

The main idea is that (as a programmer):

"You don’t give a fuck about process name, until you have full rights to modify and change the process."

[1] https://medium.com/fibery/post-agile-process-agnosticism-d4a...

Thank you :) You can check my articles in English here https://fibery.io/blog/

Overall it's about finding new generalizations and collapse your extensive complexity by new abstraction.

For example, you build a Todo-list software (everybody does). You have requests from customers "I want to be notified 3 days before due date", "I want to be notified 1 day before due date" and "I don't need notifications".

OK, so you are adding a new setting "[ON/OFF] Notify me [X] days before due date".

Then you get feedback "I want to be notified when someone unassigned me" and "I want to be notified when someone assigns me".

OK. You're adding new setting "[ON/OF] Notify me about changes of my assignments"

Then you receive feedback like "I want to be notified about important tasks assigned to me only".

You say "Fuck it" and implement a notification engine where every user can set up own notification rules.

X notifications settings were collapsed into a new more abstract (but more complex) solution. You have to choose abstractions carefully and be aware that premature abstractization is as bad as premature optimization. This is hard.

Book with a promising name, but very mixed content. Two good thoughts:

1. Modules should be deep. It is better to have fewer deep modules than more shallow modules

2. The increments of development should be abstractions, not features. When you need an abstraction, invest time and design it clearly

There are many good advices, but on my opinion the book is not deep enough to have this promising title. Also, it's a crime to spend 30 pages of 170 on how to write comments.

3/5

I think the main reason of their abandonment is Internet.

It just changed everything, people stopped create desktop apps and started to create web apps. However, web as a platform was really weak for complex apps, so only now we see how companies re-discover lost apps from 80s and re-create them in the web (Notion, Coda, Airtable, Fibery)

How you’d narrow it? We tried post-seed Saas product companies but it seems no need to do that since it doesn’t has enough differences to justify the shrink

New generation does not remember it... but I agree

Ted Nelson disagrees with you. No hyperlinks, no real connections, no networks. Too many limitations.

BTW, Here is the detailed review Fibery vs. Notion (longread) [1].

[1] https://medium.com/fibery/fibery-vs-notion-66019dd91846

We'll re-do the product page with the Fibery 2.0 release somewhere in July. Thanks for the feedback!

Thanks for advice, I’ll improve!

Good points. It seems you might enjoy Fibery[1], it addresses most of these problems (and has internal whiteboard as draw.io replacement as well). But I’m biased as a Fibery founder.

[1] https://fibery.io

Not even close. Sorry.

I really recommend to check GIST [1] as a replacement for pure roadmaps. It focuses on goals and some kind of experiments to define what should be implemented sooner.

GIST is as close to scientific approach as we have right now.

RICE model might help as well [2]

However, being 100% honest, I tried all the models above and they did not stick to me. I'm playing Product Manager role for 16 years already and rely on customers feedback + intuition. When you have deep experience in the domain, you internalize many models and your neural network in the brain quite often just makes the right decisions. Don't decide quickly though, rely on your "slow" subsystem, decide as late as possible (and collect evidence).

Another trivial observation is that customers almost always ask you about some kind of solution. They rarely provide real problems. PM job is to dig into problems as deep as possible and then find a solution. In many cases solution is completely different from what customers asked. In some cases problem can be solved without new features.

[1] https://medium.com/@itamargilad/why-i-stopped-using-product-...

[2] https://www.intercom.com/blog/rice-simple-prioritization-for...

Well, real value is that you can build internal tools quickly and connect them. As an example, you can have software development and product management apps in Fibery to track these processes and connect Features from product management to Tasks in software development.

Thanks! You are exactly right, it is hard to start, but hard to abandon when you are in.

This is one of the best article about this topic [1]. Here is the best advice I took seriously:

"Organize your notes by context, not by topic"

[1] https://fortelabs.co/blog/how-to-take-smart-notes/

Have a look at https://fibery.io

Thank you for the feedback. There is always hard balance between power and simplicity. It is remain to be seen how we handled it.

Email signup is in near plans, it was just much easier to start with Google/Microsoft signup to not be responsible for passwords.

We indeed considered that, but no decision so far. We'll see.

This would be too much :)