Yesterday we added new users to the Drummer test group. #
If you're part of this group, you should have a fresh new-user experience in your mind, having created an account on Drummer, and seen your Notes outline open, and maybe tried to do something beyond that. #
Do you have any observations on the new-user experience?#
Before reporting a problem, make sure it's repeatable. That's the first thing I'm going to need to do.#
When repeating it, read and follow the docs, and this time do it more carefully than the first time. I always try to provide a clear checklist of things you need to do. There aren't many wasted words in those checklists. You need to read all of them. #
I assume the person repeated it and it's a real problem.#
Sometimes there isn't enough info to repeat it, and I have to decide whether to ask for more info or move on. #
But if there is enough info, I go to the docs, and do it myself. #
If I spot the problem, good -- this was a success. If not, we begin a process to find out if the product is wrong, or the user is. #
If you don't try to repeat it before reporting it, there's a good chance it was your mistake, not the software's. And we will have wasted time that could have been spent more productively.#
Yesterday we added new users to the Drummer test group. #
If you're part of this group, you should have a fresh new-user experience in your mind, having created an account on Drummer, and seen your Notes outline open, and maybe tried to do something beyond that. #
Do you have any observations on the new-user experience?#
Before reporting a problem, make sure it's repeatable. That's the first thing I'm going to need to do.#
When repeating it, read and follow the docs, and this time do it more carefully than the first time. I always try to provide a clear checklist of things you need to do. There aren't many wasted words in those checklists. You need to read all of them. #
I assume the person repeated it and it's a real problem.#
Sometimes there isn't enough info to repeat it, and I have to decide whether to ask for more info or move on. #
But if there is enough info, I go to the docs, and do it myself. #
If I spot the problem, good -- this was a success. If not, we begin a process to find out if the product is wrong, or the user is. #
If you don't try to repeat it before reporting it, there's a good chance it was your mistake, not the software's. And we will have wasted time that could have been spent more productively.#
copyright 2021 Dave Winer.
Last update: Saturday September 4, 2021; 10:38 AM EDT.