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

A6 - Make a go/no-go decision


At this point, we’re almost ready for the go/no-go decision. Before asking the responsible person or group to make the decision, each hat-wearer should express their concerns:

Project Manager Hat


Do we have a proper, consistent understanding of and foundation for the project?

Creator Hat


Are the targets and expectations realistic and achievable?

User Hat


Is the existing definition of the project's output suitable for end users?

Investor Hat


Is the project goal achievable?

Is the project justifiable?

Is the project the best investment for us at this time?

After this, the person or group responsible for the go/no-go decisions (set in A1) makes a decision. If the decision is no-go, the project repository should be archived and the project stopped. You should make sure the archive remains accessible, though, because you may come up with a similar idea in the future, and checking the work you’ve done on this idea would be helpful then.

You may have to initiate multiple projects to end up with a few justifiable ones you want to execute. For this reason, the initiation of later-rejected projects shouldn’t be seen as wasted time but rather as an investment for finding the best projects.

When there’s an external customer, this activity is when the proposal will be sent to them, and the contract will be signed.


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.