Getting Started with AI at Work: A Practical Starter Kit

You open an AI tool, type a question and get a polished answer back. But how do you know whether that answer is useful, accurate or ready to use in your work?

Getting started with AI is about learning how to give it useful context, ask for something specific and check what comes back. Those habits matter whether you are drafting an update, exploring an idea or learning a new technical skill.

I’ve created the Coded Female AI Practical Starter Kit to help you practise those habits. It brings together clear explanations, worked examples and exercises you can try at your own pace.

Why I created this kit

My background spans engineering, web development, Scrum and product ownership. Over seven years, I’ve worked across development and data teams, helping people turn ideas into useful work and make decisions when things are complicated.

AI is part of my daily setup and workflow. I use it to organise information, explore options, shape drafts and support my learning. I still bring my own judgement to the result, particularly when something affects a team, a customer or a delivery decision.

That practical approach runs through this kit. I wanted to give you examples you can understand, questions you can reuse and a clear way to decide what needs checking before you use an answer.

Start with a small, useful task

You do not need an elaborate workflow to begin. Try a short task where you can easily compare the answer with the information you supplied.

An example: turn notes into an update

Imagine you have these three notes from a fictional project:

The registration form has been built in the test environment.
Confirmation email testing has not started.
The launch date has not been agreed.

A prompt you could try

“Turn these notes into a stakeholder update of no more than 60 words. Use two headings: Progress and Still to confirm. Use only the facts provided. Do not add a launch date, an owner or a claim that testing is complete.”

An illustrative response

Progress: The registration form has been built in the test environment.

Still to confirm: Confirmation email testing has not started, and the launch date has not been agreed.

Before using the update, compare it with the original notes. Has it kept the meaning? Has it added anything? Could a reader mistake “built in the test environment” for “ready to launch”?

This is the pattern you will practise throughout the kit: provide context, give a clear request and review the answer against the source.

What’s inside the starter kit?

The 35-page guide starts with the basics and builds towards practical product and delivery examples. You can work through it in order or choose the section closest to a task you already do.

Practical skills you can build

Understand the basics: learn what generative AI does, where it can help and why confident answers still need checking.
Write clearer prompts: give useful context, explain the task and describe the output you need.
Explore a product request: separate known information from assumptions and identify useful questions.
Draft backlog items: practise turning a request into a draft with acceptance criteria you can review.
Organise feedback: look for themes while keeping the link back to the original comments.
Prepare updates and planning conversations: organise information without inventing progress, estimates or commitments.
Think through product metrics: connect a measure to a question or decision, and check the calculations.
Support technical learning: use explanations and small code examples, then test your understanding.

The kit also includes a practice project, worked examples, review checklists, troubleshooting guidance and worksheets for planning a task and checking the result.

What about connecting AI to Jira?

You may have heard about AI connectors or MCP, which stands for Model Context Protocol. MCP provides a standard way for compatible AI applications to connect to external tools and information.

A Jira connection is one example. Depending on the application, connection and permissions, an AI tool may be able to retrieve work items or help you prepare changes. Reading information and changing information are different actions, so it matters which permissions you enable.

Understand the connection before using it

The kit explains the difference between pasting information into a chat and using a connected tool. It also covers checking the source, understanding permissions and reviewing a proposed change before it is carried out.

You can complete the beginner exercises without connecting Jira or any other tool. The connector section is there when you are ready to explore that next step.

How to use the kit

Start with the five-minute exercise on page 3. It gives you a small task and a simple way to check the response.
Choose one example that feels familiar. A stakeholder update or a short set of notes is a useful starting point.
Use the practice information provided. For real work, use an approved tool and follow your organisation’s rules about what you can share.
Review the result with the worksheet. Check facts, assumptions, missing information and whether the output actually answers your request.
Keep a note of what you changed. Record which instructions helped and which parts still needed your judgement.

You do not need to finish everything in one sitting. One task, one reviewed answer and a few notes about what you learned are enough for a useful practice session.

Download the AI Practical Starter Kit

Start with the PDF guide, use the worksheets to practise, or download the editable version to add your own notes and examples.

Download the starter kit (PDF) Download the editable version (Word) Download the practice worksheets (PDF)

The worked scenarios and sample responses are illustrative practice material. Use them to build your skills, then check any real output against your own sources and context.

Try one task today

Pick a task you understand well. Give the AI tool enough information to work with, ask for a specific result and compare its answer with your source.

My approach to AI fits the way I approach product and delivery: help tech teams ship work that matters, with less chaos and without burning out the people doing it. Clear requests, useful drafts and thoughtful review are a practical place to start.