Public:SC Office
Vision
Trying to build a Holistic Solution[1] which is a mix of :
* Knowledge Management & Enterprise Search like getguru.com
* Team Messaging like Microsoft Teams / Slack
* Collaboration Wiki like Notion.so
* Time Tracking like HubStaff.com
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
Chatroom for every node
A chatroom will be created for every node selected inside navigation
Configure Channel & Filter against nodes
connected will create child nodes against certain category inside navigation
Labeling Chat messages
#upskilling should help HR team to know what needs their attention
While customers respond, enterprise search would be used to source answer from documents
Enterprise search will use Document Chatbot. For every incoming customer message, a question or query would be formed and passed to the Enterprise search engine. Where a response will be suggested
Queries would be be context sensitive
Enterprise search should decide the filters that must be applied on queries such as, only the documents that belong to
- Certain category be be responded from (lets say we had a category / article named "North India" then queries must be returned only from inside that space
- Only data from inside customer's search history would be responded to
These contexts would be applied by NL on certain intents such as
- Last order
- other intents that are easy to train
User doesn't has to waste time deciding the location where message goes
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
For each Node in Treeview
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)
Notifications in Wiki (less noisy) than Notifications in Chat (more noisy)
Timeboxing
See here
Organizing Knowledge
Chrome plugin to organize knowledge
Static URL
Time would be tracked when a navigation node is selected, and some internet history is used. I a URL is opened more than once while working while keeping the navigation open, then it's link would be added with "open count" posted against the URL. And stored inside Knowledge
Query String URL based on a customer parameter
experimental. don't code it yet until the idea matures
Enterprise Search
Inside the constantly increasing organized knowledge, an enterprise search would be performed. Any questions asked to the Document chatbot would be answered by
- crawling all the documents crawled inside the selected navigation node and answered
- learning from all the past conversations that happened inside selected navigation node and answered
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
Track time based on what node is open
Notice what node is currently selected by user in the navigation. Track user's time inside that node.
Idle Time detection
Like they have in Hubstaff[2]
Uses CV (with NL and Document AI) to understand whats open on user's screen. And based on that automatically navigate the user to another node in navigation. See this video between Tushar and David
Time Budgeting
Set budgets per node
Resource allocation of person
Track (future) overage of budget
Alerts raised by bots and humans
Chat to Task/OKR/Objectives CRUD
uses NL
Chat to Wiki
via Document Similarity
Success Metrics
The metrics with which we measure that SC Office is more helpful than MS Office
Users are reminded when KPIs aren't met
ICs
Engineers
Weekly: Release URL
Weekly: QA Report
Designers
Marketers
Sales
Managers
All Managers
Weekly (start): Issue Board
Bi-weekly: QA Report
Bi-weekly: client updates
Project Managers
Weekly (end) : Money released
CXOs
Team has enough work
Team has received feedback