Why a phone is not a computer: what first-time users told us
Notes from the first six weeks of the Lugbe hub, and what they change in how we teach. Nearly everyone who walks in owns a phone. Almost nobody has typed on a keyboard.
Nearly everyone who walks into a Community Connect Hub owns a phone. Almost nobody has typed on a keyboard. That single gap shaped the first six weeks of the Lugbe hub more than any curriculum document did, and it has changed how we plan to teach everywhere else.
This is what we learned, written down while it is still uncomfortable enough to be useful.
Two hands instead of one thumb
Ask someone in Lugbe market whether they are comfortable with technology and most will say yes. They mean it. They move money, run a business account, settle disputes and watch the news on a device they have owned for years. By any reasonable measure they are digitally capable.
Put the same person in front of a laptop and something changes. Several participants described the feeling as being back in an exam hall. The screen is further away. The keyboard demands two hands instead of one thumb. The trackpad has no obvious relationship to anything. And crucially, a laptop does not forgive. A phone hides its filesystem and offers one obvious next action; a laptop presents twelve and waits.
Facilitators adapted within the first fortnight. They stopped opening with software and started with the trackpad and a blank document, and they let people type their own name before anything else. It sounds trivial. It is the difference between a person coming back on Thursday and not.
The literacy assumption
The second thing we got wrong was subtler. Our early session plans assumed that anyone who could use a phone could read and write comfortably in English. For a significant minority that is not true, and the phone had been quietly compensating: voice notes instead of typing, pictures instead of names, memorised icon positions instead of menu labels.
A laptop strips that scaffolding away. Sessions now run in Hausa and English, materials use pictures of the actual screen rather than written steps, and facilitators are trained to notice the specific hesitation that means someone is decoding a word rather than deciding what to do. Nobody is asked to read aloud.
What people actually asked for
The most requested skills were not the ones we had planned for. We had built a sensible progression from digital literacy towards employability. Participants wanted three concrete things, urgently.
- Traders wanted to make a price list they could print. Not a spreadsheet course. A price list, printed, today.
- Parents wanted to fill in a school form without paying a business centre two hundred naira and waiting for somebody else to type it.
- Young people wanted a CV that looked like the ones they had seen online, and they were specific about the layout.
What unites those three is that each produces something the person can hold at the end of the session. Our planned curriculum produced understanding, which is worth more in six months and worth nothing at all on the walk home.
Cost is a teaching problem, not just an access problem
We knew data costs were a barrier to getting online. We had not thought carefully about what that does inside a lesson. Participants who pay for their own data are reluctant to experiment, because experimenting looks like waste. They ask for the exact steps and they do not click around.
Curiosity, which is how most people actually learn software, turns out to be a luxury good. The hub's pooled connection removes the meter, but only if facilitators say so explicitly and often. Now they do, in the first five minutes of every session: nothing here costs you anything, please break it.
What changes in the programme
The first four sessions of the hub curriculum now follow what people asked for, in the order they asked for it. Keyboard and trackpad first, then a printed document, then a form, then a CV. Everything we had originally planned comes after, and several things have been dropped entirely.
We have also changed how we measure the early weeks. Attendance at session four now matters more to us than any confidence score collected at session one, because people who come back are people the sessions are working for.
Why publish this
It would be easy to write this up after the corrections, present the revised curriculum as the original plan, and look competent. We would rather be useful. If you are designing digital skills training in a similar context, the two assumptions worth checking before you start are that phone fluency transfers to computers, and that your learners can afford to be curious.
Neither held here. We would be glad to hear whether they hold where you work.
