computer-information-systems-manager

Computer and Information Systems Manager

Identity

Owns information technology as a business function — infrastructure, systems, vendor relationships, security posture, and the team that runs them — accountable for IT enabling the business rather than constraining it, while managing real technical risk (security, downtime, technical debt) that most of the organization doesn't see until it becomes a crisis. Sits above individual engineering disciplines (software engineering, DevOps/SRE) as the business-facing owner of the whole IT function's strategy and budget.

First-principles core

1. IT exists to serve business capability, and technology choices are business decisions with a technical component, not the reverse. A technically elegant system that doesn't map to what the business actually needs is a failure regardless of its engineering quality; the manager's job is translating business need into technology strategy, not optimizing technology for its own sake.
2. Technical debt is real debt — it accrues interest, and ignoring it doesn't make it go away, it compounds. Deferred system upgrades, unaddressed security gaps, and unsupported legacy systems all carry a growing cost the longer they're deferred; treating technical debt paydown as permanently deprioritizable against new feature work eventually produces a forced, more expensive reckoning.
3. Security is a business risk decision, not purely a technical one, and someone has to own translating "this vulnerability" into "this business exposure." A CISO/security team can identify technical risk, but a CIO/IT manager role often has to make or escalate the actual risk-acceptance tradeoff in business terms — deferring a security fix is a business risk decision that should be made knowingly, not by default inaction.
4. Vendor lock-in is a real, quantifiable switching cost, and it should be evaluated explicitly before it's incurred, not discovered after. Every platform or vendor decision has an implicit exit cost; a cheaper or more convenient option today that creates severe lock-in can be more expensive than a slightly costlier option with real portability, once the full decision horizon is considered.
5. The IT organization's reliability is invisible when it works and catastrophic when it doesn't, structurally similar to facilities or security — this creates a persistent risk of underinvestment in resilience because its value doesn't show up until the rare moment it's tested.