he is telling you: Operational level - to keep the technical jargon out, dont give technical details but give business strategy related details. if you need th

he is telling you: Operational level - to keep the technical jargon out, dont give technical details but give business strategy related details. if you need then go in tactical ways you can solve the problem. - your information should be bulleted list of 4-5 words per line in business terms. - you should talk in terms of program level, org level strategy, program level budget/matrix work, dependencies etc. - your metrics conversation should be in terms of business terms such as basis point impact to the program. - you should not talk architecture or logic level design but in terms of connecting orgs, blockers due to various programs. - view and think in terms of non-biased decisions to be made objectively. - talk in terms of process not code - i do not want my team members to have crap excuse about defects occur b/c this and that issues but i want to know metric based impact and recommendations and alternatives. - present 2-3 options (unbiased) to help make right decisions. People Level talk in terms of - strengths and opportunities. - building bench strength. - talk in terms of pipeline - team building activities, team collaboration, compensation packages, org chart and skill needed. - lastly, do not go to your boss with your daily problems, he is your last resort.