Sometimes the right product has no AI button

The visitor needs a vacancy, not a demonstration

A job seeker comes to a vacancy list because they want to find something worth applying for. They should not need to understand how the information was collected or which tools helped prepare the site. Their next action is to inspect a role and visit the employer’s advert.

Nottinghamshire Jobs keeps that activity central. Its purpose is to reduce fragmented searching across local recruitment sources. It is intentionally a simple public utility, even though the work of preparing useful information can be more complicated.

Keep the interface close to the task

The current application uses plain HTML, CSS and JavaScript and loads a replaceable vacancy file in the browser. There is no runtime AI, account system or database behind that public list. Those choices keep the visible product close to what the visitor needs.

A summary can help someone decide whether to open an advert. A closing date can help them plan. Neither requires a conversation when the information is already available. Putting the information directly in the right place can be more useful than making a person ask for it.

The hidden work still needs judgement

Simplicity at the front does not excuse carelessness behind it. Vacancy preparation needs source checking and review. The official employer advert remains the authority for duties, eligibility and how to apply. Updates are a separate process from browsing the public site.

Missing information also needs honest handling. A blank summary is not a reason to make up duties. A date that is not stated should not become a guessed deadline. A product can be clear without pretending the source is complete. This is especially important when someone’s time and opportunity depend on the information.

Separate collecting from interpreting

Nottinghamshire Jobs includes development-pilot tooling for collecting evidence from known sources. Fixed collectors can preserve URLs and source text for later editorial work. The pilot is not proof of an adopted automatic weekly service.

Editorial judgement then has a clearer input to inspect. It still needs source checking and should not turn a public summary into a personal suitability judgement. AI assistance belongs where interpretation helps; repeatable collection and a person’s employment decision have different responsibilities.

A smaller product can make a clearer promise

The list makes a bounded promise: help you find a role to investigate. It does not decide your suitability, write your application or guarantee the vacancy is still open. Those are different tasks, with different responsibilities and evidence.

My Next Step’s current application code includes a catalogue connection to this vacancy feed. That does not establish availability in every installation. The public list itself keeps a smaller purpose: give someone a place to begin looking, with the employer’s advert as the next source to check.

I can keep that wider possibility in mind without asking the current tool to stand for all of it. Someone deciding whether to use it needs to know what it can do now.

Begin with the easiest useful next step

If you know a problem well, you may already know where people waste time or lose confidence. That is a good place to begin building. A clear list, a readable explanation or a simple comparison may make the next step easier without needing a complex system.

Ask what the visitor needs to decide and what information they need for that decision. Then ask which work belongs before they arrive. AI may help the builder prepare, organise or inspect information. That does not automatically mean the visitor needs an AI interaction.

A static list has limits. Some needs do call for live interpretation, private information or conversation. I would add those when a particular need becomes clear. For this list, I have not yet found a reason to put a conversation between someone and the advert they want to read.

Related project