Product Development using 3D CAD Design
  • EVALUATION

    EVALUATION

Why is Methodology Important in Product Development?

Why is Methodology Important in Product Development?

Often documented methods for construction as well as the important link between users and overall processes controlling every business, are missing. Rules and best practices are spread by word-of-mouth and interpreted differently by different individuals. This may lead to:

  • Experts are forced to spend a lot of time on support and correction of data instead of development.
  • Expensive and unnecessary revisions.
  • Time consuming introductions for new recruits and consultants.
  • New functionality is introduced slowly.

Well defined work methods help users utilize their work tools more effectively. At PDSVISION we therefore recommend all companies to describe and document, at a the very minimum, the most common operations. This is a process we are more than willing to support. PDSVISION has for many years contributed to development of methodologies used by some of our most successful customers.

Methodology Development with PDSVISION

Because of our customers need to use the potential from their investment in the best way possible, PDSVision offers support for developing and documenting methodology and processes related to the tools we offer. In addition to this, we have tools for analyses, templates, general best practices and training experience.

We also know that in the end, methodology has to be as unique as the customer defining it.

What Does a Methodology Project Contain?

All of our methodology projects are conducted together with the customer. The customer’s individual needs direct the content and the proportion of the project. The common goal for all projects is to create a more controlled and coherent work flow describing proven and efficient approaches. By continuously developing tools and methods, the foundation for more efficient work and faster integration of new recruits is set.

Our recommendation is that a complete methodology project consists of the parts following below:

Analysis Phases

  1. Situation Analysis
    Analysis of how we work today and what are the shortages that we do not know of?
  2. Alteration of development environment
    What are our prerequisites to be effective? Are there tools for more effective processes that are missing? Can we effect the quality through more embedded controls?
  3. Composition of methodology
    Identify and document best practices, guidelines and requirements.
  4. User training
    The art of conveying a message and creating acceptance and participation amongst users.
  5. Follow-up
    Is there a need to change and / or add something? Are we finished, or are there more initiatives we can include?

Packaging and Presentation is Key

An investment in methodology is rather useless if no one in the organization reads or utilizes the provided methods. A key factor here is packaging of information. To reach success with the defined methodology, the content should be presented using the following conditions:

  • Easily accessible for those who need it (web, intranet)
  • Easy to consume and clear (text, images, videos)
  • Relevant and updated content

Continuous Quality Controls

When a methodology framework exists and all users are educated, only controls to ensure the methods are followed remain. By building continuous and automatic controls into systems we help users minimize the risk of faults and unnecessary rework.

Conclusion – Methodology for Everyone!

Methodology is highly recommended by PDSVision to all of our customers. A simple and modest description of standard procedures can be worth a lot when introducing consultants, new co-workers or rusty users.

Our methodology projects always start with an analysis to map out needs and conditions. A smaller company probably doesn’t have the same prerequisites to implement a complete methodology material covering a major part of the development process, as a larger company may need to. Our methodology projects are for this reason scalable to the end users needs.