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 — DevOps, then tech literacy, then AI for PM, with AI as a layer through all three rather than a chapter at the end. The material at every stage is free. I am a PM navigating this shift too, not someone who already arrived.
ls ./path
You do not graduate out of a leg. You come back to it with a harder project. A certificate is not on this list — it is a field to practise in, not the point.
DevOps
L1You understand how software actually gets built, shipped and operated.
I manage engineers whose work I can no longer read.
Tech literacy
L2You can read, wire and judge the tools — not just name them.
I can run a status meeting. I cannot run a workflow.
AI for PM
L3You have a second brain you built yourself, doing real work on a real project.
I use AI like a search box, and I know that isn't it.
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
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.
whoami
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.