UMSDNUganda Market Systems
Development Network

Market Systems Exchange / Issue 05

Build on what communities already have

A new project is rarely entering an empty market. Earlier investments can provide a starting point, but a group, agent network or warehouse still needs a workable operating arrangement.

Retrospective · IAM resilience-zone programming · Published 17 November 2026

New to this series? Start with the background

Market systems development examines how buying, selling, services and rules work together, and how those arrangements can work better for people facing barriers. UMSDN brings Uganda evidence into practical discussion.

Retrospective learning edition · Published 17 November 2026.

Read the full background and aid context →

The idea at a glance

See the connections.

01 / CHALLENGEGroups and facilities already exist
02 / CONNECTIONRepair connections, roles and operating incentives
03 / DESIGN QUESTIONCompare repair with a new investment

A UMSDN learning interpretation. Read the source account and evidence limits below.

Documented intervention / Feed the Future Uganda Inclusive Agricultural Markets

IAM’s layering approach in resilience zones

IAM’s layering brief describes building on existing farmer groups, village-agent networks and aggregation facilities associated with humanitarian and government investments. It connected private firms with local actors and co-invested in entry costs.

Documented activities included links between local seed businesses and research, input, credit and buyer services. The brief also describes aggregation partners and last-mile distribution in Karamoja and refugee-hosting areas. It is an account of complementary interventions, not a causal estimate of layering’s additional effect.

What the Activity did

01 / INTERVENTION

Mapped existing structures and convened relevant actors before investment.

02 / INTERVENTION

Connected producer organisations and service networks with commercial partners.

03 / INTERVENTION

Co-invested in entry activities and coordinated practical problem-solving.

Read the evidence carefully

Programme implementation evidence. The existence of a commercial partner does not demonstrate that every household can participate or that humanitarian assistance can safely end.

Read the original source ↗

UMSDN design interpretation

What this means for
future programme design.

UMSDN’s design interpretation starts with an inventory of functions, not simply assets. A warehouse may exist but lack maintenance, reliable access or an enforceable management agreement. An agent may have skills but no dependable revenue. A group may have been trained without having a committed buyer.

Before building something new, ask what existing arrangement could be repaired. Check ownership, access rights, operating costs and incentives. Speak to people who use the asset and people who do not. An asset described as available by one organisation may be practically inaccessible to a different group.

Layering also raises a sequencing question. A household facing severe constraints may still need direct support while a service market develops. A private firm’s willingness to enter is evidence about its business proposition; it is not evidence that every intended participant can afford the offer. Test participation conditions and monitor harm during transitions.

For coordination, write down who performs each function and what happens when one partner’s funding ends. Keep the obligations realistic. Agreements should cover maintenance, service quality, payment and recourse, not merely attendance at meetings. Evaluate the combined arrangement and be explicit about which component’s additional contribution remains uncertain.

Discuss the decision

When should a programme repair an existing market arrangement rather than finance a new asset or delivery structure?

Share the market context, your evidence and what would change your mind. Different interpretations are welcome.

Try this with your team

Choose a farmer group, agent network or aggregation facility. Record what exists, who controls access, its present users, recurrent costs and the missing connection. Compare repair, partnership and replacement before selecting an option.

Share your view on this website ↓

Pause and check

What will you take into the guide?

What should come before financing a new facility?

04 / Apply it to your work

Leave with a better
design question.

Choose one service you support. Write a short decision brief, then download it for your team. These worksheet entries stay on this page until you choose to download them.

No automatic sustainability score is assigned. Completing a checklist does not prove a programme will work.

Download the editable team worksheet ↓ / Printable PDF ↓

05 / Your voice in the exchange

Bring a decision.
Share what you learned.

What continued—or stopped—after support in a Uganda market you know? Offer a different interpretation, an example or a correction. Aim for 150–250 words, with sources where available.

Loading the submission form…

Community discussion / Reviewed contributions

What is the community
learning?

Read experiences and different perspectives approved for publication. Contributions are self-selected reader views, not a representative survey or independently evaluated results.

Loading the discussion…

Sources and credits

Keep the evidence visible.

Early evidence of successful layering in resilience zone

FtF IAM implementation learning brief. Programme partners retain credit for their interventions; the design interpretation is UMSDN editorial analysis.

The USAID-funded FtF IAM Activity was implemented by DAI with TechnoServe and MarketShare Associates. Source accounts describe programme experience; they do not establish current coverage. The design interpretation, debate prompts and exercise are UMSDN editorial analysis. UMSDN does not claim to have implemented the source interventions.

Editable edition Word file ↓ · All newsletter editions ↗