Image via Wikipedia
When I was in high school, I learned BASIC programming. We connected to a mainframe computer someplace by using a phone coupler and dialing in. There was no monitor; every interaction with the computer was typed on a long sheet of paper. Programs were written and submitted via punch-tape. I know – ancient history. But some of what I learned is applicable today and I want to discuss on bit of logic coders use all the time which has business implications (or might even be a best-practice): the “if-then” statement.
In its simplest form, this is just a programming subroutine, or a series of nested subroutines (statements which follow from previous statements) that take the form of a decision tree. If X happens, do Y. If a user says something is true, then do this next. Otherwise (the “else statement”) do something completely different. Dead simple. In fact, it’s so simple I wonder why more business people don’t do it as a routine part of running their businesses.
I’m always surprised how often folks are caught flat-footed in responding to events, particularly events that can be foreseen, even if the odds of them occurring are small. I was always taught in programming class that you had to try to anticipate every outcome as best you could or the odds were good the program would stop at a dead-end. So does your business.
Listing out “if then” statements for both successes AND failures can help you more quickly respond and recover. I think this is one of the most important functions senior management can demand of subordinates since those subordinates are usually a lot closer to the events and the possibilities.
If you’re not planning and projecting out what happens when you win as well as when you don’t, then you’re not ready to compete and win. If – then. Simple, but not. Thoughts?
Consult Keith 