Building a Blog That Thinks in Components
A sample MDX post showing custom callouts, styled images, markdown tables, and a reusable comparison table.
A sample MDX post showing custom callouts, styled images, markdown tables, and a reusable comparison table.
Six consecutive sprints with 100% commitment delivery. It did not happen by accident. It happened because of one daily habit and two non-negotiable rules.
I started integrating AI tools into my documentation process before anyone asked me to. Here is what stuck, what did not, and what actually saves time.
Most change management plans focus on the system being changed. The ones that fail do so because they ignored the people using it. Here is what I learned.
The recruitment funnel was leaking time at every stage. I documented every inefficiency, redesigned one key step, and the numbers changed permanently.
The title changed. Some of the work changed. But the most important skill — making sure everyone knows what is happening and why — stayed exactly the same.
We replaced a legacy system with a custom LMS and got 100% user adoption on day one. Here is the rollout strategy that made that possible.
A status report no one reads is just documentation overhead. After years of weekly executive reporting, I have a format that works every time.
My background is in Physics — not the typical path into project management. But it turned out to be the best preparation I could have had.