Public:SC Office: Difference between revisions
imported>Tushar (Created page with "= Capabilities = == NL: Search == == NL + CV: Screen to OKR / Article == via Document AI == NL: Task CRUD == == NL: Chat to Wiki == via Document Similarity") |
imported>Tushar No edit summary |
||
| Line 1: | Line 1: | ||
= User Experience = | |||
Conventional Team Messengers have Navigation on the left, and Chatroom on the right like this | |||
{| class="wikitable" | |||
|+ | |||
! | |||
!Desktop | |||
!Mobile | |||
|- | |||
|Slack | |||
|[[File:Slack Desktop.png|left|thumb|Slack Desktop. Left Navigation. Right chatroom]] | |||
|[[File:Slack Mobile.png|left|thumb|Slack Mobile. Left Navigation. Right Chatroom]] | |||
|- | |||
|MS Teams | |||
|Anand to fill screenshots here from Google Images | |||
|Anand to fill screenshots here Google Images | |||
|} | |||
A problem with Team Messengers is that everytime you have a chat, you later have to do extra work in filing your tasks, decisions, files from the chat into a Knowledge Base (like Confluence). | |||
GetGuru.com tries to solve this. It integrates into the messengers (like Slack, Teams) and creates a Knowledge base for you (it offers a Wiki, or Knowledge base). | |||
[[File:SC Office User Experience Anatomy.png|thumb|SC Office User Experience: Left Navigation. Center Workplace. Right Chatroom]] | |||
Our user experience offers | |||
* A Messenger + (Self Organizing) Knowledge Base inside a single place. | |||
* Not just a Knowledge Base, but also your "Workplace". | |||
Down the line we will delve more into "Self Organizing" and "Workplace". But first let's see what the anatomy of our User experience will look like | |||
== Navigation == | |||
=== N level Nested === | |||
Slack and Teams have a limit of 2 or max 3 level in Navigation. We would let N level. We would use Mediawiki category structure to let users create categories | |||
=== Yet (nearly) Flat === | |||
You can see chat conversation and activity (in workplace) when you click on any node. You can see | |||
# Only the activity / chat in selected node | |||
# All the activity / chat nested inside the selected node | |||
=== Navigation with Dashboard === | |||
see [https://gitlab.com/smarter-codes/Talking-DB/hc-inbox/product-design-epics/navigation-panel-ui/-/blob/main/README.md Navigation Panel in TalkingDB] | |||
== Workplace == | |||
=== Wiki pages === | |||
Mediawiki Article pages will open as user clicks on a node in Navigation | |||
=== Spreadsheet / Kanban / Tasks === | |||
While Mediawiki powered articles pages would be the default option in Workplace, but like in Clickup you would have option to see | |||
=== ⚠️ Your favorite Desktop or Web App === | |||
See | |||
* Desktop.com | |||
* https://www.producthunt.com/products/rambox | |||
* | |||
== Chatroom == | |||
= Capabilities = | = Capabilities = | ||
== | == Navigation to Workplace == | ||
For every navigation note, we would memorize the Workplace that was left last open. Maybe for a particular node the user prefers to see their Favorite App first, than the Wiki page. It would remember and open only that | |||
== Workplace to Navigation == | |||
== Navigation to Chatroom == | |||
== Chatroom to Navigation == | |||
While you are chatting you can do # and mention to a node in Navigation | |||
=== ⚠️ Automatic switching of Navigation Node === | |||
While chatting if you start to talk you went "off topic" and started to talk about a topic which goes in another Navigation node, then AI would automatically detect and nudge you to either MOVE or COPY your communication over there. And even JUMP you to the navigation node | |||
== Search == | |||
uses NL | |||
== | == Time Tracking == | ||
via Document AI | Screen to OKR / Article. Uses NL + CV via Document AI | ||
== | == Task CRUD == | ||
uses NL | |||
== | == Chat to Wiki == | ||
via Document Similarity | via Document Similarity | ||
Revision as of 08:36, 1 April 2023
User Experience
Conventional Team Messengers have Navigation on the left, and Chatroom on the right like this
| Desktop | Mobile | |
|---|---|---|
| Slack | ||
| MS Teams | Anand to fill screenshots here from Google Images | Anand to fill screenshots here Google Images |
A problem with Team Messengers is that everytime you have a chat, you later have to do extra work in filing your tasks, decisions, files from the chat into a Knowledge Base (like Confluence).
GetGuru.com tries to solve this. It integrates into the messengers (like Slack, Teams) and creates a Knowledge base for you (it offers a Wiki, or Knowledge base).
Our user experience offers
- A Messenger + (Self Organizing) Knowledge Base inside a single place.
- Not just a Knowledge Base, but also your "Workplace".
Down the line we will delve more into "Self Organizing" and "Workplace". But first let's see what the anatomy of our User experience will look like
N level Nested
Slack and Teams have a limit of 2 or max 3 level in Navigation. We would let N level. We would use Mediawiki category structure to let users create categories
Yet (nearly) Flat
You can see chat conversation and activity (in workplace) when you click on any node. You can see
- Only the activity / chat in selected node
- All the activity / chat nested inside the selected node
see Navigation Panel in TalkingDB
Workplace
Wiki pages
Mediawiki Article pages will open as user clicks on a node in Navigation
Spreadsheet / Kanban / Tasks
While Mediawiki powered articles pages would be the default option in Workplace, but like in Clickup you would have option to see
⚠️ Your favorite Desktop or Web App
See
- Desktop.com
- https://www.producthunt.com/products/rambox
Chatroom
Capabilities
For every navigation note, we would memorize the Workplace that was left last open. Maybe for a particular node the user prefers to see their Favorite App first, than the Wiki page. It would remember and open only that
While you are chatting you can do # and mention to a node in Navigation
While chatting if you start to talk you went "off topic" and started to talk about a topic which goes in another Navigation node, then AI would automatically detect and nudge you to either MOVE or COPY your communication over there. And even JUMP you to the navigation node
Search
uses NL
Time Tracking
Screen to OKR / Article. Uses NL + CV via Document AI
Task CRUD
uses NL
Chat to Wiki
via Document Similarity