Things to Know Before Submitting an IT Project or Innovation Request
The IT Project and Innovation Request process is a structured pathway for submitting technology-enabled ideas, improvement opportunities, and project requests. It is designed to help Stan State identify business challenges, evaluate strategic value, assess feasibility, and align potential work with OIT capacity, governance, and the budget cycle.
This process is not a suggestion box or a shortcut around governance. Submitted ideas may be reviewed, refined, and routed through the appropriate path before work begins.
Requests may be directed to a Help Desk ticket, IT initiative, formal IT project, proof of concept, pilot, operational work, budget request, or other appropriate next step.
What to Submit
Staff and faculty may submit ideas or requests that involve a technology-enabled improvement, service, system, process, integration, automation, data need, accessibility requirement, security concern, or other institutional opportunity.
Examples may include:
- A new or improved service, product, system, or application
- A process improvement or automation opportunity
- A systems integration or reporting need
- Replacement of an obsolete system or process
- Work required by CSU mandate, audit finding, policy, or law
- Responsible use of AI or other emerging technologies
- Work that may require cross-department coordination or significant OIT effort
For routine support, maintenance, or service needs expected to take fewer than 40 hours, please submit a Help Desk ticket instead.
How Requests Are Reviewed
Submitted ideas are reviewed to determine the appropriate path. Promising ideas may be shaped into a Business Challenge Brief before being considered for prioritization.
Review may consider:
- The problem or opportunity being addressed
- Impact on students, faculty, staff, operations, or the broader campus community
- Alignment with university priorities or strategic goals
- Estimated work effort, complexity, risks, dependencies, and constraints
- Security, accessibility, compliance, data, reporting, and support needs
- Funding needs or budget-cycle considerations
- OIT capacity and campus partner availability
- Whether the request is required by mandate, audit finding, policy, or law
The IT Project Priority Committee determines whether an item should move forward to discovery, proof of concept, pilot, operations, formal project work, budget request, deferral, or decline. If you have any questions regarding this process you can reach out to John Rezendes