New publication: MAPMAKERS vs OPAQUERS
In my mind-map I can resolve and explain a seeming discrepancy, but in the world of software logic, the business case of spelling a middle name in two different ways becomes quite opaque, like Kafka’s mysterious bureaucracies and dark corridors.
How can my software reconcile records that exist for years in their various forms in different database locations and relationships? How can I find the logic that prevails?
In today’s applications, the user interface, if you can find the right one, tells a stakeholder what data is for by relying on the stake-holders mental model of a process. But it does not tell the stakeholder how the data is converted so that, for example, a person’s identification credentials are accepted.
How can mapmaking help solve this?