Notice
Find the oversimplified idea — completion as proof, content as coverage, polish as quality, or AI output without judgment.
Editorial position
Where the Lab names the argument first.
Every Perspective starts as a critique of an oversimplified idea — completion as proof, content as coverage, polish as quality — then turns into a method a working learning designer can actually use.
Challenge
Question the default shape. Ask whether the real answer is a course, a system, a tool, a workflow, or support in the moment.
Translate
Turn the argument into a method a working learning designer can actually pick up and use.
Argument library
Read the thinking by problem or lane.
7
Showing all perspectives
Perspective lanes
The recurring arguments behind the Lab.
Learning is not an event. It is a system of practice, feedback, tools, support, and evidence.
Measurement works better when it starts before launch, not after the course is already built.
Retention needs retrieval, reinforcement, transfer, and support at the moment of need.
Feedback should help learners reason, recover, and improve — not just reveal whether they were right.
AI can accelerate output, but judgment determines whether the learning actually works.
Learning should be designed with usability, iteration, evidence, and real workflow behavior in mind.
From argument to action
An argument is only useful once you do something with it.
Perspectives names the thinking. The rest of the Lab is where it gets tested, built, and supported.
Need a reading path?
Ask Andy which argument fits your problem.
Describe the request, stakeholder problem, or messy design decision — and get pointed toward a Perspective, Field Guide, Design Lab tool, or Studio workflow.