n.V6-2.02 | Tech as Pacemaker
01| A pacemaker does not make the heart beat. It corrects the rhythm of a heart that is already beating, and by doing so it gives a person back the life they were losing. It raises potential. It does not create it. Take the pacemaker out of a dead man and nothing changes, because there was nothing there to correct.
02| That is the whole relationship between our technology and our Maveriqs, and I use the comparison deliberately because it puts the machine in its place. People make social progress. Technology helps them do it faster, cleaner and with less waste. A Maveriq putting on her boots to clear a ditch full of plastic is the thing itself. Every screen in this volume exists to get that ditch cleared quicker, cheaper, and with more people showing up next time. If a feature cannot be traced back to that ditch, it should not be built. Know what I mean?
03| This sounds obvious and it is routinely ignored. Technology has a gravitational pull. It is measurable, it is impressive, it produces demos, and it lets everyone in the room feel like progress is happening. Human performance is slow, uneven, and embarrassing to report. Given a choice between building another dashboard and having a hard conversation about why nobody in the third barrio is finishing their projects, most organisations build the dashboard. We will feel that pull too.
04| So here is the arithmetic that governs this volume. If the tech is below par, we fail. If the human performance is below par, we fail. Those two failures are symmetrical and neither one rescues the other. The most elegant platform ever built, handed to Maveriqs who lack the confidence to speak up in their own group, produces nothing. A room full of brilliant, motivated changemakers handed a platform that crashes on Tuesday produces nothing either — and worse, it produces the specific lesson that this whole thing is not serious.
05| Which raises the question I cannot answer and will not pretend to. Can technology raise a Maveriq's confidence? Not her skill — skill is trainable, and V4 deals with it. Confidence. The willingness to put an idea on the table when three louder people in the room have already dismissed it. That capacity is worth more to our output than any feature in this volume, and I genuinely do not know whether software can move it. Maybe visible progress does it. Maybe a record of your own contributions does it. Maybe it is entirely a human matter and the machine is irrelevant. I am flagging it as open because it is open.
06| What we want. Technology that increases what an inexperienced person can accomplish, without ever becoming the thing she has to accomplish. Boring, unglamorous, always there.
07| What that takes. Everyone who has built for low-resource users says the same thing. It takes ruthless restraint about features, and it takes putting real money into the unglamorous half — support, training, fixing what irritates people. That half never demos well and it is always the first thing cut.
08| What we sacrifice. When the budget forces a choice — and it will, repeatedly — the human side wins. We spend on training a Maveriq before we spend on making the interface prettier. The price is real and I will not dress it up. Our product will look less impressive than it could. We will lose users who expect polish and judge us by it, including some funders. Our technical maturity will lag behind organisations that made the opposite choice. I accept all of that, because a beautiful platform serving people who cannot use it well is a monument, and I am not in the monument business.
09| The technical decision — what to build first, what to buy, what to leave out entirely — is not mine. What is mine is the order of the queue when there is not enough money for everything. People first. Every time.
