Mocking Change

In software development mocking is a deliberate effort to simulate other system elements, such as a database, with a representation of the element in order to test a portion of the software without interacting with the actual database. Mocking is a tactic to make sure that software works as expected throughout the development process and when changes are introduced.

When facing the implementation of a big change in a business process or initiative, why not mock the elements of the change that might be complex or difficult in order to solicit as much feedback as necessary about what might go wrong or isn’t getting adequate consideration to ensure a positive experience for all the participants and stakeholders?

 

photo credit: Teddybear Junction / CC BY 2.0