SUGGEST
What to Suggest?
To suggest is to propose for consideration or action. So, decide if your suggestion is (or will be) more of an “alternative for your consider” or an “unequivocal recommendation”. The first amounts to “advice freely given”, and as such can be freely accepted or rejected. The second implies an imperative that should not be overlooked. In either case suggestions should carry the prospect of improvement, and should be feasible given the constraints already in place.
Why to Suggest?
Not always, but all too often, what suggestions amount to is “if I had been in charge this is the way I would have done it”. What are proposed as improvements are just ways of disguising venom. Suggestions are often premised on the assumption that their purveyors were more qualified for the assignment. Regardless, the wisest response is to thank any and all contributors for their views, and use those least disruptive, and most productive.
When to Suggest?
Only offer them when an entire section is ready for review, and only accept them on the same occasion. Projects of whatever kind should be componentialized in their design so that chapters or segments or whatever, can be reviewed on a “stand-alone” basis. So, when such a component is produced it can and should be presented for review. But make the mandate clear: what kind of suggestions are you looking for – form or substance?
Whether to Suggest?
Reviewers need to ask themselves whether they understood what they were reviewing or not. Then they need to stick to their instructions: assess according to form, or substance, or whatever. Once suggestions covered by the mandate are delivered, a reviewer can always ask “Do you want my opinion on [so and so]. Don’t give your own preferences as suggestions, and don’t expect too much from them – it’s not about you!
How to Suggest?
Base suggestions on criteria, direct them at issues and not people, construct them so as to be feasible, and phrase them so as to increase the likelihood of their acceptability. Use the term could rather than should, be gracious in rejection, and grateful even if only a few, or only “watered-down” versions are adopted. Keep a copy of all your suggestions and review notes, for defence if sued, and for more work if asked.
References
