In a recent post a user asked if anyone managed a risk log within Wrike. I'm posting this to share how we manage risks for our own projects.
We frequently have 20+ product development projects running concurrently throughout the year. We use a project template to kickoff each project with about 30 high-level tasks per project. We perform DFMEAs on every project and used to just log them in an Excel spreadsheet. However, that Excel sheet would get lost as an attachment in the sea of tasks we swim in, and makes it difficult to view DFMEA issues for multiple projects in a meeting.
To mitigate this and allow for quick access to DFMEA actions and status, I created a log folder in each project. However, I did not want to see every task in my table, only the tasks related to DFMEAs.
I created a drop-down custom field titled CATEGORY which allows me to quickly assign a category to specific tasks for filtering.
As you can see, I have numerous categories to choose from depending on the type of reports I need to generate, but that's covered in a different post.
When logging the potential failures our products might see in use, I like to work in the Table view (New Table is my preference). This allows me to just type and tab over as if I'm working in Excel to populate all of the other custom fields. As you can see below, I have a workflow specific to DFMEAs, and the following custom fields: FAILURE MODE, EFFECT OF FAILURE, SEVERITY (number), CAUSE OF FAILURE, OCCURRENCE (number), DESIGN CONTROL, and DETECTION (number). Severity, occurrence, and detection all need to be defined as "Numbers" for the custom field type to allow for report level calculations.
Now, when I run a report I can filter by Category > DFMEA and group by Parent Folder to see multiple projects at a time.
In the report, I add the calculated column "RPN" (risk priority number) which multiplies the severity, occurrence, and detection values.
From RPN, I can determine if action needs to be taken based on our threshold criteria of 100 or greater, and sort from high to low to quickly see the status of each risk.
We can also see which projects have not had a DFMEA run yet to ensure those are addressed as well. In the design phase of our project template, we have a workflow status that indicates we need to run a DFMEA. This prevents us from unknowingly moving past this process.
I hope some of you find this helpful. I would also love to hear any suggestions you have for me to improve our process.
Iniciar sesión para dejar un comentario.