I can help you understand why users might be dropping off from your invoices feature! This is a common challenge with new features.

Let me think through the key dimensions of this problem:

Key Dimensions:

• Discoverability — Can users find and understand how to use the feature?
• Usability — Is the feature intuitive once they start using it?
• Value perception — Do users see enough benefit to continue?
• Workflow fit — Does it integrate well with how they already work?
• Trust/confidence — Do users feel secure using it for financial tasks?

Now, there are a few different angles we could explore with your interviewees. Let me offer you some research directions:

Great choice — understanding the perceived value vs effort tradeoff is often the key to feature adoption. If users feel the feature takes more work than it's worth, they'll abandon it regardless of how well it's designed.

Research Question: What do users perceive as the main benefits and friction points of the invoices feature, and how do they weigh these against each other?

Let me check what interactive exercise formats I can build for you:

Now I have a good sense of what I can build. Here are some exercise ideas that would help uncover the value-vs-effort tradeoff for your invoices feature:

Love it — this exercise will give you really actionable insight into what users value most and what friction points hurt them the most.

The concept: Users have a limited budget of "investment tokens" they can spend across invoice feature benefits AND friction points. They drag tokens onto the aspects that matter most to them — either things that bring them value, or pain points that bother them. This forces prioritization and reveals what really drives (or kills) adoption.

Let me build this for you:

Here's your exercise: Invoice Trade-off Tokens

How it works:

• Users have 10 tokens to allocate across benefits they value AND pain points that frustrate them
• They drag tokens from the bank onto items — the more tokens, the stronger their feeling
• Click tokens to remove them and reallocate elsewhere
• The constraint forces real prioritization

What you'll learn:

• If tokens cluster on pain points → friction is killing adoption
• If tokens cluster on benefits → users see value but something else is blocking them
• Which specific benefits resonate (and which don't matter)
• Which friction points hurt most (guiding where to fix first)

The exercise captures the final allocation, and during the interview you'll hear users explain their reasoning as they move tokens around. That commentary is gold — it tells you why something matters, not just that it matters.

Want me to tweak the benefits/pain points to better match your actual feature, or adjust anything else?