AI in your development team’s everyday work
Your team’s tasks.
AI skills that stick.
Practise using AI on examples that fit your work. We go from clarifying the task to a checked result ready for handover — with a method your team can use the next day.
Primarily for development and technical teams. Adapted to participants’ experience and your company’s tools.
AI is in the team. Is there a shared way of working?
Some colleagues already use it well; others spend a lot of time experimenting. One result is useful, another is hard to verify. The workshop helps turn individual techniques into a method the whole team can apply.
Participants do the work themselves, with instructor support. The goal is to prepare, carry out, assess and improve AI-assisted work independently.
Shared foundations. Then your own projects.
Two parts with distinct goals. They can be booked together, with separate time for applying the methods in your own environment.
-
Shared foundations and working methods
Practise task framing, context, AI tools and verification on a prepared project.
Recommended format: four three-hour sessions, with practice between sessions.
-
Application in your own projects
Choose real tasks, prepare repositories and work with the team’s tools. Turn the experience into shared instructions and verification steps.
A separate multi-session block. Timing follows the projects and the preparation required.
Teams with the foundations already in place can start with their own projects after an initial readiness discussion.
The foundation programme.
Building on a previously delivered programme, four sessions lead from shared foundations to a checked solution ready for release. This outline covers the first part; application to your own projects follows separately.
-
Foundations and deliberate tool use
What we practise
Where is AI useful, and where do people need to stay in control? Choose tools, frame tasks, provide context and recognise common mistakes.
What you build towards
Know what to delegate to AI and what to check yourself.
-
From a request to a checked solution
What we practise
Turn an unclear request into a concrete task. Define the expected result, make a plan, then develop, test and revise with AI.
What you build towards
Work through a task and explain whether the solution is good enough.
-
Reusable team methods
What we practise
Choose a model for the task, consider costs, and establish shared project instructions and working steps. Practise code review too.
What you build towards
Start the next task with shared instructions and useful checks already in place.
-
From completed code to a safe release
What we practise
Connect implementation, automated checks and human approval. Work through release and rollback steps using small changes and fast feedback.
What you build towards
Understand what it takes to get a change safely from the repository to the user.
Each session: a short explanation → a guided live example → shared practice → a task to try at work. In a multi-session programme, we bring experience from everyday use back into the next session.
What stays with your team.
Take the work from the sessions into your next task.
Use it again tomorrow.-
Worked examples
The solution, its checks and the feedback from working through it together.
-
Reusable templates
Task descriptions, project instructions and review criteria for the next piece of work.
-
A shared working method
When to use AI, what context to provide and how to review the result.
-
An assessment and next steps
What you can already apply independently, what still gets in the way and where to go next.
Bring a team and a few real tasks.
-
Understand the starting point
Who will attend, how do they use AI today, and where would they like more independence? Choose a learning goal and representative tasks.
-
Prepare the practice
Agree which tools and data can be used, and try the required access. We can use a prepared practice project or your own repository with suitable preparation.
-
Agree the programme
Set the session count and length, group size, preparation, follow-up and fee. Your team provides a contact person and time for participants to practise.
Scope and fees are agreed before starting. For the first conversation, a short introduction to the team and its tasks is enough.
A few practical questions.
Is this only for developers?
Development is where our experience is strongest. We can also build programmes around QA, operations and project management. For other teams, we first look at a few tasks to see where we can help meaningfully.
Do we need an FDE engagement or Berek?
Workshops can stand alone. We get to know the participants, tasks and tools beforehand. Berek is not a prerequisite. If access, tools or process gaps prevent progress, we may propose separate implementation work to address them.
How do we know it helped?
We assess work on a task chosen in advance, using agreed criteria: can participants prepare the task independently, verify the result and improve it when needed? The closing assessment also identifies remaining obstacles.