1. Used to manage the overall project PMN includes: – Project name and purpose – Desired deliverables/outcome – Record of the project results – List of required actions – Identification of the very next action PMN may include: – Results from brainstorming – List of project notes – Links back to Project Action Notes or other project support material – List of references (websites or other reference documents used) The example PMN was created to show it could be used to manage a small project – PMN was created and assigned the appropriate project tag and PMN tag – Project information and expected outcomes/deliverables were recorded in the PMN – A chronological list of required actions was recorded and checked off as they were completed – The very next action is to capture screenshots. A Project Action Note (PAN) was created (example on next chart) and a link to the PAN was copied to the “Next Action” section of the PMN Project Master Note (PMN) Link to the Project Action Note

2. Project Action Note Used to manage actions or small projects associated with a larger project PAN may include: – Single action – Multiple lower-level actions to complete a higher-level action or objective – Record of research, decisions, telephone calls, e-mails concerning the overall action Upon completing the action(s) in the PAN, closing it out ends with one of the following actions: – Delete the PAN (a record of completing the action is maintained only in the Project Master Note) – Retain the PAN as part of the project file for historical/reference purposes – Copy the information you want to keep from the PAN and paste it into the Project Master Note, then delete the PAN In the example project, there was an action to capture screenshots in the Project Master Note (PMN) – A Project Action Note was created to capture the required action and list the desired screenshots – The PAN was assigned the appropriate project and context tags; a link back to the PMN was created – As time was available over a 2-3 day period, the screenshots were taken and the PAN was updated to keep track of what was complete and what still remained Link back to the Project Master Note

3. Project Management in Evernote Create Project Action Note (PAN) 1. Copy 1 or more PAN templates into the “Inbox” (recommend as many as you can at once for speed) 2. Assign project tag to each PAN 3. Move to project folder and copy PMN note link 4. Paste PMN note link to the new PAN(s) 5. Copy/paste planned actions from PMN into the new PAN(s) (1 action per PAN) 6. Add applicable next action tags to PAN(s) 7. Add title of the “very next action” PAN to that section of the PMN (if not already there) 8. Move PAN(s) to the “Processed” NB Close Project Action Note (PAN) 1. As PAN actions are completed, delete the PAN and associated PSM if no longer required or retain the notes by doing the following: a. ) ensure bi-directional traceability between PMN and PAN, and between PAN and its PSM (or between PSM and PMN if PAN is to be deleted) b.) tag PAN as completed; remove next action tag c.) move PAN and its PSM to “Reference” NB d.) update the PMN to reflect task completion and designation of the next action. Re-open Project Action Note (PAN) 1. If a closed PAN requires further action, move it from the “Reference” NB to the “Processed” NB, remove the completed task tag, and assign it an appropriate next action tag. Project Action Note (PAN) as of 08 Feb 2015 Adding Project Support Material (PSM) 1. Tag all PSM with the project tag 2. Establish bi-directional traceability between the PSM and either its PAN or the PMN 3. If further action is required for the PSM, update title to reflect action, assign next action tag, and keep/move note into “Processed” NB 4. If PSM action is complete, move it to “Reference” NB (or delete it if no longer req’d) Managing Actionable PSM (action, close) 1. View open notes for a project by selecting the “Processed” NB, hold the Ctrl-key and select the project tag. Closed PANs/PSM are filtered out. 2. Take action on PSM. (update next actions & record actions/results until complete) 3. Once PSM action is complete, update PAN or PMN as required with results. 4. If PSM no longer required, delete it. 5. If PSM should be retained, tag it as “closed” and move to “Reference” NB Project Support Material outside Evernote (e-mail, MS Office, etc.) 1. E-mail should be imported (whole e-mail or link) into Evernote for project management. 2. For support files on the computer (MS Excel, Word, Project, or other), maintain a “Project” folder on the hard drive of open and closed projects. Copy link(s) to the project file(s) into the PMN or PANs as applicable. 3. Retain or delete e-mail notes and projects on drive as PSM is completed. Duplicate in Gmail (delete or save the original e-mails in the Gmail archive with appropriate tags) and on the computer (move project to the closed folder, consider updating the file link in Evernote to reflect the change in location. Project Support Material PMN: Project Master Note PAN: Project Action Note PSM: Project Support Material NB: Notebook Key Points Assign the applicable project tag to the PMN, all PANs, and PSM Keep all PANs and PSM requiring further action in the "Processed" NB. Move completed PANs and PSM to "Reference" NB (or delete if not required) Implement bi-directional traceability from PMN to PAN to PSM so it is easy to maneuver through it Update the PMN with completed actions, important reference links, and designate the "next action"

4. Project Management in Evernote 1. Create tag under.Active Projects; format !ProjectName 2. Create Project Master Note (PMN) from template. Title note using format “ProjectName Project Master Note“ 3. Fill out key blocks of the PMN (purpose, deliverables, etc.) 4. Tag note with " PMN“ tag – facilitate quick search 5. Tag the PMN with higher-level horizons of focus tags (vertical linkage to 20k and/or 30k levels). Can be >1. 6. Create 1 or more next actions for the project – recommend use the Project Action Note template and insert link back to PMN (for traceability). See instructions for Creating PAN. 7. Move all next action notes and the PMN to the “Processed” notebook Create Project as of 04 Apr 2015 1. Select project tag to see all project notes across all notebooks 2. If retaining the project, ensure PMN is adequately filled out with project closure details (outcome of project) 3. Save any project artifacts/files that you may need in the future. 4. Delete action notes and project support material not required for future reference. (only retain notes containing important details /references) 5. For remaining notes, recommend establish bi-directional traceability (if not already done) via copying note links 6. Move all project notes to the "Reference" notebook 7. Rename project tag; precede project name with project closure date. Ex: yyyymmdd!ProjectName 8. Move project tag from.Active Projects to.Completed Projects Info: PMN, PANs, and PSM will now be in the "Reference" NB and traceable with the project name to ease future referencing. Once the project material is no longer valuable, delete all project notes no longer needed (some notes may support other projects or be useful as stand-alone reference material). Close Project View project notes with open/pending actions 1. Select the “Processed” notebook, then hold down Ctrl-key and select the project tag. (to see all project notes (open & closed), just select the project tag) Find and execute the “next action” 1. Follow process to View project notes with open/pending actions 2. Select the PMN from the open notes – the next action is listed near the top of the note 3. Find the applicable Project Action Note and take appropriate action or re-negotiate which action you actually work next. 4. Maintain running summary of PAN action/results (if required) until action complete. (see PAN closure instr.) Project Execution PMN: Project Master Note PAN: Project Action Note PSM: Project Support Material NB: Notebook Key Points Assign the applicable project tag to the PMN, all PANs, and PSM Keep all PANs and PSM requiring further action in the "Processed" NB. Move completed PANs and PSM to "Reference" NB (or delete if not required) Implement bi-directional traceability from PMN to PAN to PSM so it is easy to maneuver through it Update the PMN with completed actions, important reference links, and designate the "next action“ Closing Projects: Some project deliverables should be copied to other places so you don’t lose them by accidentally deleting a closed project (such as deleting completed projects to clear up space) as there may be no other copies of it. Ex: If I had deleted my workflow graphics project, I would have lost all the process flow documents.