Pennings, A.J. (2026, Sep 06) The TSM Graduate in the AI Workplace. apennings.com https://apennings.com/digital-coordination/the-tsm-graduate-in-the-ai-workplace/

Introduction

This post frames one version of the TSM graduate as a systems manager who is technically fluent enough to work directly with AI and technical specialists, but whose primary responsibility is integrating technology with organizational objectives.

This changes the student’s conception of AI. They stop seeing AI as a chatbot or model and start seeing it as a networked computational infrastructure embedded in an organizational system.[1] That is precisely where TSM can distinguish itself from conventional computer science. CS students need to know how to build the computational components. TSM students need to understand how those components are assembled, governed, connected to people and resources, and converted into organizational capabilities and actions.

The key is not to turn the TSM graduate into a second-rate computer scientist. It is to develop a professional profile as someone who can understand technology deeply enough to direct it, understand organizations deeply enough to transform them, and understand AI deeply enough to work with it as a computational partner.

The TSM Graduate in the AI Workplace

A graduate entering the workplace with a degree in Technological Systems Management is entering an environment in which the boundary between management and technical work is becoming increasingly permeable. Artificial intelligence is making it possible for managers to participate directly in activities that once required specialized programmers and data engineers. At the same time, technical systems are becoming too complex to manage effectively without an understanding of organizations, strategy, economics, people, and institutional constraints.

The TSM graduate therefore occupies an important middle position. They are not simply a manager who happens to use technology. Nor are they simply a technologist who has learned management techniques. Their distinctive role is to connect organizational objectives with technological systems.

This becomes particularly important as AI changes the way software is produced. A manager can increasingly ask an AI system to construct a database, create a retrieval-augmented generation pipeline, develop an MCP server, connect an API, write code, test an application, or coordinate several specialized agents. The manager does not necessarily need to implement every component personally. But they do need to understand what those components do and how they fit together.

The TSM graduate therefore needs to develop three complementary capabilities: Technical literacy + Leadership capability + Management capability. These should not be treated as three separate areas of education. They should operate as an integrated professional system.

Technical Skills Mean Learning Enough to Build, Evaluate, and Direct

The first responsibility of the TSM graduate is technical competence. This does not mean mastering every programming language or becoming an expert in every AI framework. Technology changes too quickly for that to be a durable educational strategy. Instead, the TSM graduate should understand the architecture of contemporary computational systems.

They should be able to understand what happens when data enters a system, how it is stored and represented, how AI retrieves it, how models process it, how tools are connected, how agents coordinate, and how outputs become organizational actions.

A TSM graduate should therefore be comfortable with programming fundamentals, databases, APIs, cloud infrastructure, cybersecurity, data engineering, and systems architecture. They should also understand embeddings and vector databases, RAG pipelines, LLM APIs, tool calling, MCP servers, AI agents, and multi-agent orchestration.

The objective is not necessarily “I can build everything myself.” It is “I understand enough to determine what should be built, evaluate what AI has built, and work effectively with people who build it.” That distinction is critical.

A TSM graduate might use an AI coding system to construct an initial RAG application. They should nevertheless understand enough about embeddings, chunking, retrieval, metadata, reranking, provenance, security, and evaluation to recognize whether the resulting system is appropriate.

Likewise, they might ask AI to create an MCP server connecting an agent to an enterprise database. But they need to understand authorization, permissions, data exposure, logging, and failure modes before allowing that system into production. Technical competence thus becomes a form of managerial control.

The TSM Technical Stack

A useful progression for the TSM graduate is Programming -> Data -> Networks -> Cloud -> AI -> Agents -> Systems

– Programming provides the basic computational vocabulary.
– Data provides the material upon which organizations increasingly operate.
– Networks explain how computational resources communicate.
– Cloud infrastructure provides scalable computational capacity.
– AI provides increasingly capable computational reasoning and generation.
– Agents introduce planning and autonomous tool use.
– Systems thinking connects all of these components to organizational objectives.

The graduate does not need to become a specialist in every layer. They need to understand the interfaces between the layers. That may ultimately be one of the most valuable technical skills in the AI workplace.

