Action-Oriented Projects

A simple way to turn shared purpose into organised, cumulative action

An Action-Oriented Project (AoP) is a public, ongoing project organised around a mission.

It is not primarily an event, a website, a discussion group, or a project-management system.

The work comes first. The gathering accelerates the work.

The basic idea

Most events work like this:

Event → people attend → people talk → event ends

An AoP works differently:

Mission → people → activities → projects → action → evidence → replication

People can begin contributing before any gathering, use a gathering to accelerate decisions and collaboration, and continue the work afterwards.

The project therefore doesn't end when the meeting ends.

What can people actually do?

An AoP can invite people to:

• understand the mission
• share their knowledge or experience
• research a question
• identify a problem or opportunity
• propose an idea
• connect relevant people
• build something
• test something
• document evidence and learning
• continue or replicate useful work

These are generic activities, not a rigid programme. Each AoP can adapt them to its mission.

What is produced?

The important outputs are not just presentations or minutes.

An AoP accumulates artifacts:

• People — who is contributing and what they can do
• Projects — defined pieces of work serving the mission
• Actions — concrete commitments and things actually done
• Evidence — research, experiments, results, failures and learning
• Replication — what others can reuse, adapt or start elsewhere

The project becomes a living record of work, rather than a report about an event.

What about principles?

An AoP can develop principles from the body of work surrounding its mission.

For example, the Humanity AoP began with a large body of existing writing. Recurring themes were identified and developed into fifteen principles.

That is an example, not a prescription.

Any organised body of work could potentially do this — a book, an author's writings, research, an archive, a community's knowledge, an existing movement, or years of accumulated conversations.

The process is:

Organise → publish → discuss → discover themes → challenge them → turn understanding into action → learn → accumulate

The principles themselves can therefore evolve as understanding develops.

Why publish everything cumulatively?

Because important conversations are too easily lost.

An AoP aims to make its evolving work available, connected and cumulative.

A new participant should be able to discover:

What is this about?
What has already been learned?
Who is involved?
What is happening now?
What can I contribute?
What happened when someone tried this before?

The history remains part of the project.

Is it Google Drive? Wikipedia? Jira? GitHub?

It can look a little like all of them — but the philosophy is different.

• Google Drive stores
• Wikipedia accumulates knowledge
• Slack facilitates conversation
• Jira / Trello / Asana coordinate work
• GitHub builds collaboratively
• A CRM organises relationships

An AoP can use ideas from all of these.

But it starts somewhere else:

There is something worth doing.

The tools and artifacts exist to help people understand that purpose, contribute to it, act on it, learn from it and help others continue it.

Why AmadeusWeb?

AmadeusWeb Spring was designed around the idea of organised, published and cumulative work.

That makes it a natural substrate for AoPs.

The underlying technology does not have to be complicated.

A simple, inspectable collection of documents can become:

a body of knowledge → a conversation → a set of activities → projects → action → evidence → a living public record.

Sophisticated software can be added where it helps.

But the philosophy comes first.

The shortest possible definition

An Action-Oriented Project organises people around something worth doing, makes the work cumulative and public where appropriate, uses gatherings to accelerate it, and turns what is learned into further action and replication.

Don't organise an event about the work.
Organise the work — and let the event accelerate it.