Reach each objective in as few steps as possible and think in terms of outcomes, so solutions stay practical. Drop any process, service, action or measure that does not produce value or a useful result. Write general rules for dealing with exceptions instead of designing an answer for each one. Begin simply and add controls, activities or measures only when they are really needed, deciding what to keep by how it helps create value, indirect value such as regulatory compliance included. Watch for clashing aims, such as managers wanting more data while those keeping records want easier entry, and agree a balance. Secure value; keep design simple; do fewer things and do them better; do not waste people's time; and remember that what is easier to grasp is more likely to be taken up.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.