-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Understanding the non-technical user #1280
Comments
Research ObjectiveThe goal of this research is to understand who our non-technical kedro users are, their goals, needs, and pain points when interacting with the outputs of a Kedro project and using Kedro-Viz. We hope to also get a sense of their general product/user satisfaction towards Kedro & Kedro-Viz. We want to speak to 5-8 non-technical users, both internally and externally, and across a variety of different roles and experience levels with using Kedro and Kedro-Viz. What do we want to learn?
How will we know when we’ve learned it?We will know when we are able to answer all of the questions in ‘What do we want to learn?’ with confidence and evidence. What business goals will this research support?The Kedro-Viz user base represents ~20% of all Kedro Framework users. Research understanding how to convert the other 80% of Framework users into Viz users has always yielded mediocre improvements to Viz. We want to grow the user base of Kedro-Viz so we're going to see if we can help non-technical users instead. We're mindful that these changes might even help the technical users. What decisions will this research enable?We would like to see areas that affect our roadmap for Viz. We should come out of this research with "bets" that we're going to take throughout the year. MethodsWe aim to capture qualitative feedback through 1-on-1 interviews with 5-8 users, either in-person or remotely on Zoom. Research Outcomes
TimelineInterviews conducted week of: 17-21 April ParticipantsWhat is a ‘non-technical’ user?We define non-technical kedro user here as someone who is not as comfortable using the CLI (command-line interface) and they use Kedro-Viz to follow 'what's going on' and inspect the code.
Who will we be speaking to?
Interview Guide (45 mins)User details (10 mins)
User motivation (10 mins)
User pain points (10 mins)
User recommendations & Wrap up (5 mins)
|
Slack Polly Survey (Internal & External channels)I also sent a survey via the Polly app in Slack on both internal and external channels to gather more general information about how our users are using Kedro-Viz. Poll message
Survey Questions
TimelineBoth surveys sent on: Wed 26th April 2023, 3:00 PM |
Closing this as completed. Here's a link to @stephkaiser's amazing synthesis and findings. |
Description
We have a lot of assumptions about people that interact with the outputs of a Kedro project but do not necessarily build anything within the project. Things that we don't know:
We have largely relied on second-hand information from technical users who interact with these non-technical users. It's time to put aside these assumptions and get some data from real people.
Context
This ticket is part of a larger initiative to increase the usage of Kedro-Viz by supporting this user base. This ticket has implications for #1279 and #1116.
Outcomes of this ticket
We don't currently have capacity to conduct this research but this ticket proposes designing the research study and completing recruiting for it. We must know what research outputs we need to move forward and who we will be talking to.
The text was updated successfully, but these errors were encountered: