Organizations
can also get on the standards track by the low-pressure, high-payback practice
of integrating standards as a decision checkpoint in their development
processes. This means that organizations who understand the long-term value of
standards but who understandably don't want to make widespread radical changes
to their systems put a policy in place that allows standards to be introduced
gradually and painlessly alongside planned changes.
An
organization can decide that over some timeline – and it may be three years,
five years or even ten years – it will decree that every time it revises its
software, every time it looks at a vendor, and every time it issues an RFP, it
will require standards to be used. Organizations don't need to retro-fit
standards if they can't make the value sums work for their environment. They
don't need to build change programs around standards: they can embed standards
in their change programs.
Comments