RECOMMENDATION #1:
Get clear on your organization’s flavor of PARA

My first recommendation is to define what PARA looks like for your organization specifically.

Even if you decide to follow my advice to the letter, there is always a “flavor” of PARA that makes sense for your culture.

I suggest creating a “PARA Playbook” for your team that includes decisions such as:

• •  What is our definition of a “project,” “area of responsibility,” “resource,” and “archive”?
• •  What needs to happen when we kick off a new project for it to be considered “active”?
• •  What needs to happen when a project gets completed, put on hold, or canceled (to be considered “inactive”)?
• •  What are the officially supported platforms on which PARA will be used?
• •  What are the rules, guidelines, and norms that govern how people will use PARA?
• •  Who will be the “PARA Champion” who oversees its implementation and makes sure the guidelines are being followed?