Instructional design and project management shouldn't run on instinct alone

I'm Dustin. For the last 15 years I've worked as an instructional designer — needs analyses, storyboards, e-learning builds, facilitator guides, the whole ADDIE cycle more times than I can count. For the last 4 of those years, I've also taught PMP to project managers, which means I've spent a lot of time translating between two disciplines that rarely talk to each other: the people who design how learning happens, and the people who manage whether it ships on time and on budget.

In practice, those two jobs collapse into one person constantly. An instructional designer gets handed a budget and a deadline and no PM support. A project manager gets handed a training initiative and no instructional design background. Almost nothing is written for that hybrid role specifically — most resources pick a lane and stay in it.

These days I work as a data scientist, trying to bring more measurement and automation into both fields — treating a training needs analysis or a project status report as something you can actually build a repeatable process around, instead of reinventing it every time. Promptvyn is where that work turns into prompts, playbooks, and small tools other people managing learning projects can use directly.

Everything here is meant to save you a first draft, not replace your judgment. If a prompt produces something that doesn't hold up in your context, that's useful information too — treat this as a working toolkit that gets better over time, not a finished answer key.