Hi Michael, I have been meaning to respond to you here, thank you very much for taking the time to post your thoughts and provide the clip with some insights into where you guys might be going with this!
I just added some more commentary about this need over here, and what you suggest looks great. I look forward to a comprehensive solution down the road and I know you guys have been serious about solving how communication works in Fibery from day one, and I know that this takes a lot of thought to get right.
In looking at your clip, I can tell you I particularly like the “decision” element you are featuring. My team has been in productivity apps for years, and we always had trouble figuring out ways to document decisions in them. Most productivity apps are set up with “tasks” as the atomic unit, so you could try to make a “task” a “decision,” but that’s very awkward in every app we tried it in. I can tell you that Fibery actually is working better for this than anything else we’ve ever used! We have a db called “discussions” and these work like internal memos, with requisite workflows to show where the discussions are within a given team. I once saw a Confluence example where there was a tag attached to a doc of “Decision Needed” and another of “Decision Made.” In Confluence those were simple tags so you couldn’t do anything with them like sort them, count them, etc. So I transferred that concept to a workflow on these “Discussion” entities, and now we have a great system in Fibery! To give you an example of how easy this is, if we are in a meeting and somebody is taking notes in one of these “Discussions,” and there is a decision, for example we are going to use Vendor X for SEO vs. Vendor Y, I can simple start typing “in this meeting we chose Vendor X,” create a Discussion entity inline, then choose the status from this workflow of “decision made,” and this decision lives for us to look back on. Extremely quick, extremely useful, and extremely needed in apps like Fibery! I hope this process we use around tracking decisions might be useful to your thinking about implementing something like that in the future, as you displayed above.
Thanks again for your post!