Skip to main content

Tag: Methodologies

PMTimes_Dec20_2023

Three Attributes of Construction Sector PMs and Nine Important Concepts to Know

Written by Lucas Marshall on . Posted in Articles.

The role of an effective project manager has been studied and observed—scholarly researchers studying the managerial profiles of successful project managers (ref 3) observed common traits including extroversion, rational judging, and structured behaviors, for example. Another study from researchers at Embry-Riddle Aeronautical University (ref 1) found common traits of project managers to include openness to experience, surgency, adjustment, agreeableness, and compositeness.

 

I’ve previously written about how the construction industry needs more software project managers—particularly to address labor shortages (i.e., half a million, the ABC reported) as well as help absorb some of the displaced talent from big tech layoffs, I argued.

But what attributes might those PMs need entering the construction industry, and what are some of the important concepts construction PMs should know?

 

Three Traits that Make an Effective Construction PM

Certainly, the above-mentioned managerial profiles of project managers would be useful to have as a project manager in the construction industry.

If I had to choose just three traits needed of a construction project manager, they would be:

 

1. Adaptability

The construction ecosystem is one that is fragmented and requires a high degree of finesse from its practitioners. For example, did you know that the average home has 22 subcontractors working on it? Research from the National Association of Home Builders (NAHB; ref 2) found that builders, on average, employ two dozen different subcontractors and subcontract out 84% of their construction costs in the typical home they build.

 

The job of a project manager, then, is one that requires synchronization of many moving parts and coordination through many more project stakeholders. It’s ever-critical for project managers in the construction sector to understand change management modalities, for when equipped with these, they will be able to dynamically guide customers, stakeholders, and cross-functional project delivery partners through:

  • Project kickoff and discovery to fully understand project scope.
  • Resource allocation, organizational commitments/dependencies (and possibly technical debt) to strategically facilitate project scheduling in a way that is faithful to organizational resources and customer needs.
  • Strong customer relationship management and project planning to ensure a high-quality customer experience while allowing for a dynamic response to (and also limiting the quantity of) change orders requested from customers.

 

2. Business Acumen

Forecasting construction projects properly is a mission-critical task that allows businesses to stay profitable, and it’s also a skill that requires business owners and important collaborators (e.g., project managers) to have great finesse.

A project manager might work in lockstep with a business analyst as well as an inventory manager, for example, to better calculate financial commitments annually through job costing, building financial reporting dashboards as well as project management dashboards, etc.

Seeking educational opportunities (e.g., understanding construction financial management) offered through the Construction Financial Management Association (CFMA) can help project managers strengthen these skillsets.

 

3. Collaboration

As hinted above, construction is a highly collaborative business sector that requires coordination (and cooperation) of a lot of critical cross-functional teams.

Above graphic credit: Fuks et al (ref a) via 4. Polančič (ref 4)

 

The best ways to achieve a higher degree of collaboration with fewer blind spots and information silos include:

  • Adopting cloud-based collaboration tools – Online collaboration (e-collaboration) have been studied by scholarly researchers (ref 4) and prove to deliver a “mutually beneficial relationship between at least two people, groups or organizations, who jointly design ways to work together to achieve related or common goals and who learn with and from each other, sharing responsibility, authority and accountability for achieving results.” Common advantages of cloud-based systems, the researchers highlight, include:
    • Usability – i.e., “SaaS should be easy to use, capable of providing faster and reliable services. User Experience Driven Design aims to maximize the usability, desirability and productivity of the application” (table 1).
    • Efficiency – SaaS, cloud-based solutions allow “computers [… to] be physically located in geographical areas that have access to cheap electricity whilst their computing power can be accessed over the Internet” (table 1).
    • Maintainability – “SaaS shifts the responsibility for developing, testing, and maintaining the software application to the vendor” (table 1).
  • Collaborating with IT and construction technologists to build interoperability of systems (e.g., standardization of change orders, quality control and consistency through the systemization of processes through industrialized construction, standardization of IoT deployment, etc.) as well as the implementation of advanced technology to drive greater real-time visibility and quality assurance (e.g., site-observational drones; robots to automate procedural tasks with a greater degree of consistency, while also removing humans from needlessly dangerous situations, etc.).

 

Nine Important Concepts Every Construction PM Should Know

