Laserfiche WebLink
<br />. <br /> <br />. <br /> <br />l-t 17 <br />C.Jl <br />tv In considering the four options, our analysis was based upon the following <br />~ dominant criteria that seemed to emerge from the interview data. We <br />believe that any change in the organizational structure should attempt to: <br /> <br />1. Provide a central focal point for the SCPo <br /> <br />2. Recognize the need for Regional Directors to maintain control of <br />ongoing work within their regions. <br /> <br />3. Maintain a high visibility for the SCPo <br /> <br />4. Maintain an "advocate" to "champion the cause" of the SCPo <br /> <br />~. Combine the "authority" and "responsibility" of the SCPo <br /> <br />6. Conserve personnel ceiling slots and eliminate unnecessary layers. <br /> <br />7. Reflect the actual work program through the setting of priorities. <br /> <br />8. Be politically feasible, i.e., meet the needs of constituents and <br />internal managers. <br /> <br />Option A - Retain Current Organizational Structure and Implement <br />Non-Structural Solutions <br /> <br />While this option was included as a basis for comparison for the other <br />options, we believe that its primary strength is that such a compromise may <br />well be the best solution the Service is capable of achieving at this <br />time, given the apparent diverse needs of those involved. Also, many of <br />those interviewed both inside and outside the Service believe that consider- <br />ing the constraints and restrictions of our processes and procedures, the <br />SCP is functioning fairly well, and communications are fairly good among <br />the primary offices and should not be tampered with. <br /> <br />Advantages <br /> <br />Disadvantages <br /> <br />Not working that badly; progress on <br />program is being made. <br /> <br />Perceived "split" in authority <br />responsibility. <br /> <br />Recognizes Regional Director <br />authority. <br /> <br />Conflict has resulted between CRWQP <br />and RD's. <br /> <br />Maintains central contact point <br />and visability. <br /> <br />Some confusion from outside entities, <br />e.g., FWS and SCS, on when to go to <br />CRWQO and when to go to RD. <br /> <br />Maintains "Advocate" for SCPo <br /> <br />Field offices get conflicting mes- <br />sages from CRWQO and RD; confusion <br />resul ts. <br />