Leadership Skills that Direct People and AI Together

The second capability is leadership. AI changes leadership because the manager increasingly has two kinds of collaborators, people and computational agents. A manager may eventually supervise a team in which several employees work alongside specialized AI systems. A researcher may have an AI research assistant. A financial analyst may work with an analytical agent. A software team may use coding agents. A marketing group may employ agents for customer analysis and content production. The leadership problem consequently becomes more complicated.

The manager must determine:
– What should humans do?
– What should AI do?
– Where should they work together?
– Where must humans retain authority?

This requires judgment rather than technical proficiency alone. A TSM graduate should become skilled at defining objectives, decomposing complex problems, assigning responsibilities, establishing decision rights, creating feedback mechanisms, resolving conflicts, and developing trust.

The manager’s job increasingly becomes one of orchestration.
This is an interesting parallel with multi-agent AI. A multi-agent system requires an architecture for distributing tasks among specialized agents. Organizations have always faced a similar problem with people.

The TSM graduate therefore needs to understand both. They should be able to ask “If this were an AI system, which agent would perform this task?” But also “Should this task actually be delegated to AI?” And “Who remains accountable for the result?” That is leadership in an AI-mediated organization.

Management Skills that Turn Technology Into Organizational Performance

The third capability is management. Technical systems have no organizational value simply because they are technologically sophisticated. Their value comes from what they enable an organization to accomplish.

The TSM graduate therefore needs to understand strategy, finance, operations, project management, organizational behavior, economics, risk, procurement, change management, and performance measurement. They need to translate between organizational language and technical language.

A senior executive might say “We need to reduce the cost of customer support by 30 percent.” A computer scientist might think “We need an LLM, RAG, vector database, and agent architecture.” The TSM graduate needs to bridge these statements. They should ask:

What is actually causing the cost?
What information does the organization possess?
Where are the bottlenecks?
Which processes are suitable for automation?
What should remain human?
What technology is required?
What will implementation cost?
How will performance be measured?
What risks are introduced?
How will employees respond?
And ultimately:

Does the system improve the organization’s ability to accomplish its objective? That is the management contribution.

The New Skill Is Integration

This suggests that TSM should not be organized around the idea that students need to become experts in either technology or management. They need to become integrators.

The TSM graduate should be able to move in both directions.

From management toward technology:

Strategy -> Process -> Data -> Technology -> Implementation

And from technology back toward management:

Technology -> Capability -> Organizational Change -> Performance -> Strategy

The graduate becomes the person who can see the entire system.

This is increasingly important because AI reduces the cost of moving from an idea to a working prototype. The scarce resource may therefore shift from coding capacity toward problem definition, organizational knowledge, judgment, integration, and accountability.

The Manager as an AI Systems Architect

This is where the earlier discussion of AI engineering becomes particularly relevant. A traditional software project might have looked like:

Manager -> Systems Analyst -> Programmer -> Application

The AI-mediated organization increasingly looks like:

Manager -> AI -> Computational System -> Organizational Action

The manager does not disappear from the process. In some respects, the manager becomes more important because the cost of specifying and constructing computational systems falls.

A TSM graduate might tell an AI system: “Analyze our customer-support process. Identify repetitive activities. Examine the relevant documents and historical tickets. Design a RAG system for our support staff. Connect it to the knowledge base through an MCP server. Develop an agent that drafts responses but requires human approval before sending them. Create an evaluation framework and report the results.”

That is no longer traditional management. But it is also not traditional programming. It is AI systems management.

The TSM graduate is specifying the architecture, allocating responsibility, establishing constraints, evaluating results, and connecting computational capability to organizational objectives.

From Prompting to Specification

This also changes what we should mean by “AI literacy.” Prompt engineering is useful, but it is not enough. The more durable skill is systems specification. A TSM graduate should be able to specify:

Objective -> Data -> Process -> Model -> Tools -> Agents -> Human Oversight -> Metrics -> Governance

This is much closer to engineering than simply asking an AI chatbot questions. The graduate should be able to create a system specification and then use AI to help implement it.

