Bob Baird, Author at Inverse-Square
archive,author,author-inversesquare,author-2,ajax_updown_fade,page_not_loaded,,qode-content-sidebar-responsive,qode-child-theme-ver-1.0.0,qode-theme-ver-12.0.1,qode-theme-bridge,wpb-js-composer js-comp-ver-6.4.1,vc_responsive

Author: Bob Baird

In any business, time is money, with the upshot being that labor is money. Nearly every business has looked for ways to save money by reducing the amount of labor required to perform a task. Manufacturing companies have turned this into an art form through a variety of industrial engineering activities such as operations management, ergonomics, system simulations, and ongoing performance analysis of each step in the manufacture of a part. By reducing the time to perform each action, businesses can achieve significant cost savings across their organization. You can also apply this concept to business operations. The advancements in computing hardware and software have accelerated the adoption of process automation in the office, not just on the factory floor.

When figuring out whether it makes sense to buy or build (check out our infographic to help you with this decision), you might think that a big con to building might be the cost. Most people associate anything custom with being expensive....

I'm not really sure how it happened. I swore off formal process control documents when I left corporate life fifteen years ago, yet here I sit writing a blog post defending the use of Change Requests (CR) forms and actually meaning what I'm saying. I've grown to love CR forms, and I think our clients should too. Ask anyone who's been in a contract relationship how they feel about CR forms and the response is almost unanimous, they love to hate them. The reason is pretty straight forward; they tend to add project cost, slow things down and remove freedom. I used to feel the the same way and then I had to have one too many hard conversations at the end of a web application development project.
As I sit here writing this, my broken leg elevated in an uncomfortable recliner, I can’t help but think about unforeseen challenges when it comes to software development. The inconveniences and set-backs of a broken bone can be related to the tribulations of an engagement. As our Senior Application Architect, Jesse Bacon describes, “It is inevitable that an intricate application is bound to have unforeseen challenges. It is ultimately how we prepare to meet these challenges and not necessarily how we react to them.