# User Research Team

## Summary

Commission a team to serve as experts on users' experiences with Rust. The team will assist other Rust teams in making informed decisions through

* accepting "informational RFCs" that describe the needs of Rust application domains (either potential or existing);
*

conduct active research into how Rust is used on an ongoing basis. The team will

* produce "informational RFCs"
* assist other Rust teams in investigating research hypothesis to better inform decision making

## Motivation

As the Rust programming language matures into a stable, reliable way to build software we want to ensure that there's a clearly defined structure to absorb feedback and provide it in a way which is digestable to the Project Teams.

Historically the Rust Project has been successful interacting with individual to accomplish landing features and improving the state of the ecosystem. Now that companies with a long legacy, some of which are not typically thought of as tech companies, are beginning to use Rust it's important that we have a good funnel for ensuring their experiences in Rust application domains are being surfaced.

Additionally, there is a mechanism in our RFCs for resolving a [lack of concensus], but it's not been used in practice and thus not considered in force. This can lead to teams that are considering alternatives to reach an impasse where decisions cannot be made effectively.

Some decisions are worthy of seeking outside opinions in a fair way, which is another aspect this team can support. This team would gather survey data and/or perform targeted user interviews in order to deliver a qualitative analysis report for the requesting team to consider as they'd like when making a decision.

## Charter

Q: What does success look like for this team?
Q: What is outside this team's purview?

## Frequently asked questions

* Am I bound to use the direction that the qualitative analysis report seems to be pointing our team if we request one?
* No, you are not. The intention is to help surface things which may not have been obvious originally and locate some signal which can support decision making.

[lack of concensus]: https://rust-lang.github.io/rfcs/1068-rust-governance.html#lack-of-consensus