Take the 2-minute tour ×
English Language & Usage Stack Exchange is a question and answer site for linguists, etymologists, and serious English language enthusiasts. It's 100% free, no registration required.

All,

I am preparing a technical document for a process. Another team will do the implementation based on the document.

I want to have a section which will outline some of the challenges they will face and how to overcome them. I am currently leaning towards "Challenges", but are there any better alternatives?

For the context, some other headers are 1. Requirement, 2. Analysis, 3. Technical Solution, 4. Dependencies etc.

Update: I was thinking of another heading as I will be telling about how to overcome the challenges also in this section - like "Challenges and how to overcome them"

share|improve this question
    
Challenges sounds a bit 'flip' in the context of the other section names. Besides, how do you know which particular aspects of the implementation the team will find challenging? If they're any good they'll find out for themselves, and it should be no part of your spec to tell them where their strengths and weaknesses lie. Just say what the process has to do. –  FumbleFingers May 26 '11 at 17:10
    
@FumbleFingers - We are trying to make life easier for all. I know what challenges they will face and how to overcome them because I have done a similar implementation before. So I would not want the implementation team spend time reinventing the wheel. –  rest_day May 26 '11 at 17:14
    
Perhaps it should be Guidance notes then. –  FumbleFingers May 26 '11 at 17:16
    
Thanks @FF. That is a good suggestion. –  rest_day May 26 '11 at 17:34

3 Answers 3

up vote 1 down vote accepted

We use "Special Considerations" for our similar section header. It allows everyone to save face, and it allows us to detail some of the finer points that other sections may miss.

share|improve this answer

If this section contains "gotcha" warnings not covered elsewhere, I think "Challenges" is a fine heading (or "Implementation Challenges" if that level of specificity applies to your situation). If this section calls out information that is covered elsewhere, e.g. you talk about requirements-based challenges in Requirements and design/implementation challenges in Technical Solution and so on, then perhaps "Summary of Challenges" would be better.

share|improve this answer

"Challenges" is certainly a viable option, and fits your short description very nicely. "Issues" would also do, and has essentially the same connotations in these circumstances.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.