Design philosophy

1. Inclusive, scalable design is the starting point — not the finishing touch

Accessibility and inclusion aren’t accommodation layers applied after the fact. Designing for the widest possible range of people, contexts, and uses from the outset makes learning experiences more robust, more transferable, and more genuinely useful — to more people, in more situations, for longer. This is the default I start my own work from — not a standard I’d hold over a team working under real constraints of time, budget, and competing priorities. If anything, building inclusion in from the outset is the most practical way to work within those constraints: access designed in early rarely has to be retrofitted later, and the design that reaches more learners tends to be the more durable one.

2. Good design thinks in systems

Learning design doesn’t end at the edge of a course, resource, or program — it asks how each piece connects to a larger whole. I work simultaneously at the level of individual learning interactions and at the level of platforms, curricula, and organizational infrastructure, because decisions made at one scale shape what’s possible at every other. The most durable work I’ve done has been systems designed to function, adapt, and be maintained by whoever comes next — not systems that depended on my continued presence to hold together.

3. Learning is the point — technology earns its place

The measure of any learning experience is its impact on learning — not the sophistication, novelty, or capability of the tools used to build it. I start from what learners actually need to understand, do, or become, and design backward to the technology, rather than starting with a tool and looking for a reason to use it. Years of educational technology practice, sharpened by my MEd, have given me both deep fluency with digital tools and a critical lens on them: I can tell when a feature genuinely opens learning up — improving access, comprehension, engagement, or retention — and when it pulls focus toward itself, adds cognitive load, or quietly becomes a barrier. That judgment is what makes mindful, intentional technology use possible rather than just advocated for. Some of the most important design decisions I’ve made have been the ones where I chose not to use something — and could say exactly why.

4. Do the work — don’t just describe it

The clearest test of whether I believe something is whether I apply it to my own practice. Both Articulate projects in this portfolio are themselves built to be accessible and inclusive — not just to teach about those principles. I hold my work to the same criteria I’d apply to any learning design: if it doesn’t meet the standard I’m advocating for, it needs to change. Reflexive practice isn’t a value I perform — it’s the one that keeps the others honest.

5. Build capacity, not dependency

The goal of good learning design is to build capacity over time — in learners, in teams, and in the organizations and communities they’re part of — not to make itself indispensable. I design with sustainability in mind: the platforms, resources, and frameworks I build are structured to be understood, maintained, adapted, and extended by whoever comes next. Learning ecosystems that require the designer’s continued presence to function were never really finished.