How to judge a borrowed practice

You don’t have to adopt someone’s whole approach to learn from one thing they do well. That matters when a useful practice comes from a competing team, a tool you don’t use or a person whose other views you reject.

For a team deciding whether to change how it works, the origin of an idea is a reason to investigate its assumptions. It isn’t a substitute for evaluating the idea. Enthusiasm for its source can be as misleading as hostility toward it.

Trying a different review process

Consider a hypothetical team that reviews technical proposals in a meeting. It encounters a published practice in which reviewers first record their assessments independently, then use a meeting to discuss consequential disagreements. The practice comes from a community whose preferred tools the team has previously decided not to use.

The team could reject the idea along with the tools. Or it could import the whole review process because respected people recommend it. Neither response answers whether this particular change would help its work.

A fair trial starts with the problem: perhaps reviewers leave meetings with unresolved concerns that weren’t discussed. The team tries independent written assessments on representative proposals and compares what happens. Do significant objections become easier to identify? Does the written work add preparation that people cannot sustain? Can a reviewer explain a concern without being penalized for disagreeing with the eventual decision?

The comparison needs the unglamorous cases as well as the promising ones. A short, familiar change may not warrant a separate written assessment from every reviewer. A disputed architectural decision may benefit from one. The useful result could be a narrower practice than the version the team first encountered.

In this example, good practice is to examine the records, talk to the reviewers and decide where the added step earns its cost. Bad practice is to declare success because everyone completed the template, or to move the standard of success after seeing a result one dislikes. A trial should be able to change the decision in either direction.

“Good” includes whose interests count

A practice can achieve a stated target and still be unacceptable. Suppose a team gets more complete meeting records by recording participants without their knowledge, contrary to their agreed privacy expectations. The quality of the record does not settle whether the means are acceptable. Consent is part of the decision, not an inconvenience to subtract from the benefit.

Practical conditions matter too. A method that relies on a dedicated reviewer may fail where that role is absent. A new tool may produce a better result on a sample task while imposing migration, training and maintenance costs that change the decision. Evaluate the full proposed change, including what people will have to stop doing to make room for it.

I would resist using the second sentence of this principle to end a difficult discussion. “Improving the work” does not give the person in charge the only valid definition of improvement. An objection may reveal a cost the agreed measure overlooks. Winning an argument matters less than the work, but a decision reached without examining the argument may be poorly grounded.

That is different from debating indefinitely. Agree on what is being tested, who will decide and what evidence would support adoption, revision or rejection. Keep serious objections with the decision so the next person can tell whether they were addressed or accepted as tradeoffs.

The same standard applies to synthesis practices. Use a principle where its reasoning helps, challenge it where the words do not fit, and retain a better practice when evidence supports it. No signature should require defending a method after it stops serving the people doing the work.