Now that we’ve covered the common traits that would make a project manager successful in the construction sector, what are some of the important concepts PMs entering the construction industry should know?

 

Here are nine important concepts to know:

 

1. The Five Stages of Project Management

The five stages of project management are equally applicable to the construction industry, which include the following:

  1. Project Initiation – The start of a project, typically including documentation of responsibilities, proposed work, expectations – e.g.,
    1. Project goals
    2. Scope of work
    3. Project organization
    4. Business case
    5. Constraints
    6. Stakeholders
    7. Risks
    8. Project controls
    9. Reporting frameworks
    10. Project initiation signoff
    11. Summary
  2. Project Planning – The high-level planning and scheduling of scoped work via tools like Gantt charts, project management software (e.g., for the construction industry, cloud-based tools like Procore, Contractor Foreman, Autodesk Construction Cloud, Monday Construction, Houzz Pro, etc.). Typical deliverables may include:
    1. Work breakdown structure
    2. Activity network diagram
  3. Project Execution – The completion of scoped work
  4. Project Control – Measures to prevent scope creep (see in next section), cost overruns, etc.
  5. Project Close – The conclusion of the project.

 

2. Scope of Work, Scope Creep, and Scope Management

The scope of work is the documentation in which features and functions of a project, or the required work needed to finish a project, are defined, typically involving a discovery process during which information needed to start a project is gathered (e.g., stakeholder requirements).

Scope creep refers to the continuous and/or expanding work requirements past the project’s original scope, which can happen at any point after the project begins. Scope management is the process of defining and managing the scope of a project to ensure that it stays on track, within budget, and meets the expectations of stakeholders.

 

Advertisement
[widget id=”custom_html-68″]

 

3. Lean Project Management

Project managers and project leaders in manufacturing industries may be familiar with lean manufacturing principles – lean construction is an industrialized construction method whereby companies approach the business of building things more effectively and efficiently by minimizing waste and maximizing value for all stakeholders.

 

The approach centers around:

  • Minimizing waste.
  • Reducing expenses.
  • Boosting productivity.
  • Improving quality over time.
  • Increasing value for the customer.

 

Image Source: WikiCommons

Many resources exist for project managers looking to adopt lean construction – e.g., the Lean Construction Institute offers certifications, eLearning, whitepapers, membership, as well as a directory of lean practitioners, while the Lean Construction Blog offers a Lean Academy, conferences, webinars, and its industry-known podcast. Consider, for example, a recent interview I conducted with a Milwaukee Tool continuous improvement leader about lean management and industrialization as one additional resource to get started with IC and lean principles.

 

4. Project Management vs Program Management

Harris & Associates, a civil engineering and construction management company that ranks in Engineering News-Record’s Top 100 Construction, defines project management versus program management (i.e., project manager versus program manager) in the construction industry as follows:

  • Program management/program manager – management of large portfolios encompassing multiple projects on multiple sites (they provide the example of a K12 school district, where the program manager may be responsible for upward of 10 elementary schools, five middle schools, and two high schools).
  • Project management/project manager, meanwhile, will “manage work on one of the schools [… handling] the single project from cradle to grave: pre-design, design process, bid/award, construction and close-out.”

 

5. Project Management Triangle

The project management triangle is a model employed by project managers that dates back to the 1950s and it “contends” the following principles:

  1. The quality of work is constrained by the project’s budget, deadlines, and scope (features).
  2. The project manager can trade between constraints.
  3. Changes in one constraint necessitate changes in others to compensate or quality will suffer.

 

 

Image source: WikiCommons

 

6. Scrum

Project managers from the tech and software development industries may be well familiar to scrum, though its principles are equally useful for contractors. Scrum, simply put, is a framework that helps teams work together while empowering teams to learn through experiences, prioritizes self-organization while working through problems, and encourages ongoing reflection in the constant pursuit of continuous improvement.

 

7. SWOT Analysis

SWOT analysis is a commonly used business tool and acronym for Strengths, Weaknesses, Opportunities, and Threats, described as a “framework used to evaluate a company’s competitive position and to develop strategic planning.”

 

Image Credit: swot-analyse.net via WikiCommons

 

8. Quality Management

Quality management (aka: total quality management or TQM) is defined as “the act of overseeing all activities and tasks that must be accomplished to maintain a desired level of excellence [… including] the determination of a quality policy, creating and implementing quality planning and assurance, and quality control and quality improvement.”.

