Economy is communication: what should Guatemala make possible?

Take the carpenter from the previous post. Suppose they test a set of building plans and someone abroad wants to buy them.

How does that buyer discover the plans? Can they understand the measurements and materials? Can they pay? Does the file arrive? What happens when they need help?

Now replace the download with a flat-pack desk. The same questions remain, joined by packaging, shipping costs, addresses, tracking, damage, and returns.

This is an illustrative case, not a documented transaction. But it gives us a concrete route to investigate: what does it take for someone in Guatemala to turn a useful capability into an exchange that works?

Observation: a product needs a whole chain of connections

A sale starts before checkout. Someone encounters an idea, recognizes a need, finds an offer, and decides whether to trust it. After payment, the promise still has to be fulfilled.

Every step carries information. A demonstration explains usefulness. A price lets the buyer decide. Payment confirmation tells the seller to proceed. Tracking tells both parties where the package is. A complaint tells us where the product or operation failed.

This is the sense in which economy is communication: economic activity depends on people being able to discover, understand, coordinate, and exchange. Physical goods still need physical infrastructure. Clear communication helps that infrastructure work; it cannot replace it.

For someone unfamiliar with e-commerce, showing this complete journey is more useful than telling them to “get online.” A storefront is one part of an operation that includes finding demand, making a credible promise, collecting payment, delivering, and supporting the customer.

We should investigate where Guatemalans lose access to that journey. Is the unfamiliar part the product model itself? Finding buyers? Payment access? Delivery costs? Understanding the rules? Different failures require different changes.

Analysis: individual effort depends on shared systems

Education expands what people can make. Communication connects those abilities to knowledge, collaborators, and customers. Infrastructure and rules determine how reliably those connections work.

That gives us a practical way to examine systems:

• Broadband: can someone learn, upload work, speak with a customer, and run an operation reliably?
• Payments: can the intended customer pay, can the seller receive the money, and are fees, timing, and dispute procedures understandable?
• Postal service and logistics: can a small seller quote a delivery, send the item, track it, and resolve a failure at a workable cost?
• Administration: can someone understand and fulfill their obligations without having to decode the system from scratch?
• Shared knowledge: can the next person find a usable explanation of the route, including its limitations?

These systems deserve reconsideration on their results. What purpose does a procedure serve? Does it achieve that purpose? What does it cost people in time, money, and abandoned attempts? Could a simpler mechanism work better?

Tax simplification belongs in that investigation. Even a radical proposal such as “IVA only” needs a clear test of its assumptions: revenue, distribution of the burden, compliance costs, and transition. It remains an idea to evaluate, not an established Commission position. The ambition can be bold; the reasoning has to do the work.

Communication also shapes which possibilities people encounter. If we mostly circulate the same career paths and business examples, we keep narrowing the menu. Showing how a specialized service, digital product, licensed design, or educational tool actually works can open a path someone had never considered.

80% useful, 20% beautiful applies to that communication too. Show the process, costs, mistakes, and decisions. Give people something they can use.

Proposal: make a complete route work, then improve the conditions around it

Choose one willing producer and one offer to test. Start with demand and product quality; a functioning checkout cannot fix an unwanted product.

Document the full attempt:

1. Find and understand a potential customer. What do they need, and how do they solve it now?
2. Test the offer. Can they understand the value? Will they commit to buying at a price that could cover delivery and support?
3. Complete the exchange. Record payment costs, administrative steps, delivery time, and support needs.
4. Identify the failure points. Separate problems with the offer from problems with the surrounding systems.
5. Change one thing and repeat. Publish what happened, including unsuccessful attempts, while protecting customer information.

Measure completed purchases, total costs, time spent, delivery reliability, and whether the customer received what was promised. One successful transaction establishes a possible route. Repeated attempts reveal whether it is dependable and for whom.

Use that evidence to propose changes beyond the individual seller: clearer guidance, a better delivery process, accessible payment arrangements, or a bounded pilot with the institutions involved. Each proposal should name an owner, an expected result, and what evidence would make us revise it.

The same approach can guide which industries Guatemala develops and attracts. Define “positive” through concrete contributions: useful output, worthwhile jobs, skills people acquire, opportunities for local suppliers, and costs imposed on communities. Then examine what those businesses need to operate and how local people can participate.

For the Innovation Commission, a concrete role would be to bring the relevant people together, help organize pilots, publish findings, and advance changes supported by the results. These are proposed actions, not claims that the work is already underway.

The country-level ambition is straightforward: make it easier for people here to create, exchange, and develop valuable work—and give others reasons to come build alongside them.

That requires institutions capable of learning too. Observe what happens, analyze the mechanism, propose a change, measure the result, and keep experimenting. Sin fin.

“Así se ha hecho siempre” is not a performance metric.