AYCADO Projects

These are participants who have already completed structured learning through AYCADO Academy or AYCADO Skills Lab. They arrive with foundational knowledge in areas such as communication, planning, research or digital skills, and with some experience of AYCADO's expectations around attendance, preparation and conduct.

Projects gives them the next step: applying what they learned in conditions closer to real work. Instead of completing exercises, they take responsibility for tasks that others depend on, work with teammates they did not choose, and find out which skills hold up under deadlines and which need more practice.

Facilitators review their work and give direct feedback, helping them see the gap between knowing a concept and using it well. The experience builds a practical record that supports progression into Career Hub, Fellowship or further professional development.

This group includes secondary school and university students who want to use their education beyond assignments and examinations. Many have strong subject knowledge but limited experience of working on something with real stakeholders, real constraints and results that matter to someone other than a teacher.

Students can join a project team alongside their studies, taking on defined responsibilities such as research, planning, outreach or documentation. They learn how to work with people of different ages and backgrounds, communicate professionally, manage their time and see a task through to completion.

The experience often helps students connect what they study to the kind of work they might want to do, and clarifies which interests are worth pursuing further. Participation is a practical learning experience; it does not in itself carry academic credit or guarantee employment.

Recent graduates and people early in their careers often find that a qualification alone does not show employers what they can actually do. Applications for jobs, internships and fellowships increasingly ask for examples: a project delivered, a problem solved, a responsibility carried.

In Projects, graduates take on a clearly defined role with named deliverables. Their contribution is documented through task records, progress reports, presentations and a written reflection, creating evidence they can refer to in interviews and applications.

The emphasis is on accurate, verifiable evidence of individual contribution rather than a certificate of attendance. Graduates are expected to describe their role truthfully, distinguish their own work from the team's, and be able to explain the decisions they made and what they learned.

Some participants arrive not as individuals but as an existing group of young people who share a concern about their community, such as youth unemployment, access to information or environmental conditions. They have the motivation to act but may lack a structured way to plan and deliver.

These teams use the Projects pathway to turn that concern into a practical initiative. They confirm the need through consultation, set objectives, divide responsibilities, build an implementation plan and identify what support they need, whether from AYCADO mentors, local institutions or community members.

Throughout, the initiative remains owned by the young people leading it. Teams are expected to include affected community members in decisions, use any resources responsibly, document their results and review whether the initiative made the difference they intended.

Participants work in small teams of four to six people, each team responsible for delivering one defined project from start to finish. At the outset the team agrees who leads coordination, who manages records, who handles research and who presents progress. These roles are written down, so every member knows what they own and what others are counting on them to complete.

Teams meet regularly to report progress, raise problems early and make decisions together. When views differ, members are expected to set out their reasoning, listen to alternatives and reach a decision the team can act on. Disagreements are treated as a normal part of working with others; facilitators help teams resolve them through discussion rather than by avoiding them.

Because teams bring together people with different personalities, working styles and other commitments, participants learn to balance competing priorities, keep promises to colleagues and adjust when a teammate needs support. The result belongs to the whole team, and so does responsibility when something falls short.

Before any team proposes a solution, it must show that it understands the problem. Participants speak with the people affected, observe the situation directly where possible and gather basic information from available records or published sources. The aim is to describe what is actually happening, not what the team assumes is happening.

Teams then separate symptoms from causes. Low attendance at a youth programme, for example, may be the visible symptom, while transport costs, timing or lack of information may be the underlying cause. Once the root cause is clear, the team writes a short problem statement and sets objectives that describe what a successful response would change.

Only then do teams consider possible approaches. They compare at least two options, assess each against the time, skills and resources realistically available, and choose the one most likely to work. Participants learn that evidence, not enthusiasm, should decide which solution is pursued.

Once a solution is chosen, teams turn it into a plan they can actually deliver. They define the deliverables the project will produce, break the work into specific tasks, assign an owner to each task and set realistic dates. Teams also estimate what they will need, such as materials, transport, venues, equipment or volunteer time, and identify where these will come from.

Each plan includes a short list of risks: what could delay or derail the work, how likely it is and what the team will do if it happens. During delivery, teams track progress against their plan using simple tools such as a shared task list, a timeline chart or a weekly progress report.

When tasks slip, as they often do, teams are expected to notice early, explain why and adjust the plan rather than hide the delay. Participants learn that good project management is less about a perfect plan and more about keeping honest track of where the work stands.

Some projects begin with a need in a participant's own community. Young people identify an issue they have seen first hand, then test whether others share that view by consulting residents, local leaders, schools or community groups. Initiatives proceed only when the need is confirmed by the people it affects, not assumed on their behalf.

Participants lead the initiative themselves, with facilitators and mentors offering guidance rather than direction. Teams are expected to include the voices of those often left out, such as young women, people with disabilities or those outside formal education, and to explain clearly to beneficiaries what the initiative can and cannot offer.

Where resources are needed, teams learn to approach local organisations, businesses or institutions with a clear request and to account for anything they receive. They implement their plan, keep beneficiaries informed and remain answerable to the community for how the initiative was carried out.

Every project keeps an accurate record of its work. Teams take meeting notes, log activities as they happen, keep copies of plans and correspondence, and collect evidence that work was carried out, such as attendance lists, outputs produced and, where people have given permission, photographs.

Documentation follows clear ethical standards. Participants ask for consent before photographing or quoting anyone, protect personal information and avoid presenting beneficiaries in ways that could embarrass or expose them. Records must reflect what actually happened, including what did not go to plan.

At the end of the project, teams prepare a final report and present their work to facilitators, peers and, where appropriate, partners or community members. Presentations cover objectives, activities, results, challenges and lessons learned. Participants learn to communicate achievements confidently while being honest about limitations.

Review is built into the project, not left until the end. At set points teams hold progress reviews where they compare what was planned with what actually happened, discuss what is working and identify what needs to change. Mentors and facilitators attend some of these reviews to offer guidance and challenge assumptions.

Participants also give and receive structured peer feedback, focusing on specific actions and their effects rather than personal criticism. Each member reflects on their own contribution, including mistakes and missed commitments, and identifies how they will work differently.

Teams then act on what they have learned. They agree corrective actions, test an improved approach and check whether it made a difference. Treating mistakes as information to act on, rather than something to conceal, is one of the most important professional habits this pathway develops.