You've Been Innovating on Every Project. You Just Weren't Calling It That.
My parents are immigrants. Like a lot of immigrant households, ours wasn't overflowing with extras. What we had was what we needed, and it was enough.
What I remember most isn't what we lacked. It's what we built.
My brothers and I would get shoe boxes and turn them into castles, full castles, complete with working drawbridges, moats, and towers. We took empty two-liter soda bottles and constructed buildings with glass atriums. No instructions. No kits. Just materials, imagination, and the freedom to experiment without judgment. We didn't wait for better supplies, nor could we look up how to build what we imagined on YouTube or TikTok. We looked at what was in front of us and built something that hadn't existed before.
I didn't take the traditional path into project management. No single industry, no straight line. Over the years I've become something of a Swiss Army Knife, digital agencies, healthcare startups, enterprise SaaS organizations, nonprofits, solopreneurs. Each one a different context, a different constraint, a different definition of what "done" looks like. What I've learned: innovation doesn't have a minimum project size. It shows up in ordinary moments, in small teams doing real work with whatever they have. That instinct to build something that didn't exist before? That's the skill. Indeed it’s this same instinct that allows us to use AI as fuel for better work, rather than something to fear. And right now, with AI rapidly reshaping the execution layer of our work, owning it has never mattered more.
The Projects That Don't Make Headlines Are Holding Everything Together
Not every project I'm proud of made the case study. Some of the most meaningful work I've done happened inside a small nonprofit in Chicago, a team working to connect executive directors and community leaders with corporate partners who had more than just financial resources to give.
The workflows we introduced weren't revolutionary. But they were new to that organization. We adopted technologies, adapted existing ones, and centralized information scattered across inboxes, spreadsheets, and institutional memory. We built libraries and tools. We created SOPs. We established a cadence of communication that gave the team visibility they'd never had before.
What changed wasn't the mission. What changed was the friction. A small team stopped losing time looking for information. They stopped being reactive and started being proactive, freeing up hours for programming, new ideas, reaching more Executive Directors, and deepening connections with corporate partners. The actual work the organization existed to do.
The projects that quietly hold an organization together are rarely the ones that get celebrated. But remove them, and everything downstream slows down. Build them well, and the people around you get to do their best work. That's the foundation everything else is built on.
AI Is Doing the Easy Part. Now What?
Here's the uncomfortable truth: the parts of PM work that AI is best at absorbing are the parts that were historically most visible. Status updates. Progress tracking. Meeting summaries. Risk logs. Timeline reports. Tools like Infinity AI, and a growing ecosystem of project co-pilots can generate first drafts of all of it in seconds.
What made a PM indispensable was the ability to synthesize information and hold it in one place. Now the synthesis is cheaper. The holding is automated. And the PM who built their identity around those tasks is facing a real question: what am I actually here for?
I use AI, and it has genuinely changed how I work. Managing a book launch for a client, something I'd never done before, I used PMI's Infinity AI and ChatGPT to build a high-level dependency project plan. The prompt gave me a scaffold to stress-test and make my own. What had felt like an impossible web of moving parts became a coherent picture.
But here's what the AI didn't know: which dependency was fragile, which stakeholder needed extra runway, where the real risk was hiding. I knew that. The AI gave me speed. My experience gave it direction.
That's the work AI is not built for. The PM who built the workflow that stopped a team from drowning in manual updates did that. The one who pulled a book outline out of one person's head and made it findable did that. That work doesn't feel like innovation, but it's the ground innovation grows in, and no prompt can replicate it.
If your value was status updates and timeline management, AI will feel threatening. If your value is judgment and clarity, AI becomes leverage.
AI is flattening execution. PMs must now specialize in designing environments. Environment design is innovation.
Building the Room Where Good Work Happens
That means the PM role is evolving and the PMs who lead that evolution will be the ones who deliberately expand how they see their own value. It means:
Becoming strategic designers of work systems, not just managers of tasks
Moving closer to product thinking, understanding the why behind the work, not just the what and when
Developing business acumen so the decisions you make are anchored in outcomes, not just outputs
Owning innovation, not just enabling it, claiming the result, not just holding the process
When PMs don't see themselves through this lens, they stop building the conditions that make innovation possible. And that's where things quietly fall apart, not in a single missed deadline, but in the gradual erosion of team trust, creative risk-taking, and honest communication.
I led a project at a digital agency: improve the website metrics of an optics company. Limited resources. Fixed timeline. Lean team. Not glamorous, but the opportunity was bigger than the brief.
My job wasn't to manage tasks. It was to build the room where the team could do their best work, trust where a developer can flag a problem without it becoming a political event, clear ways of working so no one hunted for context across Slack threads, and a shared goal open enough to leave room for creative problem-solving.
We brought our lead developer into the design process early, not as an executor, but as a voice at the table. During backlog grooming and estimating sessions, every team member had equal say. No hierarchy, no ego. The flashy feature got pushed in favor of backlog items quietly creating drag. Not glamorous. But the kind of decision-making that compounds.
Small wins every week. One key metric always moved, clicks, time on site, cart conversion. Revenue followed.
No AI tool generated that environment. A human built it, deliberately, structurally, one small decision at a time. The same instinct as the shoe box. Not because the materials were impressive, but because someone decided they were enough.
Stop Waiting for the Big Project to Claim the Title
My parents came to this country with limited resources and unlimited determination. What they gave me, without ever framing it this way, was the belief that what's in front of you is enough to build something real.
That's what the shoe box was. That's what the nonprofit SOP library was. That's what the small but mighty optics agency team was. None of it required perfect conditions. All of it required someone willing to look at the constraint and build anyway.
The innovation is already happening, in the SOP that saved your team hours, in the process that stopped a recurring problem, in the question you asked when nobody else would. That's not small work. That's the work that makes everything else possible.
As AI absorbs the execution layer, the PMs who stay relevant won't be the ones who resist it or the ones who outsource their thinking to it. They'll be the ones who use the time it frees up to do what it can't: build psychological safety that makes a team willing to flag a risk early, create governance that turns creative energy into something shippable, and make the calls no algorithm is empowered to make.
Innovation isn't a personality trait. It isn't a budget line. It's a discipline, and it's available to every PM, on every project, at every scale.
You've been doing it since the first project that didn't go according to plan. Claim it. Then do something with it.
This week:
Ask one better question.
Redesign one workflow.
Eliminate one recurring friction point.
Invite one quiet voice into the decision-making room.
That's not a to-do list. That's what building conditions for innovation actually looks like.
