Project Initiation Weekly Initiation Daily Management Weekly Closure Project Closure Post-Project Management Identify the high-level decision maker(s) A1 Understand and distribute the hats A2 Select tools and create a project repository A3 Create a common understanding A4 Have Project Initiation peer-reviewed A5 Make a go/no-go decision A6 Conduct a focused communication A7 Revise and refine the common understanding C1 Have the Weekly Initiation peer-reviewed C2 Make a go/no-go decision C3 Conduct a focused communication C4 Manage follow-up items D1 Close completed deliverables D2 Measure and report performance E1 Evaluate stakeholder satisfaction E2 Capture lessons and plan for improvements E3 Consider swapping hats for the week E4 Double-check and hand over the final output F1 Evaluate stakeholder satisfaction F2 Have the Project Closure peer-reviewed F3 Consider swapping hats for Post-Project Management F4 Archive the project documents F5 Celebrate! F6 Conduct a focused communication F7 Evaluate the benefits G1 Generate new ideas G2 Conduct a focused communication G3

A3 - Select tools and create a project repository


At this point, we need to set up the tools and a well-formed repository for storing the management and production documents of the project.

Creator Hat


Which tools should we use for creating the project output?

What type of repository is best for the team members who create the output?

Project Manager Hat


Which tools should we use for the managerial work of the project?

What type of repository will best meet the managerial needs of the project?

How can users access documents from multiple devices?

How can we have automated backups?

How should we organize and name our documents?

The repository can be a directory on a cloud storage platform or a local network that is synced and made available offline on team members’ computers. Alternatively, computer-savvy people can use Git and similar technologies to set up their repositories.

Project Manager Hat


Are we sure we're not locking ourselves into a service?

When using cloud services, it’s important to make sure you’re not locked into their services and that you can remain free to move to other platforms and use alternative tools to open and edit files.

Depending on the project, there may be other concerns as well:

Project Manager Hat


How do we ensure the security of the repository?

What can we do about versioning (keeping copies of the old versions of files)?

If the team is not sure what to do in this activity, they should seek help from colleagues or friends, or hire a short-term consultant.


Downloadable manual in PDF
Standard slide deck for trainers
Activity List (+)

Thanks for sharing your opinion with us. Please note the following:

  • Please write it briefly and clearly.
  • Feel free to write in any language you prefer.
  • If you have multiple suggestions, please submit them separately.

If your suggestions inspire a positive improvement, we’d be happy to credit you as a contributor (if you provide us with your name and email address in this form).



To distinguish you from random bots on the Web, please enter the number of micro.P3.express activity groups below.


If you like, you can share your name and email address with us, in case we need to talk to you about your comment, or give you credit as a contributor:




micro.P3.express is non-proprietary, open, and free for everyone.

micro.P3.express is designed for micro projects with 1 to 7 team members. For other projects, it’s best to use the regular P3.express.