Taking Smaller Steps

Have you ever worked really hard on something, only to find out that what you did wasn’t what someone wanted?

Instead of doing everything at once, take smaller steps. Implement only what is needed, not only because you may not know tomorrow’s exact needs, but also because people dislike change. It is easier to introduce slow change and get buy-in at each stage, than to put it all out there.

The other side effect: you can get input before assuming the way someone plans on consuming your ministry or a service of your ministry. Then, adjust as you go rather than forcing people to use what has already been implemented or throwing away a lot of effort. This is the biggest problem with software development (my profession): developers assume they know what the customer wants, and customers assume the developers can read their mind and/or intent.

Deliver early, deliver often, get buy in each step of the way, and don’t assume you know what people want or that people will tolerate the change.

Popularity: 1% [?]