Enough is Enough

On a project, enough is enough.
What this means is that you must provide any person only the level of detail of information that person needs at that time. Think of it, when you are packing your suitcase for a vacation, do you really need to know that the average temperature over the last 50 years for that month is 28.53987 degrees? No, you do not. All you need to know is that the average temperature is between 25 and 30 degrees, or between -10 and 0. It will make a big difference on what you pack, or not.
 
Providing too much (too detailed) information, particularly to executive levels of authority, is not only a waste of time and effort but also a big risk. The risk being that people get caught up in details, and that they completely miss what is really important.
 
We see this time and time again in project meetings; Project leads/manager/members being grilled about an apparent incongruity of details between reports. The issue at hand, that the project is over budget, gets ingored and the project member gets send back to write yet another report explaining the reason(s) for the difference.
 
In the same way that just-in-time management streamlines processes, just-enough-information management streamlines communication and decision-making. Don’t give people an excuse to talk about details that do not matter at that moment. Enough is enough already!