I think I might have the answer to your question. I am a senior manager of the IS department where I work - BUT - I am also a very technical person as well - that's where my roots are - so to speak.

My observation from being in this industry for about 20 years now - and most of that time being in the position where you find yourself - lends me to my observations on this topic.

1. Managers usually are faced with a particular topic or challenge where they need technical support or a technical solution.

2. In their attempt at providing the solution for those that are seeking it and not knowing what the proper solution should be - attempt to draw out a solution via an interative process that will ultimately fit the needs of the business model in question.

3. This process ultimately provides answers - usually by accident. This process is also very inefficient for those in the trenches.

There has been a surge recently to provide better means of process improvement - this includes but is not limited to design of systems. One of the most highly regarded BPM (Business Process Management) methodologies around today is Six-Sigma.

I am a huge proponent of 6s as it does tend to streamline and clarify processes and expected outcomes within an attainable set of expectations. It also helps reduce the "waste" in the process (ie - the multiple iterations).

Another point of view is that of RAD - Rapid Application Development - the process that you are witnessing is symptomatic of that approach. Do it - present- refine - present - refine - present - accept.

As a technical person and a manager I find that both work well - in the end. It is not necessarily how fast one gets to the solution - but how well the solution is in relation to the strategic direction and business objectives of the company. Many times unfortunately, that path is not clear and needs a bit of prodding (the iterations and continual changes) to find the solution to the question that was not formed perfectly to begin with.

We are all human - and managers like the rest of us - do not want to look foolish in front of our peers and bosses - so it is easier to not complete the thought process when our bosses are not around (adopt the RAD approach).

Just my views - I hope this helps.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.