Process Isn & #039;t Just for Project Managers
Engineers love to solve problems, especially technical ones. Unfortunately, challenges in communication and planning often result in poorly understood goals and objectives. The engineering team makes one thing while the managers and marketers want something else. That leaves everyone unsatisfied.
I will describe a very simply process that, when consistently applied, is extremely successful in generating consensus among stakeholders and driving the development of proof-of-concept devices. This process, outlined below, will help ensure the best possible outcome. While this discussion is focused on proof-of-concept devices, it works equally well, if not better, for process improvement activities.
Please keep in mind that each of these steps can be very simple if the answers are known and obvious. A few hours and a page or two of documentation suffices in many cases. The benefit of the investment of time is greater clarity of purpose and alignment of stakeholders. For a junior engineer with very senior stakeholders, this alignment can be crucial to success.
Simplified Proof of Concept Process
Mapping to Standard Development Process
Simplified Terminology
Identify Stakeholders
Who cares?
Develop Problem Statement
Why do they care?
Determine Current State
What do they have now?
Current State Strengths
What is good about it?
Current State Weaknesses
What needs to be improved?
Document Stakeholder Needs
What do they want?
Identify Req...
Source: MDDI - Category: Medical Devices Authors: Mark Wehde Tags: Design Source Type: news
More News: Conferences