When presenting OEP-56: Architectural Advisory Process to engineers, especially as it relates to ADRs, a common reaction is the belief that soliciting feedback would unnecessarily slow down the process. The unspoken conclusion is that soliciting feedback should be avoided.
What are ways we could dispel these fears? Here are some thoughts:
- I think an ADR doesn’t need to have a deadline for accepting/responding to feedback. Someone can merge an accepted ADR as soon as they believe they have made a good decision. This should not block new feedback from coming in and/or the ability to iterate on the decision. I’m not sure if others agree, and I don’t think this is codified. See next point.
- Related, I think it is ok to change an accepted ADR that has merged if the dust is still settling on the decision. The more correct approach might be to use the “Provisional” status until it is ready to be “Accepted”. However, in many cases, this just causes process overhead and a psychological feeling of a slower process. I’d call this “Accepted until proven otherwise”.
- Documenting potential short responses to feedback could help people understand how to avoid length time-consuming conversations defending what they still believe is a good decision. For example, “Interesting point, but we’ll agree to disagree” or “Thanks, but I still like the current decision. I’ll list your idea under Rejected Alternatives” or “Thanks. That is an interesting future idea if anyone wants to pick that up.” The point is, people know that differing opinions have the potential to eat up a lot of time, and we want them instead to know that this can be avoided.
- The benefit to everyone of soliciting feedback, is when your response to a comment is something like: “Wow. Great point. I’ll update the decision.” This opportunity is what we don’t want to miss out on, so I want to help people get the best of all worlds.
- If we do all of this, I hope we can increase motivation for people to actively solicit feedback where appropriate. If you no longer fear feedback slowing you down, will you be more open to finding those comment-gems? See Arch Coordination - How to announce for examples of actively soliciting feedback.
I’m not sure if the results of this discussion would result in small updates to OEP-56, and/or a new separate how-to that includes the sales pitch and recommendations.