Designing for the next meaningful step.

A question keeps returning across my work: what does it take for someone to move forward when the next step is uncertain?

That question runs through my work in mentorship, career coaching, graduate instructional design, and emerging learning technologies. These environments differ, but the design challenge is familiar: information alone rarely creates progress. People need a way to recognize where they are, understand what matters, choose a manageable action, receive feedback, and try again.

Learning design begins with a person, not a platform.

When I start a learning project, I want to know what the learner is trying to accomplish and what makes that difficult. Is the task unclear? Is the expected performance visible? Does the environment offer the right support? What would count as evidence that the learner can act independently rather than merely complete a sequence?

These questions connect my instructional design work to direct coaching. They also explain my interest in performance support, reflection, authentic assessment, and systems that make human judgment easier to exercise. A resource is useful when it helps someone take a better action, not simply when it looks polished or contains more content.

I build to make ideas testable.

Graduate coursework has given me opportunities to design modules, explanatory media, learning activities, and assessment structures. Independent prototypes have pushed that work further: I can translate a design rationale into an interface, test the flow, inspect its limitations, and revise the experience.

In Confusion Management, I designed a pathway for learners to recognize uncertainty and choose useful support. In From Compliance to Mastery, I proposed a human support pathway surrounding existing credit-recovery coursework rather than replacing the platform. In PMBaseline, I have been developing a working self-regulation prototype around check-ins and manageable next actions. These are different kinds of evidence, and I want to represent each honestly: a proposed system is not a deployed program, and a working prototype is not proof of learner impact.

My current exploration of AI-assisted development fits this pattern. I use technology to shorten the distance between a question and a working prototype, while keeping responsibility for claims, evidence, accessibility, and learner impact. A functioning feature is not proof that anyone learned from it. That distinction matters.

Agency and evidence belong together.

I am interested in adaptive pathways rather than a single fixed formula for success. Learners need meaningful choice, but choice becomes more useful when paired with clear goals, credible information, structure, feedback, and opportunities to demonstrate progress. Different learners may need different levels of support at different moments.

The systems I want to build should help people direct themselves more effectively over time, not become dependent on the tool. That is why I care about human facilitation, inspectable decisions, practical experimentation, and evidence of what changed.

The work I want to keep doing

I want to connect rigorous learning design with real problems and workable technology. Sometimes the right deliverable is a conversation guide or a job aid. Sometimes it is a course, a facilitated experience, or an interactive prototype. The format is secondary to the learner's meaningful next step.

That is the professional through-line I am developing: listen closely, define the problem, design a useful experience, build when building helps, and evaluate what the work actually makes possible.