Examples of quality management in the construction industry may include procurement managers assuring that materials to be used are not damaged; tools and equipment used to perform work are properly serviced, calibrated, and not out of specification; the right tools to drive the highest degree of quality are employed (e.g., consider, for example, how M18 FUEL™ Controlled Torque Impact Wrenches utilize proprietary sensors and machine learning algorithms to drive greater repeatability for solar installers).

 

9. Servant Leadership

Servant leadership is described as a “leadership style that prioritizes the growth, well-being, and empowerment of employees [… aiming] to foster an inclusive environment that enables everyone in the organization to thrive as their authentic self.” What’s more, Investopedia describes servant leadership as embodying “a decentralized organizational structure.”

The application of servant leadership in the construction industry has been studied by researchers for the SA Journal of Industrial Psychology and findings have “indicated”…

… job resources mediated a positive relationship between servant leadership and work engagement and a negative relationship between servant leadership and burnout. Servant leadership had a positive significant relationship with job resources and significantly explained a proportion of the variance in job resources. Job resources, in turn, significantly explained a proportion of increase in work engagement levels and a proportion of reduction in burnout levels. An insignificant relationship was found between job demands and servant leadership.

 

Final Word

The work of project managers in the construction industry shows great promise and represent continually important roles to maintain scope management, resource allocation, budgets, and schedules as the industry faces strong headwinds. For those entering the industry, your work will be highly valued, and you may find a fruitful career when shifting from more volatile industries. The above construction PM traits and industry concepts are intended to be useful in this transition. For project managers in (or entering) the construction industry, I’ve also prepared a more extensive List of Construction Project Management Terms.

 

References

  1. Henkel, T. G., Haley, G., Bourdeau, D. T., & Marion, J. (2019). An insight to project manager personality traits improving team project outcomes. Graziadio Business Review, 22(2). Retrieved from https://commons.erau.edu/publication/1353
  2. Emrath, E. (2020, 12). Average new home uses 24 different subcontractors [Data set]. National Association of Home Builders. https://www.nahb.org/-/media/NAHB/news-and-economics/docs/housing-economics-plus/special-studies/2020/special-study-average-new-home-uses-24-different-subcontractors.pdf
  3. Montequin, V.R, Nieto, A.G., Ortega, F, and Villanueva, J. (2015). Managerial style profiles of successful project managers: A Survey. Procedia Computer Science 64, 55-62, https://doi.org/10.1016/j.procs.2015.08.463
  4. Polančič, G., Jošt, G., and Hericko, M (2015, 02). An experimental investigation comparing individual and collaborative work productivity when using desktop and cloud modeling tools. Empirical Software Engineering 20(1), http://dx.doi.org/10.1007/s10664-013-9280-x
  5. Fuks, H., Raposo, A., Aurelio Gerosa, M., and Lucena, C. (2005, 06). Applying the 3C model to groupware development. International Journal of Cooperative Information Systems 14(2):0218-8430, http://dx.doi.org/10.1142/S0218843005001171

 

PMTimes_Nov1_2023

Why I Value Frameworks Over Methodologies

Written by Elizabeth Larson on . Posted in Articles.

Early in my career, the head of IT gathered us together to introduce us to a new concept—a methodology. He pitched it something like this: “We’re going to start using new processes to complete our projects in IT.”

We’ll follow this set of rules that will take us from the beginning of the project to the end.” We didn’t think that would be particularly beneficial and we were pretty vocal about how this would slow our work down. So, after a few minutes of our grumbling, he tried again: “Wouldn’t be great if we could get Harvey to leave us all alone and let us get our work done?!” That we liked because Harvey was our collective nemesis—our main client who pressured all the programmers whenever he liked with constantly changing ideas. These never-ending changes caused a chaotic environment. We found it hard to get work done on time resulting in many complaints about us throughout the organization. The new methodology was introduced, and it did indeed improve our chaotic environment.

It did not, though, help our standing in the company. It was too inflexible and the clients like Harvey hated it.

That was the first of many methodologies that were introduced to our industry over the years. Some were quite technical, and others less so. Each purported to get projects done more quickly with more client satisfaction. Each touted that it was the latest and greatest and would solve all of IT’s problems. Each advanced the idea that if it were followed, the whole organization would be eternally grateful. Each started with good intentions, but each got bogged down in its own bureaucracy.

 