In this model, AI becomes something like a computational workforce operating under human-defined objectives and constraints. The manager becomes responsible for the architecture of that workforce.

TSM and the Future of Computer Science

This also clarifies the relationship between TSM and computer science. Computer science will continue to produce specialists who understand algorithms, operating systems, distributed computing, databases, networks, AI models, security, and computational architecture at considerable depth. TSM should produce professionals who understand enough of those systems to integrate them with organizations.

The distinction might be expressed simply:

Computer Scientists will ask “how do we build the computational system? TS Managers will ask “How do we use computational systems to transform the organization?” The outcome is AI-enabled TSM that asks “How do we manage people, AI, technology, and organizational resources as one integrated system?” That third question may become increasingly important.

A TSM Professional Development Model

For a graduate entering the workplace, I would organize their development around four questions.

1. Can I understand the technology?

Learn enough programming, databases, AI, cloud, cybersecurity, APIs, RAG, vector databases, MCP, and agents to understand what is technically possible.

2. Can I design the system?

Learn systems architecture, process analysis, requirements analysis, workflow design, data architecture, AI orchestration, evaluation, and governance.

3. Can I lead the people?

Learn communication, negotiation, organizational behavior, team leadership, conflict resolution, decision-making, and change management.

4. Can I produce organizational value?

Learn strategy, finance, operations, economics, project management, risk management, and performance measurement.

The four questions form a professional progression:

Understand -> Design -> Lead -> Deliver

That is a powerful way to think about the TSM graduate.

The TSM Graduate as a Boundary-Spanner

Ultimately, the TSM graduate’s greatest advantage may be the ability to operate across boundaries. They can talk with the computer scientist about architectures. They can talk with the data engineer about pipelines. They can talk with the AI team about agents and RAG. They can talk with executives about strategy. They can talk with employees about workflow. They can talk with finance about investment. They can talk with customers about value. And they can increasingly talk directly with AI systems about how computational work should be performed.

This makes TSM particularly relevant to the workplace emerging around AI. The goal is not to produce graduates who compete directly with computer scientists, data scientists, or business managers. It is to produce graduates who can connect these professions.

The TSM graduate becomes the person who understands that a vector database is not merely a database, that an MCP server is not merely an API, that an AI agent is not merely a chatbot, and that multi-agent orchestration is not merely a programming technique. Each is a component of an increasingly integrated technological-organizational system.

And that may be the central competency of TSM in the AI era:

The ability to understand, design, lead, and manage systems in which humans and computational agents work together to accomplish organizational objectives. The traditional computer scientist learned to make computers compute. The AI engineer is learning to make machines retrieve, reason, and act. The TSM graduate must learn something broader: How to organize the people, technologies, AI systems, resources, and decisions that make those capabilities useful.

That is not simply management with more technology. It is the emergence of a new form of technological systems management.

Notes

[1] A networked computational infrastructure links various computers, servers, and hardware accelerators through communication networks to share data, balance workloads, and run large-scale applications. It invoves physical or virtual machines like servers, GPUs, and client devices that process and store information. It interconnects high-speed network fabrics, switches, and routers that move data between nodes with low delay. It uses centralized or distributed data repositories connected via dedicated backend networks.
[2]
AI Prompt(s) Take those last few responses and shape them into the perspective of a TSM graduate going into the workplace. How should they organize their technical, leadership, and management skills?

© ALL RIGHTS RESERVED

Not to be considered financial advice. AI is often used, and results are thoroughly interrogated. Links are used for some citations. Views are my own and do not express the stances of my employers, past or present.

---

Anthony J. Pennings, PhD is a Professor at the Department of Technology and Society, State University of New York, Korea and a Research Professor for Stony Brook University. He teaches AI and broadband policy. From 2002-2012 he taught digital economics and information systems management at New York University. He also taught in the Digital Media MBA at St. Edwards University in Austin, Texas, where he lives when not in Korea.

Related

Category: artificial intelligence, data analytics and meaning, digital coordination, enterprise systems, technology management
Tags: TSM

Comments

Comments are closed.