Establishing 'Making it Happen' as a 'Formal & Predictable' Discipline

Granularity Intensity	Ground Level Intelligence

Execution-MiH ENCYCLOPEDIA → Execution Making-it-Happen → SECTION - Execution Intensity →

CHAPTER -

Frequency Intensity

This chapter looks at execution intensity in terms of how frequently one applies the management. This includes moving from lower to higher frequency, from 'fixed timing to exception-based' management and from 'post-facto to pre-facto' management.

Topics

From monthly to weekly to daily

Intensify your Execution Tracking to higher frequency to get better early warning signals, ensuring that work-in-progress milestones are better tracked, and smaller-bite actions are allocated and completed. However, the frequency of execution tracking will be different for different aspects. There needs to be some new information or decisioning possible between two consecutive reviews. Having twice-a-day management review of a collection-centre business could be fine, but it will be an over-kill for a mega-engineering project going through land filling stage.

From fixed-frequency based to exception based

Intensity of execution is linked to both the extent and smartness of rigor applied. An organization can devise the alerts and early warning signals. It can get into a review and investigation mode, when there is an exception. This will lead to a more efficient use of time. This approach will need a robust and reliable sensory system.

From managing surprises to avoiding surprises

Exception-based management is a known management practice. An execution-focused business will work towards pre-empting exception much before they occur or impact the results. The early warning systems should be so created to raise an alert based on input** or leading indicators**. The alerts thus raised will be used to take corrective actions.

Output and Input based Check-Points

Apart from exception-based alerts, one can decide the review to be done at certain milestones of a project, or a certain level of performance achieved. This approach is applied, when the performance is better than expected. If the performance is less than expected, it will attract exception-based review.