Not all improvisations are successful, but I explore themes in various ways to find inspiration.

I prefer to engage in startup ideas only when there's a concrete concept, as this allows for efficient validation and execution, contrary to the common advice of exploring many alternatives.

When I come up with an idea, I acknowledge that it will face objections, but I encourage collaboration to refine it into a fully formed concept.

My writing process involves capturing the kernel of an idea and testing it on stage rather than writing it out in full beforehand.

Experiment with side projects to gain experience in turning ideas into reality, even if they start small.

It's important to quickly build and test ideas. If something doesn't work, it's better to kill it and start again rather than justifying its existence with additional features that may not address user needs.

I'm not limiting myself to good ideas; many of my ideas are not good, but this is relevant to startups because often good ideas look bad initially.

It's common to need to change your initial idea significantly to meet user needs, even if you start with a reasonably good concept. You may start with a general vision for your startup, but often you need to try several different approaches to find the right one.

I often see each project as an opportunity to explore a new style of music, which keeps my work fresh and engaging.