Garang Mayom Malek

Writing

What I Look For Before Backing a Trade-Technology Project

Before technology, I look for a real task, clear institutional responsibility and evidence that the proposed service can survive ordinary operating conditions.

Trade and payment projects often arrive with an impressive description of the technology. That is not where I begin. I begin with the task someone is trying to complete and the institution responsible for making the outcome meaningful.

A farmer waiting for a disbursement, a clearing agent completing a process and a finance team reconciling receipts do not experience a project as a list of features. They experience instructions, waiting time, records and the response when something goes wrong.

Before I support a project, I want to understand that experience in practical terms.

Is the problem specific?

The first question is simple: what is difficult today?

The answer should describe an actual process, not a broad ambition. Where does the work slow down? Which information is missing? What must a person do twice? What prevents an institution from recognising a payment or completing the next step?

A precise problem gives the team something to test. It also protects a project from expanding into every possible use before it has solved the first one.

Is there an institution that owns the outcome?

Technology does not replace institutional responsibility. A platform may route information or support reconciliation, but the relevant organisation still needs to define the service, the applicable rule and the person authorised to resolve an exception.

I therefore look for a clear owner on each side of the workflow. Who supplies the information? Who checks it? Who confirms completion? Who responds to the user? If several partners are involved, the handovers should be visible before the service is launched.

This is especially important in trade, where a user may interact with an association, an operator, a payment provider and a public authority during one process. The user should not have to discover the division of responsibility only after a problem occurs.

Can the first useful result be defined?

I prefer a first milestone that can be demonstrated and explained. It might be a validated set of payment details, a successfully matched transaction or a complete journey through a freight-administration process.

The result needs a definition. A technical connection is not the same as a completed user journey. A signing is not the same as an operating service. A small pilot is not evidence of performance at scale.

These distinctions are not barriers to ambition. They make progress easier to understand and help the team decide what evidence is needed next.

What happens when the normal path fails?

A project proposal usually shows the successful route. I also want to see the exception route.

What happens when account information needs correction? How is a duplicated or unmatched payment investigated? What does the user see during an interruption? Can support staff find the history without asking the person to begin again?

The answers reveal a great deal about whether a service is ready for real operating conditions. Reliability is not only the number of successful cases; it is also the quality of the response to the cases that need attention.

Can the project produce an inspectable record?

In my published discussion of institutional payments, I have emphasised the connection between money and the obligation or service behind it. That connection depends on records people can understand later.

I look for references that connect the transaction to the institution's work, clear statuses, retained corrections and information that can be reconciled. A useful record should remain understandable to someone who was not present when the project began.

This matters to users, partners and reviewers. It also matters when staff change or systems are replaced. The record is part of the infrastructure.

Are the partners' contributions explicit?

CapitalPay's public work includes technology and operating partnerships. An announcement can establish the direction of a relationship, but the delivery plan must say what each participant will actually do.

I look for operational ownership, authority to make changes, incident responsibility and an agreed way to measure the first stage. Commercial or security-sensitive details do not need to be public, but the delivery team must know them.

What evidence will change the decision?

Finally, a project needs a point at which the evidence is reviewed. The next decision may be to expand the service, revise a step, run another test or pause.

That decision should not be automatic. The team should know what it expected to learn, what happened and what the exceptions revealed. Good projects do not only collect evidence to prove that the original idea was right. They use evidence to improve the idea.

These are the questions I would use to make a trade-technology discussion more useful. They move attention away from the size of the announcement and toward the quality of the work: a specific problem, an accountable institution, a testable result, a usable record and a clear next decision.

Filed under Partnerships, Payments infrastructure, Trade and customs.

Sources

More writing