By Gopal K. Kapur

Computerworld |

Early in my career, when I worked as an engineer, my boss had a process by which the engineering team was expected to report project status. He insisted that we use the following steps, in the specified order:

1. Punch line: The facts; no adjectives, adverbs or modifiers. “Milestone 4 wasn’t hit on time, and we didn’t start Task 8 as planned.” Or, “Received charter approval as planned.”

2. Current status: How the punch-line statement affects the project. “Because of the missed milestone, the critical path has been delayed five days.”

3. Next steps: The solution, if any. “I will be able to make up three days during the next two weeks but will still be behind by two days.”

4. Explanation: The reason behind the punch line.