
Most products built for immigrants get the problem backwards
There is a certain kind of product that gets built for immigrants, and it almost always begins from the same quiet assumption: that the person arriving is the thing that needs fixing. The language is gentle and the intentions are usually good. Help them adjust. Help them integrate. Teach them how things are done here. But underneath all of it sits a picture of the immigrant as someone who shows up lacking, a gap to be filled by whatever the product happens to offer. We have come to believe this is the single biggest mistake in the whole category, and building for the diaspora is what taught us to see it.
Because when you actually sit with the people these products are meant to serve, the deficit is almost never where the framing assumes it is. The nurse who moved from Lagos did not forget how to be a nurse on the flight over. The engineer who lands in London did not lose years of experience somewhere over the Sahara. What they lost was context. The employer who would have vouched for them is thousands of miles away. The qualification that meant everything back home now sits unrecognised in a system that has no idea how to read it. The professional network that would have opened a door does not exist here yet. The problem was never a shortage of ability. It was that everything which used to prove that ability stopped travelling with them at the border.
The second mistake follows naturally from the first. Once you have decided the immigrant is a problem to be solved, you tend to treat all immigrants as the same problem. But there is almost nothing that a doctor on a skilled visa, an international student, a refugee, and someone joining family already settled here truly have in common, beyond a single word on a government form. Their needs are wildly different. Their starting points are wildly different. A product built for the average immigrant ends up fitting none of them, because the average immigrant is a statistical fiction that describes no actual living person. The label is administratively convenient and almost useless as a design brief.
What all of this pointed us towards is that the real barrier is recognition, not remediation. When you cross a border, your reputation quietly resets to zero, and the work of rebuilding it is enormous, invisible, and mostly done alone. That is the actual problem worth solving, and it produces a very different product than one built to fix a person who was never broken. TechBridge Academy came out of exactly that shift in thinking. It runs for six months and helps people build tech careers in the UK, and the entire premise underneath it is that the people it serves are already capable. What they need is translation and navigation, a way to make real talent legible to a system that does not yet know how to see it, not a lecture on how to become employable. We treat everyone who comes through it as a professional who has been temporarily separated from their proof, because that is genuinely what they are.
There is a deeper reason this matters beyond getting one product right. When you design from a deficit, the person can feel it, even when the product works. Something built to fix you carries a quiet insult no amount of polish removes, and people can tell the difference between a tool that respects them and one that is doing them a favour. Dignity is not a nice finishing touch you add at the end. It is a design decision you make at the very beginning, in the assumption you hold about who your user is before you build anything at all.
So if you are building for immigrants, or honestly for any group the default was never designed around, the most useful thing you can do is flip the first question. Do not start by asking what this person lacks. Start by asking what they already carry, and what the system around them is failing to see. Assume competence and solve for context. Design for recognition rather than rescue. The diaspora is not a charity case waiting to be helped. It is a large, capable, badly served group of people who simply were never the user anyone had in mind. Build as though they are exactly who you are building for, and you will end up making something people actually want to use, rather than something they are quietly expected to be grateful for.
solveX is a product studio building digital tools for African and diaspora communities across Nigeria and the UK.