1,351
edits
Governance: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
=== Acceptance of proposals === | === Acceptance of proposals === | ||
With system planning, a team prepares proposals for action that have been [https://eit.engineers.scot/index.php?title=Top-down_strategy#Test_proposals thoroughly tested] and are based on a consensus view of the members of the team. | With [https://eit.engineers.scot/index.php?title=Main_Page#System_planning system planning], a team prepares proposals for action that have been [https://eit.engineers.scot/index.php?title=Top-down_strategy#Test_proposals thoroughly tested] and are based on a consensus view of the members of the team. | ||
When acceptance or rejection of proposals is the responsibility of senior management or of a client, the following fundamental principle of good governance should be adopted: | When acceptance or rejection of proposals is the responsibility of senior management or of a client, the following fundamental principle of good governance should be adopted: | ||
| Line 8: | Line 8: | ||
Changes to proposals from system planning should only be made on the basis of further proposals that have also been thoroughly tested. | Changes to proposals from system planning should only be made on the basis of further proposals that have also been thoroughly tested. | ||
</div> | </div> | ||
If the proposals from system planning are challenged by the client/management, the matter should be referred back to the planning | If the proposals from system planning are challenged by the client/management, the matter should be referred back to the planning team. The client should not jump to a conclusion on the basis of what seems to be a good idea. With complex uncertainty the risk in doing that is likely to be unacceptably high. | ||