The Solar Capacity-Leverage Checklist for Growing Teams

A capacity-leverage intervention should change a demonstrated constraint in the work system. Faster drafting, another employee, a new supplier or a software license is an action; it is not yet evidence of more completed, accepted project work.

Use this checklist to evaluate an action before crediting it in the operating plan. The cross-stage capacity plan identifies shared work and interfaces. The growth model calculates scenarios, and the quarterly review decides commitments. This page tests the intervention’s mechanism, tradeoffs and evidence.

Name the Constraint and the Proposed Mechanism

State the work type, stage, role, readiness condition and outcome the action should affect. Attach current task, queue, return and exception records. Explain why the action addresses that cause rather than simply making another stage busier.

“Design is slow” is too broad. Missing source records, repeated customer changes, drafting work, qualified review and external decisions require different responses. Do not remove a required safety, technical, commercial or authority gate to improve a time measure.

DOE’s solar soft-cost overview discusses non-hardware business and process costs. It does not establish that a specific intervention raises throughput or saves a stated amount for your team.

Compare Candidate Levers With Their Added Work

These are evaluation options, not a recommended ranking. Use the deeper capacity-lever guide for the option discussion. This checklist owns the acceptance record for a chosen change.

Check Whether Work Was Removed or Moved

A step may become faster while review, correction or another team’s coordination increases. Separate active task time, waiting, rework, setup and recurring administration. Confirm which role benefits and which role receives the new work. Do not add savings across overlapping activities.

Hypothetical unit check: an action removes 30 hours of a defined drafting task in a period, but adds 10 hours of configuration support and 20 hours of additional review. Across these stated activities, 30 − 10 − 20 = 0 net hours removed. Drafting may still have improved locally; the calculation does not show total labor savings or increased release capacity. Different roles and timing can matter even when the total is zero.

This is an invented scenario, not a vendor result. It excludes acquisition cost, licensing, training, downstream work and monetary effects. A claim about system throughput requires evidence of accepted completions at the relevant constraint, not this hour balance alone.

Define the Pilot Before Seeing Its Results

Write the baseline population, observation period, current method, candidate configuration, permitted task scope, source quality, responsible reviewer, expected records and stop conditions. Compare equivalent work classes and preserve exclusions. A more favorable project mix can change results without the intervention causing them.

Retain quality dispositions, returns, accepted outputs and downstream effects alongside task time. A faster draft that needs more correction may not improve released work. A tool demo does not establish results in your production data or qualify a professional reviewer.

NASA’s technical-assessment guidance discusses defined indicators and periodic review to inform decisions. This is an assessment analogy, not a prescribed solar pilot or universal measurement threshold.

Account for Implementation and Operating Authority

Separate one-time setup from recurring workload. Record the funding, contract, data-use rights, access, competence, technical review, support and rollback route needed before the change can operate. Do not credit a new hire or integration before its required conditions are met.

NASA’s technical-planning guidance connects resources, interfaces and changed constraints. It supports keeping the action tied to its implementation conditions, without establishing a project duration, staffing ratio or savings guarantee.

Copy-Ready Capacity-Leverage Decision Card

1. Current constraint, work type, role and evidence.
2. Proposed action and causal mechanism.
3. Tasks removed, changed, shifted or added, with compatible units.
4. One-time implementation and recurring operating load.
5. Qualified review, technical, safety and external gates preserved.
6. Funding, access, competence and contract authority.
7. Pilot population, baseline, observation period and comparison limits.
8. Accepted output, quality, returns and downstream evidence.
9. Stop condition, rollback owner and affected customer commitments.
10. Decision: adopt, narrow, extend evidence collection, defer or reject.
11. Operating-plan effective date and conditions for crediting capacity.
12. Successor review trigger when demand, scope, people or configuration changes.

An action can be useful without justifying a higher lead target or tighter customer schedule. Record the narrower conclusion the evidence supports. Preserve the original baseline so future owners can distinguish a changed process from changed demand or definitions.

Frequently Asked Questions

What does a capacity-leverage checklist evaluate?

It evaluates whether a proposed action addresses a demonstrated constraint, what work it removes or shifts, the implementation and recurring load, required authority, and evidence needed before capacity is credited in the plan.

Does a faster task prove higher project throughput?

No. Review, returned work, shared resources, external readiness or another stage may still limit accepted completion. Compare downstream effects and compatible task classes instead of treating local speed as system capacity.

When can a proposed intervention count in the operating plan?

Only for the bounded use supported by implementation readiness, responsible authority and accepted evidence. Preserve technical and safety reviews, funding, access, support and stop conditions; do not credit an unimplemented action as current capacity.

Can a software demo prove staffing or labor savings?

No. A demo can establish observed behavior for its configuration. Measured operational claims need a defined pilot with compatible work, quality dispositions, recurring load, comparison limits and downstream evidence.