Home About Leadership News Issues Tabulators Contact Us Clerk Accessability

Picture of path into desert

Honesty, Integrity, Competence, Transparency

Please see below for links to issues that I am working or have worked.

Please send suggestions and comments to my issues management system. You can also post your ideas in response to social media posts as well.

Why am I doing this?

My profession is about helping people. My experience with business information systems is all about implementing better ideas. These new ideas are mostly driven by customers who use the systems. I take their ideas and figure out how to implement them. In the process I make suggestions for improvement as well.

How will these ideas be implemented?

NOTE: The description below assume that I have control over the decisions required. In most cases I have no control as to what is implemented or how it would be implemented. However, I can suggest how they might be done. If I do have control I will provide more details in the relevant discussions.

The implementation details are usually not understood up front. We start with general concepts and work out the details as we go. At this point I am looking for any and all ideas. The possibilities are boundless. Consider this a wish list.

Later we will evaluate the ideas for feasibility and prioritize them for implementation. This often entails a benefit/cost analysis to ensure that we are working on the most important and beneficial ideas first. Due to limited resources, some ideas may never be implemented but we will at least consider them and catalogue them for future reference.

Next we will start investigating the implementation details and come up with rough planning estimates. Although plans are rarely followed as written, if you fail to plan you plan to fail. The question is, when will you fail. Too often in information systems development the failure is at the end of the project. This is very wasteful. Ideally, you want to identify issues (potential failures) as early in the project as possible. This allows time to adjust and change plans in the most cost-effective manner.

Ideally the process improvements and automation are implemented in small increments with a focus on usable functionality at the end of each increment. This ties in well with early identification of issues and quick adjustments ultimately leading to a successful project or, in some cases, a project that is terminated before completion if the circumstances dictate. Failure should occur early in order to save time and money if the project is not going to be a success. Also, a project might be successful even if not completed as planned. Success might come early before all planned features are implemented if the features implemented so far are of sufficient value that there is no need to complete the rest.

What is the significance of the picture on this page?

Developing information systems and automating business processes is not like constructing buildings. You can not specify all of the details up front. Instead you start with a general picture of the path you will be traveling and some environmental factors to be aware of. You then identify requirements and plan accordingly with the information that is currently available to you. As you travel down the path you become more aware of the details and make adjustments to your requirements and your plan to reflect the latest information available to you.