Skip to content

Projects

A project separates one product from the rest. What you discuss inside a project goes to that project: the Office conversation is pinned to it, documents are uploaded to it and its profile goes into the prompt of the roles working on it. With no project, everything falls into the common pile, which is called General.

You reach it from Projects in the menu, or from the project list in the left bar, which is always in view.

Element What it does
“Projects” header and the + Opens the new project dialogue
General Goes back to the common pile: no project
Each project Selects it as the active project. Hovering shows its description
“None yet.” Shown when there are none

The active project is marked in the list and appears as a badge in the top bar, next to the view title. Changing it deletes nothing: it only changes where the next thing goes.

At the top, “Your projects” and a New button that opens the same dialogue as the + on the left.

If there are none:

A project separates one product from the rest: its tasks and decisions do not mix. Create the first one and choose which one you are in from the left bar.

The warning for a project without a profile

Section titled “The warning for a project without a profile”

When some project has no written goal, a warning appears above the list: “Name has no profile” or “N projects have no profile”, with this explanation: a project without a profile is a drawer with a name; whoever works in it knows what to do, but not what for. The Define button opens that project’s profile.

Element What it shows
Name The project’s, followed by “· client” if it has a client
What it is after The goal, or “not defined yet”
What it is about The description, if there is one
“here” badge Marks the active project
“N goals” badge How many goals the project has
Profile / Define button Opens the profile. It is called “Define” while there is no goal, and then it is in the primary colour

The “General” row is different: it is titled “No project: the common pile”, it has no profile or goals, and it only serves to go back to it.

The New project dialogue says: “Separate one product from the rest: what you discuss inside does not mix with the others.”

Field What it is Limit
Name Required. The project’s internal code is generated from it 80 characters
What it is about (optional) One line to recognise it 140 characters
Project folder (optional) Where the code lives, if it lives anywhere: for example /home/pedro/mi-proyecto —
How its tests run Only appears if you have set a folder. For example .venv/bin/python -m pytest —

Buttons: Cancel and Create project. Enter in the name or in the description also creates it.

If you set a folder and leave the command empty, .venv/bin/python -m pytest is used. The other way round does not work: a command with no folder gives an error, because there is nowhere to run it.

Below the form it says so plainly: with a folder, Adrián can run the project’s tests where the code lives; without a folder, the project is born only for talking and deciding.

When you create one, it is selected as active and the top bar confirms it.

It opens as a wide dialogue, titled “Project · name”, with this line below: “What you write here is what every role working on it knows.”

The company strategy is not repeated here: mission, vision, values and focus live in Strategy and are common to all projects. What gets defined here is this project’s own.

Field What it is Example from the form itself
Name The project name —
Client Who it is for, if it is not internal “Who it is for, if it is not internal”
What it is about What is in scope and what is not “ERP for workshops: assignments, quotes and invoices. Accounting stays out.”
What you want to achieve The goal, in one checkable sentence “The first workshop working without spreadsheets before June.”

Below the fields, the list of the project’s goals. If there are none:

No goals yet. Without them, whoever works here only knows what has to be done, not what for.

Each goal shows its title, how it is measured (“Measured by: …” or “No metric”), its deadline if it has one, and a badge with its state, which here uses the internal name: active, proposed, met or discarded.

Only current goals appear in this profile. If you mark one as met, it disappears from here; it stays in Strategy, where you can return it to current.

To add one, three fields and a button:

Field What it is
Add a goal The title. Required
How it will be measured The metric: “3 workshops, 0 spreadsheets”
By when The deadline, in words: “This quarter, before June…”
Add button Creates the goal. Disabled while there is no title

The goal is tied to this project: only those working on it see it, not the whole company.

Button What it does When it is active
Save Saves name, client, description and goal. Goals are saved when you add them, not here Disabled while saving
Close Closes the dialogue Always

On saving, the server’s notice appears (or “Project profile saved.”) and the project list is re-read.

The profile and its goals go into the prompt of each role assigned to the project, not just the CEO’s. A role working here knows what it is about, what is being pursued and with which goals, without having to ask. And the profile is what gets read in the project list: if the goal is empty, the project shows up marked as “no profile”.

The Work board is not filtered by project: it shows every card in the office. The active project changes the conversation, the documents and the roles’ prompt, not that list.