1. Diagnosis before Design

I begin by clarifying:

• What performance problem are we solving?
• What constraints shape delivery?
• Where does instructional intent conflict with platform behavior?
• What trade-offs are already embedded in the system?

2. Structured Methodology

My work is grounded in established instructional design frameworks, including ADDIE. I use structured analysis to define outcomes, constraints, and evaluation criteria before development begins. In complex environments, phases overlap and inform one another.

• Analysis clarifies performance gaps and environmental limits.
• Design defines structure and trade-offs.
• Development builds within platform tolerance.
• Implementation tests stability in real conditions.
• Evaluation measures durability, not just completion.

3. Constraints as Design Inputs

Design decisions are strongest when constraints are made explicit. In federal systems, constraints may include platform parity, analytics dependencies, compliance standards, and device variability. In live facilitation, they may include participant variance, time compression, and behavioral unpredictability.

4. Trade-Off Mapping

No system optimizes everything.

I map trade-offs deliberately:

• Flexibility vs. stability
• Modularity vs. load tolerance
• Autonomy vs. completion integrity
• Depth vs. time-on-task

Architectural clarity prevents accidental compromise.

5. Durability Over Optics

Visual polish matters. Structural integrity matters more.

I design for:

• Clear completion logic
• Predictable interaction behavior
• Accessibility and compliance integration
• Measurable, scalable frameworks

Systems should hold under pressure, not just present well.