Is Agile a methodology?

Before I became a Certified Scrum Master in 2010, I attended my first presentation on Agile. The speaker reviewed the Agile Manifesto and principles and I said to myself—here’s something that takes good, solid project principles and puts them together in a practical way. At that time and to my delight, Scrum was called a “set of practices” which made a great deal of sense to me. Of course face-to-face communication is preferred, if not always practical. Of course we don’t want to get bogged down in needless documentation just to follow some mandated process.

Gradually, though, the word “methodology” replaced the phrase “set of practices.” And to some teams, calling a set of best practices a methodology gets misinterpreted as an unalterable way projects are completed. I remember attending a presentation where the speaker proudly discussed how documentation had been banned in her organization. “ And in another presentation a panel discussed whether virtual communication was considered face-to-face and therefore “allowed.” Agile was in jeopardy of losing its practicality and becoming bureaucratic. But Agile still works today when used as intended. It works, though, more as a framework than a methodology.

Advertisement
[widget id=”custom_html-68″]

 

So what’s the difference?

I think there is and has always been confusion between the two. According to the Scrum Alliance website, “Agile methodologies are the conventions that a team chooses to follow in a way that follows Agile values and principles.”[i] The use of the word “conventions” implies some flexibility. So what’s a convention? It’s a norm, an agreement for how in this case a team behaves and does things. I understand behavioral conventions. It makes sense to me that each team will create its own communication and behavioral norms and guidelines. My concern is that these methodology-conventions run the risk of becoming rules for every project—rules that don’t allow for individual problem-solving.

Frameworks by their nature are flexible. They allow teams to decide which practices make sense for their projects and which do not. A best practice may work well on one type of project or in one industry or organization but not others. Another best practice may work well for one set of clients, but not for others or with one team’s skillset but not another. Frameworks allow for these differences and usually encourage teams to choose among the myriad best practices described in the framework.

Sure, frameworks usually describe more practices than can be absorbed for any given project. That’s why it’s important for teams to understand what’s contained in the framework and choose the practices that work for them. If the team views the framework as an inflexible methodology, each step of which must be done on all projects, they may become overwhelmed and abandon it entirely.

 

I value frameworks over methodologies. Not that there shouldn’t be methodologies. It’s just that in my experience, frameworks are more flexible. They allow for individuals and teams to understand the context of their specific environments and make better-informed decisions. Frameworks provide guidance without demanding that each step be followed. Methodologies tend to become rigid over time. They are often used as a crutch when teams are unable to understand context and synthesize information. Having frameworks is important. It seems to me, however, that having bureaucratic methodologies can be self-defeating.

[i] [i] https://www.agilealliance.org/agile101/. They base this definition on Alistair Cockburn’s who suggested that “a methodology is the set of conventions that a team agrees to follow.”
PMTimes_Oct18_2023

From Waterfall Walls to Agile Architecture: The New Era of Construction

Written by Lucas Marshall on . Posted in Articles.

This is a collaborative article cowritten by Lucas Marshall and Jason Braun.

 

Productivity is hard to measure. It differs depending on industry, for one. What’s more, the construction sector is what the Becker Friedman Institute for Economics at the University of Chicago considers “strange and awful,” representative of raw BEA data suggesting “that the value added per worker in the construction sector was about 40 percent lower in 2020 than in 1970.” For instance, the construction of the One World Trade Center in New York faced numerous delays and budget overruns, highlighting the challenges the industry faces. Labor shortages—whose “impacts on labor wages, cost overruns, and scheduling concerns in construction projects”—could be the driving factor here as companies struggle to fill positions while unemployment remains low. In other words, “few construction workers [are] seeking jobs, and therefore the pool to fill demand is shallow,” while onsite workers face the unique challenge of executing projects with limited resources—adding to these impacts and slowing growth.

 

At first glance, the worlds of software development and construction may seem poles apart. However, both industries grapple with the complexities of managing large-scale projects, ensuring timely delivery, and adapting to unforeseen challenges. For example, the development of the Windows 95 operating system was a monumental task for Microsoft, much like constructing a skyscraper is for a construction firm. Just as software developers transitioned from the rigid Waterfall methodology to the more adaptive Agile approach to address these challenges, the construction industry stands at a similar crossroads.

 

