evaluate the 2 structures below. Compare and contrast the impact to project management among the different organizational structures 1. The association considered for talking about the hierarchical structure is Walmart. The association has a divisional structure. The organization has different division dependent on the distinctive topographical areas and item range comprising of hardware, clothes, staple and so forth Every division has its various capacities like HR, account, promoting and so forth The divisional structure has its progressive system of layers to control and deal with the errands and capacities over the tremendous authoritative structure. Venture the board impacts the general association as it is imperative to satisfy the distinctive vital objectives of the business by overseeing ventures that are significant for business tasks including its extension, utilization of innovation, flexibly chain the executives and client assistance. The hierarchical structure impacts the organization's administration of ventures as it assists with controlling and oversee various capacities across geological and item divisions. The vertical announcing structure of workers brings about responsibility and control of the activities and screen the ideal aftereffects of ventures to be finished according to the undertaking targets and objectives. Explicit models from the experience are identified with the graceful chain of the executives and consistent utilization of most recent innovation for dealing with the business activities of the organization on worldwide business. The organization utilizes RFID labels to follow its products and deal with the sharing of data about its deals and stock. The organization oversees such ventures by preparing its workers and zeroing in on the results anticipated from the undertaking to improve the proficiency and business execution.

2.

In thinking of organizational structures, there are four main types that come to mind; Functional, Divisional, Flatarchy, and Matrix (Kenton, 2020). My current organization falls within the health insurance industry and operates under the strong matrix structure, where you may have one employee who reports directly to the manager where the job duties reside, as well as report to a number of different project managers in which the employee has tasks assigned to them for project support (Matrix Organizational Structure, 2020).

From my personal experience, the key aspects of the matrix structure involves having cooperation across the organization and living with a teamwork mentality. It is one thing to say you work inside a matrix organization, it is an entirely different thing to actually live up to those standards and practice the matrix way of life. I may have one specific manager, but at different stages of the year I might find myself reporting to up to three or more project managers that I owe deliverables to for various projects. While they are not my specific manager, I owe them the same respect and am held to the same level of responsibility within each project as the work I do for my specific job title, as the projects will impact the success of the company moving forward.

Within my organization, projects are handled through the enterprise project management office (EPMO). This department is comprised of project managers, senior project managers, program managers, and other support roles needed to ensure success. Each sector of the company, whether it be IT, Claims, Customer Service, or Legal, has their own line of project managers they can task out to take on the workload associated with each project. This helps the project teams structure to built upon a framework of success from the ground up and ensures that the project manager assigned to the project has a firm understanding of how the project will impact each area of the company. The project manager can then request and gather resources from the different departments as needed, thus prompting the matrix structure to be engaged. A claims project cannot be solely ran by the claims team, they need to know how it impact the IT space, the member services space, or if a claim change will impact how certain providers get paid for services.

A specific example I can think of to support my above points would be a transplant enhancement project I recently worked on within my organization. What started out as a project to build out my organizations own transplant network slowly turned into a list of different action items that needed to be addressed across the departments. Questions relating to how the claims will be paid and at what rate, or how we would onboard new facilities and credential the providers to our standards all came into play. Since we operate within the matrix structure, the project manager was able to simply reach out to the various stakeholders and relay the questions who then provided resources for use on the project moving forward. A matrix organization in my opinion is a melting pot of all available resources all coming together to produce success and carry projects through to completion. It takes more than one team to see something through, and when an organization can come together without pause, I think that is something worth working for.