--- tags: discovery, call --- # Discovery Call (Revised) ## General Questions - Can you describe your job? - Please elaborate on your role as `{role}` - How does data play a part in your work? - What tools do you currently use to manage those tasks? - How would you rate your experience with these tools? - You've mentioned `{tool}` as `{hard to use, complicated, easy, intuitive, user-friendly, time-consuming, efficient, powerful, flexible, frustrating}`. Can you provide more details? *Repeat this question if for other tools if needed.* - Are you open to sharing a step-by-step walkthrough of what you tried to accomplish with `{tool}`? If possible, please share your screen and guide me through the process. If not, describe in detail what you see and do. :::info **During the Walkthrough** - Ask the user to talk through what they're doing and why as they go along. Encourage them to share their thoughts openly. - Keep an eye out for moments when the user seems unsure or hesitates. Use these opportunities to ask them about their thoughts and feelings, as it might uncover hidden pain points. - If the user spends too long on one step, nudge them to explain their next step. This helps to keep the walkthrough moving and cover more ground. Questions ::: ### Questions for Mathesar Users *Emphasis on understanding the impact of Mathesar on the user's workflow.* - How long have you been using Mathesar for? - Since using Mathesar, **has your workflow evolved** in any way? What specific changes did you notice? - You've mentioned `{change}`. How has this change impacted your overall **productivity or efficiency**? - With this change in your workflow, have you discovered any new **use cases** for Mathesar or areas where it could further improve your work? - You mentioned `{area}`. Can you describe the specific tasks within this area where you think Mathesar could be **beneficial**? - How have you been addressing these tasks **without Mathesar**? What alternative methods or tools have you used? - Do you see any potential **challenges or limitations** when using Mathesar for these tasks? If so, what are they and how might they be addressed? ### Questions for Non-Mathesar Users *Emphasis on exploring the potential of Mathesar to help with the user's current needs.* - Introduce Mathesar - Quick walkthrough demonstrating schemas, tables, and explorations. - After seeing Mathesar, how do you think it compares to the **tools or methods you're currently using** to tackle your problems? - What aspect of Mathesar **stands out the most to you**? - Depending on the response, ask follow-up questions like, "Why is that important to you?" - Considering your current workflow, can you describe the **most significant problems** you encounter? - You've mentioned `{problem}`. Are there any `{aspects|features}` of Mathesar that could potentially help with `{problem}`? - You've pointed out `{feature|aspect}` as something that might be useful for `{problem}`. Could you share more about **how you've been addressing this issue**? What methods or tools have you employed so far? - Do you see any potential **challenges or limitations** when using Mathesar for these tasks? If so, what are they and how might they be addressed? ## Additional Insights (Optional) Questions to ask if we have time left. ### Previous Solutions and Switching Factors - Have you tried other tools or solutions before using `{tool/Mathesar}`? If so, what were they and why did you decide to switch? ### Decision-making Process and Research - What factors led you to choose `{tool/Mathesar}` for your tasks? - What was your research process like? What resources did you use to make a decision? - What specific insights did these resources provide that helped guide your decision? ### Preferences and Habits - What are your preferences when it comes to selecting and using a tool for `{task}`? - Are there any habits you've formed with `{tool/Mathesar}` that have made your work more efficient? ### Pain Points and Enhancements - Are there any areas where you feel `{tool/Mathesar}` could be improved? - You've mentioned `{area}`, are there any specific features or functionalities that you find lacking or need refinement in this area? - How have these issues impacted your work or workflow? - Have you experienced any difficulties with `{tool/Mathesar}` user interface or user experience? - How do these aspects influence your ability to work effectively with the tool? ## Closing (2-3 minutes) - Thank the participant for their time and valuable insights. - Inform them about any follow-up steps or when they can expect to see improvements based on their feedback. - Offer contact information for any additional questions or comments they may have. --- :::info **During the Interview** - Focus on the person's experiences and life rather than discussing Mathesar or any other tools directly - Ask about specific past experiences instead of general opinions or future predictions - Practice active listening and encourage the person to speak more - Investigate feature requests by asking about their importance, impact on user experience, workarounds, and integration into the workflow. - Delve into emotional signals by encouraging users to elaborate, share stories, and discuss their feelings related to frustrations, excitement, and enjoyment. ::: ## Analysis (to complete after the call) ### Most pressing issues(s) ### Observed User Behavior ### Unmet Needs and Improvement Suggestions