Capacity-to-deliver thinking

  1. There are 2 aspects of any functional output – ‘What’ and ‘How’. The ‘What’ is whether you are doing it in a Blast Furnace, Pellet Plant, etc. They may be different contexts, but the deliverable is the same – the how.
  1. In any system, when there is a matrix of specializations on one side and there are deliverables on the other side, there is a group of people responsible for making these deliverables happen and ensuring these specialized competencies tie up. In short, there is a need for people who will deliver what is needed for the project. And further, all these deliverables are combined by the Engineering Manager in the G6.
  2. This space of “capacity to deliver” has been shown below:

At one end there is a DU. As part of a DU, say an engineering manager is assembling multiple resource deliverables which s/he is tying up to the DU.

On the other side, there are i) a set of expert groups/ specialists and ii) reusable packages, iii) There are deliverable teams of 1 or more people who use their own knowledge work and inputs from experts and they are responsible for deliverables, and pre-packages, if any, can also be used by the deliverable teams to meet commitments faster & better.

  1. While this is the framework, the key question is how to improve the capacity-to-deliver of the functions.

Clarify your doubts & questions about the model with the Implementation Team: Post your question