While it may seem alien to the construction sector, the software industry has subbed one framework (i.e., waterfall) for another (agile), resulting in success ratios two times greater, 37% faster delivery, and greater impact on improving product quality, a 2023 scholarly study found. Popular apps like Spotify and Airbnb have notably benefited from Agile methodologies, iterating rapidly based on user feedback.

 

In this article, we propose applying similar agile and lean construction methodologies illustrative of industrialized construction. Like software—which replaces a rigid, monolithic release cycle with a more agile framework—we explain that industrialized construction looks to replace the old-school, one-off “project” mindset with a fast and dependable productization framework. Consider the construction of modular homes, which are built offsite in controlled environments and then assembled on-site, mirroring the iterative development and deployment in software.

 

Software Project Management: From Waterfall to Agile

Companies in the software industry generally use one of two frameworks when building software products:

 

Waterfall

Waterfall is a more traditional approach to software development where production takes place in a linear, sequential manner (i.e., every task needs to be finished before the next one begins). This means new software solutions begin by defining requirements, then shifting into the software design phase, then shifting to the software developers building what has been proposed, then verifying the release is stable, and finally shifting into maintenance (i.e., finding and squashing bugs). For instance, the early development of Microsoft Office followed a Waterfall approach, with distinct phases and milestones.

 

Key point: Like construction projects that oftentimes involve a considerable deal of back-and-forth with approvals before breaking ground, then contend with unpredictable access to onsite labor and materials as well as rapidly changing weather conditions, we’ll argue later that construction is due for breaking from the waterfall-like processes through industrialization.

 

Agile

Agile is an iterative, team-based approach to software development where rapid delivery of functional products over a short period of time (known as sprints) is used (similar to lean manufacturing methods applied to construction). Continuous improvement is adopted, and subsequent batches are planned in cyclical schedules. Tech giants like Google and Facebook have adopted Agile methodologies for many of their projects, allowing for rapid iteration and improvement based on user feedback.

 

Agile methodology is more collaborative and customer-focused. Oftentimes, customers have the opportunity to offer their feedback through the software development process (e.g., beta releases). Through this approach, developers can improve the overall functionality of the software for the target end user and establish a 1-1 relationship based in trust and mutual respect. It also offers a fixed, predictable schedule and delivery, improved quality for customers through their hands-on participation, as well as adaptability through change.

 

Advertisement
[widget id=”custom_html-68″]

 

From One-Off Projects to Finished Goods through Industrialized Construction

Industrialized construction (IC) refers to “the process through which construction aims to improve productivity through increased mechanization and automation,” similar to how Ford’s early assembly line offered the mechanized approach necessary to meet the demands of customers for the Model-T while ensuring product consistency and quality through mechanized orchestration.

 

The mention of Ford’s Model-T isn’t merely a nostalgic nod to the past but a pivotal example of industrial transformation. In the early 20th century, the automobile industry faced challenges similar to today’s construction sector: Inefficiencies, inconsistencies, and a demand that outpaced supply. Ford’s introduction of the assembly line for the Model-T revolutionized production, offering a standardized, efficient, and scalable solution.

 

At a high-level, industrialized construction as a concept moves beyond approaching each build as one-off projects. Instead, practitioners apply a foundational framework where building deliverables are treated as building products and the same attention to build quality, customer satisfaction, and continuous improvement seen from manufacturers of marketable finished goods (e.g., automobiles, electronic devices, perishable goods, etc.) is applied to construction. A real-world example can be seen in the rise of prefabricated homes, which are built in factories and then assembled onsite, ensuring consistent quality and faster construction times.

 

The traditional approach to construction, as we highlighted earlier, comes with its set of challenges. For instance, 45% of all construction projects face disruptions due to inclement weather. A staggering 93% of construction firms grapple with material shortages. Furthermore, the limited access to skilled workers, a point we touched upon earlier, restricts the efficiency of an onsite workforce, especially under tight deadlines. This can jeopardize schedules, budgets, and even the quality of work.

 

For instance, the construction of the Berlin Brandenburg Airport faced numerous delays due to planning and execution challenges, showcasing the need for a more streamlined approach.

 

