Projects are the basic concept in Operating. All work is related to a project. This document explains how to use the different metadata fields.

Project owner

The won project has no owner. This isn’t ideal! Who is able to build the team and make the client happy? Assign the person who takes care of it.

We believe that each project should have exactly one person at a time responsible for keeping that project – or opportunity – alive and well.

• Early in the sales process, the salesperson
  • If you’re using a CRM for opportunities/deals, the salesperson does a lot over there. The relevant information is synced with Operating.
• Later, whoever is responsible for the team setup – make it clear for everyone if this work is handed over
• Once the project is in progress, the owner is typically the project manager, as they are most likely to answer questions like “is the schedule still realistic” or “when does Alice have availability”.

Filtering per owner is super useful – in this case, for Kanchana herself:

Project group

Each Group is a part of your organization’s structure. The bigger the company, the more sense it makes to run reports per business unit, office, etc.

Using project groups is completely optional. In the filtering example above, you can see that Kanchana’s projects (2 of them) don’t have Groups set – that’s why it says Group: None.

Project Group suggests Groups from the MattiCo Five organization structure.

Project tags

Categorizing projects and clients with Tags is useful when groups, roles and skills don’t carry the right information about the nature of the work done in the project.

Read more about using Tags here.

See the “implementation” and “health” tags above the description field.

Estimated start date