Problem validation context in Duo Chat
What’s this issue all about?
Understand if and which context users want to reference when seeking help with code creation and code analytics tasks in Duo Chat or when using Code Suggestions.
Who is the target user of the feature?
- Primarily the software engineer persona
- Use Duo Chat or other AI in the IDE
What questions are you trying to answer?
- What tasks in the developer workflow require Duo to have context?
- What does it to developers when they say they want "context?" (defining context)
- What types of context are needed in a dev workflow?
- How much context does a user need (everything, partial, etc)?
- How does context differ between dev tasks? Does it change as the dev moves through the task?
- What tasks don't require context?
- What level of control do users expect to have over context used in a response?
- How would users expect to control context?
- Do these expectations vary between Chat/Code Suggestions?
- How long should Duo carry context (over a single turn or multi-turn, across sessions, when a user changes pages, etc)
What hypotheses and/or assumptions do you have?
- Increasing context provided to Duo Chat will improve responses
- Users may want to use specific context in some situations
- Users may not want context on specific tasks
- Users may have security concerns about context
- Context will vary by developer task
- Design will vary between IDE and .com, as well as between IDE inline and DUO chat.
What decisions will you make based on the research findings?
- Define types of context needed for creating, explaining, troubleshooting, and modifying code
- Pinpoint levels of control needed when accessing context in a coding workflow
- Define the type of context needed by task in a developer workflow
- Identify security concerns when accessing information/files/code
What's the latest milestone that the research will still be useful to you?
17.5
Discussion guide and screener
Edited by Nicolle Merrill