For instructional designers, L&D teams, and career changers
Future of ID
A capability development system for moving from course production toward learning systems design through a repeatable method and reusable learning architecture.
Bradley's current seven-capability pathway is the first complete demonstration of the system—not a universal or permanent prescription for every instructional designer.
How the Platform Teaches
Learn, practice, inspect the build, then apply it.
Future of ID uses a reusable learning architecture: Theory, Experience, Reverse Build, and Reflection. Each module moves from understanding to practice and feedback, then opens the design decisions behind the experience so learners can transfer the insight into their own work.
- 01Theory
Learn
Start with the concept, why it matters, and how it connects to instructional design work.
- 02Experience
Practice
Use scenarios, decisions, or guided activities to test the idea in context.
- 03Reverse Build
Inspect the Build
Open the design rationale, tradeoffs, and implementation choices behind the learning experience.
- 04Reflection
Apply
Connect the lesson to your own tools, role, constraints, and future design decisions.
Experience, feedback, and Reverse Build in one learning loop.
Future of ID teaches through experience: learners practice, receive AI-supported feedback, reflect on their judgment, and then use Reverse Build to inspect why the experience was designed that way.
What Future of ID Is
A repeatable system for intentional capability development.
Future of ID helps practitioners identify, develop, apply, and share future-relevant capabilities through a reusable learning architecture. Sharing means making professional reasoning, artifacts, reflections, and design lessons understandable for others to inspect or adapt.
Practical Learning Pathway
Explore Bradley's current seven-capability pathway as a complete demonstration of the method, not as the only valid pathway.
Transparent Implementation
Use Reverse Builds to see what shaped the work, what was simplified, where AI helped, and where human judgment stayed central.
Systems Thinking
Connect learning science, workflow decisions, evidence, learner support, and technical constraints in one design conversation.
Calibrate Your Future
Choose the level of AI adoption, technical depth, and system ownership that fits your role and context.
What Future of ID Is Not
Not a prediction platform. Not a universal prescription.
This is not a claim that every instructional designer needs the same capabilities, technical depth, or professional path. The current platform does not diagnose needs or generate personalized pathways automatically.
01Not a trend reportView clarificationHide clarification
It does not try to forecast the future of the profession or package AI as a broad industry prediction.
02Not a replacement for fundamentalsView clarificationHide clarification
Instructional design judgment, performance analysis, accessibility, sequencing, and evaluation still matter.
03Not a mandate to codeView clarificationHide clarification
Some IDs may stay close to writing and authoring tools. Others may explore custom systems. Both paths can be valid.
04Not complexity for statusView clarificationHide clarification
Technical depth only matters when it helps solve a real learning or workflow problem.
Different Paths
There is more than one credible future for instructional designers.
Roles, responsibilities, organizations, industries, career directions, and goals vary. Future of ID meets practitioners where they are through practitioner-led professional calibration: understanding current context, experience, responsibilities, goals, and development needs before identifying relevant growth areas. Different practitioners may build different pathways—and revisit them as their work changes—while reusing the method and learning architecture; the platform does not diagnose needs, recommend capabilities, generate pathways, or personalize the experience automatically.
Different Paths
Which capabilities matter in my context, and how might I organize them into an intentional pathway?
Roles, responsibilities, organizations, industries, career directions, and goals vary. Future of ID meets practitioners where they are through practitioner-led professional calibration: understanding current context, experience, responsibilities, goals, and development needs before identifying relevant growth areas. Different practitioners may build different pathways—and revisit them as their work changes—while reusing the method and learning architecture; the platform does not diagnose needs, recommend capabilities, generate pathways, or personalize the experience automatically.
Why This Exists
The profession needs a clearer bridge from commentary to implementation.
AI can make content generation faster, but speed does not remove the need for design judgment. Instructional designers still need to define what matters, evaluate outputs, protect trust, and connect learning work to performance.
The work is expanding unevenly
Different organizations are adopting AI and learning technology at different speeds, with different risks and constraints.
The implementation details are often hidden
Many conversations skip the build decisions, failed attempts, tradeoffs, and maintenance problems that shape real work.
The point is practical clarity
Future of ID documents what was built, what was learned, and what another designer might adapt for their own learning ecosystem.
Current Implemented Pathway
Bradley's seven-capability demonstration.
These seven areas form Bradley's launch-stable professional pathway and the first complete demonstration of the capability development system. They are coherent and practical, but not universal, exhaustive, or the permanent boundary of Future of ID.
Stronger Together
What does this implemented pathway demonstrate, and which capability areas might change in another practitioner's context?
Bradley's current seven capabilities are connected parts of the first complete system demonstration: judgment, performance, evidence, practice, adaptation, maintainability, and trust.
AI Literacy and Agent-Enabled Learning Design
Performance Consulting and Business Alignment
Learning Analytics and Evidence-Based Design
Scenario, Simulation, and Conversation Design
Adaptive and Personalized Learning Architecture
Content Systems Thinking and Workflow Automation
Human-Centered Change, Ethics, and Learner Trust
Platform Principles
Built for judgment, not novelty.
These principles guide the course, the Reverse Build sections, and the way AI is discussed across the platform.
Observed, not predicted
The platform shares what has been built, tested, changed, and learned through implementation.
Implemented, not theorized
The work itself is the evidence. Concepts matter when they change real design decisions.
Transparent, not performative
Tradeoffs, limits, AI support, human review, and design constraints are part of the story.
Useful, not trendy
The goal is not to impress people with AI terms. The goal is to make better learning design decisions.
Inside the Platform
A course structure that turns concepts into design decisions.
Each module connects explanation, scenario practice, Reverse Build notes, and reflection so you can see both the learning concept and the system choices behind it.
Guided modules
Bradley's current implemented pathway covers AI literacy, performance consulting, analytics, scenarios, adaptive learning, content systems, and trust.
Scenario practice
Each module gives you a place to make design decisions and receive AI-supported feedback.
Reverse Build notes
Design notes explain why each module was built the way it was, including constraints, tradeoffs, and reusable patterns.
Reflection prompts
Reflection sections help you connect the ideas to your own role, tools, and work context.
Choose Your Entry Point
Start with the frame, or explore the capability map.
Use Orientation to understand the reusable method and Bradley's current pathway. Use the Dashboard to browse the seven implemented capabilities and choose the area that fits your current questions. Neither path is required before the other.
