Redefining Functional Tribal IT Leadership and AI Approaches

Most functional leaders I talk to describe their AI plan as giving their people better tools. Procurement gets a contract summarizer, HR gets a drafting assistant, and finance gets faster reconciliation. Each helps, and none changes what the function is. A department built on the assumption that reading, drafting, matching, and routing are expensive human tasks doesn't become a different department just because those tasks got cheaper.

In the Army, a staff section built around couriers and typed orders didn't improve much when it got radios. It improved when someone redesigned the section around what instant communication made possible, including who needed to be in the room and which steps could disappear. AI puts every functional leader in that same position. The useful question is what your function should look like if most of its current effort became nearly free.

Procurement shows it clearly. If AI can read every contract, flag every deviation, and monitor every vendor continuously, the buyer's job moves from processing requests to negotiating strategy and managing supplier risk. HR follows the same path: when benefits questions and policy interpretation are handled automatically, HR staff spend their time on the conversations that require trust. Finance shifts from closing the books to advising on decisions, since reconciliation and variance analysis no longer consume the calendar.

IT and legal change in less obvious ways. IT stops being the group that builds and supports applications and becomes the group that governs which systems may act on the organization's behalf, with what data, and under whose authority. Legal moves from reviewing documents one at a time to setting the rules that automated review operates under. In both cases, the work becomes judgment about boundaries, and that is harder to hand to a tool than the work it replaces.

Tribal enterprises tend to run lean functions that carry heavy compliance and sovereignty obligations. Every hour freed from routine processing can go toward work that protects the nation, which is a stronger return than most commercial organizations can claim. Leaving a function as-is keeps a small team busy with tasks a machine could already handle.

Redesign is uncomfortable for the person leading it, because it requires admitting that parts of the current structure exist because of old constraints. Leaders who do this work will rewrite job descriptions, move their people into higher-judgment roles, and tell their councils plainly what the function now delivers. Those who wait will find a vendor has drawn the new boundaries for them.