We plan several sessions around one project.
Work on a robotics or AI task with MazTech over a sequence of group sessions. We start with the participants' experience and the equipment they can use.
The project gives each meeting a purpose. We agree what the group will try, where the next session picks up and what participants will keep. Send us the hours you have available and the problem you want the group to work on.
Plan a series for your group
A series gives the group time to return to the work.
A single MazTech workshop centres on a focused activity. A series is useful when the group needs to carry the same project between meetings: try a change, record what happened and use the next session to address it.
Choose the format around that need. If the task fits into one meeting, we can discuss a workshop. If it depends on several practical steps or the group already has a project under way, describe those steps in your brief. We will help turn them into a sequence that fits the available time.
Start with a robot behaviour or an AI task.
Robotics
A robotics project can connect code to movement or a sensor reading to an action. We discuss the hardware already available and a manageable task for the group. The sessions can follow the same robot through changes to its control, with participants observing what their changes do.
For a group that already writes code, send a sample of the current project and name the tools it uses. That gives us a better starting point than a broad topic label.
AI
An AI sequence begins with a defined task and suitable data. We agree the tools the group will use, then build sessions around trying the task and examining the output. Participants need time to discuss where a result is useful and where it still needs a person's judgement. Use a sample task that you are comfortable sharing at the planning stage.
Tell us which devices the group can use.
For a MazTech robotics series, list the robots, controllers and sensors on site. Include the number of working devices and whether participants will share them. For activities using software, tell us the available computers, operating systems and internet access.
We use this information to plan the practical work. Let us know who can install software and whether devices can remain set up between meetings. Sessions take place at an agreed venue. If the project also needs equipment supply, we identify that separately in the proposal so your organiser can see which items belong to each part of the request.
We set the hours around your group.
Send the preferred dates and the length of each available slot. A robotics task involving shared hardware has different pacing from an AI activity on individual computers. We discuss the sequence with those limits in view, including the time the group needs to test its work.
Tell us if participants will work on the project between meetings. If they will, we can define what they should bring back to the next session. If all work happens in the room, the session plan should account for that. We put the agreed schedule and responsibilities into the scope.
Name what the group will keep.
With MazTech, the output belongs in the brief.
The intended output might be project files, a record of a test or a small working task. We agree it with you before the sessions begin, using the group's experience and the available equipment to set the scope.
For an ongoing robotics project, explain who will use the files afterwards and which tools they have. For an AI task, describe how the organiser expects to review the result. This helps us specify a useful handover. If your main need is a technical review of an existing project, our technical and AI advisory work may fit the request.
Send us the project and the available hours.
Include the group size, starting experience and equipment list. We can discuss the sequence from there.