As a project manager, I remember how overwhelming it was to handle that big Drupal multi-site rollout. There were so many tickets to track, and the client’s priorities kept shifting. With different teams depending on each other, I often felt like I was just putting out fires instead of steering the project.

I started looking into AI tools, not to replace me, but to act as an assistant — something to help me see things clearly and make decisions faster. I used the OODA Loop (Observe, Orient, Decide, Act) to give structure to how I worked with AI.

a) Observe: I had AI scan Jira boards, Slack chats, and long client emails to pull key points and risks into short summaries.
b) Orient: It helped me analyze workflows, spot stuck tickets, and highlight dependencies.
c) Decide: With that context, I could prioritize better, unblock the team, and shift focus where it mattered most.
d) Act: I laid out the next steps simply, kept the team aligned, and updated the client so everyone stayed on the same page.

This gave me structure, reduced chaos, and helped me feel in control. AI is everywhere now, but without a framework, it can add clutter. The OODA Loop bridges that gap — not replacing PMs but helping us make quicker, clearer decisions. Using this, we caught problems earlier, sprints felt more manageable, meetings ran shorter, and clients noticed steady progress with fewer surprises. For me, it meant less time lost in my inbox and more time moving the project forward.