---
tags: discovery, call, feature
---

# Discovery Call (Feature-Oriented)

## Goals

The user in this case has expressed their interest regarding a specific feature, in this case `<database security>`, and has suggested that Mathesar implements it. We want to know the following:

- Is `<database security>` a deal-breaker for them? Is it determining their decision to switch to Mathesar?
- What are the details of the feature they want to see implemented?
- What are the pain points they've experienced with other tools that they would like to see addressed through this feature?
- What are the other concerns they have that are not addressed by this feature?
- Why aren't those features as important to them as this one?
- What are the other tools they've looked at and how do they compare to Mathesar?

## Outcomes

By the end of the call, we should have a better understanding of the following:

- Is `<database security>` feature worth implementing?
- Is there a better way to solve the problem this feature is trying to address?
- What are the other concerns the user has that are not addressed by this feature?

## Intro

1. Can you tell me a bit about your work as a `<role>` and the projects you're currently working on? Especially with regards to `<managing database security>`?
2. It sounds like `<database security>` is a key concern for your team. Can you elaborate on the challenges you face in this area?

## Section 1: Initial Thoughts and Experiences (5-7 minutes)

1. How did you first learn about Mathesar?
2. What aspects/features initially caught your attention?
3. You mentioned `<database security>` as a concern, how do you think Mathesar addresses this? How does it compare to other tools you've used?
4. How were you solving `<database security>` challenges before using Mathesar?

## Section 2: Desired Feature and Other Solutions (5-7 minutes)

1. Can you provide more details about the feature from `<previous or alternative tool>` that you would like to see implemented in Mathesar?
2. If you didn't have this feature, what would you do instead? How else would you solve this problem if you had no other options?

## Section 3: Switching Factors (7-10 minutes)

1. What factors motivated you to look for a new database tool?
2. Was there a particular situation happening around the time you started looking for a new tool? If so, can you describe it?
3. How was this related to your `<database security>` concerns?

## Section 4: Decision-making Process and Research (7-10 minutes)

1. Is `<database security>` the only concern you have? If not, what other concerns do you have?
2. Can you describe the process of looking for a solution that addresses your specific needs?
3. What are deal-breakers for you? What are the features that you absolutely need to have?
4. What are nice-to-haves? What are the features that you would like to have, but can live without?
5. How does Mathesar hold up against other tools you've looked at?

## Section 5: Pain Points and Enhancements (7-10 minutes)

1. What are the pain points when it comes to `<database security>` that you've experienced with other tools?
2. How about in other areas? What are the pain points you've experienced with other tools?
3. What in those other tools actually worked well against those pain points?

## 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.

---

## Analysis (to complete after the call)

### Most pressing issues(s)

### Observed User Behavior

### Unmet Needs and Improvement Suggestions