Make digital work visible: a practical portfolio plan

For someone trying to enter digital work, “learn to code” is too broad to be a plan. Start with a task a person or small organisation already has: keeping stock records, making a service page easier to use on a phone, or turning a repeated paper form into a clear digital draft. Build a modest example, then show exactly what it does and what still needs a person.

That approach fits Namibia’s stated direction without pretending that a course or portfolio guarantees employment. The Ministry of Information and Communication Technology’s 2025–2030 strategic plan treats digital skills as one of five pillars of the national digital strategy. The National Planning Commission’s NDP6 names employment creation among the plan’s three fundamental needs for 2025/26–2029/30. These are policy priorities and targets, not evidence that a particular learner has secured work.

Start from an existing skills pathway

The Namibia Training Authority lists ICT vocational qualifications including ICT Foundation at Level 2, Computer System Support at Level 3 and Networking at Level 4. Its apprenticeship information describes a model combining workplace training with classroom learning. Availability, entry requirements and intake dates can change, so check the NTA or training centre directly before making a decision.

The practical lesson is to pair structured learning with a piece of work you can explain. A certificate records learning; a portfolio can make your method visible to a training provider, employer or potential client. It does not replace a recognised qualification where one is required.

A four-week proof-of-work sprint

1. Choose one narrow task. Ask a local club, shop, community group or training project what routine task takes time. Agree on a small improvement and use dummy data unless the owner has clearly approved real data.
2. Define “done” before building. Write down who uses it, what they need to accomplish, which device and connection they have, and what the first version will not cover.
3. Make the simplest useful version. It might be a tidy spreadsheet, a mobile-friendly page, a small script, or a clear how-to guide. A digital project does not need to be an app.
4. Try it with people. Ask a few intended users to complete the task while you observe. Record where they hesitate, fix the clearest problem, and say how small your test was.
5. Publish a short case note. Show the original task, your choices, screenshots or a demo, what you checked, what changed after feedback, and the limits. Remove personal information and credentials.

Show the conditions you designed for

A portfolio can be stronger when it explains the conditions around the work: whether it loads on a modest phone, what happens when a connection drops, how a person with limited technical confidence gets help, and what data the tool stores. Do not claim that a prototype is secure, accessible or production-ready unless you have actually checked those things.

The official page for the 9th National ICT Summit lists a 12–16 October programme in Ongwediva under the theme “Harnessing ICT for Inclusive Growth: Digital Pathways to Reduce Unemployment and Eradicate Poverty.” Its published theme signals what the programme set out to discuss; it does not prove that the event created jobs or that announced ideas have been implemented. The same distinction matters in a portfolio: show the evidence you have, label the rest as a proposal.

A useful next step

Pick one task this week and ask permission to make a small demonstration. If the organisation cannot share data, use fictional examples. If you are still learning, say so and show your process. A clear, modest proof gives someone a better basis for a conversation than a sweeping promise about what you can build.

Corrections or feedback? Contact On-delo. · Browse the daily desk