A PM practice, not a course catalogue

You were handed a project. Nobody trained you.

Most project managers learn the job by surviving it. This is the path I teach instead — three stages, with AI as a layer through all of them, not a chapter at the end. The material at every stage is free.

ls ./path

You do not graduate out of a stage. You come back to it with a harder project.

  1. [1]

    Foundation

    L1

    You understand how projects actually work.

    I'm running a project and nobody ever trained me.

    AI lab: AI to learn faster — explain a concept, generate worked examples, drill yourself.

  2. [2]

    Delivery reality

    L2

    Your plan survives contact with a real business.

    My plan looked fine until week three.

    AI lab: AI in the work — risk registers, stakeholder analysis, status reporting.

  3. [3]

    Credential

    L3

    You can show professional deliverables. PMP is one extra deliverable, not the point.

    I can do the work but I can't show it.

    AI lab: AI for leverage — second brain, skills, agents.

cat ./manifesto

AI is a layer, not a rung.

— the rule the whole path is built on

Putting “AI-native” last would tell you it comes after the fundamentals. In the room where I taught this, applying AI in PM was rated the joint-standout of the whole program — across every seniority level present. It belongs at stage one.

cat ./receipts

1,018practice questions, every single one explained
+20how a paying enterprise room rated applying AI in PM, top of the board
13 daysfrom first commit to a live exam platform, built solo with AI

The method was delivered onsite at IMC, a ~200-person health-supplements manufacturer in Hanoi — three sessions over two days, designed from their own four-team survey rather than off a shelf. Their PMs rated the PM approach +24 and applying AI in PM +20 on the post-course board.

Everything on this page is something I built or delivered, not something I read about.

./get-guide

Which PM tool do I actually pick? The most common question I get, and the honest answer is unpopular: there is no best tool and no real all-in-one. Pick the tool by the job, not the brand — and start with the lightest thing that makes the work visible. Most teams need three small things working together, not one big platform they’ll abandon by March.

The guide is the pick-by-job map, the “don’t” list, and a default stack for a team starting from zero.

Your email goes into a private table I read each week. No sequence, no newsletter. If I write back, it’ll be because you described a project I have something specific for.

whoami

Anh Vu

I’m Anh Vu. I came into project management from the factory floor — automation engineering — and spent 13 years in the space between the people who build things and the people who need them delivered.

I teach PMs and PMO teams, and I build the tools I teach with. PMPilot and the study garden aren’t products I’m selling you; they’re proof that the method survives contact with real work.

More about the practice →