I appreciate the updates/fixes etc. that is being pushed out so quickly based on user feedback, but it’s time to put some extra effort in creating/building a user guide and documentation to teach everyone how to properly use the features that’s available today. It seems like we are on a free for all to figure out how to properly use the app.
Topics that can be covered:
How to create/assign/change speakers
USB-C Web Sync
Detail description and example of each of the Summary Templates
Explain how the “Today’s Highlights” feature work
The meaning in different color check boxes for tasks
Exporting/importing recordings
How to split transcript text (this one stomped me for awhile to figure out)
How to use “Ask Pocket” (what happens with the “Pocket Memory” button is selected vs. not selected)
How to hide and unhide conversations? What the benefit (if any) to even hide them?
What does the “Auto Transcript” toggle means in settings? (I still haven’t really figured this one out. I haven’t even wanted to turn off to find out)
How to sync/unsync calendars?
Start/stopping recording
Conversation vs phone toggle switch on device
Meanings of the different light colors on the device
There’s much more that can be added as well. The device/app provides no value if the user does not know how to properly use it.
I think this idea does make a lot of sense, but given the number of changes and workflow adjustments they’ve been making, I wonder if it’s not quite time. Maybe temporarily a FAQ thread that can be updated with answers to these?
The number of changes makes sense but some type of documentation should be provided. If you want to users to try features and provide feedback, you should provide some instructions on how you at least expect it to be used.
For instance, tags were just released and I have no idea how it should work besides the fact that I can make a tag now. I created one tag under a conversation, then tried to go to another to add the same tag, but I don’t see it as an option. At this point I don’t know if that’s how it’s supposed to be, is it a bug, does tagging even work the way I “think” it should work.
I participate in many beta programs and work in Quality Assurance professionally, and the key has always been providing some level of details to the user to know what/how to use. This allows them to first know what has even changed and then enables them to quickly try it out and provide feedback. Doesn’t have to be any formal user guide or extensive document, but even making a post on here with a sentence or two about it would make a huge difference.