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

Five Ways to Incorrectly Use Technology

How you adopt technology in your personal life is a personal choice. How technology is used in an organization affects many others, requiring careful consideration to provide its benefits without negative repercussions.

The top five ways organizations incorrectly use technology:

1. Implement a technology for technology’s sake.
2. Pick a technology because it is cool, trendy, or new.
3. Use it to fix a broken process.
4. Introduce it without adequate trials or testing.
5. Pick the version with the most bells and whistles.

I’m a big proponent for the use of technology when it is used in a way that truly supports the organization from every perspective. Nobody Likes Bad Change™ in technology, work, or life. Let’s do our part to introduce only good change:

• use the right technology
• for a specific process
• considering the available resources
• at the appropriate time
• to achieve the desired outcome

 

Photo credit: Qole Tech / CC BY 2.0

Resistance to Change – Inevitable or Preventable?

I hear and read about resistance to change frequently. Most of the time it is referred to in a negative light or as an inherent human weakness. Wouldn't it be more productive if we focused on the “Change” itself rather than the “Resistance”?

We have all been on the receiving end of change that didn’t work out well for us, so it is natural to be apprehensive. If we think back to one of those “bad” changes, can we think of ways the change could have been approached that would have made it a better experience for the both the leaders and the participants?

Resistance to change can often be prevented – and I don’t mean through the use of force, quite the opposite. Just a few ways to improve the adoption of change is through the application of:

• betas
• simplified learning tools
• prototypes
• pilot trials
• demonstration
• user experience observation and testing
• involvement

The general expectation is that change should be “good”. A common experience is that it isn’t. If change wasn’t actually “good”, we wouldn’t constantly be trying to introduce it. We should probably put more effort into making sure everyone that is impacted by the change understands the benefits and agrees that it actually is “good”. If they did, we probably wouldn’t be experiencing so much resistance.

Other posts about keys to successful change implementation