New: Boardroom MCP Engine!

Ready to put this into action?

Get the complete AI Integration PlaybookPractical AI implementation guide — prompt engineering, workflow automation, and ROI frameworks.

A Scorecard for the Benefits We Were Promised

By Randy SalarsArticle 59 of 60 in Building the Lunar Economy

Suppose a lunar project has been operating for several years. It has photographs, statistics, and a polished annual report. How can a general reader tell whether it is delivering value?

Recommended Resource

AI Integration Playbook

Practical AI implementation guide — prompt engineering, workflow automation, and ROI frameworks.

Building the Lunar Economy

Part 59 of 60 · Series date:

Suppose a lunar project has been operating for several years. It has photographs, statistics, and a polished annual report. How can a general reader tell whether it is delivering value?

Start with a small set of questions that connect activity to results.

The U.S. Bureau of Economic Analysis distinguishes gross output from value added, reminding us that sales throughout a supply chain are not the same measure as its contribution after intermediate inputs. That distinction is useful when large space-economy numbers appear. BEA’s explanation of gross output and value added.

For a lunar base, a practical scorecard could look like this:

QuestionUseful evidenceA weak substitute
Are services dependable?Completed jobs, outages, recovery timeEquipment delivered
Are customers returning?Repeat orders and funding sourcesExpressions of interest
Is work becoming more affordable?Cost per completed comparable taskA lower launch quote alone
Is science improving?Validated results and usable dataRaw data volume
Does local production help?Accepted output and full delivered costOne successful extraction
Are Earth benefits real?Adopted products and measured outcomesA list of possible spinoffs
Is participation broadening?Actual access by new organizationsMore logos on a presentation
Are public costs controlled?Full commitments and explained changesConstruction spending alone

The scorecard should not pretend that each value can be reduced to one number. Cultural meaning and fundamental knowledge deserve discussion. But measured claims should have measured evidence, and uncertain claims should remain labeled.

Definitions must stay consistent. If one year reports cost per kilogram landed and the next reports cost per kilogram launched, the apparent improvement may be misleading. If “buyer” includes both paying users and groups receiving free access, the categories should be separated.

Time periods matter too. A good month does not establish annual reliability. A temporary grant does not prove recurring demand. A successful trial does not show that gear will operate for its planned lifetime.

The best reports include failures and changes. What did not work? What cost more? Which assumption proved wrong? What was improved as a result? Hiding those answers makes the next choice harder.

Independent review can strengthen confidence. That might involve technical review, financial audit, peer review, or buyer confirmation, depending on the claim. Different claims need different kinds of review.

Picture a supplier reporting lower costs. The scorecard asks whether the same quality, destination, reliability, and support are included. If they are, the improvement is real. If they are not, the comparison needs adjustment.

The same approach applies to Earth benefits. A device adopted by a clinic or utility should show a documented contribution from the space work and a useful result in its new setting. A possibility mentioned in a report is not yet an outcome.

Public access to evidence makes the scorecard more useful. Readers should be able to follow links to methods, results, and clear summaries without needing to trust a promotional headline.

Give each claim a definition

Suppose an annual report says reliability improved. Readers need to know what counted as a successful service, which time period was measured, and whether the customer received the same level of support as before.

If the definition changes, the report should explain the change and, where possible, provide a comparable series. Otherwise an apparent gain may reflect a new counting method rather than better performance.

The same discipline applies to customers, costs, jobs, and scientific output. A paying customer differs from a free trial user. A job-year differs from a continuing position. A published dataset differs from a dataset that other researchers can actually use. Clear definitions prevent those categories from drifting together.

Put the missing result on the page

A useful scorecard includes incomplete work. Which services missed their commitments? Which products failed inspection? Which expected customers did not arrive? Which Earth applications remain only proposed?

These entries should lead to explanation and action. Some failures may reveal a design problem. Others may reflect an unrealistic schedule or weak demand. A report that names the cause and the response is more useful than one that hides the result behind a general statement of progress.

The scorecard should also distinguish a test from an operating service. A successful demonstration can support the next stage without establishing long-term reliability. Reporting it accurately preserves its value while keeping the remaining work visible.

Compare the completed task

A provider may reduce the price of one step while moving costs to the customer. For example, a cheaper delivery could require more handling or additional support at the base. A fair comparison follows the cargo or service to the same endpoint.

This is why the cost per completed comparable task can be more informative than a single technical price. Quality, timing, destination, and responsibilities should match. Where they do not, the report should describe the difference rather than force a misleading trend.

For science and cultural value, some judgments will remain qualitative. A good report can combine measured outputs with expert assessment and clear examples of use. It should not pretend that one numerical score can replace all judgment.

Let the scorecard change the plan

Measurement is useful when it informs decisions. If a service has persistent spare capacity, expansion may need to wait. If one bottleneck blocks valuable work, it may deserve attention. If a promised benefit remains unsupported, its status should change.

Independent review can help where the claim warrants it. Technical performance, financial accounts, and scientific conclusions need different forms of checking. The reviewer should have access to enough evidence to assess the actual claim.

The public gain is a clearer relationship between promises and results. A lunar economy will earn confidence when its successes can withstand ordinary questions and its setbacks lead to better choices. A good scorecard makes both visible, giving the next investment a stronger foundation than enthusiasm alone.

The purpose is not to drain excitement from exploration. It is to make the excitement durable. When a lunar economy delivers a real gain, a good scorecard helps everyone see it.

Progress becomes more convincing when it can answer straightforward questions in plain language: What worked? Who benefited? What did it cost? And what have we learned to do better next time?

Back to contents

Get the AI Dispatch

Weekly insights on ai & technology — delivered to your inbox. No spam, unsubscribe any time.

Want to choose specific topics? Customize your interests

Get the AI Dispatch

Weekly insights on ai & technology — delivered to your inbox. No spam, unsubscribe any time.

Want to choose specific topics? Customize your interests