Employee Data Needs an Obligation
Design-fiction questions about employee databases expose the obligations that follow when a directory records informal expertise and personal information.
An employee directory looks harmless when it contains only a name, a role, and a route to contact someone. It becomes a different kind of record when it starts identifying capabilities that formal credentials do not capture, especially once colleagues can endorse those capabilities and someone else can act on the result.
A design-fiction exercise makes that change visible through questions rather than a finished answer. It begins with achievement patches distributed with educational books, then asks what visible community markers might mean for learning outside institutional credentialing. It moves to Roster Intelligence, an imagined system that tracks formal credentials and demonstrated informal expertise through peer endorsement. From there, the questions reach professional licensing, hiring criteria, and expertise validation.
I am not proposing that every directory become an assessment system; I am pointing to the moment when identity, access, and obligation become inseparable, which happens as soon as the system records more than employment facts.
A marker can recognize learning without settling it
The patch scenario asks what happens when readers recognize fellow learners in the world through a visible marker. The question separates recognition from formal certification. A marker may tell someone that another person has engaged with a shared educational material or practice. It does not automatically establish the meaning, depth, or authority of that learning.
That distinction is useful for employee data. A system can make experience more visible without claiming that every visible experience has the same status as a professional credential. The difficult work lies in keeping those categories clear. Formal credentials and informal expertise may both matter, but they do not become interchangeable because they appear in the same database.
Peer endorsement makes the problem more concrete. An endorsement records a relation: someone has recognized a capability in another person. It may provide a useful signal. It may also require a careful account of what the endorsement means, who can see it, and what decisions it may influence.
Informal expertise changes the directory
An ordinary directory helps people locate one another. A directory that records demonstrated informal expertise can help a person locate relevant practice as well. That may be valuable in an organization where much knowledge is not captured by credentials alone.
It also changes the directory’s responsibilities. The record is no longer merely a contact route. It becomes a representation of a person’s capabilities, possibly assembled from peer recognition. The system has to distinguish what is formal, what is informal, and what evidence supports each claim.
The exercise poses questions rather than prescribing one architecture. That restraint is appropriate. Professional licensing, hiring criteria, and expertise validation carry different stakes. A capability visible in a peer network may be useful for finding a colleague to ask a question. It may be inadequate, or inappropriate, as the basis for a formal employment decision.
Access remains part of the design
The exercise directs attention to identity, access, and obligation. A system that holds personal information about a person has an obligation to decide who may see it and why. It does not prescribe a complete policy, but the questions show why access cannot be treated as an afterthought.
Informal expertise can be personally revealing. It may describe work a person does beyond a formal role, interests that have not been offered for broad use, or a reputation built through particular relationships. A useful directory must therefore account for the difference between information that helps people find a colleague and information that exposes a colleague to a use they did not expect.
The same concern applies when a person changes roles or leaves an organization. A directory must decide how to treat personal information after either event. Data does not become neutral simply because it remains technically available.
Design fiction supplies the question before the rule
The prompts do not supply a ready-made solution. They make an ordinary employee database strange enough to inspect, and once informal expertise, peer endorsement, visible learning markers, and future access appear together, a team has to decide what each record is allowed to mean before the interface gives that meaning the appearance of fact.
That decision belongs before implementation. A directory can make people and their knowledge easier to find, but it should not quietly convert recognition into certification or present availability into permanent permission. If the record grows more ambitious, the obligation around its use, access, correction, and eventual removal has to grow with it.
