Bryan Skwirut

Deeply researched project management, transformation, change, and career advice

[Bryan Skwirut @bskwizz]

@lennysan I had so many “why’s” today we brought it back to the big bang.

[Bryan Skwirut @bskwizz]

https://t.co/Hg3zHoPoeD

[Bryan Skwirut @bskwizz]

Ever wondered what the differences are between a project manager and a program manager?

I also cover tips to landing your first PM role.

Link below 👇

[Bryan Skwirut @bskwizz]

Project Managers, Program Managers, and Transformation Leads - What's the biggest change to your role and work in the age of AI? (this is for a piece I'm writing)

[Bryan Skwirut @bskwizz]

@mattshumer_ Building agentic workflows over here 👋

[Bryan Skwirut @bskwizz]

@broookscooks @chamath Fair question, but this is about operating margin. Time only matters if it shows up in margin. This reads like token spend is funding adoption, not margin expansion. That’s fine, but let’s call it what it is.

[Aaron Levie @levie]

Another week on the road meeting with a couple dozen IT and AI leaders from large enterprises across banking, media, retail, healthcare, consulting, tech, and sports, to discuss agents in the enterprise.

Some quick takeaways:

* Clear that we’re moving from chat era of AI to agents that use tools, process data, and start to execute real work in the enterprise. Complementing this, enterprises are often evolving from “let a thousand flowers bloom” approach to adoption to targeted automation efforts applied to specific areas of work and workflow.

* Change management still will remain one of the biggest topics for enterprises. Most workflows aren’t setup to just drop agents directly in, and enterprises will need a ton of help to drive these efforts (both internally and from partners). One company has a head of AI in every business unit that roles up to a central team, just to keep all the functions coordinated.

* Tokenmaxxing! Most companies operate with very strict OpEx budgets get locked in for the year ahead, so they’re going through very real trade-off discussions right now on how to budget for tokens. One company recently had an idea for a “shark tank” style way of pitching for compute budget. Others are trying to figure out how to ration compute to the best use-cases internally through some hierarchy of needs (my words not theirs).

* Fixing fragmented and legacy systems remain a huge priority right now. Most enterprises are dealing with decades of either on-prem systems or systems they moved to the cloud but that still haven’t been modernized in any meaningful way. This means agents can’t easily tap into these data sources in a unified way yet, so companies are focused on how they modernize these.

* Most companies are *not* talking about replacing jobs due to agents. The major use-cases for agents are things that the company wasn’t able to do before or couldn’t prioritize. Software upgrades, automating back office processes that were constraining other workflows, processing large amounts of documents to get new business or client insights, and so on. More emphasis on ways to make money vs. cut costs.

* Headless software dominated my conversations. Enterprises need to be able to ensure all of their software works across any set of agents they choose. They will kick out vendors that don’t make this technically or economically easy.

* Clear sense that it can be hard to standardize on anything right now given how fast things are moving. Blessing and a curse of the innovation curve right now - no one wants to get stuck in a paradigm that locks them into the wrong architecture. One other result of this is that companies realize they’re in a multi-agent world, which means that interoperability becomes paramount across systems.

* Unanimous sense that everyone is working more than ever before. AI is not causing anyone to do less work right now, and similar to Silicon Valley people feel their teams are the busiest they’ve ever been.

One final meta observation not called out explicitly. It seems that despite Silicon Valley’s sense that AI has made hard things easy, the most powerful ways to use agents is more “technical” than prior eras of software. Skills, MCP, CLIs, etc. may be simple concepts for tech, but in the real world these are all esoteric concepts that will require technical people to help bring to life in the enterprise.

This both means diffusion will take real work and time, but also everyone’s estimation of engineering jobs is totally off. Engineers may not be “writing” software, but they will certainly be the ones to setup and operate the systems that actually automate most work in the enterprise.

[Bryan Skwirut @bskwizz]

Hot take: the companies best positioned for agentic AI transformation may be the ones that successfully offshored work over the past 20 years.

To offshore you had to codify everything. Runbooks, SOPs, defined inputs. That discipline is what agents need. Potentially an advantage.