{"questions":[{"id":"making-complex-systems-accessible","title":"How do you make complex systems accessible?","externalTitle":"Making Complex Systems Accessible","summary":"Designing visual programming systems that help domain experts create complex behavior without writing code.","capabilities":["visual-programming-systems"],"story":{"whyItMattered":"Domain experts often need to create complex behaviors, but traditional tools force them to either write code or depend on engineers for every change.","whatIBuilt":"A visual programming experience for authoring, inspecting, and evolving complex behavior.","whatChanged":"The work reduced barriers to creation and made complex systems easier to understand and discuss.","whatILearned":"The right abstraction matters more than the surface UI."}},{"id":"building-trust-in-digital-commerce","title":"How do you help creators earn money and customers buy with confidence?","externalTitle":"Building Trust in Digital Commerce","summary":"Designing commerce experiences for digital goods where customers need confidence and creators need clear value communication.","capabilities":["creator-economy-design"],"story":{"whyItMattered":"Digital goods are harder to evaluate than physical products, so both creator value and customer confidence have to be designed into the experience.","whatIBuilt":"External-facing product and purchase patterns that made digital goods easier to understand before purchase.","whatChanged":"The experience helped connect creator expression, product clarity, and buyer trust.","whatILearned":"Trust is part of the product, especially when the thing being sold is intangible."}},{"id":"prototypes-as-strategy","title":"How can prototypes drive strategy?","externalTitle":"Prototypes as Strategy","summary":"Using functional prototypes to make ambiguous futures tangible and turn product debate into evidence.","capabilities":["proof-through-prototyping","organizational-enablement"],"story":{"whyItMattered":"In ambiguous product spaces, discussion alone is too slow. Teams need something concrete to react to.","whatIBuilt":"Functional prototypes and reusable workflows that helped product, design, and engineering evaluate direction together.","whatChanged":"The prototypes created shared evidence for strategy, roadmap thinking, and team alignment.","whatILearned":"Slides create opinions. Prototypes create evidence."}},{"id":"designers-ai-workbench","title":"What should a designer's AI workbench look like?","externalTitle":"Building the Designer's AI Workbench","summary":"Creating environments for designers to work with real components, real interaction logic, and AI-assisted local workflows.","capabilities":["designer-workbench","organizational-enablement"],"story":{"whyItMattered":"As AI changes how software is made, designers need better environments than static mockups alone.","whatIBuilt":"Local prototyping and design sandbox workflows for experimenting with production-like components and AI assistance.","whatChanged":"The work helped designers move faster from concept to working product evidence.","whatILearned":"Designers need working materials, not only static canvases."}},{"id":"designing-ai-behavior","title":"How should AI agents behave?","externalTitle":"Designing AI Behavior","summary":"Designing when AI should speak, suggest, act, wait, explain, or stay silent.","capabilities":["ai-behavior-design"],"story":{"whyItMattered":"As AI systems become more agentic, the design problem shifts from screens to behavior.","whatIBuilt":"Principles and interaction patterns for AI systems that need to collaborate with people.","whatChanged":"The work framed AI product design around trust, initiative, uncertainty, and timing.","whatILearned":"For AI products, the interface is often adaptive. The deeper design work is behavior."}}]}