Public:SC Office
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
| Web | Desktop | Mobile |
|---|---|---|
| Navigation could be docked & pinned on the left of desktop
User can continue to open whatever apps they want on their desktop. That becomes their workspace On every app, there would appear a "Chat Anywhere" button. Or this chat anywhere pane would appear docked with Navigation Panel |
Multiple Hamburger to choose Navigation
Once chosen Navigation appears on top bar Workspace or Chatroom appears next. Whatever was accessed by user last time Multiple hamburger to choose between Workspace and Chat |
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
for every "View" created inside article page, we would create an item in navigation panel too
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
Mindmap
See Mindmap and Graph Software
⚠️ Your favorite Desktop or Web App
See
- Desktop.com
- https://www.producthunt.com/products/rambox
Chatroom
A chatroom will be created for every node selected inside navigation
Communication Channels connected will create child nodes against certain category inside navigation
User doesn't has to think of the location there message should be posted
People start typing a message, and a list of channels are searched, and suggested where the message must go
People start typing the message based on a window they had open
Notifications
Using "near natural language" the notification would be split in following types
Where I am
a Driver / responsible
as of RACI
mentioned..
..to Approve something (Take a decision)
..to Contribute something (Do a task)
..to be Informed (Acknowledge something)
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
Time Tracking
Screen to OKR / Article. Uses NL + CV via Document AI. See this video between Tushar and David
Chat to Task/OKR/Objectives CRUD
uses NL
Chat to Wiki
via Document Similarity
Success Metrics
The metics with which we measure that SC Office is more helpful than MS Office