The transition towards Industrialized Construction isn’t just a theoretical proposition; it has tangible, real-world implications that can redefine the construction landscape. For starters, IC can lead to significant cost savings. By shifting much of the construction process to controlled environments, we can mitigate the risks and uncertainties of on-site construction, from weather disruptions to labor shortages. This not only ensures projects stay on budget but also can lead to faster completion times. For example, the Broad Sustainable Building company in China constructed a 57-story skyscraper in just 19 days using prefabricated modules, showcasing the potential of IC.

 

Industrialized construction, meanwhile, looks to improve quality by affecting factors within a business’s control:

  • Third-party prefabrication and offsite construction partners or building out your own infrastructure to support offsite preassembly can improve schedule certainty by 90%, while cutting down on construction costs by 10% and improving quality by mechanizing the preassembly process in a temperature-controlled factory setting where stringent quality measures can be enforced.
  • Robotics and additive manufacturing technology to increase output, capabilities, and design freedom of human installers; smart tools and IoT solutions in the hands of these installers, meanwhile, can further assist in performing installations more safely with reporting/quality verifiability. For instance, the use of drones in construction sites for surveying and monitoring has become increasingly common, providing real-time data and insights.
  • Building information modeling (BIM) can help construction professionals and stakeholders (e.g., customers, inspectors) collaborate virtually, envisioning finished products in their natural environment while improving the 1-1 relationship and trust through construction projects similar to how earlier discussed software teams run beta tests. The construction of the Shanghai Tower, for example, heavily relied on BIM for its design and execution.
  • A wealth of data via digital twins (e.g., real-time inventory data, predictive analytics, data synchronization to remove information silos, etc.) can help professionals manage projects with more certainty and deliver data-driven insights to drive proactive decision-making and quality.

 

In the broader discourse on project management methodologies, Antonio Nieto-Rodriguez’s article, “It’s Time to End the Battle Between Waterfall and Agile,” offers a compelling perspective. Nieto-Rodriguez critiques the rigid dichotomy many project leaders maintain between Waterfall and Agile, suggesting that such binary thinking has fostered tribalism within the project community, stifling innovation and potential. This tribal mindset has even led entire organizations to “go agile,” often at the expense of sidelining the foundational principles of traditional methodologies that certain projects might still benefit from. The real-world implications of this divisive approach can result in tangible losses for organizations. Nieto-Rodriguez advocates for a more nuanced approach: hybrid project management methodologies. By merging the meticulous planning of Waterfall with the adaptability of Agile, these hybrid methods can address the shortcomings of a one-size-fits-all strategy. Such an approach not only bridges the divide between the two methodologies but also paves the way for more effective and innovative project outcomes.

Top of Form

Bottom of Form

 

Bottom Line

The construction industry and its fragmented ecosystem is in desperate need of industry-governing interoperability where critical project data is shared in real-time, enabling collaboration and a nimble building process adaptive to change.

 

As project managers in our industry look to the software industry for ways to improve quality, one conclusion they may come to is breaking away from the monolithic, waterfall delivery methods. Instead, they may implement an agile framework and industrialization of processes that facilitate the same increased output and uncompromised product quality that allowed the iconic Model-T to roll off the production line and meet customer demands.

 

About Authors

Jason Braun is the author of Designing Context-Rich Learning by Extending Reality and an educator with over a decade of producing, delivering, and promoting critically acclaimed multimedia learning experiences. Recognized for collaborating effectively with programmers to create educational software featured in The Chronicle of Higher Education and with subject matter experts like New York Times best-selling authors and FBI cybersecurity agents.

PMTimes_Aug1_2023

Engagement Management: A Key to Successful Projects

Written by George Pitagorsky on . Posted in Articles.

If you are experiencing unproductive disagreements, dissatisfied stakeholders, finger pointing, and misunderstood roles and responsibilities, look to your engagement management (EM) process.

 

All projects are engagements among project managers, performers, clients, sponsors, functional managers, and “customer care” people in sales and support roles. Whether you are in an organization providing contracted services or you are managing in-house projects with clients in your same organization, if you manage a project without managing the engagement, you are likely to fail to satisfy stakeholders, even if your project achieves its objectives.

 

