Climate Tech

A practical workflow begins with a clearly bounded emissions problem, then moves through deployment blockers before it gets seduced by TAM language. If a technology cannot survive financing, siting, or interconnection reality, the technical elegance alone will not rescue it.

A sequence I would actually hand to a teammate:
1. Start by defining the emissions problem and the system boundary around it.
2. Track deployment blockers such as supply chain, permitting, and project finance.
3. Compare company claims with market structure, customer behavior, and policy timing.

Useful operating references:
- DOE Liftoff reports: liftoff.energy.gov/
Useful for understanding commercialization pathways and deployment bottlenecks in the US.
- PyPSA documentation: docs.pypsa.org/
An accessible place to start with open power-system analysis and optimization.

If your team has a better workflow, post it with the context around team size, constraints, and exactly where the process tends to break.