THE BREAKING POINT: WHEN GOOD INTENTIONS AREN’T ENOUGH
If you’re an IT leader in state or local government, you already know the drill. Departments are managing requests through inboxes, spreadsheets and phone calls. Projects get prioritized based on whoever is loudest, not what matters most. And your IT team? They’re stretched thin, fielding questions and completing manual tasks that should have been automated years ago.
That was the reality at the South Carolina Department of Commerce. As CIO, Doug Foster wasn’t dealing with a technology problem. Instead, he was dealing with an organizational alignment problem.
Project intake was, in his own words, “a little bit like the wild west.” The loudest voice in the room determined which initiatives moved forward. There was no standard mechanism to compare initiatives, no visibility across the portfolio, and no way to connect strategic objectives to daily execution.
“People were surprised,” Foster recounted. “They didn’t know projects were happening and consuming resources. It was a chaotic, hectic environment.”
Something had to change.
AN UNCONVENTIONAL STARTING POINT
What makes the South Carolina Department of Commerce’s story particularly instructive for other government IT leaders is how they approached this problem.
Most organizations begin with ITSM and get their help desk in order before expanding to other groups outside of IT. Foster’s team did it differently. They started with project portfolio management (PPM).
The logic was sound: Before you can manage services efficiently, you need to know what you’re actually working on. By first establishing visibility across all initiatives and scoring them against value drivers, risk, cost and strategic alignment, leadership could finally make rational decisions about where to focus resources.
More critically, that transparency diffused the political tension that often derails public-sector modernization efforts.
“The scoring mechanism really took a lot of the opinion out of the equation,” Foster explained. “When you add up the numbers, it becomes obvious which initiatives are worth pursuing. It doesn’t completely dictate decisions, but it removes the noise.”
Once leadership saw movement against strategic priorities with real, measurable progress, buy-in came quickly. That foundation of trust made everything that came next possible.
EXPANDING THE VISION: FROM ITSM TO TRUE ESM
With portfolio management proving its value, the team moved to IT service management (ITSM) and then introduced the concept of enterprise service management (ESM).
ESM is the idea that the same principles of structured, trackable, automated service delivery that work for IT can work for every department in an organization.
The response from other departments was not what Foster expected. It didn’t require a hard sell. It started with a conversation.
“We brought some leaders together and talked to them about their pain points,” Foster said. “It was a slow burn at first, but then more and more people started showing up to the conversation.”
HR was one of the first departments to see the potential. They were fielding a constant stream of “where is my request?” calls, manually tracking service levels that they couldn’t even articulate yet, and spending significant time on communication overhead that added no value. Once they understood what a structured service management approach could do for them, they were all in.
Then legal expressed interest. Then procurement. Then marketing — whose complex back-and-forth approval workflows turned out to be one of the most sophisticated use cases in the entire organization.
“It became obvious to the larger business community that this could be a solution to a lot of problems across the agency,” Foster said. “It was almost like word of mouth.”
WHY TEAMDYNAMIX? THE NO-CODE DIFFERENCE
For ESM to succeed across a government agency, the platform has to meet one nonnegotiable requirement: Non-IT departments must be able to own and operate it themselves. If every workflow change or form update requires a ticket to IT, the model falls apart.
This is where TeamDynamix’s no-code approach became the deciding factor. The platform’s visual, drag-and-drop workflow builder meant that HR staff and other non-technical employees could build and manage automated workflows on their own. Contract management automation that would have previously required months of development was up and running in about a month, built entirely without developer involvement, Foster explained.
“There are problems we’ve had for years that we just thought would be monumental to figure out,” Foster said. “We started in contract management. It’s now giving us automatic alerts one month before contract renewals. And this was done by somebody who is not a developer.”
The integration capabilities were equally compelling. As a Microsoft Intune shop, the department needed its assets synchronized with its ITSM tool. The process took 10 minutes, Foster said. TeamDynamix connected to Intune, pulled all the data and populated the system automatically.
“I’ve been doing this for about 40 years,” Foster noted. “I can remember people sitting with spreadsheets, pounding data into systems. By the time they’re done, it’s wrong, and they start over. This kind of automation brings a whole set of possibilities to light.”
The platform’s support for departmental language mattered too. TeamDynamix doesn’t force HR to call things “incidents” or require facilities to use “problem records” for what are clearly work orders. Each department can configure the platform to match how they actually work — a small detail with an outsized impact on adoption.
GETTING BUY-IN WITHOUT A HARD SELL
One of the most common questions IT leaders ask when considering ESM is: How do you get other departments to actually use it?
Foster’s answer is surprisingly straightforward.
“Showing them the product, demonstrating the capabilities, showing them one single integrated portal, it wasn’t a lot of selling,” he said. “Once they saw it, they were asking how to sign up.”
That “show, don’t tell” approach is backed by the improvements to the service consumer experience, as well. When employees can submit a request and track it in real time without calling their favorite HR contact to ask for a status update, they don’t resist the change. They embrace it.
“The user community has been overwhelmingly positive,” Foster said. “They feel like they’ve been given a gift. They can do this when they need it. It can be 8:00 at night, I can be in Germany, it doesn’t matter.”
HR, now the highest-volume user of the platform, manages its service workflows largely independently, consulting IT only for design guidance and total-cost-of-ownership questions. That’s ESM working exactly as it should.
WHAT THE RESULTS ACTUALLY LOOK LIKE
The South Carolina Department of Commerce didn’t just implement a new tool. They built a foundation for sustainable, scalable government service delivery.
Software license requests that once required IT staff at every step are now fully automated: An employee submits the request, their manager approves it through the portal and the software is available to download immediately. Contract renewals are flagged automatically. Assets are synchronized in minutes, not weeks.
The broader impact extends beyond efficiency metrics. Standardized business processes mean institutional knowledge is documented and preserved; this is critical in a government environment where turnover can erode operational continuity. New employees inherit structured workflows rather than undocumented tribal knowledge.
THE TAKEAWAY FOR GOVERNMENT IT LEADERS
The South Carolina Department of Commerce’s journey offers a clear blueprint for any state or local government IT leader looking to modernize. Start somewhere strategic, whether it’s portfolio management or a single high-pain department, and establish a visible win that builds trust and creates momentum.
Let the results do the selling; other departments will come to you once they see what’s possible. Choose a platform built for the reality of government, one where non-IT teams can own their workflows, integrations actually work, and the total cost of ownership is sustainable.
“For us, this has been an amazing journey,” Foster said. “It’s covered so much ground. The only regret I have is that we should have done this sooner.”
In government, that kind of outcome is worth paying attention to.
Want to see how TeamDynamix can help your agency make the move from ITSM to ESM? Explore the platform or watch the full webinar featuring Doug Foster and the South Carolina Department of Commerce.
Sponsor Content
From Chaos to Clarity: Transforming Service Delivery With ESM
What happens when a state agency decides it’s done with the “wild west” of project requests, siloed service management and email-based workflows? The answer is enterprise service management.
(Shutterstock)