Guidelines on Conflict of Interest
ACM Awards Committee
Conflict of interest (COI) is generally recognized as a situation where there is risk that a professional judgment or decision could be influenced by some secondary interest. In the context of ACM award committees, COI derives from a committee member’s relationship with a nominee and/or affiliation with a nominee’s institution. Members of ACM award subcommittees avoid the appearance of any impropriety by adhering to the following guidelines.
- ACM officers and executives do not serve as nominator or endorser for any nomination submitted for an ACM award, including awards sponsored by ACM’s Special Interest Groups. This restriction includes the ACM President, Vice President, Secretary/Treasurer, Past President, CEO, and COO.
- Members of an ACM award committee do not serve as nominator or endorser for any nomination submitted to that committee. If you have nominated/endorsed a candidate, inform the committee chair1 immediately so that one of two actions may be taken: (a) the nomination will be set aside for the year, or (b) you will step down from the committee for the year.
- Members of an ACM award committee are not eligible for that award during their term of committee service. When agreeing to serve on a committee, you should understand that if you were to be nominated, the nomination would be disqualified. Persons preparing nominations should be advised that committee members are not eligible.
- Members of an ACM award committee should not be directly involved in nominations prior to their submittal. You can answer general questions about what a nomination should include, but you should not pre-review or comment on draft nominations.
It is normal for the committee as a group to develop a list of potential candidates and a committee member may be asked to contact a potential nominator, but such communications should be kept general in nature so that they cannot be construed as assistance or raise expectations about the outcome.
- Members of an ACM award committee maintain confidentiality about the internal discussions of the committee. Information about committee deliberations should not be shared with anyone outside the committee, nor should the winner be discussed until ACM has issued the formal press release.
- Members of an ACM award committee do not provide feedback to unsuccessful candidates. If a member is asked for feedback, this policy should be cited.
On rare occasions, and with the approval of the committee, the chair may contact a nominator to encourage/discourage future re-nomination of a particular candidate. In such cases, feedback should be limited to general information about elements of the package that made the case weak (e.g., over-reliance on endorsements from the same institution as the candidate/nominator, endorsements that just reiterate the nomination without providing new insight, or candidates whose accomplishments are not a good fit for the award). Note that it is not appropriate to offer evaluative comments on the candidate’s qualifications or specific endorsements. The committee is under no obligation to provide feedback for any candidate, and it must be made clear that responding to the suggestions will not necessarily result in future success.
- Members of an ACM award committee self-identify any relationships/affiliations that might be perceived as a source of potential bias, and inform the committee chair of the COIs before any candidates have been discussed. Identify any candidates with whom you have had close personal or working relationships within the past 4 years, anyone for whom you were thesis advisor/advisee, or any other case where your judgment could be affected. Also identify any candidates from your current institution or one where you worked within the past 4 years. In the case of the Doctoral Dissertation Award Committee, also identify all candidates on whose PhD committees you served in any capacity, or whose dissertations contain work that was done jointly with you.
- If COIs are identified, the normal practice is for conflicted committee members to recuse themselves from discussions related to the corresponding nominations. In this sense, recusal means that the committee member will refrain from any commentary/input before or during the decision-making process, and will absent him/herself during committee discussions of the nomination.
When it is the chair who is conflicted, recusal suffices only in the case of membership grade decisions and the Doctoral Dissertation Award Committee. For other awards, it is not acceptable for the chair to have any type of conflict with an awardee. Potential conflict should be identified in advance, and the chair should contact the Awards Chair immediately to determine whether the nomination might be deferred a year (in consultation with the nominator) or whether the chair should be replaced.
Why I Belong to ACM
Hear from Bryan Cantrill, vice president of engineering at Joyent, Ben Fried chief information officer at Google, and Theo Schlossnagle, OmniTI founder on why they are members of ACM.
Written by leading domain experts for software engineers, ACM Case Studies provide an in-depth look at how software teams overcome specific challenges by implementing new technologies, adopting new practices, or a combination of both. Often through first-hand accounts, these pieces explore what the challenges were, the tools and techniques that were used to combat them, and the solution that was achieved.
ACM Queue’s “Research for Practice” consistently serves up expert-curated guides to the best of computing research, and relates these breakthroughs to the challenges that software engineers face every day. This installment of RfP is by Anna Wiedemann, Nicole Forsgren, Manuel Wiesche, Heiko Gewald, and Helmut Krcmar. Titled “The DevOps Phenomenon,” this RfP gives an overview of stories from across the industry about software organizations overcoming the early hurdles of adopting DevOps practices, and coming out on the other side with tighter integration between their software and operations teams, faster delivery times for new software features, and achieving a higher level of stability.