Change is a challenge

By Kenneth Van Coppenolle, Feb 28th 2017

When you finally release that new application you have been working on, it is important to remember that this is just the first stage in its life. All products evolve, and changes will be required sooner or later. And some of those changes may become obstacles. How will you deal with people already using your application?


People are creatures of habit. They like to stick with things that work for them. It can be tempting to try to impress everyone with a new release that is filled to the brim with new features and improvements, but you risk overwhelming and frustrating end users by doing this. Remember: if user adoption fails, your product fails.


An alternative approach is to release early, and release often. This offers a number of benefits both technical and non-technical and pleases all involved stakeholders:

  • The impact on end users is much smaller; change one thing and many users won't even notice it. Change everything and people will get confused.
  • If changes make it to the application sooner, you can get more valuable feedback from a broader audience
  • End users can get improvements to features they use, without having to wait for you to complete work on features they don't use
  • The smaller the release, the less likely it is that something will break
  • When something does break, it is much easier to find the cause - and to fix it

This is not a synonym for impulsive and unplanned; but rather a philosophy that can make life easier for product owners, end users and developers alike.


Change is good.

Kenneth Van Coppenolle is one of our digital workplace architects that develops, maintains and deploys numerous applications for our customers.

sharing is caring