Personal space and project space

Workomator has two places for information because not every useful thought is ready to become shared direction. Personal space is for thinking in progress. Project space is for the context a team needs to act together.

Keeping those roles separate protects both. People can capture ideas without performing them for a group, and the project stays a clear record rather than a stream of every unfinished thought.

Personal space: where work starts

Personal space is your place to capture a tension, a question, an observation, or a possible next move while it is still forming. Your Idea field and Build queue stay private to you.

Use it to:

• capture the thought before it is polished or classified;
• explore whether it is a task, a decision, or a potential specification;
• refine the intended outcome and identify what is still unclear; and
• take on work without making every early move visible to the team.

The important rule is simple: private does not mean disposable. The source context stays attached as a thought moves forward, so you do not have to reconstruct why it mattered later.

Project space: the shared product record

Project space holds the information that changes the product’s direction or helps others understand it. This is the place to publish the decisions, constraints, and plans that should outlast one person’s active task.

It includes:

• Roadmap — the sequence of meaningful outcomes and their current state;
• Features — the product capabilities under consideration, their horizon, intended outcome, and success signal;
• Specs — build-ready definitions of behavior, scope, review state, and published revisions; and
• Project memory and wiki — the brief, product language, decisions, constraints, and references that give the plan its meaning.

Project memory is not another backlog. It is the durable context behind the plan. Features and specs should use that context without copying it into every record.

When should something move from personal to project?

Move information into the project when it needs to become a reliable reference for more than one person. A useful test is: would someone else need this to make the same decision or do the work well?

If the answer is yes, make it part of the project record. That might mean adding a constraint to memory, recording a decision in the wiki, placing an outcome on the roadmap, or creating a feature or spec for shared review.

If the thought is still exploratory, uncertain, or only affects your own next move, leave it personal until it earns that role.

The result: shared direction without shared noise

The boundary lets each person think freely while the project remains legible. Personal work can be messy, provisional, and focused. Project work can be deliberate, durable, and ready for collaboration.

That is how Workomator keeps the reasoning close to the work without turning every private note into a team obligation.