This article describes engagement management and the critical importance of collaboration and the clarity of roles, responsibilities and objectives to ensure that stakeholders are satisfied:

  • Clients are satisfied because their expectations are met – what you promised, what they bought, what they need, and what you deliver match up.
  • Sponsors are satisfied because there is value to the organization, desired benefits are realized at an acceptable and expected cost
  • Performers and managers are satisfied when they are not overburdened by impossible demands, unnecessary bureaucracy, unhealthy relationships, and poor working conditions
  • Regulators, accountants, attorneys, procurement specialists are satisfied when their views are respected and rules, protocols, and regulations are followed

 

The Engagement Management Process

Wise service industry organizations formally recognize the engagement management process with pre-sales, sales, performance (projects and services), relationship management, and support functions as part of an overall engagement.

 

For example, a typical service organization has the following functions involved in each engagement

  • sales and marketing to attract and ‘close’ clients
  • engagement management to oversee and coordinate
  • delivery to manage and perform projects
  • functional managers and staff to provide resources and expertise
  • procurement to find vendors, negotiate, and manage contracts
  • legal to make sure that contracts are clear, valid, and satisfy needs of the parties
  • quality management to make sure what is delivered is acceptable
  • customer service to manage the relationship, maintain communications, and provide support,  before, during and after the project
  • administration and finance for accounting, billing, reporting and other services.

 

Roles and Responsibilities

Roles and responsibility assignments vary depending on organization structure and the relationship between the client and the providers. The structure and degree of formality of the process depends on the stakeholders’ legal relationship. If they are in separate corporations, procurement, accounting, and legal issues must be formal and precise to avoid unnecessary conflict and better manage the conflict that does arise.

 

When the providers are in-house, there is a similar need for clear understanding among the stakeholders. Though, since there are no legal requirements, it takes greater discipline to follow best practice standards that manage disagreements and unmet expectations. Legal and procurement professionals may have no involvement but someone (the PM, a PMO, or a quality management group) needs to make sure that agreements are clearly documented, and decisions are made with objectivity.

Whether in-house or not, a project manager (PM) may play multiple roles. For example, sometimes the PM provides customer support and sometimes business analysts, salespeople, or customer service specialists play this role. Sometimes the PM is the engagement manager.

 

Advertisement
[widget id=”custom_html-68″]

 

The Engagement Manager

Everyone should be clear about who is doing what, who has final authority, what reporting is required, and how decisions will be made – majority, consensus, authority.

Holding the engagement together is an engagement manager, who may be managing a portfolio of accounts with multiple projects and is responsible for making sure the clients are happy and the contributors to the engagement are playing together nicely.

 

Whether the client and provider are in the same organization or not, there is a similar need for attracting and closing realistic deals, establishing and performing a project, maintaining healthy stakeholder relations, and following up with support.

The Engagement manager makes sure all engagement functions are assigned, coordinated, and well performed, and that the expectations of all parties, including performers and executive sponsors in both provider and client organizations are managed.

 

The Sales Role

The sales role is as important when the project is in-house as it is in vendor situations.  Though in-house engagements often fail to recognize the need for a sales role.  Some of the in-house sales work, performed by “champions,” evangelists, or advocates, may be to promote project ideas and “sell” sponsors and clients on an in-house solution over vendor alternatives.

The sales function often leads when it comes to setting client and sponsor expectations and pricing, though these must be influenced by project constraints and costs.

 

Effective engagement management (EM) avoids a disconnect between the people who set client expectations (sales)and the project and support people charged with delivering the results. A well-defined EM process will ensure input from delivery and a decision by engagement management or sponsors as to the final deal. Salespeople are most effective for the organization when they are compensated based on the profitability of their sales.

Consultative selling ensures that both the client and provider understand the client’s needs. Collaborative selling involves delivery experts in the process of defining and pricing the work.

 

What You Can Do

Engagement management is both necessary and complex. If you are experiencing dissatisfied stakeholders and lots of useless and avoidable conflicts, it is likely that your engagement management process needs to be assessed and improved.

The first question to ask is “Do we have a defined process?” There is always a process, but if it isn’t defined, roles and responsibilities are likely to be unclear and some functions may not be performed well or at all.

 

For example, if customer service and engagement management functions are not identified and assigned, responsibility defaults to the PM. If the PM is aware of the needs and has the necessary competency, all will be well. But if the PM expects someone else to handle the relationships and accountabilities, and no one picks up the work, there will be trouble – arguments, dissatisfaction, etc.

