Three interactive tools I use to teach service blueprint, value proposition, and futures methods and a small experiment in what happens when a designer who teaches can build their own instruments.
The tools were built with Claude as a coding partner across a few evenings. That fact is part of what they are, not a footnote.
For ten years, the gap between "I have a teaching method that works" and "I can hand my students a thing they can use without me" was a developer's gap. I'd run workshops with slides, whiteboards, and printed canvases, and I'd wish - in roughly the same way every time - that the workshop could leave the room with the students. It mostly couldn't. Building the version that travelled was someone else's job, and someone else's budget.
That gap has narrowed sharply. Not for production software, where it remains a developer's gap, but for the specific class of tool that needs to be used by about twelve students for two hours. For things that small and that local, a designer who can prompt clearly can now close the gap themselves. The interesting question for me isn't whether this is good or bad - that's the wrong frame - but what teaching becomes when the instruments stop being aspirational. I don't fully know yet. These tools are part of finding out.