I was making some slides for myself for a project I am doing, and decided to make some blanks given others may like the structure of what I am doing and want to use them as well. My Product Development Case Study has an example of what they look like when completed. Good luck with your project, and these are pretty intense, but the structure is very sound, been using it or a variant for 22 years.
1 of 7
Download to read offline
More Related Content
Process Design - Blank ºÝºÝߣs to Map Processes
1. 1Jay Martin Process BLANK ºÝºÝߣs.ppt
Name 1
Phase 1
Name 2
Phase 2
Name 3
Phase 3
Name 4
Phase 4
Name 5
Phase 5
• In here we have bullets for this
Phase with respect to what has
to be completed or ready for it to
proceed to the following Phase.
This is where
the output of
the Phase
can be
recorded
XXXX XXXX XXXX XXXX
• XXXX • XXXX • XXXX?
Output
Gate
The highest level, Level 1 descriptions, are sometimes called Phases.
Project Name Level 1 Process
2. 2Jay Martin Process BLANK ºÝºÝߣs.ppt
Level 1 Description of Steps Inside the Phase
Name Description#
Step Name • Description of what is done in the step1.1
Participants
People or functions
involved in the step
XXXX • XXXX1.2 XXXX
XXXX • XXXX1.3 XXXX
XXXX • XXXX1.4 XXXX
XXXX • XXXX1.5 XXXX
XXXX • XXXX1.6
XXXX • XXXX1.8 XXXX
XXXX • XXXX1.9 XXXX
XXXX • XXXX1.10 XXXX
XXXX
XXXX • XXXX1.7 XXXX
Project Name Level 1 Step Descriptions
3. 3Jay Martin Process BLANK ºÝºÝߣs.ppt
Process Phase Flows show who is main owner for each process step.
1Who 2 3 4 5 6 8 9 10 11 12 13 14 157
Person 1
Function 3
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
Optional, possibly consultation if required
Group 2
Project Name Level 1 Function/Organization Diagram
4. 4Jay Martin Process BLANK ºÝºÝߣs.ppt
Owner Who owns the step or completes the work
Prerequisite for this step to start, also possibly the ‘trigger’
Inputs
• Prerequisite items to be
completed or deliverables to be
available for proper completion of
overall step or tasks below
Outputs
• Work outputs, including information,
decisions, physical products that
are created or decided in this step
or its tasks below
Activities (Level 3)
1. List of tasks or activities that need to happen within this step
Metrics (Potential ones to track)
• Any metrics or measures used to track or
measure performance of this step or its
lower level tasks
Description
Below is a Level 2 Step layout, with Level 3 Tasks/Activities at left.
Ideas / Issues / Problems
• Additional information, such as common
issues, problems and challenges that the
reader needs to be aware of
Step Name
Gate
X.Y
Project Name Level 2 Descriptions with Level 3 Activities
5. 5Jay Martin Process BLANK ºÝºÝߣs.ppt
Owner
XXXX
Step Item / Question
XXXX
Yes No Skip Sign-off
XXXX XXXX
XXXX XXXX
XXXX XXXX
XXXX
XXXX
Person or
Function 1
Question or action to complete? Can process move forward? Yes No Skip Signature
XXXX
XXXX
XXXX
XXXX
XXXX XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
XXXX
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Yes No Skip
Signature
Signature
Signature
Signature
Signature
Signature
Signature
Signature
Signature
Signature
Signature
Signature
Signature
Signature
Signature
Signature
Signature
Signature
XXXXXXXX
1.5
1.2
1.3
1.4
Checklists for State/Gate Processes can be very useful as well.
Project Name Level 2 Checklist for Completion
6. 6Jay Martin Process BLANK ºÝºÝߣs.ppt
1
2
3
4
5
6
7
8
9
Below is a tool I use to map steps versus functions or participants,
just to better understand the flows.
Project Name Level 2 Flow Chart Blank
7. 7Jay Martin Process BLANK ºÝºÝߣs.ppt
A Process is simply a coordinated and structured succession of
steps and can be broken down into its many components for further
analysis.
Process Analysis Schematics of a Step and its Components
Skills & Knowledge
Feedback
Mechanism
Prerequisites Deliverable(s)
Tools
Gates/Checks/QA
Measure(s)
Transfers
Mechanism
Communication
Responsibility
Ownership
Completion
Requirements
Activities
Information Storage
I created this slide in the Spring of 1995! Wow, old school!