Project Management

Please login or join to subscribe to this thread

Moving from "Firefighter" to "Architect": How Are You Evolving Your PM Role in the Age of Data & AI?

linkedin twitter facebook   Artificial Intelligence   Career Development   Leadership  
avatar
Chia Fang Chang
Community Champion
PM Consultant| CLOUD SAFE CO., LTD. New Taipei City, NWT, Taiwan

Hi everyone!

In today’s fast-paced, data- and AI-driven landscape, I’ve been reflecting a lot on how our day-to-day responsibilities as project and technical leads are shifting.

Too often, project teams get caught in the endless cycle of "fixing pipes"—dealing with brittle, hard-coded logic, wrestling with messy data formats, and constantly reacting to operational bottlenecks. While keeping the lights on is necessary, it often pulls us away from high-value architectural planning and strategic leadership.

Real progress isn't about patching broken workflows; it's about leveraging modern tools to rethink project architectures:

  1. Automation Over Hardcoding: Shifting focus from manual troubleshooting to high-level governance and workflow design.
  2. Seamless Integration: Utilizing tools like modern serverless data integration to keep data flowing effortlessly into AI models.
  3. Role Evolution: Transitioning from an operational firefighter on the front lines to a strategic conductor orchestrating the entire system.

By refusing to confine ourselves to rigid, traditional role definitions, we open up a much broader vision for technology and project delivery.

In your daily routine, what percentage of your time is spent "firefighting/fixing pipes" versus "orchestrating as a strategic conductor"? What tools, frameworks, or mindset shifts have helped you or your team make that leap?

I’d love to hear your experiences and insights!

Sort By:
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Chia Fang, I agree that AI creates an opportunity to move project professionals away from repeatedly absorbing operational problems and create more capacity for strategic and integrative work.
I would hesitate, though, to frame the evolution simply as moving from firefighter to architect.

Firefighting is not necessarily low-value work, and architecture is not necessarily within the project manager’s authority.
The more important question may be why particular problems keep reaching the PM and whether they require intervention, redesign, different decision rights, or a different allocation of work between people and AI.

I would also be careful with the idea of the PM as the conductor orchestrating the entire system.
In increasingly distributed environments, knowledge, expertise and authority may reside in different places. Integration remains essential, but it need not mean centralization.

So perhaps the real evolution is from personally absorbing complexity to helping create the conditions through which complexity can be sensed, interpreted and acted upon coherently across people, AI and the wider organization.

And if we expect PMs to shape those conditions, we also need to ask whether they have the legitimate authority and decision rights required to do so.
avatar
Syed Ashir Riaz
Community Champion
AI-Powered Social Media Strategist
I reduced my firefighting time from 80% to 30% by adopting an "automate first" mindset for repetitive tasks.
For example, instead of manually chasing the team for status updates, I use automated dashboards that flag risks instantly so I can focus on planning solutions.
avatar
Lissette Indhira Pimentel Sosa
Community Champion
Program Manager| HARPER SRL Santo Domingo / Distrito Nacional, Dominican Republic
It varies depending on the project and the stage it is in, but I still see firefighting taking more time than it should. One thing I’ve been trying to do is look at recurring issues instead of treating each one as a separate problem.

If the same type of issue keeps coming back, there is probably something in the process, ownership, or way we are working that needs to change. Fixing that gives me more time to focus on priorities, decisions, and what comes next.
avatar
Verónica Elizabeth Pozo Ruiz RYLAI Access Control Quito, Pichincha, Ecuador
Being a firefighter is the behavior of a Project Manager without experience, attending to failures after they occur.

An experienced Project Manager evaluates risks, establishes an adequate risk management plan, and determines risk responses.

Risk prevention can prevent most risks from occurring, and if the risk finally happens, there is a plan and a fast response that allows the project to get back on track.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Talk low, talk slow, and don't say too much."

- John Wayne

ADVERTISEMENT

Sponsors