Please enable JavaScript.

Coggle requires JavaScript to display documents.

IT loses effectiveness when it has no process, no ownership, and no real…

- - - - IT never wrote down how the system works or how to request changes
    - - No process was ever built for documentation or prioritizing requests
    - - A new IT person picks it up cold every time
    - - Same explanation over and over, delays real fixes
    - - Wastes time relearning something they should already know
    - - HR loses trust and patience in IT
    - - IT management
  - - - No specific person or group owns the orientation system
    - - Treated as a side task, not a real responsibility
    - - Whoever gets assigned gets pulled onto other projects
    - - Work never really finishes, nothing carries over
    - - Resources spread with no clear priority
    - - HR cannot count on a fix schedule
    - - IT leadership
  - - - Known bugs were never fixed
    - - No long term owner to catch and fix them
    - - Registration caps and cancellations were not shown in the system
    - - Wrong session mix, Cascade pays for empty hotel rooms
    - - Looks incompetent
    - - Real avoidable cost and a worse new hire experience
    - - IT, tracing back to no ownership or process
  - - - IT and HR only talk once a year when Maggie tracks someone down
    - - Nick does not fully trust the consultant's review that created Ryan's role
    - - Nick calls it consultants needing to find problems
    - - Rest of IT may not take fixing the relationship seriously
    - - Keeps its reputation as disconnected from the business
    - - HR and other departments stay frustrated
    - - Nick and IT leadership
  - - - Don did not treat it as a real evaluation
    - - No weighting, no cost or effort numbers, vendor options skipped
    - - Don decided on his own an RFP was not worth the effort
    - - Ryan and Maggie have to start over
    - - Wasted the time already spent
    - - Delays the whole decision further
    - - Don
- - - - Purpose built system, not tied to the ERP timeline
      - Includes the vendors Maggie already found
      - Gives HR a real say in picking the system
    - - Takes time and possibly money to run the RFP
      - Still needs to integrate with the ERP later
    - - Next ERP release is a year or more out and not guaranteed to cover everything
      - CRM and scheduling tools already have known gaps
    - - Yes - Maggie already has vendor leads, and Cascade's own ERP vendor recommended a standalone system
    - - Appendix 1 shows most in-house options need heavy customization or come back unknown
      - Don's own admission that the ERP path is a year or more away