To avoid trouble, whether you are part of a contractor firm or an in-house service department, step back, assess and define your process. You can do this for a single project, but it is better if it is done on a broader scale. It requires involvement and buy-in from all the stakeholders in the sales, customer service, and performance organization.

 

Related articles
Improving Project and Engagement Management Performance
Vision and Systems View to Improve Performance
The Challenge Of PM In Engagement Management
PMTimes_Jun06_2023

Shu-Ha-Ri and Servant Leadership

Written by Lawrence Dong on . Posted in Articles.

In today’s rapidly evolving IT landscape, leadership styles play a pivotal role in shaping the culture and success of companies. With unique challenges and demands, it is crucial for leaders to adopt effective approaches that resonate with the modern workforce. Among many leadership styles, there are two prominent styles within IT companies – servant leadership and dictator leadership. Each leadership style has different implications for IT project delivery and for the delivery leads and/or project managers.

 

What is Dictator Leadership

Dictator (or dictatorship) leadership, despite its negative connotations, can be effective in specific situations (e.g., where discipline and obedience are absolutely necessary). This style involves a more autocratic approach, with leaders making independent decisions and providing clear directives to the team. IT delivery leads may adopt dictatorship leadership during high-pressure scenarios or when immediate action is required. However, it is crucial to balance this style with open communication channels and involving the team in decision-making whenever possible.

 

What is Servant Leadership

Servant leadership is a people-centered approach that prioritises empowering and serving the needs of the team. IT delivery leads following this style foster collaboration, open communication, and trust-building within the organisation. Creating an inclusive work environment, providing resources and support for team members to excel and offering coaching opportunities are key elements of servant leadership.

 

What is Shu-Ha-Ri

Shu-Ha-Ri is a concept that originates from the Japanese martial art Aikido. Aikido master Endo Seishiro explains the concept via the following statement:

“It is known that, when we learn or train in something, we pass through the stages of shu, ha, and ri. These stages are explained as follows. In shu, we repeat the forms and discipline ourselves so that our bodies absorb the forms that our forebears created. We remain faithful to these forms with no deviation. Next, in the stage of ha, once we have disciplined ourselves to acquire the forms and movements, we make innovations. In this process the forms may be broken and discarded. Finally, in ri, we completely depart from the forms, open the door to creative technique, and arrive in a place where we act in accordance with what our heart/mind desires, unhindered while not overstepping laws.”

Shu-Ha-Ri is increasingly popular with companies where Agile methodology influences their project delivery ways of working.

 

Advertisement
[widget id=”custom_html-68″]

 

How Shu-Hai-Ri Complements Servant Leadership

In the “Shu-Ha-Ri” framework, the servant leader guides the team closely at the beginning (Shu), transitions to a more hands-off approach (Ha), and ultimately reaches the stage where team members can make decisions independently while aligning with the organisational vision (Ri).

Example of Servant Leadership with Shu-Ha-Ri: Estimation

 

Shu: A delivery lead provides a pre-defined method of user story estimation, and the newly launched Agile development team follow the method in their first month.

Ha: In the second month, the Agile development team members reach out to the deliver lead to learn other estimation methods. They then decide to use a different estimation method under the guidance of the delivery lead.

Ri: Six months later, Agile development team members review all estimation methods and choose another fit-for-purpose estimation method all by themselves, without involvement of the delivery lead.

 

Playbook of Shu-Ha-Ri

 

Conclusion

Effective leadership in modern IT companies requires an understanding of different leadership styles and the ability to adapt to specific situations. IT delivery leads must navigate the complex challenges of the industry, drive success and inspire their teams to achieve their fullest potential. By adopting a fit-for-purpose leadership style based on the context, IT delivery leads can create a positive and productive work environment that fosters innovation, engagement and continuous growth. The concept of “Shu-Ha-Ri” provides a “test case” for leadership development and allows leaders to evolve alongside their teams.

 

 

Reference:
  1. Wikipedia, “Shu-Ha-Ri”, https://en.wikipedia.org/wiki/Shuhari
  2. Brian Tait, “Traditional Leadership Vs. Servant Leadership”, https://www.forbes.com/sites/forbescoachescouncil/2020/03/11/traditional-leadership-vs-servant-leadership/