HCI IT AWP Apr 27, 2026 [HCI CA]

https://docs.google.com/spreadsheets/d/1y8elnqIE1AG390wraDzg8L6UX2B6Ds1I5we_Q4YEGrA/edit?gid=564078312#gid=564078312

Thanks for sharing this. Looking at the list, it’s clear your team is the "engine room" for the organization—handling everything from fundamental support to specialized fundraising tech.

However, if I’m being honest (and a bit witty), your "Day to Day" list looks less like a plan and more like a broken record. Repeating the same tasks 12 times suggests you're thinking in monthly buckets, but it makes the actual strategy hard to find.

Here is my breakdown of your plan’s strengths and the "red flags" you should address before presenting this to leadership.


### 1. The "Big Ticket" Reality Check

Your big projects are high-value, but they are massive in scope.

  • ERP Implementation (Odoo): This is a beast. If you are doing this while managing the repetitive "Day to Day" tasks listed, your team is at high risk for burnout.

  • Omatic Cloud & Data Automation: This is a smart move. Automation is the only way to escape the "Day to Day" loop you’ve described.

  • IT Security: You’ve listed Email and Endpoint security. In 2026, these are "table stakes." Ensure you have a specific timeline for these, or they will constantly be pushed aside by "urgent" donation form requests.


### 2. Strategic Red Flags 🚩

  • The "Repetition" Trap: Your "Day to Day" section lists 12 iterations of the same tasks. While I get that these happen every month, a work plan should focus on process improvement. Instead of "Address service requests x12," the goal should be "Reduce ticket resolution time by 15% via a new knowledge base."

  • Ad-hoc Projects: You have "Adhoc Projects" listed under Big Tickets. Warning: "Ad-hoc" is where productivity goes to die. If you don't cap the time spent on unplanned requests, your ERP and Security projects will never finish.

  • Data Health: You have "Data Health Actions" as a milestone. Data health is usually a state, not a one-time event. You might want to define what "Healthy" looks like (e.g., "95% record accuracy").


### 3. Suggested Refinements

To make this look like a professional Transformation Plan rather than a to-do list, I’d suggest grouping your tasks into three pillars:

Pillar

Focus Area

Key Outcomes

Operational Excellence

Service Desk, ITAM, Asset Tracking

Moving from "reactive" to "proactive" support.

Digital Transformation

Odoo ERP, Omatic Automation

Consolidating tools and reducing manual data entry.

Governance & Risk

Security, Policy, IT Reporting

Protecting donor data and ensuring compliance.


### Summary Verdict

The good news: You are focused on the right things (Automation, ERP, Security).

The bad news: Your current formatting hides your value. If I’m your boss, I see a team that is overwhelmed by repetitive manual tasks ("Set up donation forms x12").

My advice: Focus the "Day to Day" section on SLA targets (how fast you help people) and use the "Big Ticket" section to show how you are going to eliminate those repetitive tasks through the Odoo and Omatic implementations.

Does your team currently have the headcount to manage the Odoo rollout while still handling the daily "firefighting" of service requests?