Application Upgrade - Developer Experience Research
Help us understand developer pain points by answering a short set of application and package upgrade experience questions.
Screening & Eligibility
Role
*
Software Developer / Engineer
Tech Lead / Engineering Manager
DevOps / Platform / SRE
Works closely with developers (PM, QA, etc.)
None of the above
Are you a software developer, or do you work closely with developers?
*
Yes, I'm a developer
No, but I work closely with developers
No
Organization & Upgrade Cadence
How large is your engineering team or organization?
*
1-10
11-50
51-200
201-1000
1000+
What programming language(s) is your application built in?
*
Java
Node.js / JavaScript / TypeScript
Go
Python
Ruby / Ruby on Rails
Other
From planning and scoping to production release, how long does a typical application upgrade take?
*
Less than 1 day
1-3 days
3-5 days
More than 5 days
How many upgrades do you typically do per quarter across all apps you own or maintain? (For ex: like upgrading java/nodejs or any other tool version, jar/package version, upgrading CI/CD pipeline with new feature or change, a bug or vulnerable code fix across the apps. Excluding feature/major development)
Do you repeat similar upgrade work across different apps, sometimes even work another team has already done,?
*
Yes, frequently
Sometimes
Rarely
No, never
Ownership, Sharing & Current Tools
How much time do you spend figuring out ownership, scope and priority for an upgrade before you can start the work?
*
Less than 1 hr
Within few hours
Within a day
2 days or more
How often do you share your upgrade process and knowledge with other teams?
*
Always documented and shared
Sometimes shared informally
Rarely shared, everything happens in my local and PR
Never shared, stays with me
Does your company have a concept of a Tiger Team (a dedicated cross-functional team) that handles these upgrades for you?
Yes
No
I don't know what a Tiger Team is
What tools do you currently use to manage dependency and version upgrades?
*
Dependabot
Renovate
Snyk
Manual
Internal custom tooling
None
Other
Pain Points, Support & Value
What is your biggest pain point in the upgrade process?
*
Testing and validation
Coordinating across teams
Lack of visibility into who owns what and priority/scope
Risk of breaking changes / rollback
Documentation gaps
Communication overhead
Recurring and boring work
Other
How would you rate the support experience when you get stuck during an upgrade?
*
1
2
3
4
5
Overall, do you find the upgrade process enjoyable or frustrating?
*
Enjoyable
Somewhat enjoyable
Neutral
Somewhat frustrating
Very frustrating
Would a tool that automates and centralizes visibility into upgrade status, ownership, and priority across teams be valuable to you?
*
Yes, definitely
Maybe
Not really
No
Would you be interested in a 1:1 user research session and get a sneak peek of what we're building?
*
Yes
No
Email address
Enter your email, or skip if not interested.
Any additional thoughts, frustrations, or feature requests you'd like to share?
Submit
Should be Empty: