About Execution Signal

Practical systems, templates, and AI workflows for project managers delivering technology initiatives.

Projects rarely stall on execution

Most late projects are not late because people cannot do the work. They are late because decisions sit unmade and unowned. The trade-off is unclear, nobody can see the decision being asked for, and the status update proves effort instead of surfacing the choice.

Execution Signal exists to fix that. Every issue turns one recurring delivery problem into a system you can run this week: how to frame the decision, what to say in the room, and a tool you can adapt instead of building from scratch.

Written for practitioners

Execution Signal is for project and program managers delivering technology initiatives: software builds, cloud migrations, ERP rollouts, automation, and AI adoption. You run cross-functional teams you do not directly control, you translate between technical and business, and you keep work moving while priorities shift around you.

It is not exam prep, tool reviews, or AI hype. It is the connective tissue between textbook project management and how delivery actually happens.

One issue every two weeks

Each issue follows the same structure: a shift in how to see the problem, a system to run, and a companion tool (a template, checklist, or prompt pack) that is free for subscribers. Past tools live in the tool library.

Who writes this

Jesus Romero, senior IT project manager and author of Execution Signal

I’m Jesus Romero, a senior IT project manager based in Toronto. I have almost 20 years of experience delivering technology initiatives, including over 10 years as a project management consultant and postgraduate professor. Most of that work happened in complex, risk-heavy environments: software delivery, PMO governance, dashboards and reporting, stakeholder communication, and lately AI-enabled project management.

Execution Signal is where I turn that scar tissue into systems. I write it for the version of me who was staring at a stalled project wondering why nothing moved when everyone was busy.

If you want the day-to-day version, I write on LinkedIn several times a week.

Connect on LinkedIn

Get the next issue

One issue every two weeks. A practical system and a free tool in each one.