Back to The Openbit JournalResponsible AI · 3 minute read
Home / The Openbit Journal / Starting With AI
Responsible AI

Where to start with AI, and what actually matters.

Most owners do not need another tool to manage. Start with the work that already slows people down, then check that the time you saved survives the review.

Openbit Field Guide05Clear guidance for better technology decisions
A team reviewing an automated workflow and its approval points

Most owners do not need another piece of software to manage. They need more time, fewer repetitive tasks and a team that can get through the day without playing catch-up. That is where AI can be useful, and the question is a simple one: where could it make work easier for the people you already have?

Start with the work that slows people down.

Before choosing a tool, talk to the people who will use it. Ask what takes too long. Ask what they copy and paste, which questions they answer every week, and what keeps getting pushed aside because there is never enough time. Their answers will give you a better starting point than any product demonstration.

A sales team might need help drafting follow-ups. A customer service team might spend too long on routine questions. Someone in operations might lose an afternoon a week rebuilding the same report. Pick one of those and find out whether AI helps.

The same customer questions, every day.

Your team already knows the answers to “what should I prepare before my appointment” and “does your service cover this”, but writing each reply still takes time. An AI tool could draft one from your approved service information. An employee checks it, changes what needs changing, and sends it. A modest change, but a useful one: less time starting from a blank page, and someone who understands the customer still owns the answer.

Are replies faster?

Measure the whole task including the check, not the moment the draft appears on screen.

Are they accurate?

A wrong detail sent to a customer costs more than the minutes saved writing it.

Small edits or full rewrites?

If every draft gets rewritten, the tool is not helping with that particular task.

Does the team still use it?

Adoption after the novelty wears off is the honest signal that it works.

Give your team time to learn.

Handing out accounts and expecting people to work it out rarely goes smoothly. They need to know what the tool is good at, when to use it and what to check, plus room to experiment and ask questions. Some will be enthusiastic. Others will quietly wonder what it means for their job. Be clear about why you are introducing it, and involve them in deciding how it fits their work. Start with a few real examples from their own week rather than a presentation about everything AI might one day do.

Watch the accuracy.

The easiest mistake is trusting an answer because it sounds confident. AI gets details wrong, drops context and invents information. A polished email can promise a service you do not offer. A meeting summary can miss the decision everyone was waiting on. An answer about company policy can be two years out of date. Someone has to review the work before it reaches a customer or shapes a decision. NIST lists inaccurate generated content as a risk businesses should plan for. The rule worth giving employees is short: treat the output as a draft you are responsible for checking.

Decide what information goes in.

Before anyone uploads a customer list, a contract or an internal report, set the rules on what may be shared. Check how the provider handles data: who can access it, how long it is kept, and whether it is used to train their models. The answers depend on the product, the plan and the settings you chose. If an assistant connects to your company files, check its permissions too, so employees can only retrieve what they were already allowed to see. These decisions are far easier before the tool becomes part of everyone's routine, which is why the NCSC treats security as part of setup rather than something added later.

Four questions a pilot should answer.

  • Are we saving time once the work has been checked?
  • Is the quality as good as before, or better?
  • Does the team genuinely find it useful?
  • Is the improvement worth the cost, including the hours spent training people?

If the answer is no, change the approach or try a different task. A pilot exists to teach you that while it is still cheap to learn. You do not have to roll AI into every department at once: one task, a small group and a clear goal is enough to start.

The practical takeawayAsk your team this week what they spend too much time doing. Their answer is usually the best place to begin.